W3C home > Mailing lists > Public > xml-dist-app@w3.org > August 2005

ImmediateSender ambiguity

From: Mark Baker <distobj@acm.org>
Date: Wed, 24 Aug 2005 14:33:27 -0400
To: xml-dist-app@w3.org
Message-ID: <20050824183326.GO3412@markbaker.ca>

Greetings,

I have a concern about the WS-Addressing specifications that boils down
to an interpretation of part of the SOAP 1.2 default HTTP binding.

The WS-Addressing WG appears to believe that the Request-URI in a
SOAP/HTTP message is hop-by-hop, while I maintain it's end-to-end.  As a
result of this belief, WS-Addressing created a wsa:To header whose role
was to carry the end-to-end address for a SOAP message.  I believe this
interpretation is inconsistent with the SOAP 1.2 default HTTP binding
(as well as HTTP itself).

As evidence of this claim, I referred to the following part of the spec
where the value of the ImmediateDestination property is declared;

 "An identifier (URI) that denotes the responding SOAP node"
 -- http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#tabreqcon

Although the actual definition of the property seems ambiguous, and
potentially inconsistent with the above;

 "The identifier of the immediate destination of an outbound message."
 -- http://www.w3.org/TR/2003/REC-soap12-part2-20030624/#tabreqresprops

I'd like to request that the WG clarify which interpretation is
intended.

Thanks!

P.S. I'll be out of email range until Sept 1.

Mark.
-- 
Mark Baker.  Ottawa, Ontario, CANADA.          http://www.markbaker.ca
Coactus; Web-inspired integration strategies   http://www.coactus.com
Received on Wednesday, 24 August 2005 18:31:46 GMT

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