- From: Mark Baker <distobj@acm.org>
- Date: Thu, 7 Mar 2002 21:50:43 -0500 (EST)
- To: xmlp-comments@w3.org
The XML Protocol WG has agreed to close this issue with the following text ... 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. MB -- Mark Baker, Chief Science Officer, Planetfred, Inc. Ottawa, Ontario, CANADA. mbaker@planetfred.com http://www.markbaker.ca http://www.planetfred.com
Received on Thursday, 7 March 2002 21:46:35 UTC