- From: Williams, Stuart <skw@hplb.hpl.hp.com>
- Date: Mon, 18 Feb 2002 12:24:26 -0000
- To: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
As part of the resolution of Issue 133: SOAP and Web Architecture [1], I was actioned to draft text for inclusion in the SOAP 1.2 spec. to address the resolution of Issue 133. Issue 133 was closed during the WG telcon on 13th Feb with resolution reported to xmlp-comments@w3.org in [2]. Proposed draft text for insertion into SOAP 1.2 Part 2 Section 7 [3] follows below: <draft> 7 Default HTTP Binding <insertion> The SOAP Binding Framework enables the definition of multiple bindings between SOAP and a given underlying protocol. The HTTP binding specified in the following subsections makes use of the HTTP POST method to transfer SOAP messages between SOAP Nodes. Note that nothing precludes the specification of different HTTP bindings that make use of other HTTP methods, or indeed that make different use of the HTTP POST method. It is also possible to use the HTTP binding specified here in a way that preserves the semantics of the HTTP POST method [ref RFC2616], however the onus to ensure the preservation of HTTP POST semantics falls upon the SOAP application developer. </insertion> 7.1 Introduction This SOAP binding specification adheres to the SOAP Binding Framework (see SOAP Transport Binding Framework), and as such uses abstract properties as a descriptive tool for defining the functionality of certain features. </draft> Comments? Flames? etc. Best regards Stuart Williams [1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x133 [2] http://lists.w3.org/Archives/Public/xmlp-comments/2002Feb/0011.html [3] http://www.w3.org/2000/xp/Group/1/10/11/soap12-part2.html#soapinhttp
Received on Monday, 18 February 2002 07:24:32 UTC