W3C home > Mailing lists > Public > www-ws-desc@w3.org > April 2007

[Bug 4458] Multiple whttp:inputSerialization

From: <bugzilla@wiggum.w3.org>
Date: Wed, 11 Apr 2007 16:11:45 +0000
To: www-ws-desc@w3.org
Message-Id: <E1HbfQ9-00065z-BD@wiggum.w3.org>


           Summary: Multiple whttp:inputSerialization
           Product: WSDL
           Version: 2.0
          Platform: All
               URL: http://lists.w3.org/Archives/Public/public-ws-desc-
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Adjuncts
        AssignedTo: plh@w3.org
        ReportedBy: jonathan@wso2.com
         QAContact: www-ws-desc@w3.org

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: 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>SELECT * WHERE { ... } </st:query>

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.


Elias Torres on behalf of the DAWG.

[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
Received on Wednesday, 11 April 2007 16:12:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:04 UTC