Re: Proposed issue; Visibility of Web services

That's right, it isn't required that the client understand the query 
parameters. I never
said it was. And who said that the client even created the uri-encoded 
SOAP message? It is a
perfectly valid URI that could have been created at the origin server for 
that matter
and used in a VERY RESTful manner. For that matter, I could encode the 
SOAP message
in a URI by using a canonicalization and hashing algorithm that produced a 
unique identifier
for the SOAP message and append that to http://myserver.com/service/ 
without any query string
involved and as long as 

Are you suggesting that HTML Forms disallow uri-encoding and use of the
GET method? If so, why aren't you pestering the XForms WG or the HTML
activity or the IETF to get them to abolish query arguments in the URI. 
Oh, but that
would mean that you would have to use POST to effect a GET because you
would have to make the request in the form of a POST with an entity body
that was really tunnelling a GET. Is that what you had in mind? I doubt 
it.

Finally, who said that it changes the semantics of the message?!? It is a 
GET
of a URI, nothing more and nothing less. Like I said, the implementation
details of what happens at the origin server to turn the GET/URI into a
representation of the identified resource are of no concern of anyone
but the origin server. Likewise, while it may not be required
that the client understand the semantics of the query parameters, there is
nothing that says that it may not, should not, or must not, only that it 
should not 
attempt to *guess* at their meaning/significance.

Come on, let's get real here. Your argument holds no water.

Cheers,

Christopher Ferris
STSM, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
phone: +1 508 234 3624

www-ws-request@w3.org wrote on 05/30/2003 05:11:19 PM:

> 
> On Fri, May 30, 2003 at 04:22:24PM -0400, Christopher B Ferris wrote:
> > Mark,
> > 
> > Nonsense! It is just a parameter to the query that is an HTTP GET.
> 
> In the SOAP message, it was the action being requested.  How did it
> suddenly turn into a parameter?  Parameters in an identifier are
> things that the client isn't required to understand.  Is it still an
> encoding if it changes the semantics of the message?
> 
> P-)
> 
> Just some pedantic silliness on a Friday afternoon, in an attempt to
> explain that encoding messages in URIs is broken.
> 
> MB
> -- 
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
> Web architecture consulting, technical reports, evaluation & analysis
>   Actively seeking contract work or employment
>

Received on Friday, 30 May 2003 20:00:28 UTC