W3C home > Mailing lists > Public > public-ws-addressing@w3.org > February 2006

Action item for cr23: cr15 resolution nullified cr4 resolution: proposed text

From: Katy Warr <katy_warr@uk.ibm.com>
Date: Wed, 22 Feb 2006 11:04:18 +0000
To: "public-ws-addressing@w3.org" <public-ws-addressing@w3.org>
Message-ID: <OF3A9CA161.18095FB8-ON8025711D.0038883B-8025711D.003CCF18@uk.ibm.com>
Further to my action on Monday to propose resolution text for CR23, here 
is a suggestion.  I've tried to maintain the previously agreed text from 
CR4 and CR15 where possible. 

The intention is that the first paragraph enables the use of anonymous EPR 
in semantics including (but not exclusive to) replyTo and faultTo (such as 
WS-RX acksTo).  This satisfies CR4.

The second paragraph gives the semantics specific to replyTo/faultTo - 
this is very similar to the resolution of CR15 but specific to the 
replyTo/faultTo scenario so that it does not undo the resolution to CR4 in 
the first paragraph. 

This text is applicable to section 5.1 of the SOAP binding document.

-------------------------
The "http://www.w3.org/@@@@/@@/addressing/anonymous" URI MAY be specified 
as
the [address] of an EPR to designate that the target endpoint is 
reached by a channel of the underlying SOAP protocol binding.
The specification of the channel to which the 
"http://www.w3.org/@@@@/@@/addressing/anonymous" URI refers depends on the
Message Exchange Pattern (MEP) and on the 
defined semantics of the EPR in question.  Any underlying protocol binding 
supporting the SOAP
request-response MEP provides such a channel for
response messages. 
 
In the context of a SOAP request-response MEP, sending a response message 
to a 
ReplyTo or FaultTo 
EPR whose [address] is "http://www.w3.org/@@@@/@@/addressing/anonymous" 
means sending it as the response message of the MEP. 
For instance, the SOAP 1.2 HTTP binding[SOAP 1.2 Part 2: Adjuncts] 
puts the reply message in the HTTP response. 
--------------------------

We may be able to omit the sentence:  " Any underlying protocol binding 
supporting the SOAP
request-response MEP provides such a channel for
response messages. "

This second paragraph requires restructure to fit with the SOAP 1.1/HTTP 
and SOAP 1.2 split in the editors'
draft.  I suggest that we defer this until we have reached agreement on 
the general structure of the text above.

thanks
Katy
Received on Wednesday, 22 February 2006 11:04:21 GMT

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