W3C home > Mailing lists > Public > xml-dist-app@w3.org > May 2002

RE: [getf] Proposal for Web-friendly representation of RPC's in SOAP

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Wed, 29 May 2002 11:39:29 -0400
Message-ID: <9A4FC925410C024792B85198DF1E97E40345657C@usmsg03.sagus.com>
To: xml-dist-app@w3.org

> -----Original Message-----
> From: noah_mendelsohn@us.ibm.com [mailto:noah_mendelsohn@us.ibm.com]
> Sent: Wednesday, May 29, 2002 10:05 AM
> To: xml-dist-app@w3.org
> Subject: [getf] Proposal for Web-friendly representation of RPC's in

Overall, I think this looks great.  One quibble ...

> In general, this specification concerns itself with the creation and
> processing of SOAP envelopes, and does not formally constrain 
> the means by which RPC or non-RPC URIs are constructed for use with SOAP.

I don't think this rationale is very compelling. SOAP 1.2 offers an XML
serialization format for RPC parameters, so it wouldn't be out of scope to
offer a URI serialization format for RPC parameters.  

>  Thus, no standard means of mapping resource-identifying arguments or 
> method names to URIs is provided herein; it is anticipated that such 
> conventions would be developed in conjunction with the creation of 
> Web service description languages, language bindings, and so on.

I can understand if we don't think that it can be defined quickly enough for
the 1.2 timeframe, but I would *hope* that a SOAP-level argument-to-URI
mapping could be standardized.  If the mapping is language-specific, or
requires WSDL on both sides, then interoperability would be greatly reduced.
Received on Wednesday, 29 May 2002 11:40:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:20 UTC