- 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 treatunderlying application protocols as transport protocols. It does thisby requiring that a wsa:Address EII map to the wsa:To SOAP header,rather than providing for the possibility of mapping to the identifierin 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 editedversion 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 exampleof one email delivery protocol).I think the shortcoming will significantly hamper the ability forWS-Addressing enabled agents and services to integrate with existingapplications on the Internet, such as email, instant messaging, and theWeb.Mark.-- Mark Baker. Ottawa, Ontario, CANADA.http://www.markbaker.ca
Received on Monday, 13 December 2004 15:14:55 UTC