- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 13 May 2005 18:56:35 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv8141
Modified Files:
ws-addr-soap.xml ws-addr.xsd
Log Message:
Added resolutions to issues 33 and 34: editorial corrections to binding MAP to SOAP headers and new rule against multiple headers targetted at same recipient
Index: ws-addr.xsd
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr.xsd,v
retrieving revision 1.10
retrieving revision 1.11
diff -C2 -d -r1.10 -r1.11
*** ws-addr.xsd 22 Apr 2005 19:26:53 -0000 1.10
--- ws-addr.xsd 13 May 2005 18:56:33 -0000 1.11
***************
*** 15,20 ****
[1] http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
-->
! <!DOCTYPE xs:schema PUBLIC '-//W3C//DTD XMLSCHEMA 200102//EN'
! 'http://www.w3.org/2001/XMLSchema.dtd' [
<!ENTITY % entities SYSTEM 'entities.dtd' >
%entities;
--- 15,19 ----
[1] http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
-->
! <!DOCTYPE xs:schema PUBLIC '-//W3C//DTD XMLSCHEMA 200102//EN' 'http://www.w3.org/2001/XMLSchema.dtd' [
<!ENTITY % entities SYSTEM 'entities.dtd' >
%entities;
Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.57
retrieving revision 1.58
diff -C2 -d -r1.57 -r1.58
*** ws-addr-soap.xml 5 May 2005 18:10:03 -0000 1.57
--- ws-addr-soap.xml 13 May 2005 18:56:33 -0000 1.58
***************
*** 306,310 ****
gathered by an intermediary when receiving a SOAP message do
not necessarily get replayed as MAPs when resending the
! message along the message path.</p>
</div2>
<div2 id="additionalinfoset">
--- 306,315 ----
gathered by an intermediary when receiving a SOAP message do
not necessarily get replayed as MAPs when resending the
! message along the message path. 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>
</div2>
<div2 id="additionalinfoset">
***************
*** 327,336 ****
<head>Binding Message Addressing Properties</head>
<p>When a message is to be addressed to an endpoint, the XML
! Infoset representation of each specified message addressing
! property is inserted into the message as a SOAP header block
subject to the following additional constraints:</p>
<ulist>
<item>
! <p>The value of the [reference parameters]
property is added to the SOAP message header: the element
information item of each of the [reference parameters]
--- 332,342 ----
<head>Binding Message Addressing Properties</head>
<p>When a message is to be addressed to an endpoint, the XML
! Infoset representation of each message addressing
! property that has been assigned a value is inserted into the
! message as a SOAP header block
subject to the following additional constraints:</p>
<ulist>
<item>
! <p>The value, if any, of the [reference parameters]
property is added to the SOAP message header: the element
information item of each of the [reference parameters]
***************
*** 358,361 ****
--- 364,371 ----
an absolute IRI in the corresponding SOAP header block.</p>
</item>
+ <item>
+ <p>Each optional element or attribute that has a value equal to the
+ defined default value for that element or attribute MAY be omitted.</p>
+ </item>
</ulist>
<p>The following example shows how the SOAP 1.2 Addressing 1.0
Received on Friday, 13 May 2005 18:56:41 UTC