W3C home > Mailing lists > Public > xml-dist-app@w3.org > August 2001

RE: Issue 107: Clarify the terms application, actor & related no tions of identity.

From: Williams, Stuart <skw@hplb.hpl.hp.com>
Date: Tue, 7 Aug 2001 12:20:03 +0100
Message-ID: <5E13A1874524D411A876006008CD059F1925B7@0-mail-1.hpl.hp.com>
To: "'Nilo Mitra (EMX)'" <Nilo.Mitra@am1.ericsson.se>, "'Marc Hadley'" <marc.hadley@sun.com>
Cc: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
Nilo,
 
What you suggest is fine, although I think that one single-ended definition
from the point of view of either SOAP Receiver or a SOAP Sender would be
better:
 
ie.
 
"At a SOAP Receiver the special URI "
http://www.w3.org/2001/06/soap-envelope/actor/next
<http://www.w3.org/2001/06/soap-envelope/actor/next> " indicates that the
SOAP Header block is targetted at the current SOAP Receiver/Node."
 
OR
 
"At a SOAP Sender the special URI "
http://www.w3.org/2001/06/soap-envelope/actor/next
<http://www.w3.org/2001/06/soap-envelope/actor/next> " indicates that the
SOAP Header block is targetted at the next SOAP Receiver/Node along the SOAP
Message 
Path".
 
The first avoids the need to mention message path, while the second is very
close to Marc's original. Either would be ok... take your pick!
 
Regards
 
Stuart

-----Original Message-----
From: Nilo Mitra (EMX) [mailto:Nilo.Mitra@am1.ericsson.se]
Sent: 06 August 2001 21:05
To: 'Williams, Stuart'; 'Marc Hadley'
Cc: 'xml-dist-app@w3.org'
Subject: RE: Issue 107: Clarify the terms application, actor & related no
tions of identity.



Marc, Stuart: 
Please see an amended proposal inlined below. 
Nilo 


> 
> > -----Original Message----- 
> > From: Marc Hadley [ mailto:marc.hadley@sun.com
<mailto:marc.hadley@sun.com> ] 
> > Sent: 06 August 2001 12:35 
> > To: Marc Hadley 
> > Cc: Eric Jenkins; 'xml-dist-app@w3.org' 
> > Subject: Re: Issue 107: Clarify the terms application, 
> actor & related 
> > notions of identity. 
> > 
> > 
> > As a result of some private discussion I'd like to offer 
> the following 
> > small change to my original proposal for reworking 4.2.2 and 4.2.3. 
> > 
> > Replace: "The special URI 
> > " http://www.w3.org/2001/06/soap-envelope/actor/next
<http://www.w3.org/2001/06/soap-envelope/actor/next> " 
> indicates that the 
> > SOAP header block is intended for the very first SOAP node that 
> > processes the message." 
> > 
> > With: "The special URI 
> > " http://www.w3.org/2001/06/soap-envelope/actor/next
<http://www.w3.org/2001/06/soap-envelope/actor/next> " 
> > indicates that the SOAP header block is intended for the next SOAP 
> > node in the SOAP message path." 
> 
> Not sure... feels like "tomorrow never comes". Your suggested revision 
> captures the meaning of ".../next" on transmission from the a 
> node/actor/application/processor, but not receipt at a 
> node/actor/application/processor. 

How about the following (with additions in CAPITALS) to take care of the
concern from a receiver's point of view: 

"The special URI " http://www.w3.org/2001/06/soap-envelope/actor/next
<http://www.w3.org/2001/06/soap-envelope/actor/next> " 
indicates that the SOAP header block is intended for the next SOAP node in
the SOAP message path OR THE CURRENT SOAP RECEIVER, IN THE CASE WHEN SUCH A
HEADER BLOCK IS RECEIVED AT A SOAP NODE."

                                                                        
Received on Thursday, 9 August 2001 07:57:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:03 GMT