W3C home > Mailing lists > Public > public-ws-addressing@w3.org > December 2004

NEW ISSUE; wsa:To interaction with application protocols

From: Mark Baker <distobj@acm.org>
Date: Mon, 13 Dec 2004 10:17:25 -0500
To: public-ws-addressing@w3.org
Message-ID: <20041213151725.GD32418@markbaker.ca>

The SOAP binding currently only supports uses of SOAP which treat
underlying application protocols as transport protocols.  It does this
by requiring that a wsa:Address EII map to the wsa:To SOAP header,
rather than providing for the possibility of mapping to the identifier
in the underlying protocol.  The spec says;

  "The [address] property in the endpoint reference is copied in the
   [destination] message information property. The infoset
   representation of the [destination] property becomes a header block
   in the SOAP message."

As an example of the problem, consider the following EPR (an edited
version of one from the spec);

<wsa:EndpointReference xmlns:wsa="..." xmlns:fabrikam="...">
   <wsa:Address>foobar@fabrikam123.example</wsa:Address>
   <wsa:ReferenceProperties>
       <fabrikam:CustomerKey>123456789</fabrikam:CustomerKey>
   </wsa:ReferenceProperties>
   <wsa:ReferenceParameters>
       <fabrikam:ShoppingCart>ABCDEFG</fabrikam:ShoppingCart>
   </wsa:ReferenceParameters>
</wsa:EndpointReference>

Here, "foobar@fabrikam123.example" is required to go in the SOAP header,
rather than in the "RCPT TO" command of the SMTP protocol (as an example
of one email delivery protocol).

I think the shortcoming will significantly hamper the ability for
WS-Addressing enabled agents and services to integrate with existing
applications on the Internet, such as email, instant messaging, and the
Web.

Mark.
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Received on Monday, 13 December 2004 15:14:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:00 GMT