This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 4458 - Multiple whttp:inputSerialization
Summary: Multiple whttp:inputSerialization
Alias: None
Product: WSDL
Classification: Unclassified
Component: Adjuncts (show other bugs)
Version: 2.0
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Philippe Le Hegaret
QA Contact: WSDL Mailing List
Depends on:
Reported: 2007-04-11 16:11 UTC by Jonathan Marsh
Modified: 2007-04-19 16:12 UTC (History)
0 users

See Also:


Description Jonathan Marsh 2007-04-11 16:11:45 UTC
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 ( ), we
see that there are serialization rules given explicitly for
application/xml. These rules are at 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 ( ) 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.

Comment 1 Jonathan Marsh 2007-04-19 16:12:39 UTC
Close with no action on the WSDL spec.  Jonathan will follow up with commenter to explain the options for extending WSDL in this way.