W3C home > Mailing lists > Public > www-tag@w3.org > May 2002

Re: TAG document: SOAP HTTP GET binding available

From: Tim Bray <tbray@textuality.com>
Date: Tue, 14 May 2002 17:21:39 -0700
Message-ID: <3CE1AA13.1080300@textuality.com>
To: David Orchard <dorchard@bea.com>
Cc: "'XML Protocol Discussion'" <xml-dist-app@w3.org>, www-tag@w3.org
David Orchard wrote:
> http://www.w3.org/2001/tag/doc/ws-uri.html

Quoting from the above, the SOAP request packet:

<env:Envelope xmlns:env="http://www.w3.org/2001/12/soap-envelope">

is URI-encoded as (I fixed a couple of what look like typos to me)


Let me suggest a couple of potential improvements:

1. Place a '?' rather than a '&' after the name of the service, why not 
make this look like a conventional CGI encoding.
2. Use ';' rather than '&' to separate arguments, so they'll be easier 
to store in XML documents



Next, we have a problem in that it's hard to distinguish built-in SOAP 
machinery (the ns URI and the encoding style) from the service arguments
("Symbol" in this case).  Suppose you had an argument named 
"encodingStyle"?  We need some syntax to signal this.  A perusal of SOAP 
doesn't reveal any characters which are guaranteed not to show up as 
service names, but RFC2396's "mark" (part of "unreserved") production 
has lots of candidates.

mark        = "-" | "_" | "." | "!" | "~" | "*" | "'" | "(" | ")"

As a strawman I propose that built-ins start with '*' and that they be 
given conventional shorter names, *ns and *enc.  Thus


Finally, I propose that encodingStyle's values be supplied as follows: 
by default, if '*enc' is absent, the encoding style is 
w3.orc/soap-encoding as in the example above.  Otherwise you supply the 
URI for your encoding.  Thus:


Received on Wednesday, 15 May 2002 01:20:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:51 UTC