This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I'm currently one of the SPARQL protocol editors and we have received a request [1] to add support for an additional input serialization and am seeking your advice. We have done a review of the current documents [2] to see if this is possible but we were unable to come up with a solution and are hoping you can help us. Ideally, we would like to know how to add support for both application/x-www-form-urlencoded and application/sparql-query in our query operation [3]. Additionally, my colleague Lee Feigenbaum believes we also support an XML version of our x-www-form-urlencoded data by virtue of our WSDL defining the input message parts via a reference to an XML schema element (<input ... element="st:query-request"/>), the query message has a message content model of "element". Turning to: 6.3.2.1 Serialization rules for XML messages ( http://www.w3.org/TR/wsdl20-adjuncts/#_http_binding_default_rule_psf ), we see that there are serialization rules given explicitly for application/xml. These rules are at http://www.w3.org/TR/wsdl20-adjuncts/#_http_operation_xml_encoding and say that serializing a message as application/xml means that the message's instance data is serialized as Canonical XML. Further, the instance data is explicitly defined ( http://www.w3.org/TR/wsdl20-adjuncts/#instance_data ) to be "The internal tree representation of an input...constrained by...the XML element referenced in the {element declaration} property of the Interface Message Reference component". As I read it, this means that the inclusion of application/xml amongst our inputSerialization allows for POSTed content that looks like: <st:query-request> <st:query>SELECT * WHERE { ... } </st:query> <st:default-graph-uri>http://example.org/graph1</st:default-graph-uri> <st:default-graph-uri>http://example.org/graph2</st:default-graph-uri> <st:named-graph-uri>http://example.org/graph3</st:named-graph-uri> </st:query-request> However, we don't believe that this was our intention, furthermore, our real interest is whether we can use multiple whttp:inputSerialization values to add support for POSTing application/sparql-query documents. Thanks, Elias Torres on behalf of the DAWG. [1] http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2006Sep/0007 [2] http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0112 [3] http://www.w3.org/TR/rdf-sparql-protocol/sparql-protocol-query.wsdl [4] http://www.w3.org/TR/rdf-sparql-protocol/sparql-protocol-types.xsd
Close with no action on the WSDL spec. Jonathan will follow up with commenter to explain the options for extending WSDL in this way.