RE: NEW ISSUE; wsa:To interaction with application protocols

Hi Mark!
 
i think this is closely related to issue 6 "Message Property Optionality":
http://www.w3.org/2002/ws/addr/wd-issues/#i006

 
AIUI you'd like an addressing xxTo: value to map to an populate a transport 
xxTo: value, whereas Marc is suggesting that a missing addressing xxTo: 
could default to to a value derrived from the transport.
 
i guess both issues raise an issue with the way the spec is structured given 
that the SOAP and WSDL bindings are thus far "transport-neutral". 
 
Paul

 -----Original Message----- 
 From: public-ws-addressing-request@w3.org on behalf of Mark Baker 
 Sent: Mon 13/12/2004 15:17 
 To: public-ws-addressing@w3.org 
 Cc: 
 Subject: NEW ISSUE; wsa:To interaction with application protocols
 
 


 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 19:42:54 UTC