- From: Yalcinalp, Umit <umit.yalcinalp@sap.com>
- Date: Mon, 26 Sep 2005 17:28:25 -0700
- To: <public-ws-addressing-comments@w3.org>
- Message-ID: <2BA6015847F82645A9BB31C7F9D641654185F0@uspale20.pal.sap.corp>
Title - The utility of the anonymous address in SOAP binding specification is too restrictive Description - OASIS WS-RX tc needs to utilize the semantics of the anonymous URI as defined by the WS-Addressing specification as the address of other EPRs that it defines, in particular as the value of wsrm:AcksTo EPR defined in the WS-ReliableMessaging specification[1]. OASIS WS-RX tc noticed that WS-Addressing SOAP binding specification defines the semantics of the anonymous URI we need, but only wrt the ReplyTo and FaultTo EPRs in Section 3.5 [2] as quoted below: { When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified as the address of the ReplyTo or FaultTo EPR, the underlying SOAP protocol binding provides a channel to the specified endpoint. Any underlying protocol binding supporting the SOAP request-response message exchange pattern provides such a channel. For instance, the SOAP 1.2 HTTP binding[SOAP 1.2 Part 2: Adjuncts <> ] puts the reply message in the HTTP response. } This definition is too restrictive since it does not allow other EPRs defined by specifications other than WS-Addressing to utilize the same semantics that WS-Addressing SOAP binding specification defines for the anonymous URI. This restriction does not appear to be intentional, therefore we would like this definition to be extended. Justification - Providing a channel to a specified endpoint is a general concept that may be used by other specifications that utilize WS-Addressing. Therefore, it seems to us that it will be beneficial for the WS-Addressing SOAP binding specification to allow the definition of anonymous IRI to apply to other EPRs that have the similar semantics to ReplyTo/FaultTo EPRs. Otherwise, individual specifications would need to redefine the same semantics that is already provided by the WS-Addressing specification. This change will benefit interoperability and reduce the need for other specifications to replicate the definition for additional EPRs. The current restriction also restricts composibility since such extensions need to be addressed for each binding within extending binding specifications that refer to WS-Addressing rather than WS-Addressing binding specifications (such as SOAP binding). Target - soap binding Proposal - Preferably the paragraph in question should be extended to allow other EPRs to use the same semantics defined for the anonymous address. --umit yalcinalp On behalf of OASIS WS-RX tc [1] http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/13493/WS -ReliableMessaging-v1.0-wd-01.pdf [2] http://www.w3.org/TR/2005/CR-ws-addr-soap-20050817/#soaphttp ---------------------- Dr. Umit Yalcinalp Standards Architect NetWeaver Industry Standards SAP Labs, LLC umit.yalcinalp@sap.com Tel: (650) 320-3095
Received on Tuesday, 27 September 2005 00:28:14 UTC