- From: Mark Baker <distobj@acm.org>
- Date: Wed, 17 Aug 2005 23:08:47 -0400
- To: www-tag@w3.org
Greetings, I just wanted to point out that the just announced WS-Addressing SOAP Binding CR[1] still has the problem described in the endPointsRefs-47[2] issue. FWIW, in case it helps, another way to look at this issue is to observe that there is functional overlap between the WS-Addressing SOAP binding and the SOAP 1.2 HTTP binding, and the meaning of that overlap is undefined. Specifically, each has its own definition for the concepts of "operation" and "destination address"; the former defines the wsa:To and wsa:Action headers, while the latter defines the "ImmediateDestination"[3] and "Method"[4] (and "Action"[5], to confuse things even more) properties. Cheers, [1] http://www.w3.org/TR/2005/CR-ws-addr-soap-20050817/ [2] http://www.w3.org/2001/tag/issues.html#endPointRefs-47 [3] http://www.w3.org/2003/05/soap/mep/ImmediateDestination [4] http://www.w3.org/2003/05/soap/features/web-method/Method [5] http://www.w3.org/2003/05/soap/features/action/Action Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Coactus; Web-inspired integration strategies http://www.coactus.com
Received on Thursday, 18 August 2005 03:07:10 UTC