W3C home > Mailing lists > Public > xml-dist-app@w3.org > November 2001

Meta issue 54 [1]--proposed resolution

From: Marwan Sabbouh <ms@mitre.org>
Date: Tue, 20 Nov 2001 17:34:55 -0500
Message-ID: <3BFADA8F.340E484D@mitre.org>
To: xml-dist-app@w3.org, distobj@acm.org
Proposed resolution c/o Mark Baker- Thanks

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.

[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x54
Received on Tuesday, 20 November 2001 17:35:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:05 GMT