Issue 133: SOAP and The Web Architecture

Hugo,

Issue 133 [1] came up for discussion on the TBTF today, in particular the
concern over SOAP's use of HTTP POST in a manner that may not be compliant
with Web Architecture [2].

The TBTF are currently proposing that we recognise in the spec. that the
HTTP binding in Part 2 Adjuncts is 'an' HTTP binding rather than 'the' HTTP
binding. The HTTP binding we intend to offer will follow the pattern of
using the HTTP POST method established in SOAP 1.1 [3]. 

The topic of Web Architecture is the subject of continuing debate, including
and referenced from the thread that originated this issue[4]. The TBTF do
not find themselves able to resolve the philosophical issues enclosed
there-in, but believe that the SOAP protocol binding framework is flexible
enough to allow the creation of different bindings to HTTP as and when these
issues are resolved.

So, at this time the proposal from the TBTF to close Issue 133 is that the
binding we offer in SOAP 1.2 continue to use the HTTP POST method in the
manner established in SOAP 1.1 and to note that our binding framework makes
it is possible to define additional HTTP bindings.

I anticipate this topic being on the agenda for the next WG telcon. 

Best regards

Stuart Williams
(for the TBTF)
[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x133
[2] http://www.w3.org/DesignIssues/Axioms.html#state
[3] http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
[4] http://lists.w3.org/Archives/Public/xml-dist-app/2001Aug/0202.html

Received on Thursday, 31 January 2002 12:44:32 UTC