- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 27 Mar 2006 19:54:11 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv21831
Modified Files:
ws-addr-soap.html
Log Message:
Sync with XML
Index: ws-addr-soap.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.html,v
retrieving revision 1.59
retrieving revision 1.60
diff -C2 -d -r1.59 -r1.60
*** ws-addr-soap.html 13 Mar 2006 22:28:23 -0000 1.59
--- ws-addr-soap.html 27 Mar 2006 19:54:09 -0000 1.60
***************
*** 67,72 ****
no official standing.</strong></p><p></p></div>
<hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro"> Introduction</a><br> 1.1 <a href="#notation"> Notational Conventions</a><br> 1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#s12feature">SOAP 1.2 Addressing 1.0 Feature</a><br> 2.1 <a href="#s12featurename">Feature Name</a><br> 2.2 <a href="#s12featuredesc">Description</a><br> 2.3 <a href="#s12featureprops">Properties</a><br> 2.4 <a href="#s12featureinteractions">Interactions with Other SOAP Features</a><br>3. <a href="#s12module">SOAP 1.2 Addressing 1.0 Module</a><br> 3.1 <a href="#s12modulename">Module Name</a><br> 3.2 <a href="#s12moduledesc">Description</a><br> 3.2.1 <a href="#N66089">Sending Messages</a><br> 3.2.2 <a href="#N66101">Reeiving Messages</a><br> 3.3 <a href="#additionalinfoset">Additional Infoset Items</a><br> 3.4 <a href="#bindrefp">Binding Message Addressing Properties</a><br> 3.5 <a href="#soaphdrvtransport">Relationship between SOAP Headers and transport-level properties</a><br>4. <a href="#s11ext">SOAP 1.1 Addressing 1.0 Extension</a><br> 4.1 <a href="#s11extname">Extension Name</a><br> 4.2 <a href="#s11extdesc">Description</a><br>5. <a href="#addressesinsoap">Addresses in SOAP</a><br> 5.1 <a href="#anonaddress">Use of Anonymous Address in SOAP Response Endpoints</a><br> 5.1.1 <a href="#N66336">SOAP 1.1/HTTP</a><br> 5.1.2 <a href="#N66345">SOAP 1.2</a><br> 5.2 <a href="#nonanonaddress">Use of Non-Anonymous Addresses in SOAP Response Endpoints</a><br> &nsp; 5.2.1 <a href="#N66367">SOAP 1.1/HTTP</a><br> 5.2.2 <a href="#N66379">SOAP 1.2</a><br>6. <a href="#faults">Faults</a><br> 6.1 <a href="#N66446">SOAP 1.2 Fault Binding</a><br> 6.2 <a href="#N66528">SOAP 1.1 Fault Binding</a><br> 6.3 <a href="#faultdetailelements">Fault Detail Elements</a><br> 6.3.1 <a href="#N66628">Problem Header QName</a><br> 6.3.2 <a href="#N66664">Problem IRI</a><br> 6.3.3 <a href="#N66700">Problem Action</a><br> 6.3.4 <a href="#N66760">Retry After</a><br> 6.4 <a href="#soapfaults">Predefined Faults</a><br> 6.4.1 <a href="#invalidmapfault"> Invalid Addressing Header</a><br> &nbp; 6.4.1.1 <a href="#N66827">wsa:InvalidAddress</a><br> 6.4.1.2 <a href="#N66836">wsa:InvalidEPR</a><br> 6.4.1.3 <a href="#N66845">wsa:InvalidCardinality</a><br> 6.4.1.4 <a href="#N66854">wsa:MissingAddressInEPR</a><br> 6.4.1.5 <a href="#N66863">wsa:DuplicateMessageID</a><br> 6.4.1.6 <a href="#N66872">wsa:ActionMismatch</a><br> 6.4.1.7 <a href="#N66881">wsa:OnlyAnonymousAddressSupported</a><br> 6.4.1.8 <a href="#N66890">wsa:OnlyNonAnonymousAddressSupported</a><br> &nbs; 6.4.2 <a href="#missingmapfault"> Message Addressing Header Required</a><br> 6.4.3 <a href="#destinationfault"> Destination Unreachable</a><br> 6.4.4 <a href="#actionfault"> Action Not Supported</a><br> 6.4.5 <a href="#unavailablefault"> Endpoint Unavailable</a><br>7. <a href="#securityconsiderations">Security Considerations</a><br> 7.1 <a href="#N67035">Establishing EPR Trust</a><br> 7.2 <a href="#N67053">Additional Security Considerations</a><br> 7.3 <a href="#N67071">Additional Considerations for SOAP Intermediaries</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#references"> References</a><br></p>
! <h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Change Log</a> (Non-Normative)<br> B.1 <a href="#N67522">Changes Since Candidate Recommendation</a><br> B.2 <a href="#N67532">Changes Since Last Call Working Draft</a><br> B.3 <a href="#N67542">Changes Since Second Working Draft</a><br> B.4 <a href="#N67552">Changes Since First Working Draft</a><br> B.5 <a href="#N67562">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
--- 67,72 ----
no official standing.</strong></p><p></p></div>
<hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#intro"> Introduction</a><br> 1.1 <a href="#notation"> Notational Conventions</a><br> 1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#s12feature">SOAP 1.2 Addressing 1.0 Feature</a><br> 2.1 <a href="#s12featurename">Feature Name</a><br> 2.2 <a href="#s12featuredesc">Description</a><br> 2.3 <a href="#s12featureprops">Properties</a><br> 2.4 <a href="#s12featureinteractions">Interactions with Other SOAP Features</a><br>3. <a href="#s12module">SOAP 1.2 Addressing 1.0 Module</a><br> 3.1 <a href="#s12modulename">Module Name</a><br> 3.2 <a href="#s12moduledesc">Description</a><br> 3.2.1 <a href="#N66086">Sending Messages</a><br> 3.2.2 <a href="#N66098">Reeiving Messages</a><br> 3.3 <a href="#additionalinfoset">Additional Infoset Items</a><br> 3.4 <a href="#bindrefp">Binding Message Addressing Properties</a><br> 3.5 <a href="#soaphdrvtransport">Relationship between SOAP Headers and transport-level properties</a><br>4. <a href="#s11ext">SOAP 1.1 Addressing 1.0 Extension</a><br> 4.1 <a href="#s11extname">Extension Name</a><br> 4.2 <a href="#s11extdesc">Description</a><br>5. <a href="#addressesinsoap">Addresses in SOAP</a><br> 5.1 <a href="#anonaddress">Use of Anonymous Address in SOAP Response Endpoints</a><br> 5.1.1 <a href="#N66333">SOAP 1.1/HTTP</a><br> 5.1.2 <a href="#N66342">SOAP 1.2</a><br> 5.2 <a href="#nonanonaddress">Use of Non-Anonymous Addresses in SOAP Response Endpoints</a><br> &nsp; 5.2.1 <a href="#N66364">SOAP 1.1/HTTP</a><br> 5.2.2 <a href="#N66376">SOAP 1.2</a><br>6. <a href="#faults">Faults</a><br> 6.1 <a href="#N66443">SOAP 1.2 Fault Binding</a><br> 6.2 <a href="#N66525">SOAP 1.1 Fault Binding</a><br> 6.3 <a href="#faultdetailelements">Fault Detail Elements</a><br> 6.3.1 <a href="#N66625">Problem Header QName</a><br> 6.3.2 <a href="#N66661">Problem IRI</a><br> 6.3.3 <a href="#N66697">Problem Action</a><br> 6.3.4 <a href="#N66757">Retry After</a><br> 6.4 <a href="#soapfaults">Predefined Faults</a><br> 6.4.1 <a href="#invalidmapfault"> Invalid Addressing Header</a><br> &nbp; 6.4.1.1 <a href="#N66824">wsa:InvalidAddress</a><br> 6.4.1.2 <a href="#N66833">wsa:InvalidEPR</a><br> 6.4.1.3 <a href="#N66842">wsa:InvalidCardinality</a><br> 6.4.1.4 <a href="#N66851">wsa:MissingAddressInEPR</a><br> 6.4.1.5 <a href="#N66860">wsa:DuplicateMessageID</a><br> 6.4.1.6 <a href="#N66869">wsa:ActionMismatch</a><br> 6.4.1.7 <a href="#N66878">wsa:OnlyAnonymousAddressSupported</a><br> 6.4.1.8 <a href="#N66887">wsa:OnlyNonAnonymousAddressSupported</a><br> &nbs; 6.4.2 <a href="#missingmapfault"> Message Addressing Header Required</a><br> 6.4.3 <a href="#destinationfault"> Destination Unreachable</a><br> 6.4.4 <a href="#actionfault"> Action Not Supported</a><br> 6.4.5 <a href="#unavailablefault"> Endpoint Unavailable</a><br>7. <a href="#securityconsiderations">Security Considerations</a><br> 7.1 <a href="#N67032">Establishing EPR Trust</a><br> 7.2 <a href="#N67050">Additional Security Considerations</a><br> 7.3 <a href="#N67068">Additional Considerations for SOAP Intermediaries</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#references"> References</a><br></p>
! <h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Change Log</a> (Non-Normative)<br> B.1 <a href="#N67519">Changes Since Candidate Recommendation</a><br> B.2 <a href="#N67529">Changes Since Last Call Working Draft</a><br> B.3 <a href="#N67539">Changes Since Second Working Draft</a><br> B.4 <a href="#N67549">Changes Since First Working Draft</a><br> B.5 <a href="#N67559">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
***************
*** 148,152 ****
<tr>
<td rowspan="1" colspan="1">wsaw</td>
! <td rowspan="1" colspan="1"> http://www.w3.org/2005/03/addressing/wsdl </td>
</tr>
<tr>
--- 148,152 ----
<tr>
<td rowspan="1" colspan="1">wsaw</td>
! <td rowspan="1" colspan="1"> http://www.w3.org/2006/02/addressing/wsdl </td>
</tr>
<tr>
***************
*** 156,162 ****
</tbody>
</table><br>
- <p>The Working Group intends to maintain the value of the Web Services Addressing 1.0 - Core namespace URI
- that was assigned in the Candidate Recommendation unless significant changes are made that
- impact the implementation of the specification.</p>
<p>WS-Addressing is defined in terms of the XML Information Set [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]. WS-Addressing is conformant to the SOAP 1.2 [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>] processing
model and is also compatible with SOAP 1.1[<cite><a href="#SOAP11">SOAP 1.1</a></cite>] for backwards
--- 156,159 ----
***************
*** 284,288 ****
<div class="div3">
! <h4><a name="N66089"></a>3.2.1 Sending Messages</h4>
<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
--- 281,285 ----
<div class="div3">
! <h4><a name="N66086"></a>3.2.1 Sending Messages</h4>
<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
***************
*** 294,298 ****
<div class="div3">
! <h4><a name="N66101"></a>3.2.2 Receiving Messages</h4>
<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,
--- 291,295 ----
<div class="div3">
! <h4><a name="N66098"></a>3.2.2 Receiving Messages</h4>
<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,
***************
*** 305,310 ****
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>
</div>
</div>
--- 302,307 ----
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 parameter or use of the soap:relay attribute can override this default
! behavior.</p>
</div>
</div>
***************
*** 352,356 ****
<p>Each header block added as a result of the above rule is annotated with a
wsa:IsReferenceParameter attribute (see <a href="#additionalinfoset"><b>3.3 Additional Infoset Items</b></a>) whose
! value is a valid xs:boolean representaion of "true". Any existing
wsa:IsReferenceParameter attribute on the header block is replaced.</p>
<div class="note"><p class="prefix"><b>Note:</b></p>
--- 349,353 ----
<p>Each header block added as a result of the above rule is annotated with a
wsa:IsReferenceParameter attribute (see <a href="#additionalinfoset"><b>3.3 Additional Infoset Items</b></a>) whose
! value is a valid xs:boolean representation of "true". Any existing
wsa:IsReferenceParameter attribute on the header block is replaced.</p>
<div class="note"><p class="prefix"><b>Note:</b></p>
***************
*** 377,381 ****
<wsa:EndpointReference
xmlns:wsa="http://www.w3.org/2005/08/addressing"
! xmlns:wsaw="http://www.w3.org/2005/03/addressing/wsdl"
xmlns:fabrikam="http://example.com/fabrikam"
xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
--- 374,378 ----
<wsa:EndpointReference
xmlns:wsa="http://www.w3.org/2005/08/addressing"
! xmlns:wsaw="http://www.w3.org/2006/02/addressing/wsdl"
xmlns:fabrikam="http://example.com/fabrikam"
xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
***************
*** 483,487 ****
<div class="div3">
! <h4><a name="N66336"></a>5.1.1 SOAP 1.1/HTTP</h4>
<p>When "http://www.w3.org/2005/08/addressing/anonymous" is specified for the response
endpoint then there is no change to the SOAP 1.1/ HTTP binding. </p>
--- 480,484 ----
<div class="div3">
! <h4><a name="N66333"></a>5.1.1 SOAP 1.1/HTTP</h4>
<p>When "http://www.w3.org/2005/08/addressing/anonymous" is specified for the response
endpoint then there is no change to the SOAP 1.1/ HTTP binding. </p>
***************
*** 489,493 ****
<div class="div3">
! <h4><a name="N66345"></a>5.1.2 SOAP 1.2</h4>
<p>When "http://www.w3.org/2005/08/addressing/anonymous" is specified for the response
endpoint and the message is the http://www.w3.org/2003/05/soap/mep/InboundMessage
--- 486,490 ----
<div class="div3">
! <h4><a name="N66342"></a>5.1.2 SOAP 1.2</h4>
<p>When "http://www.w3.org/2005/08/addressing/anonymous" is specified for the response
endpoint and the message is the http://www.w3.org/2003/05/soap/mep/InboundMessage
***************
*** 502,506 ****
<div class="div3">
! <h4><a name="N66367"></a>5.2.1 SOAP 1.1/HTTP</h4>
<p>When "http://www.w3.org/2005/08/addressing/anonymous" is not specified for the response
endpoint, then the message SHOULD be part of a binding that supports not returning a
--- 499,503 ----
<div class="div3">
! <h4><a name="N66364"></a>5.2.1 SOAP 1.1/HTTP</h4>
<p>When "http://www.w3.org/2005/08/addressing/anonymous" is not specified for the response
endpoint, then the message SHOULD be part of a binding that supports not returning a
***************
*** 508,516 ****
response message SHOULD be sent using a separate connection and using the address value
specified by response endpoint. Note that other specifications MAY define special URIs
! that have other behaviours (similar to the anonymous URI).</p>
</div>
<div class="div3">
! <h4><a name="N66379"></a>5.2.2 SOAP 1.2</h4>
<p>When "http://www.w3.org/2005/08/addressing/anonymous" is not specified for the response
endpoint, then any response SHOULD NOT be the
--- 505,513 ----
response message SHOULD be sent using a separate connection and using the address value
specified by response endpoint. Note that other specifications MAY define special URIs
! that have other behaviors (similar to the anonymous URI).</p>
</div>
<div class="div3">
! <h4><a name="N66376"></a>5.2.2 SOAP 1.2</h4>
<p>When "http://www.w3.org/2005/08/addressing/anonymous" is not specified for the response
endpoint, then any response SHOULD NOT be the
***************
*** 519,523 ****
binding that supports a one-way MEP could put the reply message in a separate one-way
MEP and a separate HTTP request. As in SOAP 1.1/HTTP, note that other specifications MAY
! define special URIs that have other behaviours (similar to the anonymous URI).</p>
</div>
</div>
--- 516,520 ----
binding that supports a one-way MEP could put the reply message in a separate one-way
MEP and a separate HTTP request. As in SOAP 1.1/HTTP, note that other specifications MAY
! define special URIs that have other behaviors (similar to the anonymous URI).</p>
</div>
</div>
***************
*** 561,565 ****
<div class="div2">
! <h3><a name="N66446"></a>6.1 SOAP 1.2 Fault Binding</h3>
<p>The fault properties bind to a SOAP 1.2 fault as follows:</p>
<dl>
--- 558,562 ----
<div class="div2">
! <h3><a name="N66443"></a>6.1 SOAP 1.2 Fault Binding</h3>
<p>The fault properties bind to a SOAP 1.2 fault as follows:</p>
<dl>
***************
*** 633,637 ****
<div class="div2">
! <h3><a name="N66528"></a>6.2 SOAP 1.1 Fault Binding</h3>
<p>The SOAP 1.1 fault is slightly less expressive than the SOAP 1.2 fault and maps only
[Subcode], [Reason] and [Detail]. These the properties bind to a SOAP 1.1 fault as
--- 630,634 ----
<div class="div2">
! <h3><a name="N66525"></a>6.2 SOAP 1.1 Fault Binding</h3>
<p>The SOAP 1.1 fault is slightly less expressive than the SOAP 1.2 fault and maps only
[Subcode], [Reason] and [Detail]. These the properties bind to a SOAP 1.1 fault as
***************
*** 704,708 ****
<div class="div3">
! <h4><a name="N66628"></a>6.3.1 Problem Header QName</h4>
<p> The following describes the <wsa:ProblemHeaderQName> element:</p>
<dl>
--- 701,705 ----
<div class="div3">
! <h4><a name="N66625"></a>6.3.1 Problem Header QName</h4>
<p> The following describes the <wsa:ProblemHeaderQName> element:</p>
<dl>
***************
*** 724,728 ****
<div class="div3">
! <h4><a name="N66664"></a>6.3.2 Problem IRI</h4>
<p> The following describes the <wsa:ProblemIRI> element:</p>
<dl>
--- 721,725 ----
<div class="div3">
! <h4><a name="N66661"></a>6.3.2 Problem IRI</h4>
<p> The following describes the <wsa:ProblemIRI> element:</p>
<dl>
***************
*** 743,747 ****
<div class="div3">
! <h4><a name="N66700"></a>6.3.3 Problem Action</h4>
<p> The following describes the <wsa:ProblemAction> element:</p>
<dl>
--- 740,744 ----
<div class="div3">
! <h4><a name="N66697"></a>6.3.3 Problem Action</h4>
<p> The following describes the <wsa:ProblemAction> element:</p>
<dl>
***************
*** 774,778 ****
<div class="div3">
! <h4><a name="N66760"></a>6.3.4 Retry After</h4>
<p> The following describes the <wsa:RetryAfter> element:</p>
<dl>
--- 771,775 ----
<div class="div3">
! <h4><a name="N66757"></a>6.3.4 Retry After</h4>
<p> The following describes the <wsa:RetryAfter> element:</p>
<dl>
***************
*** 816,835 ****
<div class="div4">
! <h5><a name="N66827"></a>6.4.1.1 wsa:InvalidAddress</h5>
<p>Specifies that an [address] was invalid.</p>
</div>
<div class="div4">
! <h5><a name="N66836"></a>6.4.1.2 wsa:InvalidEPR</h5>
<p>Specifies that the invalid header was expected to be an EPR but was not valid.</p>
</div>
<div class="div4">
! <h5><a name="N66845"></a>6.4.1.3 wsa:InvalidCardinality</h5>
<p>Specifies that there was a greater than expected number of the specified header.</p>
</div>
<div class="div4">
! <h5><a name="N66854"></a>6.4.1.4 wsa:MissingAddressInEPR</h5>
<p>Specifies that the invalid header was expected to be an EPR but did not contain an
[address].</p>
--- 813,832 ----
<div class="div4">
! <h5><a name="N66824"></a>6.4.1.1 wsa:InvalidAddress</h5>
<p>Specifies that an [address] was invalid.</p>
</div>
<div class="div4">
! <h5><a name="N66833"></a>6.4.1.2 wsa:InvalidEPR</h5>
<p>Specifies that the invalid header was expected to be an EPR but was not valid.</p>
</div>
<div class="div4">
! <h5><a name="N66842"></a>6.4.1.3 wsa:InvalidCardinality</h5>
<p>Specifies that there was a greater than expected number of the specified header.</p>
</div>
<div class="div4">
! <h5><a name="N66851"></a>6.4.1.4 wsa:MissingAddressInEPR</h5>
<p>Specifies that the invalid header was expected to be an EPR but did not contain an
[address].</p>
***************
*** 837,841 ****
<div class="div4">
! <h5><a name="N66863"></a>6.4.1.5 wsa:DuplicateMessageID</h5>
<p>Specifies that the invalid header conveyed a [message id] that was a duplicate of one
already received.</p>
--- 834,838 ----
<div class="div4">
! <h5><a name="N66860"></a>6.4.1.5 wsa:DuplicateMessageID</h5>
<p>Specifies that the invalid header conveyed a [message id] that was a duplicate of one
already received.</p>
***************
*** 843,847 ****
<div class="div4">
! <h5><a name="N66872"></a>6.4.1.6 wsa:ActionMismatch</h5>
<p>Specifies that the [action] and SOAPAction for the message did not match, [Details]
MAY contain a <wsa:ProblemAction> element in addition to the
--- 840,844 ----
<div class="div4">
! <h5><a name="N66869"></a>6.4.1.6 wsa:ActionMismatch</h5>
<p>Specifies that the [action] and SOAPAction for the message did not match, [Details]
MAY contain a <wsa:ProblemAction> element in addition to the
***************
*** 851,860 ****
<div class="div4">
! <h5><a name="N66881"></a>6.4.1.7 wsa:OnlyAnonymousAddressSupported</h5>
<p>Specifies that the only address supported is the anonymous address.</p>
</div>
<div class="div4">
! <h5><a name="N66890"></a>6.4.1.8 wsa:OnlyNonAnonymousAddressSupported</h5>
<p>Specifies that the anonymous address is not supported, and that only a non-anonymous
address will be accepted.</p>
--- 848,857 ----
<div class="div4">
! <h5><a name="N66878"></a>6.4.1.7 wsa:OnlyAnonymousAddressSupported</h5>
<p>Specifies that the only address supported is the anonymous address.</p>
</div>
<div class="div4">
! <h5><a name="N66887"></a>6.4.1.8 wsa:OnlyNonAnonymousAddressSupported</h5>
<p>Specifies that the anonymous address is not supported, and that only a non-anonymous
address will be accepted.</p>
***************
*** 943,947 ****
<div class="div2">
! <h3><a name="N67035"></a>7.1 Establishing EPR Trust</h3>
<p>There are many mechanisms that could be used to supply proof that a message sender has
authority to represent the [address] of EPRs supplied within the message. Typically such
--- 940,944 ----
<div class="div2">
! <h3><a name="N67032"></a>7.1 Establishing EPR Trust</h3>
<p>There are many mechanisms that could be used to supply proof that a message sender has
authority to represent the [address] of EPRs supplied within the message. Typically such
***************
*** 961,965 ****
<div class="div2">
! <h3><a name="N67053"></a>7.2 Additional Security Considerations</h3>
<p>The wsa:isReferenceParameter attribute is only meaningful on SOAP headers. Message
processors should consider its appearance elsewhere in a SOAP message as a possible
--- 958,962 ----
<div class="div2">
! <h3><a name="N67050"></a>7.2 Additional Security Considerations</h3>
<p>The wsa:isReferenceParameter attribute is only meaningful on SOAP headers. Message
processors should consider its appearance elsewhere in a SOAP message as a possible
***************
*** 968,977 ****
appearing as reference parameters in an EPR as a possible attack.</p>
<p>There are known XML ID and re-structuring attacks which should be considered by message
! processors, see [<cite><a href="#WS-Security">WS-Security</a></cite>] - Security Conciderations: Removal and
modification of XML elements.</p>
</div>
<div class="div2">
! <h3><a name="N67071"></a>7.3 Additional Considerations for SOAP Intermediaries</h3>
<p>To avoid breaking signatures, intermediaries MUST NOT change the XML representation of
WS-Addressing headers when relaying those headers. Specifically, intermediaries MUST NOT
--- 965,974 ----
appearing as reference parameters in an EPR as a possible attack.</p>
<p>There are known XML ID and re-structuring attacks which should be considered by message
! processors, see [<cite><a href="#WS-Security">WS-Security</a></cite>] - Security Considerations: Removal and
modification of XML elements.</p>
</div>
<div class="div2">
! <h3><a name="N67068"></a>7.3 Additional Considerations for SOAP Intermediaries</h3>
<p>To avoid breaking signatures, intermediaries MUST NOT change the XML representation of
WS-Addressing headers when relaying those headers. Specifically, intermediaries MUST NOT
***************
*** 1050,1056 ****
XML</a> is available at http://www.w3.org/TR/REC-xml-names. </dd>
<dt class="label"><a name="XMLInfoSet"></a>[XML Information Set] </dt><dd>
! <cite><a href="http://www.w3.org/TR/2001/REC-xml-infoset-20011024">XML Information Set</a></cite>, J. Cowan and R. Tobin, Editors. W3C Recommendation, World
! Wide Web Consortium, 24 October 2001. This version of the XML Information Set
! Recommendation is http://www.w3.org/TR/2001/REC-xml-infoset-20011024. The <a href="http://www.w3.org/TR/xml-infoset">latest version of XML Information
Set</a> is available at http://www.w3.org/TR/xml-infoset. </dd>
<dt class="label"><a name="XMLSchemaP1"></a>[XML Schema Structures] </dt><dd>
--- 1047,1053 ----
XML</a> is available at http://www.w3.org/TR/REC-xml-names. </dd>
<dt class="label"><a name="XMLInfoSet"></a>[XML Information Set] </dt><dd>
! <cite><a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204">XML Information Set (Second Edition)</a></cite>, J. Cowan and R. Tobin, Editors. W3C Recommendation, World
! Wide Web Consortium, 4 February 2004. This version of the XML Information Set
! Recommendation is http://www.w3.org/TR/2004/REC-xml-infoset-20040204. The <a href="http://www.w3.org/TR/xml-infoset">latest version of XML Information
Set</a> is available at http://www.w3.org/TR/xml-infoset. </dd>
<dt class="label"><a name="XMLSchemaP1"></a>[XML Schema Structures] </dt><dd>
***************
*** 1084,1091 ****
March 2004.</dd>
<dt class="label"><a name="SOAP11-ROR"></a>[SOAP 1.1 Request Optional Response HTTP Binding] </dt><dd>
! <cite><a href="http://www.w3.org/2002/ws/addr/6/03/drafts/NOTE-soap11-ror-httpbinding-20060399/">SOAP 1.1 Request Optional Response HTTP Binding</a></cite>, D. Orchard, Editor.
! W3C Note, World Wide Web Consortium, March 2006. This version of the "SOAP 1.1 Request
! Optional Response HTTP Binding" is
! http://www.w3.org/2002/ws/addr/6/03/drafts/NOTE-soap11-ror-httpbinding-20060399/. The <a href="http://www.w3.org/TR/soap11-ror-httpbinding">latest version of "SOAP 1.1 Request
Optional Response HTTP Binding"</a> is available
http://www.w3.org/TR/soap11-ror-httpbinding.
--- 1081,1086 ----
March 2004.</dd>
<dt class="label"><a name="SOAP11-ROR"></a>[SOAP 1.1 Request Optional Response HTTP Binding] </dt><dd>
! <cite><a href="http://www.w3.org/TR/soap11-ror-httpbinding">SOAP 1.1 Request Optional Response HTTP Binding</a></cite>, D. Orchard, Editor.
! World Wide Web Consortium. The <a href="http://www.w3.org/TR/soap11-ror-httpbinding">latest version of "SOAP 1.1 Request
Optional Response HTTP Binding"</a> is available
http://www.w3.org/TR/soap11-ror-httpbinding.
***************
*** 1114,1138 ****
<div class="div2">
! <h3><a name="N67522"></a>B.1 Changes Since Candidate Recommendation</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-03-13 @ 22:27</td><td>mhadley</td><td>Added editorial fixes from Glen</td></tr><tr><td>2006-03-13 @ 14:45</td><td>mhadley</td><td>Added editorial fixes from Hugo</td></tr><tr><td>2006-03-10 @ 15:26</td><td>mhadley</td><td>Added resolution of CR23</td></tr><tr><td>2006-03-09 @ 18:36</td><td>mhadley</td><td>Fixed editorial glitch</td></tr><tr><td>2006-03-09 @ 18:35</td><td>mhadley</td><td>Removed ProblemHeader detail element and made 'Destination Unreachable', 'Action Not Supported' and 'Endpoint Unavailable' faults optional</td></tr><tr><td>2006-03-09 @ 18:17</td><td>mhadley</td><td>Switched Inbound and Outbound to reflect perspective of responder</td></tr><tr><td>2006-03-06 @ 19:02</td><td>mhadley</td><td>Removed redundant ed notes re additional fault codes</td></tr><tr><td>2006-03-03 @ 14:10</td><td>mhadley</td><td>Fixed editor list in references</td></tr><tr><td>2006-03-03 @ 09:54</td><td>mhadley</td><td>Adde resolution of CR25 - use property names for SOAP request-response MEP</td></tr><tr><td>2006-03-02 @ 14:41</td><td>mhadley</td><td>Tweaked description of wsa:To with anonymous</td></tr><tr><td>2006-03-02 @ 10:14</td><td>mhadley</td><td>Added definition of term 'response endpoint'</td></tr><tr><td>2006-03-02 @ 08:51</td><td>mhadley</td><td>Added resolution to CR24, finessing text about use of predefined fault actions</td></tr><tr><td>2006-03-01 @ 17:01</td><td>mhadley</td><td>Added CR20 resolution - Strengthen guidance on protocol-specifc fault action values</td></tr><tr><td>2006-03-01 @ 16:52</td><td>mhadley</td><td>Added CR18 resolution. Also fixed some terminology 'response endpoint' to '[reply endpoint] property, changed explicit URIs to use predefined entity and fixed use of invalid markup '<a>' to '<xspecref>'</td></tr><tr><td>2006-02-18 @ 23:38</td><td>trogers</td><td>Added editorial note in place of a reference to the WG Note which will define the SOAP 1.1/HTTP request/optional-response MP.</td></tr><tr><td>2006-02-08 @ 07:05</td><td>trogers</td><td>Changed Change Log limit from 20060101 to 20061201</td></tr><tr><td>2006-02-08 @ 06:48</td><td>trogers</td><td>Added the resolution of CR15/i067/i068 - discussion of anonymous/non-anonymous in SOAP 1.1/SOAP 1.2.</td></tr><tr><td>2006-02-08 @ 06:23</td><td>trogers</td><td>Added the resolution of CR14 - stating independence of SOAP headers and transport properties</td></tr><tr><td>2006-02-08 @ 06:13</td><td>trogers</td><td>Added the resolution of CR13 - adding the OnlyAnonymousSupported and OnlyNonAnonymousSupported subsubcodes</td></tr><tr><td>2005-11-22 @ 20:41</td><td>mhadley</td><td>Added issue cr11 resolution, minor editorial teaks to SOAPAction to [action] relationship text</td></tr><tr><td>2005-11-08 @ 05:21</td><td>trogers</td><td>Implemented the resolution of CR7, stating when WSA is engaged.</td></tr><tr><td>2005-11-07 @ 07:18</td><td>mhadley</td><td>Added resolution to issue cr9, added URI for use with generic SOAP faults</td></tr><tr><d>2005-11-06 @ 12:48</td><td>trogers</td><td>Incorporated the resolution of CR8 by rephrasing the requirements on the SOAPAction HTTP header for SOAP 1.1.</td></tr><tr><td>2005-11-06 @ 12:30</td><td>trogers</td><td>Incorporated the resolution of CR4 by extending the definition of the anonymous URI.</td></tr><tr><td>2005-10-24 @ 05:02</td><td>trogers</td><td>Removed ProblemIRI from InvalidAddress explanation, resolving Issue CR6</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-09-15 @ 19:42</td><td>mhadley</td><td>Added new section for post CR changes</td></tr><tr><td>2005-09-15 @ 18:27</td><td>mhadley</td><td>Added resolution to issue cr1 - changed ActionMismatch to ProblemAction</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67532"></a>B.2 Changes Since Last Call Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-07-20 @ 19:04</td><td>mhadley</td><td>Added ednote asking for feedback on removal of [source endpoint] and wsa:From</td></tr><tr><td>2005-07-20 @ 18:21</td><td>mhadley</td><td>Added resolution to issues lc55 and lc87 - reworked security section</td></tr><tr><td>2005-07-20 @ 15:53</td><td>mhadley</td><td>Added resolution to issue lc76 - expanded faults section</td></tr><tr><td>2005-07-19 @ 20:08</td><td>mhadley</td><td>Added partial resolution to issue lc76 - added new sections for standard detail items and grouped faults in new section</td></tr><tr><td>2005-07-19 @ 18:46</td><td>mhadley</td><td>Added revised resolution to issue lc20 - clarified meaning of anonymous uri in SOAP</td></tr><tr><td>2005-06-21 @ 17:12</td><td>mhadley</td><td>Added issue 71 resolution - clarified that the value of reason text is recommended but not required</td></tr><tr><td>2005-06-14 @ 14:25</td><td>mhadley</td><td>Added resolutions o issues lc56 and lc72 - Added new fault detail elements and header block for SOAP 1.1</td></tr><tr><td>2005-06-03 @ 20:36</td><td>mhadley</td><td>Fixed typo in document prologue</td></tr><tr><td>2005-06-03 @ 20:33</td><td>mhadley</td><td>Added resolutions to issues lc58, lc79, lc91, lc102</td></tr><tr><td>2005-06-02 @ 19:45</td><td>mhadley</td><td>Added resolution to issue lc62 - added note confirming that endpoints may consume and respond to messages that do not use any WS-Addr headers</td></tr><tr><td>2005-06-02 @ 19:12</td><td>mhadley</td><td>Added resolution to issue lc6 and lc35 - added new conformance section, moved conformance text from module and extension sections</td></tr><tr><td>2005-06-02 @ 18:56</td><td>mhadley</td><td>Added resolution to issue lc73 - added note warning about use of reference parameters conflicting with normal message semantics</td></tr><tr><td>2005-06-02 @ 18:15</td><td>mhadley</td><td>Added resolution to issue lc37 - added DOS attack security considerations</td></tr><tr><td>005-06-02 @ 17:43</td><td>mhadley</td><td>Added clarifications of fault property values</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-25 @ 21:20</td><td>mhadley</td><td>Added resolution to issue lc105 - added requirement that no additional %-escaping be peformed on IRI type message addressing properties when serialized</td></tr><tr><td>2005-05-25 @ 21:07</td><td>mhadley</td><td>Added resolution to issue lc73 - clarrified meaning of omitting RetryAfter</td></tr><tr><td>2005-05-25 @ 21:03</td><td>mhadley</td><td>Added resolution to issue lc57 - added normative text describing fault binding</td></tr><tr><td>2005-05-25 @ 20:20</td><td>mhadley</td><td>Added resolution to issue lc66 - made it clear that type often refers to the content of elements rather than the element as a whole which can often also include attributes</td></tr><tr><td>2005-05-18 @ 19:44</td><td>mhadley</td><td>Added lc59 resolution -added missing namespace declaration in example</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:37</td><td>mhadley</td><td>Added lc52 resolution - MessageId to MessageID</td></tr><tr><td>2005-05-18 @ 19:35</td><td>mhadley</td><td>Added lc51 resolution - reordered property list to match order in core</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-05-18 @ 19:16</td><td>mhadley</td><td>Added lc38 resolution - nonNegativeInteger to unsignedLong for RetryAfter</td></tr><tr><td>2005-05-18 @ 18:03</td><td>mhadley</td><td>Added lc67 resolution - made namespace uri a link</td></tr><tr><td>2005-05-18 @ 17:58</td><td>mhadley</td><td>Added lc64 resolution - numerous editorial fixes</td></tr><tr><td>2005-05-16 @ 20:20</td><td>mgudgin</td><td>Fixed reference to RFC3987 to match format of othe biblio entries</td></tr><tr><td>2005-05-13 @ 18:56</td><td>mhadley</td><td>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</td></tr><tr><td>2005-05-05 @ 18:10</td><td>mhadley</td><td>Added issue 28 resolution: fixed use of mixed notation and indirect terminology for MAPs in Binding Message Addressing Properties section</td></tr><tr><td>2005-05-05 @ 17:39</td><td>mhadley</td><td>Added resolution to issues 26 and 36: Clarified use of invalid map fault for mismatched wsa:Action and SOAPAction; renamed and clarified invalid map and missing map faults.</td></tr><tr><td>2005-04-22 @ 20:01</td><td>mhadley</td><td>Added resolution to lc32 - added note warning of infoset changes due to IsReferenceParameter addition when binding [reference parameter] to SOAP.</td></tr><tr><td>2005-04-22 @ 19:51</td><td>mhadley</td><td>Added resolution to lc31 - clarified what to do if a reference parameter already has an IsRferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:46</td><td>mhadley</td><td>Added resolution to lc30 - added new section for definition of IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:26</td><td>mhadley</td><td>Added resolution to lc29 - capitalized first character of IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:07</td><td>mhadley</td><td>Added resolution to lc27 - clarified confusing use of XML infoset terminology in XML representation of properties.</td></tr><tr><td>2005-04-22 @ 18:58</td><td>mhadley</td><td>Added resolution to lc24 - editorial nits.</td></tr><tr><td>2005-04-22 @ 18:49</td><td>mhadley</td><td>Added resolution to lc23 - changed IRI to URI for constant values that are URIs.</td></tr><tr><td>2005-04-22 @ 15:27</td><td>mhadley</td><td>Added resolution to lc1 - clarified impact of omitting [message id], [reply endpoint] and [fault endpoint] on fault message generation</td></tr><tr><td>2005-04-12 @ 13:17</td><td>mhadley</td><td>Fixed closing eement in example</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67542"></a>B.3 Changes Since Second Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Added sentence about SOAP 1.1 to section 4</td></tr><tr><td>2005-03-18 @ 23:21</td><td>mgudgin</td><td>s/Addresssing/Addressing</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 03:16</td><td>mhadley</td><td>Incorporated additional issue resolution text for issues 7 and 44 from H. Haas.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-09 @ 07:11</td><td>mhadley</td><td>Fixed example that didn't reflect the chnage from wsa:Type to wsa:isReferenceParameter</td></tr><tr><td>2005-03-08 @ 20:50</td><td>mhadley</td><td>Added resolution to issue 53 (schema tweaks)</td></tr><tr><td>2005-03-02 @ 21:18</td><td>mhadley</td><td>Added resolution to issue 4</td></tr><tr><td>2005-03-02 @ 20:30</td><td>mhadley</td><tdAdded resolution to issue 7</td></tr><tr><td>2005-03-02 @ 19:36</td><td>mhadley</td><td>Added resolution to issues 22 and 51/</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-17 @ 15:37</td><td>mhadley</td><td>Added issue 47 resolution</td></tr><tr><td>2005-02-15 @ 22:06</td><td>mhadley</td><td>Fixed some references to message information headers to message information properties</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67552"></a>B.4 Changes Since First Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-24 @ 20:22</td><td>mgudgin</td><td>Removed spurious reference to section 3.3.2 from Section 3</td></tr><tr><td>2005-01-23 @ 21:11</td><td>mgudgin</td><td>Incorporated resolution of issue i008; added wsa:Type attribute to reference parameters</td></tr><tr><td>2005-01-20 @ 13:10</td><td>mgudgin</td><td>Removed text from first paragraph of section 3 per resolution of issue i040</td></tr><tr><td>2005-01-16 @ 22:41</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10<td><td>mhadley</td><td>Switched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67562"></a>B.5 Changes Since Submission</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-11-24 @ 15:32</td><td>mhadley</td><td>Added note that addressing is backwards compatible with SOAP 1.1</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 22:25</td><td>mhadley</td><td>Removed static change log and added dynamically generated change log from cvs.</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
</div>
--- 1109,1133 ----
<div class="div2">
! <h3><a name="N67519"></a>B.1 Changes Since Candidate Recommendation</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-03-27 @ 19:45</td><td>mhadley</td><td>Fixed a couple of typos</td></tr><tr><td>2006-03-13 @ 22:27</td><td>mhadley</td><td>Added editorial fixes from Glen</td></tr><tr><td>2006-03-13 @ 14:45</td><td>mhadley</td><td>Added editorial fixes from Hugo</td></tr><tr><td>2006-03-10 @ 15:26</td><td>mhadley</td><td>Added resolution of CR23</td></tr><tr><td>2006-03-09 @ 18:36</td><td>mhadley</td><td>Fixed editorial glitch</td></tr><tr><td>2006-03-09 @ 18:35</td><td>mhadley</td><td>Removed ProblemHeader detail element and made 'Destination Unreachable', 'Action Not Supported' and 'Endpoint Unavailable' faults optional</td></tr><tr><td>2006-03-09 @ 18:17</td><td>mhadley</td><td>Switched Inbound and Outbound to reflect perspective of responder</td></tr><tr><td>2006-03-06 @ 19:02</td><td>mhadley</td><td>Removed redundant ed notes re additional fault codes</td></tr><tr><td>2006-03-03 @ 14:10</td><td>mhadley</td><td>Fixed editorlist in references</td></tr><tr><td>2006-03-03 @ 09:54</td><td>mhadley</td><td>Added resolution of CR25 - use property names for SOAP request-response MEP</td></tr><tr><td>2006-03-02 @ 14:41</td><td>mhadley</td><td>Tweaked description of wsa:To with anonymous</td></tr><tr><td>2006-03-02 @ 10:14</td><td>mhadley</td><td>Added definition of term 'response endpoint'</td></tr><tr><td>2006-03-02 @ 08:51</td><td>mhadley</td><td>Added resolution to CR24, finessing text about use of predefined fault actions</td></tr><tr><td>2006-03-01 @ 17:01</td><td>mhadley</td><td>Added CR20 resolution - Strengthen guidance on protocol-specifc fault action values</td></tr><tr><td>2006-03-01 @ 16:52</td><td>mhadley</td><td>Added CR18 resolution. Also fixed some terminology 'response endpoint' to '[reply endpoint] property, changed explicit URIs to use predefined entity and fixed use of invalid markup '<a>' to '<xspecref>'</td></tr><tr><td>2006-02-18 @ 23:38</td><td>trogers</td><td>Added editorial note in place of a refeence to the WG Note which will define the SOAP 1.1/HTTP request/optional-response MEP.</td></tr><tr><td>2006-02-08 @ 07:05</td><td>trogers</td><td>Changed Change Log limit from 20060101 to 20061201</td></tr><tr><td>2006-02-08 @ 06:48</td><td>trogers</td><td>Added the resolution of CR15/i067/i068 - discussion of anonymous/non-anonymous in SOAP 1.1/SOAP 1.2.</td></tr><tr><td>2006-02-08 @ 06:23</td><td>trogers</td><td>Added the resolution of CR14 - stating independence of SOAP headers and transport properties</td></tr><tr><td>2006-02-08 @ 06:13</td><td>trogers</td><td>Added the resolution of CR13 - adding the OnlyAnonymousSupported and OnlyNonAnonymousSupported subsubcodes</td></tr><tr><td>2005-11-22 @ 20:41</td><td>mhadley</td><td>Added issue cr11 resolution, minor editorial teaks to SOAPAction to [action] relationship text</td></tr><tr><td>2005-11-08 @ 05:21</td><td>trogers</td><td>Implemented the resolution of CR7, stating when WSA is engaged.</td></tr><tr><td>2005-11-07 @ 07:18</td><td>mhadley</td><td>Adde resolution to issue cr9, added URI for use with generic SOAP faults</td></tr><tr><td>2005-11-06 @ 12:48</td><td>trogers</td><td>Incorporated the resolution of CR8 by rephrasing the requirements on the SOAPAction HTTP header for SOAP 1.1.</td></tr><tr><td>2005-11-06 @ 12:30</td><td>trogers</td><td>Incorporated the resolution of CR4 by extending the definition of the anonymous URI.</td></tr><tr><td>2005-10-24 @ 05:02</td><td>trogers</td><td>Removed ProblemIRI from InvalidAddress explanation, resolving Issue CR6</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-09-15 @ 19:42</td><td>mhadley</td><td>Added new section for post CR changes</td></tr><tr><td>2005-09-15 @ 18:27</td><td>mhadley</td><td>Added resolution to issue cr1 - changed ActionMismatch to ProblemAction</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67529"></a>B.2 Changes Since Last Call Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-07-20 @ 19:04</td><td>mhadley</td><td>Added ednote asking for feedback on removal of [source endpoint] and wsa:From</td></tr><tr><td>2005-07-20 @ 18:21</td><td>mhadley</td><td>Added resolution to issues lc55 and lc87 - reworked security section</td></tr><tr><td>2005-07-20 @ 15:53</td><td>mhadley</td><td>Added resolution to issue lc76 - expanded faults section</td></tr><tr><td>2005-07-19 @ 20:08</td><td>mhadley</td><td>Added partial resolution to issue lc76 - added new sections for standard detail items and grouped faults in new section</td></tr><tr><td>2005-07-19 @ 18:46</td><td>mhadley</td><td>Added revised resolution to issue lc20 - clarified meaning of anonymous uri in SOAP</td></tr><tr><td>2005-06-21 @ 17:12</td><td>mhadley</td><td>Added issue 71 resolution - clarified that the value of reason text is recommended but not required</td></tr><tr><td>2005-06-14 @ 14:25</td><td>mhadley</td><td>Added resolutions o issues lc56 and lc72 - Added new fault detail elements and header block for SOAP 1.1</td></tr><tr><td>2005-06-03 @ 20:36</td><td>mhadley</td><td>Fixed typo in document prologue</td></tr><tr><td>2005-06-03 @ 20:33</td><td>mhadley</td><td>Added resolutions to issues lc58, lc79, lc91, lc102</td></tr><tr><td>2005-06-02 @ 19:45</td><td>mhadley</td><td>Added resolution to issue lc62 - added note confirming that endpoints may consume and respond to messages that do not use any WS-Addr headers</td></tr><tr><td>2005-06-02 @ 19:12</td><td>mhadley</td><td>Added resolution to issue lc6 and lc35 - added new conformance section, moved conformance text from module and extension sections</td></tr><tr><td>2005-06-02 @ 18:56</td><td>mhadley</td><td>Added resolution to issue lc73 - added note warning about use of reference parameters conflicting with normal message semantics</td></tr><tr><td>2005-06-02 @ 18:15</td><td>mhadley</td><td>Added resolution to issue lc37 - added DOS attack security considerations</td></tr><tr><td>005-06-02 @ 17:43</td><td>mhadley</td><td>Added clarifications of fault property values</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-25 @ 21:20</td><td>mhadley</td><td>Added resolution to issue lc105 - added requirement that no additional %-escaping be peformed on IRI type message addressing properties when serialized</td></tr><tr><td>2005-05-25 @ 21:07</td><td>mhadley</td><td>Added resolution to issue lc73 - clarrified meaning of omitting RetryAfter</td></tr><tr><td>2005-05-25 @ 21:03</td><td>mhadley</td><td>Added resolution to issue lc57 - added normative text describing fault binding</td></tr><tr><td>2005-05-25 @ 20:20</td><td>mhadley</td><td>Added resolution to issue lc66 - made it clear that type often refers to the content of elements rather than the element as a whole which can often also include attributes</td></tr><tr><td>2005-05-18 @ 19:44</td><td>mhadley</td><td>Added lc59 resolution -added missing namespace declaration in example</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:37</td><td>mhadley</td><td>Added lc52 resolution - MessageId to MessageID</td></tr><tr><td>2005-05-18 @ 19:35</td><td>mhadley</td><td>Added lc51 resolution - reordered property list to match order in core</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-05-18 @ 19:16</td><td>mhadley</td><td>Added lc38 resolution - nonNegativeInteger to unsignedLong for RetryAfter</td></tr><tr><td>2005-05-18 @ 18:03</td><td>mhadley</td><td>Added lc67 resolution - made namespace uri a link</td></tr><tr><td>2005-05-18 @ 17:58</td><td>mhadley</td><td>Added lc64 resolution - numerous editorial fixes</td></tr><tr><td>2005-05-16 @ 20:20</td><td>mgudgin</td><td>Fixed reference to RFC3987 to match format of othe biblio entries</td></tr><tr><td>2005-05-13 @ 18:56</td><td>mhadley</td><td>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</td></tr><tr><td>2005-05-05 @ 18:10</td><td>mhadley</td><td>Added issue 28 resolution: fixed use of mixed notation and indirect terminology for MAPs in Binding Message Addressing Properties section</td></tr><tr><td>2005-05-05 @ 17:39</td><td>mhadley</td><td>Added resolution to issues 26 and 36: Clarified use of invalid map fault for mismatched wsa:Action and SOAPAction; renamed and clarified invalid map and missing map faults.</td></tr><tr><td>2005-04-22 @ 20:01</td><td>mhadley</td><td>Added resolution to lc32 - added note warning of infoset changes due to IsReferenceParameter addition when binding [reference parameter] to SOAP.</td></tr><tr><td>2005-04-22 @ 19:51</td><td>mhadley</td><td>Added resolution to lc31 - clarified what to do if a reference parameter already has an IsRferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:46</td><td>mhadley</td><td>Added resolution to lc30 - added new section for definition of IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:26</td><td>mhadley</td><td>Added resolution to lc29 - capitalized first character of IsReferenceParameter attribute.</td></tr><tr><td>2005-04-22 @ 19:07</td><td>mhadley</td><td>Added resolution to lc27 - clarified confusing use of XML infoset terminology in XML representation of properties.</td></tr><tr><td>2005-04-22 @ 18:58</td><td>mhadley</td><td>Added resolution to lc24 - editorial nits.</td></tr><tr><td>2005-04-22 @ 18:49</td><td>mhadley</td><td>Added resolution to lc23 - changed IRI to URI for constant values that are URIs.</td></tr><tr><td>2005-04-22 @ 15:27</td><td>mhadley</td><td>Added resolution to lc1 - clarified impact of omitting [message id], [reply endpoint] and [fault endpoint] on fault message generation</td></tr><tr><td>2005-04-12 @ 13:17</td><td>mhadley</td><td>Fixed closing eement in example</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67539"></a>B.3 Changes Since Second Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Added sentence about SOAP 1.1 to section 4</td></tr><tr><td>2005-03-18 @ 23:21</td><td>mgudgin</td><td>s/Addresssing/Addressing</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 03:16</td><td>mhadley</td><td>Incorporated additional issue resolution text for issues 7 and 44 from H. Haas.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-09 @ 07:11</td><td>mhadley</td><td>Fixed example that didn't reflect the chnage from wsa:Type to wsa:isReferenceParameter</td></tr><tr><td>2005-03-08 @ 20:50</td><td>mhadley</td><td>Added resolution to issue 53 (schema tweaks)</td></tr><tr><td>2005-03-02 @ 21:18</td><td>mhadley</td><td>Added resolution to issue 4</td></tr><tr><td>2005-03-02 @ 20:30</td><td>mhadley</td><tdAdded resolution to issue 7</td></tr><tr><td>2005-03-02 @ 19:36</td><td>mhadley</td><td>Added resolution to issues 22 and 51/</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-17 @ 15:37</td><td>mhadley</td><td>Added issue 47 resolution</td></tr><tr><td>2005-02-15 @ 22:06</td><td>mhadley</td><td>Fixed some references to message information headers to message information properties</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67549"></a>B.4 Changes Since First Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-24 @ 20:22</td><td>mgudgin</td><td>Removed spurious reference to section 3.3.2 from Section 3</td></tr><tr><td>2005-01-23 @ 21:11</td><td>mgudgin</td><td>Incorporated resolution of issue i008; added wsa:Type attribute to reference parameters</td></tr><tr><td>2005-01-20 @ 13:10</td><td>mgudgin</td><td>Removed text from first paragraph of section 3 per resolution of issue i040</td></tr><tr><td>2005-01-16 @ 22:41</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10<td><td>mhadley</td><td>Switched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67559"></a>B.5 Changes Since Submission</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-11-24 @ 15:32</td><td>mhadley</td><td>Added note that addressing is backwards compatible with SOAP 1.1</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 22:25</td><td>mhadley</td><td>Removed static change log and added dynamically generated change log from cvs.</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
</div>
Received on Monday, 27 March 2006 19:54:24 UTC