Semantic web and XPL

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Semantic web and XPL

Ross Horne
XPL community,

Has anyone else considered writing processors for dealing with RDF? Just checking to see whether there are any thoughts from the community on the semantic web standards and their relation to XPL which might be worth considering with the advent of the XML processing model working group.

I'm considering using the Jena API to create and persist RDF models in a database as well as performing manipulations, applying ontology reasoners and querying using SPARQL.

The obvious issues are that SPARQL is not yet a W3C recommendation (but is not far off being one) and RDF is not XML. However, RDF can be presented in an XML syntax as can the results of SPARQL queries which will probably need to be made use of in an implementation for XPL. There may be a better alternative in extending the XPL language in some way to make RDF processing as natural as XML processing but I suspect the RDF standards are not ready for such a move.

Here is an outline of what the processors might do:

The SPARQL processor
Should receive configuration information for the persistent store to access, the models to query, any ontology reasoner to use for inference and the SPARQL query itself. It should return the result of the query in SPARQL results XML syntax.

The create RDF model processor
Should take in a parse RDF/XML, open a connection to the persistent store and create a new model in the store using the parsed RDF.

The edit RDF model processor
Should receive configuration information detailing the model to manipulate and the type of manipulation as well as some optional RDF/XML to be used in the manipulation process.

The delete RDF model processor
Should delete the model specified in the configuration from the persistent store also specified in the configuration input.

Just in case it interests or relates to any one else,
Ross Horne.

--
telephones
07921 906 453 (mobile)
07879 052 143 (alternative mobile)

address
1 Tweedsyde Park
Kelso
Roxburghshire
TD5 7RF

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Semantic web and XPL

Erik Bruchez
Administrator
Ross,

We haven't done this at Orbeon, but it sounds like something valuable.
Let us know if you make some progress there, and if you actually write
some code we would be happy to see it make it back into OPS. And if you
*really* need something soon, then we are of course available to help you.

-Erik

Ross Horne wrote:

> XPL community,
>
> Has anyone else considered writing processors for dealing with RDF? Just
> checking to see whether there are any thoughts from the community on the
> semantic web standards and their relation to XPL which might be worth
> considering with the advent of the XML processing model working group.
>
> I'm considering using the Jena API to create and persist RDF models in a
> database as well as performing manipulations, applying ontology
> reasoners and querying using SPARQL.
>
> The obvious issues are that SPARQL is not yet a W3C recommendation (but
> is not far off being one) and RDF is not XML. However, RDF can be
> presented in an XML syntax as can the results of SPARQL queries which
> will probably need to be made use of in an implementation for XPL. There
> may be a better alternative in extending the XPL language in some way to
> make RDF processing as natural as XML processing but I suspect the RDF
> standards are not ready for such a move.
>
> Here is an outline of what the processors might do:
>
> The SPARQL processor
> Should receive configuration information for the persistent store to
> access, the models to query, any ontology reasoner to use for inference
> and the SPARQL query itself. It should return the result of the query in
> SPARQL results XML syntax.
>
> The create RDF model processor
> Should take in a parse RDF/XML, open a connection to the persistent
> store and create a new model in the store using the parsed RDF.
>
> The edit RDF model processor
> Should receive configuration information detailing the model to
> manipulate and the type of manipulation as well as some optional RDF/XML
> to be used in the manipulation process.
>
> The delete RDF model processor
> Should delete the model specified in the configuration from the
> persistent store also specified in the configuration input.
>
> Just in case it interests or relates to any one else,
> Ross Horne.
>
> --
> telephones
> 07921 906 453 (mobile)
> 07879 052 143 (alternative mobile)
>
> address
> 1 Tweedsyde Park
> Kelso
> Roxburghshire
> TD5 7RF



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Portlet problems

mjgraham
Hi,

I am trying to get a modification of the examples portal working using
OPS 3.0 syntax - the XForms model is not declared in the page-flow.xpl
but dynamically defined in the examples.xpl as I'm passing around
sensitive user information and don't want to just put this into a URL call.

The main difference to the front page is that the list of examples is
now a set of xforms:submit but appearing as links. This works fine and
takes me to a simple example page consisting of 3 input boxes and a
submit. However, when I try and submit this, I get:

Unable to retrieve XForms engine state
oxf:/ops/xforms/xforms-server-submit.xpl 55 43 executing processor
(name='{http://www.orbeon.com/oxf/processors}xforms-server')
  <p:processor name="oxf:xforms-server">...</p:processor>


and trying to use any of the submit links on the left brings up the date
widget.

This is using OPS 3.0final.

    Cheers,

    Matthew



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Portlet problems

Erik Bruchez
Administrator
Matthew,

This is probably not as easy as it may seem, because the portal actually
does things such as enhancing the HTML forms in the portlet, etc.

For now we don't have an answer unfortunately.

-Erik

Matthew Graham wrote:

> Hi,
>
> I am trying to get a modification of the examples portal working using
> OPS 3.0 syntax - the XForms model is not declared in the page-flow.xpl
> but dynamically defined in the examples.xpl as I'm passing around
> sensitive user information and don't want to just put this into a URL call.
>
> The main difference to the front page is that the list of examples is
> now a set of xforms:submit but appearing as links. This works fine and
> takes me to a simple example page consisting of 3 input boxes and a
> submit. However, when I try and submit this, I get:
>
> Unable to retrieve XForms engine state
> oxf:/ops/xforms/xforms-server-submit.xpl     55     43     executing
> processor (name='{http://www.orbeon.com/oxf/processors}xforms-server')
>  <p:processor name="oxf:xforms-server">...</p:processor>
>
>
> and trying to use any of the submit links on the left brings up the date
> widget.
>
> This is using OPS 3.0final.
>
>    Cheers,
>
>    Matthew
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws