W3C home > Mailing lists > Public > public-xml-processing-model-comments@w3.org > August 2008

rdf processing steps

From: Paul Tyson <phtyson@sbcglobal.net>
Date: Tue, 26 Aug 2008 06:30:17 -0500
Message-ID: <48B3E949.5080203@sbcglobal.net>
To: public-xml-processing-model-comments@w3.org

My last note [1] was overly pessimistic.  While I do believe it is 
overly restrictive to require XML to flow between processing steps, this 
does not prevent a useful amount of rdf processing to be specified.

I submit the following steps for the WG to consider including as 
optional steps in the XProc 1.0 specification.  I think you should seek 
technical assistance from the Semantic Web Deployment WG to design the 
signatures for these steps.

<!-- rewrite RDF input in specified output serialization syntax -->
<!-- allow input from external source -->
<!-- output to port as RDF/XML, or to external sink in some other
      notation -->
<!-- could be static error if implementation doesn't handle specified
      notation -->

<!-- run sparql query against zero or more input RDF graphs -->
<!-- allow in-line definition of sparql query -->
<!-- output stream to be RDF/XML or sparql results XML -->
<!-- specify sparql version -->

<!-- emit RDF/XML from RDFa markup in XML input -->
<!-- specify version of RDFa to glean -->

<!-- apply GRDDL transformation to input, emit RDF/XML -->
<!-- allow xproc to specify grddl:transformation list to append to
      or replace transformations specified in source -->
<!-- specify version of GRDDL to use -->

<!-- parse RDF input and emit error stream and status -->

rdf-parse might be dispensable, but it could be a useful guard step.


Received on Tuesday, 26 August 2008 11:28:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:41:07 UTC