W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > January to March 2006

2004/ws/addressing ws-addr-soap.xml,1.126,1.127

From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 13 Mar 2006 22:27:42 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1FIvVu-0001ZQ-3d@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv6006

Modified Files:
	ws-addr-soap.xml 
Log Message:
Added editorial fixes from Glen

Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.126
retrieving revision 1.127
diff -C2 -d -r1.126 -r1.127
*** ws-addr-soap.xml	13 Mar 2006 14:45:51 -0000	1.126
--- ws-addr-soap.xml	13 Mar 2006 22:27:39 -0000	1.127
***************
*** 262,283 ****
            Module defines SOAP headers corresponding to the XML Infoset representation of the
            abstract message addressing properties defined in &wsa-core.title;.</p>
!         <p>When sending a message each property is represented using the appropriate element
!           information item as a SOAP header block. By default, the resulting header blocks are
!           targeted at the ultimate recipient in the SOAP message path (note that extensions to
!           WS-Addressing could be written to specify different targetting). <specref ref="bindrefp"/>
!           describes additional processing required when binding message addressing properties to
!           SOAP header blocks.</p>
!         <p>When receiving a message, the abstract properties are populated from their corresponding
!           element information items in the message. A message MUST NOT contain more than one wsa:To,
!           wsa:ReplyTo, wsa:FaultTo, wsa:Action, or wsa:MessageID header targeted at a recipient. A
!           recipient MUST generate a wsa:InvalidAddressingHeader (see <specref ref="invalidmapfault"
!           />) fault if such a message is received.</p>
!         <note>
!           <p>The SOAP processing model dictates that message addressing properties targeted at an
!             intermediary do not normally get relayed as message addressing properties when the
!             message is forwarded along the message path. The specification for a SOAP header used as
!             a reference property or use of the soap:relay attribute can override this default
!             behaviour.</p>
!         </note>
        </div2>
        <div2 id="additionalinfoset">
--- 262,293 ----
            Module defines SOAP headers corresponding to the XML Infoset representation of the
            abstract message addressing properties defined in &wsa-core.title;.</p>
!         <div3>
!           <head>Sending Messages</head>
!           <p>When sending a message each property is represented using the appropriate element
!             information item as a SOAP header block. By default, the resulting header blocks are
!             targeted at the ultimate recipient in the SOAP message path (note that extensions to
!             WS-Addressing could be written to specify different targetting). <specref ref="bindrefp"/>
!             describes additional processing required when binding message addressing properties to
!             SOAP header blocks.</p>
!         </div3>
!         <div3>
!           <head>Receiving Messages</head>
!           <p>When receiving a message, the abstract properties are populated from their corresponding
!             element information items in the message. A message MUST NOT contain more than one wsa:To,
!             wsa:ReplyTo, wsa:FaultTo, wsa:Action, or wsa:MessageID header targeted at a recipient;
!             headers with an incorrect cardinality MUST NOT be used to populate the corresponding
!             abstract properties. A
!             recipient MUST generate a wsa:InvalidAddressingHeader (see <specref ref="invalidmapfault"
!             />) fault if such a message is received.</p>
!           <note>
!             <p>The SOAP processing model dictates that message addressing properties targeted at an
!               intermediary do not normally get relayed as message addressing properties when the
!               message is forwarded along the message path. The specification for a SOAP header used as
!               a reference property or use of the soap:relay attribute can override this default
!               behaviour.</p>
!           </note>
!         </div3>
!         
! 
        </div2>
        <div2 id="additionalinfoset">
Received on Monday, 13 March 2006 22:27:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:41 GMT