- From: Yves Lafon <ylafon@w3.org>
- Date: Thu, 11 Apr 2002 16:07:48 +0200 (MET DST)
- To: xmlp-comments@w3.org
- cc: john_ibbotson@uk.ibm.com
The XMLP WG have closed issue 54 with the following resolution: <<< While it is true that not all uses of SOAP meet requirement R505, the specification itself can be used in a manner that meets the requirement. When SOAP is used such that it inherits the semantics of the underlying protocol, and if that protocol provides the necessary a priori agreement, then SOAP also inherits it. This is the case for the default HTTP binding. It is not required there be a priori agreement about the use of SOAP, as HTTP provides the necessary features by which support, or lack thereof, is communicated. Also, SOAP does provide a "mechanism for submitting a SOAP request to a generic HTTP (or other protocol) server", as any HTTP URI can have a SOAP message POSTed to it, and both sender and receiver can coordinate the view of the success or failure of that POST with existing HTTP features. Other protocols that provide similar capabilities will allow SOAP to inherit them when bound in this way. >>> (see [2]) Please let us know if this resolution is not satisfactory to you. Thanks, [1] http://www.w3.org/2000/xp/Group/xmlp-issues#x54 [2] http://lists.w3.org/Archives/Public/xmlp-comments/2002Mar/0020.html -- Yves Lafon - W3C "Baroula que barouleras, au tiéu toujou t'entourneras."
Received on Thursday, 11 April 2002 10:07:51 UTC