W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2005

Use cases for XML serialization

From: Bijan Parsia <bparsia@isr.umd.edu>
Date: Tue, 22 Mar 2005 11:28:23 -0500
Message-Id: <419623574ca85ffafd48421529c71303@isr.umd.edu>
To: DAWG Mailing List <public-rdf-dawg@w3.org>

For Howard(?), I restate (I hope concisely) some use cases for XML 
Serialization:

1) I think for a good WSDL for SPARQL, having an XML Schema type for 
specifying the input and output messages in the abstract interface is 
highly desirable. This generates, as a side effect, and XML 
serialization.

2) I think for actual bodies of SOAP messages, XML is preferable. I 
guess, in general, embedding XML in XML formats is better than 
embedding strings in other formats. Especially if validatable.

3) I was already generating a XML format in order to support legacy 
applications with say, RDQL, Versa, and SeRQL services. I prefer 
generating XML from a SPARQL query, and using XSLT or XQuery to 
generate RDQL or other query languages.

4) Having schema (which entails XML serialization) allows us to express 
what parts of the query language a server does or does not support for 
various datasets (or all of them). So I can, I believe, restrict the 
query to only allow select queries if I don't support ask, describe, or 
construct *without* the working group having to define any conformance 
levels.

There are others, but I hope this is a good start. (Am I trying to 
convince people, or trying to generate something for the use case 
document?)

Cheers,
Bijan.
Received on Tuesday, 22 March 2005 17:20:24 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:22 GMT