- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 22 Nov 2005 21:33:44 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing In directory hutz:/tmp/cvs-serv5499 Modified Files: ws-addr-core.html ws-addr-soap.html ws-addr-wsdl.html Log Message: Updated to match latest XML Index: ws-addr-wsdl.html =================================================================== RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v retrieving revision 1.30 retrieving revision 1.31 diff -C2 -d -r1.30 -r1.31 *** ws-addr-wsdl.html 2 Nov 2005 16:37:48 -0000 1.30 --- ws-addr-wsdl.html 22 Nov 2005 21:33:42 -0000 1.31 *************** *** 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="#tocRange"> Introduction</a><br> 1.1 <a href="#notation"> Notational Conventions</a><br> 1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#metadatinepr">Including WSDL Metadata in EPRs</a><br> 2.1 <a href="#refmetadatfromepr">Referencing WSDL Metadata from an EPR</a><br> 2.2 <a href="#embedmetadataepr">Embedding WSDL Metadata in an EPR</a><br>3. <a href="#indicatinguse">Indicating Use of WS-Addressing</a><br> 3.1 <a href="#N66018">UsingAddressing Extension Element</a><br> 3.2 <a href="#N66189">WSDL SOAP Module</a><br>4. <a href="#mapvaluesinwsdl">Specifying Message Addressing Properties in WSDL</a><br> 4.1 <a href="#destinwsdl">Destination</a><br> 4.2 <a href="#actioninwsdl">Action</a><br> 4.2.1 a href="#explicitaction">Explicit Association</a><br> 4.2.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br> 4.2.3 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br> 4.3 <a href="#refpinwsdl">Reference Parameters</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br> 5.1 <a href="#WSDL11MEPS">WSDL 1.1 Message Exchange Patterns</a><br> 5.1.1 <a href="#wsdl11oneway">One-way</a><br> 5.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br> 5.1.3 <a href="#wsdl11notification">Notification</a><br> 5.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br> 5.2 <a href="#WSDL20MEPS">WSL 2.0 Message Exchange Patterns</a><br> 5.2.1 <a href="#wsdl20inonly">In-only</a><br> 5.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br> 5.2.3 <a href="#wsdl20inout">In-out</a><br> 5.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br> 5.2.5 <a href="#wsdl20outonly">Out-only</a><br> 5.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br> 5.2.7 <a href="#wsdl20outin">Out-in</a><br> 5.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>6. <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="#actioncompatibility">Compatibility of [action] with previous versions of WS-Addressing</a> (Non-Normative)<br>C. <a href="#changelog">Change Log</a> (Non-Normative)<br> C.1 <a href="#N68622">Changes Since Third Working Draft</a><br> C.2 <a href="#N68632">Changes Since Second Working Draft</a><br> C.3 <a href="#N68642">Changes Since First Working Draft</a><br> C.4 <a href="#N68652">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="#tocRange"> Introduction</a><br> 1.1 <a href="#notation"> Notational Conventions</a><br> 1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#metadatinepr">Including WSDL Metadata in EPRs</a><br> 2.1 <a href="#refmetadatfromepr">Referencing WSDL Metadata from an EPR</a><br> 2.2 <a href="#embedmetadataepr">Embedding WSDL Metadata in an EPR</a><br>3. <a href="#indicatinguse">Indicating Use of WS-Addressing</a><br> 3.1 <a href="#N66018">UsingAddressing Extension Element</a><br> 3.1.1 <a href="#N66188">WSDL 2.0 Component Model Changes</a><br> 3.2 <a href="#N66207">WSDL SOAP Module</a><br>4. <a href="#mapvaluesinwsdl">Specifying Message Addressing Properties in WSDL</a><br> 4.1 <a href="#destinwsdl">Destination</a><br> &nsp; 4.2 <a href="#actioninwsdl">Action</a><br> 4.2.1 <a href="#explicitaction">Explicit Association</a><br> 4.2.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br> 4.2.3 <a href="#N66541">WSDL 2.0 Component Model Changes</a><br> 4.2.4 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br> 4.3 <a href="#refpinwsdl">Reference Parameters</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br> 5.1 <a href="#WSDL11MEPS">WSDL 1.1 Message Exchange Patterns</a><br> 5.1.1 <a href="#wsdl11oneway">One-way</a><br> 5.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br> &bsp;5.1.3 <a href="#wsdl11notification">Notification</a><br> 5.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br> 5.2 <a href="#WSDL20MEPS">WSDL 2.0 Message Exchange Patterns</a><br> 5.2.1 <a href="#wsdl20inonly">In-only</a><br> 5.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br> 5.2.3 <a href="#wsdl20inout">In-out</a><br> 5.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br> 5.2.5 <a href="#wsdl20outonly">Out-only</a><br> 5.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br> 5.2.7 <a href="#wsdl20outin">Out-in</a><br> 5.2.8 <a href="#wsd20outoptionalin">Out-optional-in</a><br>6. <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="#actioncompatibility">Compatibility of [action] with previous versions of WS-Addressing</a> (Non-Normative)<br>C. <a href="#changelog">Change Log</a> (Non-Normative)<br> C.1 <a href="#N68664">Changes Since Third Working Draft</a><br> C.2 <a href="#N68674">Changes Since Second Working Draft</a><br> C.3 <a href="#N68684">Changes Since First Working Draft</a><br> C.4 <a href="#N68694">Changes Since Submission</a><br></p></div><hr><div class="body"> <div class="div1"> *************** *** 351,356 **** </tr> <tr> ! <td rowspan="1" colspan="1">Yes, using another protocol or using SOAP headers with a soap:mustUnderstand ! value of "false"</td> <td rowspan="1" colspan="1">REQUIRED</td> <td rowspan="1" colspan="1">REQUIRED</td> --- 351,356 ---- </tr> <tr> ! <td rowspan="1" colspan="1">Yes, using another protocol or using SOAP headers with a ! soap:mustUnderstand value of "false"</td> <td rowspan="1" colspan="1">REQUIRED</td> <td rowspan="1" colspan="1">REQUIRED</td> *************** *** 367,379 **** </tbody> </table><br> ! ! <p>If WS-A is engaged, use of the ! message addressing properties MUST be fully compliant with this specification; ! in particular, senders MUST use all message addressing properties mandated by ! the Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>], applicable WS-Addressing ! protocol bindings (e.g. Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]), and ! this specification, and MUST follow all applicable WS-Addressing normative ! requirements.</p> ! <p>The wsaw:UsingAddressing element SHOULD appear as a child of the wsdl:binding element. Alternatively, the wsaw:UsingAddressing element MAY instead be included --- 367,375 ---- </tbody> </table><br> ! <p>If WS-A is engaged, use of the message addressing properties MUST be fully ! compliant with this specification; in particular, senders MUST use all message ! addressing properties mandated by the Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>], applicable WS-Addressing protocol bindings (e.g. ! Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]), and this specification, ! and MUST follow all applicable WS-Addressing normative requirements.</p> <p>The wsaw:UsingAddressing element SHOULD appear as a child of the wsdl:binding element. Alternatively, the wsaw:UsingAddressing element MAY instead be included *************** *** 424,431 **** </binding></pre></div> </div> </div> <div class="div2"> ! <h3><a name="N66189"></a>3.2 WSDL SOAP Module</h3> <p>In WSDL 2.0, the wsoap:module construct may be used to declare the use of the WS-Addressing 1.0 Module for the SOAP binding. The meaning of such a --- 420,441 ---- </binding></pre></div> </div> + <div class="div3"> + + <h4><a name="N66188"></a>3.1.1 WSDL 2.0 Component Model Changes</h4> + <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0 + component model:</p> + <ul> + <li> + <p>A property of the binding or endpoint named {addressing required} of + type xs:boolean. The property value is the value of the + wsdl:required attribute information item on the wsaw:UsingAddressing + extension element, if present; otherwise "false".</p> + </li> + </ul> + </div> </div> <div class="div2"> ! <h3><a name="N66207"></a>3.2 WSDL SOAP Module</h3> <p>In WSDL 2.0, the wsoap:module construct may be used to declare the use of the WS-Addressing 1.0 Module for the SOAP binding. The meaning of such a *************** *** 460,464 **** <h3><a name="destinwsdl"></a>4.1 Destination</h3> <p>The value of the [destination] message addressing property for a message sent to ! an endpoint SHOULD match the value of the {address} property of the endpoint component (WSDL 2.0) or the address value provided by the relevant port extension (WSDL 1.1). For a SOAP 1.1 port described using WSDL 1.1, the value is --- 470,474 ---- <h3><a name="destinwsdl"></a>4.1 Destination</h3> <p>The value of the [destination] message addressing property for a message sent to ! an endpoint MUST match the value of the {address} property of the endpoint component (WSDL 2.0) or the address value provided by the relevant port extension (WSDL 1.1). For a SOAP 1.1 port described using WSDL 1.1, the value is *************** *** 471,475 **** property with input, output and fault elements within a WSDL description: explicit and defaulting. Explicit association is described in section <a href="#explicitaction"><b>4.2.1 Explicit Association</b></a>; action defaulting (where a unique value for the ! [action] property is automatically generated) is described in section <a href="#defactionwsdl11"><b>4.2.3 Default Action Pattern for WSDL 1.1</b></a> for WSDL 1.1 and section <a href="#defactionwsdl20"><b>4.2.2 Default Action Pattern for WSDL 2.0</b></a> for WSDL 2.0.</p> <p>Ensuring that there is sufficient information within a message to distinguish which WSDL operation it is associated with is specified as a best practice in --- 481,485 ---- property with input, output and fault elements within a WSDL description: explicit and defaulting. Explicit association is described in section <a href="#explicitaction"><b>4.2.1 Explicit Association</b></a>; action defaulting (where a unique value for the ! [action] property is automatically generated) is described in section <a href="#defactionwsdl11"><b>4.2.4 Default Action Pattern for WSDL 1.1</b></a> for WSDL 1.1 and section <a href="#defactionwsdl20"><b>4.2.2 Default Action Pattern for WSDL 2.0</b></a> for WSDL 2.0.</p> <p>Ensuring that there is sufficient information within a message to distinguish which WSDL operation it is associated with is specified as a best practice in *************** *** 482,486 **** explicitly define the value of the [action] property for messages in a WSDL description. The type of the attribute is xs:anyURI and it is used as an ! extension on the WSDL input, output and fault elements.</p> <p>The inclusion of wsaw:Action without inclusion of wsaw:UsingAddressing has no normative intent and is only informational. In other words, the inclusion of --- 492,503 ---- explicitly define the value of the [action] property for messages in a WSDL description. The type of the attribute is xs:anyURI and it is used as an ! extension on the WSDL input, output and fault elements. A SOAP binding can ! specify SOAPAction values for the input messages of operations. In the ! absence of a wsaw:Action attribute on a WSDL input element where a ! SOAPAction value is specified, the value of the [action] property for the ! input message is the value of the SOAPAction specified. ! Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] specifies restrictions ! on the relationship between the values of [action] and SOAPAction for SOAP ! 1.1 and SOAP 1.2.</p> <p>The inclusion of wsaw:Action without inclusion of wsaw:UsingAddressing has no normative intent and is only informational. In other words, the inclusion of *************** *** 666,670 **** <div class="div3"> ! <h4><a name="defactionwsdl11"></a>4.2.3 Default Action Pattern for WSDL 1.1</h4> <p>A default pattern is also defined for backwards compatibility with WSDL 1.1. In the absence of the wsa:Action attribute, the following pattern is used to --- 683,703 ---- <div class="div3"> ! <h4><a name="N66541"></a>4.2.3 WSDL 2.0 Component Model Changes</h4> ! <p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0 ! component model:</p> ! <ul> ! <li> ! <p>A property of the Interface Message ! Reference and Interface Fault components named {action}. The ! property is of type xs:anyURI. The ! property value is the value of the wsaw:action attribute information item, if present; ! otherwise the default value computed following the rules from ! section <a href="#defactionwsdl20"><b>4.2.2 Default Action Pattern for WSDL 2.0</b></a>.</p> ! </li> ! </ul> ! </div> ! <div class="div3"> ! ! <h4><a name="defactionwsdl11"></a>4.2.4 Default Action Pattern for WSDL 1.1</h4> <p>A default pattern is also defined for backwards compatibility with WSDL 1.1. In the absence of the wsa:Action attribute, the following pattern is used to *************** *** 801,807 **** wsdl20:endpoint or wsdl11:port elements. When present, the value of the [reference parameters] message addressing property for a message sent to an ! endpoint MUST match the contents of the wsa:ReferenceParameters extension ! element. If omitted, the value of the [reference parameters] message addressing ! property is empty.</p> </div> </div> --- 834,839 ---- wsdl20:endpoint or wsdl11:port elements. When present, the value of the [reference parameters] message addressing property for a message sent to an ! endpoint MUST include the contents of the wsa:ReferenceParameters WSDL extension ! element.</p> </div> </div> *************** *** 1462,1481 **** <div class="div2"> ! <h3><a name="N68622"></a>C.1 Changes Since Third Working Draft</h3> ! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-10-31 @ 20:35</td><td>mhadley</td><td>Updated UsingAddressing section to move some dense text into a simpler tabular form</td></tr><tr><td>2005-10-31 @ 20:12</td><td>mhadley</td><td>Added resolution to issues 56 and 57, added new top level section that describes how MAP values are derived from WSDL for [destination], [action] and [reference properties]</td></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley<td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</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-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:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr>/table> </div> <div class="div2"> ! <h3><a name="N68632"></a>C.2 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>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</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 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><td>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Changed MUST to SHOULD in section 2.2 wrt matching port name</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-23 @ 16:11</td><td>mhadley</td><td>Incorporated resolution to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added reolution to issue 45</td></tr></table> </div> <div class="div2"> ! <h3><a name="N68642"></a>C.3 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-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</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>Swtched 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="N68652"></a>C.4 Changes Since Submission</h3> <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</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-11 @ 18:31</td><td>mgudgin</td><td> Added some TBD sections</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 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</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> --- 1494,1513 ---- <div class="div2"> ! <h3><a name="N68664"></a>C.1 Changes Since Third Working Draft</h3> ! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-11-22 @ 21:29</td><td>mhadley</td><td>Added resolution to issue 63, new subsections describing impacts of extension elements on WSDL 2.0 component model</td></tr><tr><td>2005-11-07 @ 07:08</td><td>mhadley</td><td>Added resolution to issue 65, [action] defaults to same as SOAPAction in absence of wsaw:Action</td></tr><tr><td>2005-11-07 @ 06:44</td><td>mhadley</td><td>Updated resolution to issues 56, 57</td></tr><tr><td>2005-10-31 @ 20:35</td><td>mhadley</td><td>Updated UsingAddressing section to move some dense text into a simpler tabular form</td></tr><tr><td>2005-10-31 @ 20:12</td><td>mhadley</td><td>Added resolution to issues 56 and 57, added new top level section that describes how MAP values are derived from WSDL for [destination], [action] and [reference properties]</td></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)/td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new sectin in changelog to account for previous draft publication</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:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table> </div> <div class="div2"> ! <h3><a name="N68674"></a>C.2 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>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</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 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><td>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Changed MUST to SHOULD in section 2.2 wrt matching port name</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-23 @ 16:11</td><td>mhadley</td><td>Incorporated resolution to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added reolution to issue 45</td></tr></table> </div> <div class="div2"> ! <h3><a name="N68684"></a>C.3 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-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</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>Swtched 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="N68694"></a>C.4 Changes Since Submission</h3> <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</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-11 @ 18:31</td><td>mgudgin</td><td> Added some TBD sections</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 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</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> Index: ws-addr-core.html =================================================================== RCS file: /sources/public/2004/ws/addressing/ws-addr-core.html,v retrieving revision 1.38 retrieving revision 1.39 diff -C2 -d -r1.38 -r1.39 *** ws-addr-core.html 8 Nov 2005 06:18:58 -0000 1.38 --- ws-addr-core.html 22 Nov 2005 21:33:42 -0000 1.39 *************** *** 1,3 **** ! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - Core</title><style type="text/css"> code { font-family: monospace; } --- 1,3 ---- ! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd"> <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - Core</title><style type="text/css"> code { font-family: monospace; } *************** *** 45,49 **** div.exampleHeader { font-weight: bold; margin: 4px} ! </style><link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link type="" href="" title="" rel="alternate"><link href="#contents" rel="contents"></head><body> <div class="head"> <h1>Web Services Addressing 1.0 - Core</h1> --- 45,49 ---- div.exampleHeader { font-weight: bold; margin: 4px} ! </style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="alternate" title="" href="" type=""><link rel="contents" href="#contents"></head><body> <div class="head"> <h1>Web Services Addressing 1.0 - Core</h1> *************** *** 72,77 **** 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="#tocRange">Introduction</a><br> 1.1 <a href="#notation">Notational Conventions</a><br> 1.2 <a href="#namespaces">Namespaces</a><br>2. <a href="#eprs">Endpoint References</a><br> 2.1 <a href="#eprinfomodel">Information Model for Endpoint References</a><br> 2.2 <a href="#eprinfoset">Endpoint Reference XML Infoset Representation</a><br> 2.3 <a href="#eprcomp">Endpoint Reference Comparison</a><br> 2.4 <a href="#eprlifecycle">Endpoint Reference Lifecycle</a><br> 2.5 <a href="#eprextensibility">Endpoint Reference Extensibility</a><br>3. <a href="#msgaddrprops">Message Addressing Properties</a><br> 3.1 <a href="#abstractmaps">Abstract Property Definitions</a><br> 3.2 <a href="#msgaddrpropsinfoset">XML Infoset Representation of MessageAddressing Properties</a><br> 3.2.1 <a href="#compiri">Comparing IRIs</a><br> 3.3 <a href="#sendmsgepr">Sending a Message to an EPR</a><br> 3.4 <a href="#formreplymsg">Formulating a Reply Message</a><br>4. <a href="#securityconsiderations">Security Considerations</a><br> 4.1 <a href="#N105B5">Additional Security Considerations</a><br>5. <a href="#references">References</a><br></p> ! <h3><a id="appendix" name="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="#N1071E">Changes Since Candidate Recommendation</a><br> B.2 <a href="#N10728">Changes Since Last Call Working Draft</a><br> B.3 <a href="#N10732">Changes Since Second Working Draft</a><br> B.4 <a href="#N1073C">Changes Since First Working Draft</a><br> B.5 <a href="#N10746">Changes Since Submission</a><br></p></div><hr><div class="body"> <div class="div1"> --- 72,77 ---- 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="#tocRange">Introduction</a><br> 1.1 <a href="#notation">Notational Conventions</a><br> 1.2 <a href="#namespaces">Namespaces</a><br>2. <a href="#eprs">Endpoint References</a><br> 2.1 <a href="#eprinfomodel">Information Model for Endpoint References</a><br> 2.2 <a href="#eprinfoset">Endpoint Reference XML Infoset Representation</a><br> 2.3 <a href="#eprcomp">Endpoint Reference Comparison</a><br> 2.4 <a href="#eprlifecycle">Endpoint Reference Lifecycle</a><br> 2.5 <a href="#eprextensibility">Endpoint Reference Extensibility</a><br>3. <a href="#msgaddrprops">Message Addressing Properties</a><br> 3.1 <a href="#abstractmaps">Abstract Property Definitions</a><br> 3.2 <a href="#msgaddrpropsinfoset">XML Infoset Representation of MessageAddressing Properties</a><br> 3.2.1 <a href="#compiri">Comparing IRIs</a><br> 3.3 <a href="#sendmsgepr">Sending a Message to an EPR</a><br> 3.4 <a href="#formreplymsg">Formulating a Reply Message</a><br>4. <a href="#securityconsiderations">Security Considerations</a><br> 4.1 <a href="#N66997">Additional Security Considerations</a><br>5. <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="#N67358">Changes Since Candidate Recommendation</a><br> B.2 <a href="#N67368">Changes Since Last Call Working Draft</a><br> B.3 <a href="#N67378">Changes Since Second Working Draft</a><br> B.4 <a href="#N67388">Changes Since First Working Draft</a><br> B.5 <a href="#N67398">Changes Since Submission</a><br></p></div><hr><div class="body"> <div class="div1"> *************** *** 95,99 **** http://example.com/fabrikam/Purchasing (see Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] for more information on the use of WS-Addressing in SOAP):</p> <div class="exampleOuter"> ! <p class="exampleHead" style="text-align: left"><i><span>Example 1-1. </span>Use of message addressing properties in a SOAP 1.2 message.</i></p> <div class="exampleInner"><pre> (01) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" --- 95,99 ---- http://example.com/fabrikam/Purchasing (see Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] for more information on the use of WS-Addressing in SOAP):</p> <div class="exampleOuter"> ! <p style="text-align: left" class="exampleHead"><i><span>Example 1-1. </span>Use of message addressing properties in a SOAP 1.2 message.</i></p> <div class="exampleInner"><pre> (01) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" *************** *** 421,425 **** the endpoint at the URI "http://example.com/fabrikam/acct".</p> <div class="exampleOuter"> ! <p class="exampleHead" style="text-align: left"><i><span>Example 2-1. </span>Example endpoint reference.</i></p> <div class="exampleInner"><pre> <wsa:EndpointReference xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"> --- 421,425 ---- the endpoint at the URI "http://example.com/fabrikam/acct".</p> <div class="exampleOuter"> ! <p style="text-align: left" class="exampleHead"><i><span>Example 2-1. </span>Example endpoint reference.</i></p> <div class="exampleInner"><pre> <wsa:EndpointReference xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"> *************** *** 514,518 **** <dd> <p>Reference to the endpoint from which the message originated.</p> ! <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right"> </td></tr><tr><td valign="top" align="left" colspan="2">The working group is considering removing the [source endpoint] abstract property due to lack of use-cases and seeks feedback on this decision.</td></tr></table> --- 514,518 ---- <dd> <p>Reference to the endpoint from which the message originated.</p> ! <table border="1" summary="Editorial note"><tr><td align="left" valign="top" width="50%"><b>Editorial note</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">The working group is considering removing the [source endpoint] abstract property due to lack of use-cases and seeks feedback on this decision.</td></tr></table> *************** *** 634,638 **** <p>This OPTIONAL element (of type wsa:EndpointReferenceType) provides the value for the [source endpoint] property.</p> ! <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right"> </td></tr><tr><td valign="top" align="left" colspan="2">The working group is considering removing the wsa:From element due to lack of use-cases and seeks feedback on this decision.</td></tr></table> --- 634,638 ---- <p>This OPTIONAL element (of type wsa:EndpointReferenceType) provides the value for the [source endpoint] property.</p> ! <table border="1" summary="Editorial note"><tr><td align="left" valign="top" width="50%"><b>Editorial note</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">The working group is considering removing the wsa:From element due to lack of use-cases and seeks feedback on this decision.</td></tr></table> *************** *** 789,793 **** properties serialized as header blocks in a SOAP 1.2 message:</p> <div class="exampleOuter"> ! <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Example message.</i></p> <div class="exampleInner"><pre> <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" --- 789,793 ---- properties serialized as header blocks in a SOAP 1.2 message:</p> <div class="exampleOuter"> ! <p style="text-align: left" class="exampleHead"><i><span>Example 3-1. </span>Example message.</i></p> <div class="exampleInner"><pre> <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" *************** *** 831,835 **** <p>The following example illustrates a reply to the above message:</p> <div class="exampleOuter"> ! <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Example reply message.</i></p> <div class="exampleInner"><pre> <S:Envelope --- 831,835 ---- <p>The following example illustrates a reply to the above message:</p> <div class="exampleOuter"> ! <p style="text-align: left" class="exampleHead"><i><span>Example 3-2. </span>Example reply message.</i></p> <div class="exampleInner"><pre> <S:Envelope *************** *** 911,915 **** <div class="div2"> ! <h3><a name="N105B5"></a>4.1 Additional Security Considerations</h3> <p>To prevent information disclosure, EPR issuers should not put sensitive information --- 911,915 ---- <div class="div2"> ! <h3><a name="N66997"></a>4.1 Additional Security Considerations</h3> <p>To prevent information disclosure, EPR issuers should not put sensitive information *************** *** 1018,1032 **** <div class="div2"> ! <h3><a name="N1071E"></a>B.1 Changes Since Candidate Recommendation</h3> <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-11-08 @ 06:10</td><td>trogers</td><td>Implemented the resolution of CR5, adding a section describing sending a message to an EPR</td></tr><tr><td>2005-11-07 @ 06:43</td><td>mhadley</td><td>Fixed typo</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></table> </div> <div class="div2"> ! <h3><a name="N10728"></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-19 @ 19:13</td><td>mhadley</td><td>Added resolution to issue lc101, lc104 - clarified extensibility of abstract properties</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-07-19 @ 18:28</td><td>mhadley</td><td>Added revised resolution to issue lc68 - updated text warning designers of EPR extensions that default processing prevails when their extension is not understood</td></tr><tr><td>2005-07-12 @ 18:46</td><td>mhadley</td><td>Added resolution to issues lc69, lc108 - made wsa:ReplyTo default to anonymous, added new predefied address URI that designates no reply/fault</td></tr><tr><td>2005-07-12 @ 15:57</td><td>mhadley</td><td>Added resolution to issue 107 - assorted editorial fixes wrt alignment with WSDL terminology</td></tr><tr><td>2005-07-11 @ 19:58</td><td>mhadley</td><td>Added resolution to issue lc90 - clarified use of message id as uniqueness metric</td></tr><tr><td>2005-06-21 @ 17:46</td><td>mhadley</td><td>Added resolution to issues lc75 and lc88 - updated description of [message id]</td></tr><tr><td>2005-06-20 @ 19:08</td><td>mhadley</td><td>Added resolution to issue lc106 - updated pseudo schemas to match the notational conventions used by WSDL 2.0</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:48</td><td>mhadley</td><td>Added resolution to issue lc78 - reworked formulating reply message text related to [relationship] to make it clear that the reply relationsship is not added top the relationships specified in the mesage being replied to</td></tr><tr><td>2005-06-02 @ 19:39</td><td>mhadley</td><td>Added resolution to issue lc84 - removed redundant co-occurrence requirements and concentrated conformance requirements in section 3.3</td></tr><tr><td>2005-06-02 @ 18:47</td><td>mhadley</td><td>Added resolution to issue lc89 - assorted editorial fixes</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>2005-06-02 @ 18:07</td><td>mhadley</td><td>Added explanation of cardinality notation</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 @ 20:25</td><td>mhadley</td><td>Added resolution to issue lc39 - changed mandatory to 1..1</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 ca often also include attributes</td></tr><tr><td>2005-05-18 @ 19:49</td><td>mhadley</td><td>Added lc81 resolution - remove mustUnderstand attributes from examples</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 @ 18:58</td><td>mhadley</td><td>Added lc97 resolution - Endpoint Reference to endpoint reference</td></tr><tr><td>2005-05-18 @ 18:56</td><td>mhadley</td><td>Added lc95 resolution - added WSDL 1.1 citation to introduction</td></tr><tr><td>2005-05-18 @ 18:51</td><td>mhadley</td><td>Added lc94 resolution - changed element to Element Information Item</td></tr><tr><td>2005-05-18 @ 18:48</td><td>mhadley</td><td>Added lc93 resolution - added ref to soap binding document prior to soap example in introduction</td></tr><tr><td>2005-05-18 @ 18:44</td><td>mhadley</td><td>Added lc92 resoltion - clarified document being referenced in introduction</td></tr><tr><td>2005-05-18 @ 18:40</td><td>mhadley</td><td>Added lc80 resolution - made abstract properties into a separate list</td></tr><tr><td>2005-05-18 @ 18:34</td><td>mhadley</td><td>Added lc74 resolution - added suggested security consideration</td></tr><tr><td>2005-05-18 @ 18:24</td><td>mhadley</td><td>Added lc63 resolution - editorial fixes to security section</td></tr><tr><td>2005-05-18 @ 18:19</td><td>mhadley</td><td>Added lc44 resolution - changed and to or in security section</td></tr><tr><td>2005-05-18 @ 18:17</td><td>mhadley</td><td>Added lc43 resolution - added ref to SOAP 1.1</td></tr><tr><td>2005-05-18 @ 18:12</td><td>mhadley</td><td>Added lc42 resolution - reordered infoset representation to match order of abstract properties</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 editrial fixes</td></tr><tr><td>2005-05-16 @ 20:28</td><td>mgudgin</td><td>Fixed mismatched endtag in Section 3.1</td></tr><tr><td>2005-05-16 @ 20:16</td><td>mgudgin</td><td>Fixed reference to RFC3987 to match format of other biblio entries</td></tr><tr><td>2005-04-22 @ 18:26</td><td>mhadley</td><td>Added resolution to lc22 - clarified ignore rule for extension attributes.</td></tr><tr><td>2005-04-22 @ 18:24</td><td>mhadley</td><td>Added resolution to lc21 - removed HTTP specific restriction on use of anonymous URI in [destination] for replies only.</td></tr><tr><td>2005-04-22 @ 18:18</td><td>mhadley</td><td>Added resolution to lc19 - clarified that [destination] value comparison is out of scope except for using simple string comparison to determine whether the anonymous destination is being used.</td></tr><tr><td>2005-04-22 @ 18:12</td><td>mhadley</td><td>Added resolution to lc18 - simplified description of wsa:To and wsa:Action elements</td></tr><tr><td>2005-04-22 @ 18:04</td><td>mhadley</td><td>Added resoluton to lc17 - clarified that anonymous destination URI is not just for use in replies</td></tr><tr><td>2005-04-22 @ 18:01</td><td>mhadley</td><td>Added resolution to lc16 and lc54 - removed suggestion that required was required to use [destination] and [action] properties for dispatch</td></tr><tr><td>2005-04-22 @ 17:55</td><td>mhadley</td><td>Added resolution to lc15 - clarified cardinality of [relationship] properties using predefined reply URI</td></tr><tr><td>2005-04-22 @ 17:50</td><td>mhadley</td><td>Added resolution to lc14 - clarified reply IRI targetting</td></tr><tr><td>2005-04-22 @ 17:41</td><td>mhadley</td><td>Added resolution to lc13 - clarified wording in description of metadata</td></tr><tr><td>2005-04-22 @ 17:38</td><td>mhadley</td><td>Added resolution to lc12 - removed data encoding from description of reference parameters</td></tr><tr><td>2005-04-22 @ 17:30</td><td>mhadley</td><td>Added resolution to lc10 and lc11 - clarified types and opacity of reference parameters</td></tr><tr><td>2005-0-22 @ 17:25</td><td>mhadley</td><td>Added resolution to lc9 - changed IRI to absolute IRI where appropriate</td></tr><tr><td>2005-04-22 @ 16:16</td><td>mhadley</td><td>Added resolution to lc8 - changed IRI to URI where used to refer to IRIs in the specification that are actually URIs</td></tr><tr><td>2005-04-22 @ 15:49</td><td>mhadley</td><td>Added resolution to lc7 - fixed editorial nits</td></tr><tr><td>2005-04-22 @ 15:32</td><td>mhadley</td><td>Added resolution to lc3 - removed single extensibility point from infoset representation to avoid impression that other extenisibility points are not also valid</td></tr><tr><td>2005-04-22 @ 15:06</td><td>mhadley</td><td>Added resolution to lc2 - assorted editorial changes</td></tr></table> </div> <div class="div2"> ! <h3><a name="N10732"></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-30 @ 21:02</td><td>plehegar</td><td>Removed some extra blanks Added the note from David Hull at --- 1018,1032 ---- <div class="div2"> ! <h3><a name="N67358"></a>B.1 Changes Since Candidate Recommendation</h3> <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-11-08 @ 06:10</td><td>trogers</td><td>Implemented the resolution of CR5, adding a section describing sending a message to an EPR</td></tr><tr><td>2005-11-07 @ 06:43</td><td>mhadley</td><td>Fixed typo</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></table> </div> <div class="div2"> ! <h3><a name="N67368"></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-19 @ 19:13</td><td>mhadley</td><td>Added resolution to issue lc101, lc104 - clarified extensibility of abstract properties</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-07-19 @ 18:28</td><td>mhadley</td><td>Added revised resolution to issue lc68 - updated text warning designers of EPR extensions that default processing prevails when their extension is not understood</td></tr><tr><td>2005-07-12 @ 18:46</td><td>mhadley</td><td>Added resolution to issues lc69, lc108 - made wsa:ReplyTo default to anonymous, added new predefied address URI that designates no reply/fault</td></tr><tr><td>2005-07-12 @ 15:57</td><td>mhadley</td><td>Added resolution to issue 107 - assorted editorial fixes wrt alignment with WSDL terminology</td></tr><tr><td>2005-07-11 @ 19:58</td><td>mhadley</td><td>Added resolution to issue lc90 - clarified use of message id as uniqueness metric</td></tr><tr><td>2005-06-21 @ 17:46</td><td>mhadley</td><td>Added resolution to issues lc75 and lc88 - updated description of [message id]</td></tr><tr><td>2005-06-20 @ 19:08</td><td>mhadley</td><td>Added resolution to issue lc106 - updated pseudo schemas to match the notational conventions used by WSDL 2.0</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:48</td><td>mhadley</td><td>Added resolution to issue lc78 - reworked formulating reply message text related to [relationship] to make it clear that the reply relationsship is not added top the relationships specified in the mesage being replied to</td></tr><tr><td>2005-06-02 @ 19:39</td><td>mhadley</td><td>Added resolution to issue lc84 - removed redundant co-occurrence requirements and concentrated conformance requirements in section 3.3</td></tr><tr><td>2005-06-02 @ 18:47</td><td>mhadley</td><td>Added resolution to issue lc89 - assorted editorial fixes</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>2005-06-02 @ 18:07</td><td>mhadley</td><td>Added explanation of cardinality notation</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 @ 20:25</td><td>mhadley</td><td>Added resolution to issue lc39 - changed mandatory to 1..1</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 ca often also include attributes</td></tr><tr><td>2005-05-18 @ 19:49</td><td>mhadley</td><td>Added lc81 resolution - remove mustUnderstand attributes from examples</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 @ 18:58</td><td>mhadley</td><td>Added lc97 resolution - Endpoint Reference to endpoint reference</td></tr><tr><td>2005-05-18 @ 18:56</td><td>mhadley</td><td>Added lc95 resolution - added WSDL 1.1 citation to introduction</td></tr><tr><td>2005-05-18 @ 18:51</td><td>mhadley</td><td>Added lc94 resolution - changed element to Element Information Item</td></tr><tr><td>2005-05-18 @ 18:48</td><td>mhadley</td><td>Added lc93 resolution - added ref to soap binding document prior to soap example in introduction</td></tr><tr><td>2005-05-18 @ 18:44</td><td>mhadley</td><td>Added lc92 resoltion - clarified document being referenced in introduction</td></tr><tr><td>2005-05-18 @ 18:40</td><td>mhadley</td><td>Added lc80 resolution - made abstract properties into a separate list</td></tr><tr><td>2005-05-18 @ 18:34</td><td>mhadley</td><td>Added lc74 resolution - added suggested security consideration</td></tr><tr><td>2005-05-18 @ 18:24</td><td>mhadley</td><td>Added lc63 resolution - editorial fixes to security section</td></tr><tr><td>2005-05-18 @ 18:19</td><td>mhadley</td><td>Added lc44 resolution - changed and to or in security section</td></tr><tr><td>2005-05-18 @ 18:17</td><td>mhadley</td><td>Added lc43 resolution - added ref to SOAP 1.1</td></tr><tr><td>2005-05-18 @ 18:12</td><td>mhadley</td><td>Added lc42 resolution - reordered infoset representation to match order of abstract properties</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 editrial fixes</td></tr><tr><td>2005-05-16 @ 20:28</td><td>mgudgin</td><td>Fixed mismatched endtag in Section 3.1</td></tr><tr><td>2005-05-16 @ 20:16</td><td>mgudgin</td><td>Fixed reference to RFC3987 to match format of other biblio entries</td></tr><tr><td>2005-04-22 @ 18:26</td><td>mhadley</td><td>Added resolution to lc22 - clarified ignore rule for extension attributes.</td></tr><tr><td>2005-04-22 @ 18:24</td><td>mhadley</td><td>Added resolution to lc21 - removed HTTP specific restriction on use of anonymous URI in [destination] for replies only.</td></tr><tr><td>2005-04-22 @ 18:18</td><td>mhadley</td><td>Added resolution to lc19 - clarified that [destination] value comparison is out of scope except for using simple string comparison to determine whether the anonymous destination is being used.</td></tr><tr><td>2005-04-22 @ 18:12</td><td>mhadley</td><td>Added resolution to lc18 - simplified description of wsa:To and wsa:Action elements</td></tr><tr><td>2005-04-22 @ 18:04</td><td>mhadley</td><td>Added resoluton to lc17 - clarified that anonymous destination URI is not just for use in replies</td></tr><tr><td>2005-04-22 @ 18:01</td><td>mhadley</td><td>Added resolution to lc16 and lc54 - removed suggestion that required was required to use [destination] and [action] properties for dispatch</td></tr><tr><td>2005-04-22 @ 17:55</td><td>mhadley</td><td>Added resolution to lc15 - clarified cardinality of [relationship] properties using predefined reply URI</td></tr><tr><td>2005-04-22 @ 17:50</td><td>mhadley</td><td>Added resolution to lc14 - clarified reply IRI targetting</td></tr><tr><td>2005-04-22 @ 17:41</td><td>mhadley</td><td>Added resolution to lc13 - clarified wording in description of metadata</td></tr><tr><td>2005-04-22 @ 17:38</td><td>mhadley</td><td>Added resolution to lc12 - removed data encoding from description of reference parameters</td></tr><tr><td>2005-04-22 @ 17:30</td><td>mhadley</td><td>Added resolution to lc10 and lc11 - clarified types and opacity of reference parameters</td></tr><tr><td>2005-0-22 @ 17:25</td><td>mhadley</td><td>Added resolution to lc9 - changed IRI to absolute IRI where appropriate</td></tr><tr><td>2005-04-22 @ 16:16</td><td>mhadley</td><td>Added resolution to lc8 - changed IRI to URI where used to refer to IRIs in the specification that are actually URIs</td></tr><tr><td>2005-04-22 @ 15:49</td><td>mhadley</td><td>Added resolution to lc7 - fixed editorial nits</td></tr><tr><td>2005-04-22 @ 15:32</td><td>mhadley</td><td>Added resolution to lc3 - removed single extensibility point from infoset representation to avoid impression that other extenisibility points are not also valid</td></tr><tr><td>2005-04-22 @ 15:06</td><td>mhadley</td><td>Added resolution to lc2 - assorted editorial changes</td></tr></table> </div> <div class="div2"> ! <h3><a name="N67378"></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-30 @ 21:02</td><td>plehegar</td><td>Removed some extra blanks Added the note from David Hull at *************** *** 1037,1046 **** <div class="div2"> ! <h3><a name="N1073C"></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-23 @ 21:13</td><td>mgudgin</td><td>Incorporated resolution of issue i014; edits to Section 2.3</td></tr><tr><td>2005-01-23 @ 20:52</td><td>mgudgin</td><td>Incorporated resolution of issue i006; made wsa:To optional</td></tr><tr><td>2005-01-23 @ 19:32</td><td>mgudgin</td><td>Incorporated resolution of Issue i001 by removing Reference Properties</td></tr><tr><td>2005-01-17 @ 02:13</td><td>mgudgin</td><td>Incorporated Paco's proposal for resolving Issue 038</td></tr><tr><td>2005-01-16 @ 22:40</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</td></tr><tr><td>2004-12-17 @ 16:08</td><td>mhadley</td><td>Improved readability of introduction</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="N10746"></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-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-22 @ 15:40</td><td>mhadley</td><td>Removed reference to WS-Policy</td></tr><tr><td>2004-11-15 @ 19:43</td><td>mhadley</td><td>Fixed some inter and intra spec references.</td></tr><tr><td>2004-11-12 @ 21:19</td><td>mgudgin</td><td>Removed TBD sections</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td> Added some TBD sections</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> --- 1037,1046 ---- <div class="div2"> ! <h3><a name="N67388"></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-23 @ 21:13</td><td>mgudgin</td><td>Incorporated resolution of issue i014; edits to Section 2.3</td></tr><tr><td>2005-01-23 @ 20:52</td><td>mgudgin</td><td>Incorporated resolution of issue i006; made wsa:To optional</td></tr><tr><td>2005-01-23 @ 19:32</td><td>mgudgin</td><td>Incorporated resolution of Issue i001 by removing Reference Properties</td></tr><tr><td>2005-01-17 @ 02:13</td><td>mgudgin</td><td>Incorporated Paco's proposal for resolving Issue 038</td></tr><tr><td>2005-01-16 @ 22:40</td><td>mgudgin</td><td>s/PortType/InterfaceName in certain examples</td></tr><tr><td>2004-12-17 @ 16:08</td><td>mhadley</td><td>Improved readability of introduction</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="N67398"></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-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-22 @ 15:40</td><td>mhadley</td><td>Removed reference to WS-Policy</td></tr><tr><td>2004-11-15 @ 19:43</td><td>mhadley</td><td>Fixed some inter and intra spec references.</td></tr><tr><td>2004-11-12 @ 21:19</td><td>mgudgin</td><td>Removed TBD sections</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td> Added some TBD sections</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> Index: ws-addr-soap.html =================================================================== RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.html,v retrieving revision 1.43 retrieving revision 1.44 diff -C2 -d -r1.43 -r1.44 *** ws-addr-soap.html 8 Nov 2005 06:18:58 -0000 1.43 --- ws-addr-soap.html 22 Nov 2005 21:33:42 -0000 1.44 *************** *** 1,3 **** ! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - SOAP Binding</title><style type="text/css"> code { font-family: monospace; } --- 1,3 ---- ! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd"> <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - SOAP Binding</title><style type="text/css"> code { font-family: monospace; } *************** *** 45,49 **** div.exampleHeader { font-weight: bold; margin: 4px} ! </style><link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link type="" href="" title="" rel="alternate"><link href="#contents" rel="contents"></head><body> <div class="head"> <h1>Web Services Addressing 1.0 - SOAP Binding</h1> --- 45,49 ---- div.exampleHeader { font-weight: bold; margin: 4px} ! </style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="alternate" title="" href="" type=""><link rel="contents" href="#contents"></head><body> <div class="head"> <h1>Web Services Addressing 1.0 - SOAP Binding</h1> *************** *** 57,61 **** <dd>Martin Gudgin, Microsoft Corp</dd> <dd>Marc Hadley, Sun Microsystems, Inc</dd> ! <dd>Tony Rogers, Computer Associates International, Inc</dd> </dl><p>This document is also available in these non-normative formats: <a href=""></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div> <h2><a name="abstract">Abstract</a></h2> --- 57,61 ---- <dd>Martin Gudgin, Microsoft Corp</dd> <dd>Marc Hadley, Sun Microsystems, Inc</dd> ! <dd>Tony Rogers, Computer Associates International, Inc</dd> </dl><p>This document is also available in these non-normative formats: <a href=""></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © @@@@ <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr><div> <h2><a name="abstract">Abstract</a></h2> *************** *** 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.3 <a href="#additionalinfoset">Additional Infoset Items</a><br> 3.4 <a href="#bindrefp">Binding Message Addressing Properies</a><br> 3.5 <a href="#soaphttp">Use of Anonymous Address in SOAP</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="#faults">Faults</a><br> 5.1 <a href="#N10334">SOAP 1.2 Fault Binding</a><br> 5.2 <a href="#N10386">SOAP 1.1 Fault Binding</a><br> 5.3 <a href="#faultdetailelements">Fault Detail Elements</a><br> 5.3.1 <a href="#N103F0">Problem Header</a><br> 5.3.2 <a href="#N10414">Problem Header QName</a><br> 5.3.3 <a href="#N10438">Problem IRI</a><br> 5.3.4 <a href="#N1045C">Problem Action</a><br> 5.3.5 <a href="#N1498">Retry After</a><br> 5.4 <a href="#soapfaults">Predefined Faults</a><br> 5.4.1 <a href="#invalidmapfault"> Invalid Addressing Header</a><br> 5.4.1.1 <a href="#N104E1">wsa:InvalidAddress</a><br> 5.4.1.2 <a href="#N104EA">wsa:InvalidEPR</a><br> 5.4.1.3 <a href="#N104F3">wsa:InvalidCardinality</a><br> 5.4.1.4 <a href="#N104FC">wsa:MissingAddressInEPR</a><br> 5.4.1.5 <a href="#N10505">wsa:DuplicateMessageID</a><br> 5.4.1.6 <a href="#N1050E">wsa:ActionMismatch</a><br> 5.4.2 < href="#missingmapfault"> Message Addressing Header Required</a><br> 5.4.3 <a href="#destinationfault"> Destination Unreachable</a><br> 5.4.4 <a href="#actionfault"> Action Not Supported</a><br> 5.4.5 <a href="#unavailablefault"> Endpoint Unavailable</a><br>6. <a href="#securityconsiderations">Security Considerations</a><br> 6.1 <a href="#N10594">Establishing EPR Trust</a><br> 6.2 <a href="#N105A6">Additional Security Considerations</a><br> 6.3 <a href="#N105B8">Additional Considerations for SOAP Intermediaries</a><br>7. <a href="#conformance">Conformance</a><br>8. <a href="#references"> References</a><br></p> ! <h3><a id="appendix" name="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="#N10754">Changes Since Candidate Recommendation</a><br> B.2 <a href="#N1075E">Changes Since Last Call Working Draft</a><br> B.3 <a href="#N10768">Changes Since Second Working Draft</a><br> B.4 <a href="#N10772">Changes Since First Working Draft</a><br> B.5 <a href="#N1077C">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.3 <a href="#additionalinfoset">Additional Infoset Items</a><br> 3.4 <a href="#bindrefp">Binding Message Addressing Properies</a><br> 3.5 <a href="#soaphttp">Use of Anonymous Address in SOAP</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="#faults">Faults</a><br> 5.1 <a href="#N66356">SOAP 1.2 Fault Binding</a><br> 5.2 <a href="#N66438">SOAP 1.1 Fault Binding</a><br> 5.3 <a href="#faultdetailelements">Fault Detail Elements</a><br> 5.3.1 <a href="#N66544">Problem Header</a><br> 5.3.2 <a href="#N66580">Problem Header QName</a><br> 5.3.3 <a href="#N66616">Problem IRI</a><br> 5.3.4 <a href="#N66652">Problem Action</a><br> 5.3.5 <a href="#N6712">Retry After</a><br> 5.4 <a href="#soapfaults">Predefined Faults</a><br> 5.4.1 <a href="#invalidmapfault"> Invalid Addressing Header</a><br> 5.4.1.1 <a href="#N66785">wsa:InvalidAddress</a><br> 5.4.1.2 <a href="#N66794">wsa:InvalidEPR</a><br> 5.4.1.3 <a href="#N66803">wsa:InvalidCardinality</a><br> 5.4.1.4 <a href="#N66812">wsa:MissingAddressInEPR</a><br> 5.4.1.5 <a href="#N66821">wsa:DuplicateMessageID</a><br> 5.4.1.6 <a href="#N66830">wsa:ActionMismatch</a><br> 5.4.2 < href="#missingmapfault"> Message Addressing Header Required</a><br> 5.4.3 <a href="#destinationfault"> Destination Unreachable</a><br> 5.4.4 <a href="#actionfault"> Action Not Supported</a><br> 5.4.5 <a href="#unavailablefault"> Endpoint Unavailable</a><br>6. <a href="#securityconsiderations">Security Considerations</a><br> 6.1 <a href="#N66966">Establishing EPR Trust</a><br> 6.2 <a href="#N66984">Additional Security Considerations</a><br> 6.3 <a href="#N67002">Additional Considerations for SOAP Intermediaries</a><br>7. <a href="#conformance">Conformance</a><br>8. <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="#N67414">Changes Since Candidate Recommendation</a><br> B.2 <a href="#N67424">Changes Since Last Call Working Draft</a><br> B.3 <a href="#N67434">Changes Since Second Working Draft</a><br> B.4 <a href="#N67444">Changes Since First Working Draft</a><br> B.5 <a href="#N67454">Changes Since Submission</a><br></p></div><hr><div class="body"> <div class="div1"> *************** *** 80,84 **** sent from http://example.com/business/client1 to http://example.com/fabrikam/Purchasing:</p> <div class="exampleOuter"> ! <p class="exampleHead" style="text-align: left"><i><span>Example 1-1. </span>Use of message addressing properties in a SOAP 1.2 message.</i></p> <div class="exampleInner"><pre> (01) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" --- 80,84 ---- sent from http://example.com/business/client1 to http://example.com/fabrikam/Purchasing:</p> <div class="exampleOuter"> ! <p style="text-align: left" class="exampleHead"><i><span>Example 1-1. </span>Use of message addressing properties in a SOAP 1.2 message.</i></p> <div class="exampleInner"><pre> (01) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" *************** *** 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,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 *************** *** 361,365 **** message addressed to the endpoint:</p> <div class="exampleOuter"> ! <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Example endpoint reference.</i></p> <div class="exampleInner"><pre> <wsa:EndpointReference --- 361,365 ---- message addressed to the endpoint:</p> <div class="exampleOuter"> ! <p style="text-align: left" class="exampleHead"><i><span>Example 3-1. </span>Example endpoint reference.</i></p> <div class="exampleInner"><pre> <wsa:EndpointReference *************** *** 384,388 **** addressed to this endpoint. The resulting SOAP message would look as follows:</p> <div class="exampleOuter"> ! <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Example endpoint reference mapped to SOAP message header blocks.</i></p> <div class="exampleInner"><pre> <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" --- 384,388 ---- addressed to this endpoint. The resulting SOAP message would look as follows:</p> <div class="exampleOuter"> ! <p style="text-align: left" class="exampleHead"><i><span>Example 3-2. </span>Example endpoint reference mapped to SOAP message header blocks.</i></p> <div class="exampleInner"><pre> <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" *************** *** 412,416 **** binding[<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>] puts the reply message in the HTTP response.</p> </div> - </div> <div class="div1"> --- 412,415 ---- *************** *** 443,452 **** <dt class="label">SOAP Action</dt> <dd> ! <p>Use of the SOAPAction HTTP header is required when using the SOAP 1.1 HTTP binding. ! The value of the SOAPAction HTTP header MUST either be the value of the wsa:Action ! header enclosed in quotation marks, or the empty value "". The latter case supports ! the ability to obscure the wsa:Action header through SOAP-level security mechanisms, ! without requiring otherwise unnecessary transport-level security. Any other value ! for SOAPAction results in an Invalid Message Addressing Property fault (see <a href="#invalidmapfault"><b>5.4.1 Invalid Addressing Header</b></a>).</p> </dd> --- 442,452 ---- <dt class="label">SOAP Action</dt> <dd> ! <p>Use of the SOAPAction HTTP request header field is required when using the SOAP 1.1 ! HTTP binding. The field-value of the SOAPAction HTTP request header MUST either be ! the value of the [action] property enclosed in quotation marks, or the empty value ! "". The latter case supports the ability to obscure the [action] property through ! SOAP-level security mechanisms, without requiring otherwise unnecessary ! transport-level security. Any other value for SOAPAction results in an Invalid ! Message Addressing Property fault (see <a href="#invalidmapfault"><b>5.4.1 Invalid Addressing Header</b></a>).</p> </dd> *************** *** 457,462 **** <h2><a name="faults"></a>5. Faults</h2> ! <p>The faults defined in this section are generated if the condition stated in the ! preamble in each subsection is met.</p> <p>Endpoints compliant with this specification MUST include the required message addressing properties serialized as SOAP headers in generated fault messages. Fault messages are --- 457,462 ---- <h2><a name="faults"></a>5. Faults</h2> ! <p>The faults defined in this section are generated if the condition stated in the preamble in ! each subsection is met.</p> <p>Endpoints compliant with this specification MUST include the required message addressing properties serialized as SOAP headers in generated fault messages. Fault messages are *************** *** 471,483 **** http://www.w3.org/@@@@/@@/addressing/fault </pre></div> ! <p>SOAP modules and extensions MAY define custom [action] values for the faults they ! describe or MAY designate use of the following [action] value instead:</p> <div class="exampleInner"><pre> http://www.w3.org/@@@@/@@/addressing/soap/fault </pre></div> ! <p>The above [action] value SHOULD be used for generic SOAP faults including ! version mismatch, must understand, and data encoding unknown.</p> ! <p>Each of the predefined faults listed below is defined by specifying values ! for the following abstract properties:</p> <p> [Code] The fault code, use of the specified fault code is REQUIRED.</p> <p> [Subcode] The fault subcode, use of the specified fault subcode is REQUIRED.</p> --- 471,483 ---- http://www.w3.org/@@@@/@@/addressing/fault </pre></div> ! <p>SOAP modules and extensions MAY define custom [action] values for the faults they describe ! or MAY designate use of the following [action] value instead:</p> <div class="exampleInner"><pre> http://www.w3.org/@@@@/@@/addressing/soap/fault </pre></div> ! <p>The above [action] value SHOULD be used for generic SOAP faults including version mismatch, ! must understand, and data encoding unknown.</p> ! <p>Each of the predefined faults listed below is defined by specifying values for the ! following abstract properties:</p> <p> [Code] The fault code, use of the specified fault code is REQUIRED.</p> <p> [Subcode] The fault subcode, use of the specified fault subcode is REQUIRED.</p> *************** *** 486,494 **** <p> [Reason] The English language reason element, use of the specified fault code is RECOMMENDED but alternate text MAY be used.</p> ! <p> [Details] The detail elements, use of the specified detail elements is REQUIRED. If absent, ! no detail elements are defined for the fault.</p> <div class="div2"> ! <h3><a name="N10334"></a>5.1 SOAP 1.2 Fault Binding</h3> <p>The fault properties bind to a SOAP 1.2 fault as follows:</p> <dl> --- 486,494 ---- <p> [Reason] The English language reason element, use of the specified fault code is RECOMMENDED but alternate text MAY be used.</p> ! <p> [Details] The detail elements, use of the specified detail elements is REQUIRED. If ! absent, no detail elements are defined for the fault.</p> <div class="div2"> ! <h3><a name="N66356"></a>5.1 SOAP 1.2 Fault Binding</h3> <p>The fault properties bind to a SOAP 1.2 fault as follows:</p> <dl> *************** *** 530,534 **** </dl> <div class="exampleOuter"> ! <p class="exampleHead" style="text-align: left"><i><span>Example 5-1. </span>Binding of fault properties to SOAP 1.2 messages.</i></p> <div class="exampleInner"><pre> <S:Envelope> --- 530,534 ---- </dl> <div class="exampleOuter"> ! <p style="text-align: left" class="exampleHead"><i><span>Example 5-1. </span>Binding of fault properties to SOAP 1.2 messages.</i></p> <div class="exampleInner"><pre> <S:Envelope> *************** *** 562,575 **** <div class="div2"> ! <h3><a name="N10386"></a>5.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 follows:</p> <dl> <dt class="label">[Subcode] or [Subsubcode]</dt> <dd> ! <p>The value of the [Subsubcode] or, if that is not specified, the value of the [Subcode] ! property is bound as the value of the SOAP faults ! S11:Fault/faultcode element.</p> </dd> --- 562,576 ---- <div class="div2"> ! <h3><a name="N66438"></a>5.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 ! follows:</p> <dl> <dt class="label">[Subcode] or [Subsubcode]</dt> <dd> ! <p>The value of the [Subsubcode] or, if that is not specified, the value of the ! [Subcode] property is bound as the value of the SOAP faults S11:Fault/faultcode ! element.</p> </dd> *************** *** 586,591 **** <p>The SOAP 1.1 fault detail is only for use with faults related to the body of a message and is therefore not used for SOAP 1.1 faults related to processing of ! addressing headers. Instead the value of the [Details] property is bound as the value ! of a new wsa:FaultDetail SOAP header block. The following describes the wsa:FaultDetail element:</p> <dl> --- 587,592 ---- <p>The SOAP 1.1 fault detail is only for use with faults related to the body of a message and is therefore not used for SOAP 1.1 faults related to processing of ! addressing headers. Instead the value of the [Details] property is bound as the ! value of a new wsa:FaultDetail SOAP header block. The following describes the wsa:FaultDetail element:</p> <dl> *************** *** 607,611 **** </dl> <div class="exampleOuter"> ! <p class="exampleHead" style="text-align: left"><i><span>Example 5-2. </span>Binding of fault properties to SOAP 1.1 messages.</i></p> <div class="exampleInner"><pre> <S11:Envelope> --- 608,612 ---- </dl> <div class="exampleOuter"> ! <p style="text-align: left" class="exampleHead"><i><span>Example 5-2. </span>Binding of fault properties to SOAP 1.1 messages.</i></p> <div class="exampleInner"><pre> <S11:Envelope> *************** *** 625,640 **** </div> </div> - <div class="div2"> <h3><a name="faultdetailelements"></a>5.3 Fault Detail Elements</h3> <p>The following subsections define a set of elements used to convey additional information ! in the faults described in <a href="#soapfaults"><b>5.4 Predefined Faults</b></a>.</p> ! <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right"> </td></tr><tr><td valign="top" align="left" colspan="2">Additional detail elements may be defined if feedback during CR indicates that this would be useful.</td></tr></table> - <div class="div3"> ! <h4><a name="N103F0"></a>5.3.1 Problem Header</h4> <p> The following describes the <wsa:ProblemHeader> element:</p> <dl> --- 626,639 ---- </div> </div> <div class="div2"> <h3><a name="faultdetailelements"></a>5.3 Fault Detail Elements</h3> <p>The following subsections define a set of elements used to convey additional information ! in the faults described in <a href="#soapfaults"><b>5.4 Predefined Faults</b></a>.</p> ! <table border="1" summary="Editorial note"><tr><td align="left" valign="top" width="50%"><b>Editorial note</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">Additional detail elements may be defined if feedback during CR indicates that this would be useful.</td></tr></table> <div class="div3"> ! <h4><a name="N66544"></a>5.3.1 Problem Header</h4> <p> The following describes the <wsa:ProblemHeader> element:</p> <dl> *************** *** 643,647 **** <dd> <p>The root element of the invalid header block, all descendants of the root element ! are also included.</p> </dd> --- 642,646 ---- <dd> <p>The root element of the invalid header block, all descendants of the root element ! are also included.</p> </dd> *************** *** 656,660 **** <div class="div3"> ! <h4><a name="N10414"></a>5.3.2 Problem Header QName</h4> <p> The following describes the <wsa:ProblemHeaderQName> element:</p> <dl> --- 655,659 ---- <div class="div3"> ! <h4><a name="N66580"></a>5.3.2 Problem Header QName</h4> <p> The following describes the <wsa:ProblemHeaderQName> element:</p> <dl> *************** *** 662,666 **** <dt class="label">/wsa:ProblemHeaderQName</dt> <dd> ! <p>A QName representing the name of the root element of the problem header block.</p> </dd> --- 661,666 ---- <dt class="label">/wsa:ProblemHeaderQName</dt> <dd> ! <p>A QName representing the name of the root element of the problem header ! block.</p> </dd> *************** *** 675,679 **** <div class="div3"> ! <h4><a name="N10438"></a>5.3.3 Problem IRI</h4> <p> The following describes the <wsa:ProblemIRI> element:</p> <dl> --- 675,679 ---- <div class="div3"> ! <h4><a name="N66616"></a>5.3.3 Problem IRI</h4> <p> The following describes the <wsa:ProblemIRI> element:</p> <dl> *************** *** 694,698 **** <div class="div3"> ! <h4><a name="N1045C"></a>5.3.4 Problem Action</h4> <p> The following describes the <wsa:ProblemAction> element:</p> <dl> --- 694,698 ---- <div class="div3"> ! <h4><a name="N66652"></a>5.3.4 Problem Action</h4> <p> The following describes the <wsa:ProblemAction> element:</p> <dl> *************** *** 725,729 **** <div class="div3"> ! <h4><a name="N10498"></a>5.3.5 Retry After</h4> <p> The following describes the <wsa:RetryAfter> element:</p> <dl> --- 725,729 ---- <div class="div3"> ! <h4><a name="N66712"></a>5.3.5 Retry After</h4> <p> The following describes the <wsa:RetryAfter> element:</p> <dl> *************** *** 732,737 **** <dd> <p>This element (whose content is of type xs:unsignedLong) is a suggested minimum ! duration in milliseconds to wait before retransmitting the message. Omission of this ! element indicates that a retry is never likely to succeed.</p> </dd> --- 732,737 ---- <dd> <p>This element (whose content is of type xs:unsignedLong) is a suggested minimum ! duration in milliseconds to wait before retransmitting the message. Omission of ! this element indicates that a retry is never likely to succeed.</p> </dd> *************** *** 744,756 **** </dl> </div> - </div> - <div class="div2"> <h3><a name="soapfaults"></a>5.4 Predefined Faults</h3> ! <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right"> </td></tr><tr><td valign="top" align="left" colspan="2">Additional faults may be defined if feedback during CR indicates that ! this would be useful.</td></tr></table> ! <div class="div3"> --- 744,753 ---- </dl> </div> </div> <div class="div2"> <h3><a name="soapfaults"></a>5.4 Predefined Faults</h3> ! <table border="1" summary="Editorial note"><tr><td align="left" valign="top" width="50%"><b>Editorial note</b></td><td align="right" valign="top" width="50%"> </td></tr><tr><td colspan="2" align="left" valign="top">Additional faults may be defined if feedback during CR indicates that this would ! be useful.</td></tr></table> <div class="div3"> *************** *** 764,792 **** <p> [Reason] the string: "A header representing a Message Addressing Property is not valid and the message cannot be processed" </p> ! <p> [Details] either a <wsa:ProblemHeader> element that conveys a copy of the ! offending header or a ! <wsa:ProblemHeaderQName> element that conveys the QName of the root element of the ! offending header.</p> ! <p>The invalid addressing header fault can be further narrowed in scope by use of the additional [Subsubcode]s specified in the following subsections. Use of these [Subsubcode] values is OPTIONAL.</p> <div class="div4"> ! <h5><a name="N104E1"></a>5.4.1.1 wsa:InvalidAddress</h5> <p>Specifies that an [address] was invalid.</p> </div> <div class="div4"> ! <h5><a name="N104EA"></a>5.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="N104F3"></a>5.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="N104FC"></a>5.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> --- 761,788 ---- <p> [Reason] the string: "A header representing a Message Addressing Property is not valid and the message cannot be processed" </p> ! <p> [Details] either a <wsa:ProblemHeader> element that conveys a copy of ! the offending header or a <wsa:ProblemHeaderQName> element that conveys ! the QName of the root element of the offending header.</p> ! <p>The invalid addressing header fault can be further narrowed in scope by use of the additional [Subsubcode]s specified in the following subsections. Use of these [Subsubcode] values is OPTIONAL.</p> <div class="div4"> ! <h5><a name="N66785"></a>5.4.1.1 wsa:InvalidAddress</h5> <p>Specifies that an [address] was invalid.</p> </div> <div class="div4"> ! <h5><a name="N66794"></a>5.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="N66803"></a>5.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="N66812"></a>5.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> *************** *** 794,810 **** <div class="div4"> ! <h5><a name="N10505"></a>5.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> </div> <div class="div4"> ! <h5><a name="N1050E"></a>5.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 <wsa:ProblemHeader> element or ! <wsa:ProblemHeaderQName> element.</p> </div> - </div> <div class="div3"> --- 790,805 ---- <div class="div4"> ! <h5><a name="N66821"></a>5.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> </div> <div class="div4"> ! <h5><a name="N66830"></a>5.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 ! <wsa:ProblemHeader> element or <wsa:ProblemHeaderQName> ! element.</p> </div> </div> <div class="div3"> *************** *** 816,821 **** <p> [Reason] the string: "A required header representing a Message Addressing Property is not present"</p> ! <p> [Details] a <wsa:ProblemHeaderQName> element that conveys the QName of the ! message addressing header that was missing.</p> </div> <div class="div3"> --- 811,816 ---- <p> [Reason] the string: "A required header representing a Message Addressing Property is not present"</p> ! <p> [Details] a <wsa:ProblemHeaderQName> element that conveys the QName of ! the message addressing header that was missing.</p> </div> <div class="div3"> *************** *** 826,831 **** <p> [Subcode] a QName representing the value wsa:DestinationUnreachable</p> <p> [Reason] the string: "No route can be determined to reach [destination]"</p> ! <p> [Details] an optional <wsa:ProblemIRI> element that conveys the [address] of the ! [destination].</p> </div> <div class="div3"> --- 821,826 ---- <p> [Subcode] a QName representing the value wsa:DestinationUnreachable</p> <p> [Reason] the string: "No route can be determined to reach [destination]"</p> ! <p> [Details] an optional <wsa:ProblemIRI> element that conveys the ! [address] of the [destination].</p> </div> <div class="div3"> *************** *** 836,841 **** <p> [Subcode] a QName representing the value wsa:ActionNotSupported</p> <p> [Reason] the string: "The [action] cannot be processed at the receiver"</p> ! <p> [Details] a <wsa:ProblemAction> element with a REQUIRED <wsa:Action> child ! element</p> </div> <div class="div3"> --- 831,836 ---- <p> [Subcode] a QName representing the value wsa:ActionNotSupported</p> <p> [Reason] the string: "The [action] cannot be processed at the receiver"</p> ! <p> [Details] a <wsa:ProblemAction> element with a REQUIRED ! <wsa:Action> child element</p> </div> <div class="div3"> *************** *** 849,959 **** <p> [Subcode] a QName representing the value wsa:EndpointUnavailable</p> <p> [Reason] the string "The endpoint is unable to process the message at this time"</p> ! <p> [Details] an optional <wsa:RetryAfter> element and an optional <wsa:ProblemIRI> element that conveys the [address] of the ! [destination].</p> </div> </div> - </div> <div class="div1"> <h2><a name="securityconsiderations"></a>6. Security Considerations</h2> ! ! <div class="note"><p class="prefix"><b>Note:</b></p><p>No assumptions are made herein of the application level security ! requirement, the organization of the application, implementation of senders ! or receivers, or of the ways that other protocols may make use of ! WS-Addressing, and what security mechanisms they may employ. A holistic ! approach to security which considers all components of the application, ! other protocols utilized, the way that these protocols compose with ! WS-Security, and the use of other methods or additional techniques is highly ! recommended.</p></div> ! ! <p>As discussed in Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>], ! WS-Addressing supports capabilities that allow a message sender to ! instruct a message receiver to send additional unsolicited messages to ! other receivers of their choice and to control the contents of those ! messages to an extent using reference parameters. The SOAP binding of ! WS-Addressing transforms EPR reference parameters into SOAP headers and ! this allows a message sender to request a message receiver to send ! additional unsolicited SOAP messages to other receivers of their choice ! and to specify a set of SOAP headers that must be included in such ! messages.</p> ! ! <p>SOAP headers are a powerful extension mechanism and therefore great care ! should be taken before honoring a [reply endpoint] or [fault endpoint] ! to avoid inadvertent participation in the activities of malicious SOAP ! message senders.</p> ! ! <p>WS-Addressing message addressing properties serialized as SOAP headers ! (wsa:To, wsa:Action et al.) including those headers present as a result ! of the [reference parameters] property should be integrity protected as ! explained in Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>].</p> ! ! <p>Messages that use wsa:ReplyTo or wsa:FaultTo headers whose [address] is ! not the predefined anonymous URI should include claims that allow a ! receiver to confirm that the EPR was issued by a principle with ! authority to represent the [address] of the EPR.</p> ! ! <p>When receiving a SOAP message, certain SOAP headers may have resulted ! from the serialization of an EPR's [reference parameters] property. A ! SOAP message receiver should perform additional security and sanity ! checks to prevent unintended actions.</p> ! <div class="div2"> ! <h3><a name="N10594"></a>6.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 mechanisms require the inclusion of a ! WS-Security[<cite><a href="#WS-Security">WS-Security</a></cite>] header that contains XML digital signatures ! binding the wsa:ReplyTo and wsa:FaultTo elements to the SOAP message ! using a security token issued by an authority trusted by the receiver of ! the message for the domain of the [address] of the EPR. Possession of a ! security token issued by a trusted authority for the domain of the ! [address] of the EPR provides a level of confidence that the message ! sender has authority to represent the [address].</p> ! <p>For example, a message could include a WS-Security[<cite><a href="#WS-Security">WS-Security</a></cite>] header ! that contains XML digital signatures binding the wsa:ReplyTo and ! wsa:FaultTo elements to the SOAP message using an X.509 certificate for ! the domain addressed by the [address] of the EPR. If the certificate is ! issued by a certificate authority trusted by the receiver of the message ! then the receiver can can have some level of confidence that the message sender has authority to represent the [address] of the EPR.</p> - </div> - <div class="div2"> ! <h3><a name="N105A6"></a>6.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 attack.</p> ! ! <p>Message processors should consider elements from the soap11, soap12 and ! wsa namespaces 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="N105B8"></a>6.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 remove XML content that explicitly ! indicates otherwise-implied content, and intermediaries MUST NOT insert ! XML content to make implied values explicit. For instance, if a ! RelationshipType attribute is present with a value of ! "http://www.w3.org/@@@@/@@/addressing/reply", an intermediary MUST NOT ! remove it; similarly, if there is no RelationshipType attribute, an ! intermediary MUST NOT add one.</p> </div> - </div> <div class="div1"> --- 844,924 ---- <p> [Subcode] a QName representing the value wsa:EndpointUnavailable</p> <p> [Reason] the string "The endpoint is unable to process the message at this time"</p> ! <p> [Details] an optional <wsa:RetryAfter> element and an optional ! <wsa:ProblemIRI> element that conveys the [address] of the ! [destination].</p> </div> </div> </div> <div class="div1"> <h2><a name="securityconsiderations"></a>6. Security Considerations</h2> ! <div class="note"><p class="prefix"><b>Note:</b></p> ! <p>No assumptions are made herein of the application level security requirement, the ! organization of the application, implementation of senders or receivers, or of the ways ! that other protocols may make use of WS-Addressing, and what security mechanisms they may ! employ. A holistic approach to security which considers all components of the application, ! other protocols utilized, the way that these protocols compose with WS-Security, and the ! use of other methods or additional techniques is highly recommended.</p> ! </div> ! <p>As discussed in Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>], WS-Addressing supports ! capabilities that allow a message sender to instruct a message receiver to send additional ! unsolicited messages to other receivers of their choice and to control the contents of those ! messages to an extent using reference parameters. The SOAP binding of WS-Addressing ! transforms EPR reference parameters into SOAP headers and this allows a message sender to ! request a message receiver to send additional unsolicited SOAP messages to other receivers ! of their choice and to specify a set of SOAP headers that must be included in such messages.</p> ! <p>SOAP headers are a powerful extension mechanism and therefore great care should be taken ! before honoring a [reply endpoint] or [fault endpoint] to avoid inadvertent participation in ! the activities of malicious SOAP message senders.</p> ! <p>WS-Addressing message addressing properties serialized as SOAP headers (wsa:To, wsa:Action ! et al.) including those headers present as a result of the [reference parameters] property ! should be integrity protected as explained in Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>].</p> ! <p>Messages that use wsa:ReplyTo or wsa:FaultTo headers whose [address] is not the predefined ! anonymous URI should include claims that allow a receiver to confirm that the EPR was issued ! by a principle with authority to represent the [address] of the EPR.</p> ! <p>When receiving a SOAP message, certain SOAP headers may have resulted from the ! serialization of an EPR's [reference parameters] property. A SOAP message receiver should ! perform additional security and sanity checks to prevent unintended actions.</p> <div class="div2"> ! <h3><a name="N66966"></a>6.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 ! mechanisms require the inclusion of a WS-Security[<cite><a href="#WS-Security">WS-Security</a></cite>] header that ! contains XML digital signatures binding the wsa:ReplyTo and wsa:FaultTo elements to the ! SOAP message using a security token issued by an authority trusted by the receiver of the ! message for the domain of the [address] of the EPR. Possession of a security token issued ! by a trusted authority for the domain of the [address] of the EPR provides a level of ! confidence that the message sender has authority to represent the [address].</p> <p>For example, a message could include a WS-Security[<cite><a href="#WS-Security">WS-Security</a></cite>] header ! that contains XML digital signatures binding the wsa:ReplyTo and wsa:FaultTo elements to ! the SOAP message using an X.509 certificate for the domain addressed by the [address] of ! the EPR. If the certificate is issued by a certificate authority trusted by the receiver ! of the message then the receiver can can have some level of confidence that the message sender has authority to represent the [address] of the EPR.</p> </div> <div class="div2"> ! <h3><a name="N66984"></a>6.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 attack.</p> ! <p>Message processors should consider elements from the soap11, soap12 and wsa namespaces ! 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="N67002"></a>6.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 ! remove XML content that explicitly indicates otherwise-implied content, and intermediaries ! MUST NOT insert XML content to make implied values explicit. For instance, if a ! RelationshipType attribute is present with a value of "http://www.w3.org/@@@@/@@/addressing/reply", ! an intermediary MUST NOT remove it; similarly, if there is no RelationshipType attribute, ! an intermediary MUST NOT add one.</p> </div> </div> <div class="div1"> *************** *** 979,985 **** <p>Endpoints MAY accept and respond to messages which contain no WSA headers.</p> </div> ! <p>If a receiver processes a message containing a wsa:Action header, ! this SOAP binding is engaged, and the rules of this specification are in force.</p> ! </div> <div class="div1"> --- 944,950 ---- <p>Endpoints MAY accept and respond to messages which contain no WSA headers.</p> </div> ! <p>If a receiver processes a message containing a wsa:Action header, this SOAP binding is ! engaged, and the rules of this specification are in force.</p> ! </div> <div class="div1"> *************** *** 990,1000 **** <dt class="label"><a name="WSADDR-WSDL"></a>[WS-Addressing-WSDL] </dt><dd> <cite><a href="ws-addr-wsdl.html">Web Services Addressing 1.0 - WSDL Binding</a></cite>, M. Gudgin, M. Hadley, Editors.</dd> ! <dt class="label"><a name="WSDL20"></a>[WSDL 2.0] </dt><dd> ! <cite><a href="ws-addr-wsdl.html">Web Services Description Language (WSDL) ! Version 2.0 Part 1: Core Language</a></cite>, ! R. Chinnici, J. J. Moreau, A. Ryman, S. Weerawarana, Editors. World Wide Web ! Consortium, 3 August 2005. This version of the WSDL 2.0 specification is ! http://www.w3.org/TR/2005/WD-wsdl20-20050803. The <a href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</a> is ! available at http://www.w3.org/TR/wsdl20.</dd> <dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd> <cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a></cite>, S. Bradner, --- 955,963 ---- <dt class="label"><a name="WSADDR-WSDL"></a>[WS-Addressing-WSDL] </dt><dd> <cite><a href="ws-addr-wsdl.html">Web Services Addressing 1.0 - WSDL Binding</a></cite>, M. Gudgin, M. Hadley, Editors.</dd> ! <dt class="label"><a name="WSDL20"></a>[WSDL 2.0] </dt><dd> ! <cite><a href="ws-addr-wsdl.html">Web Services Description Language (WSDL) Version 2.0 Part 1: Core ! Language</a></cite>, R. Chinnici, J. J. Moreau, A. Ryman, S. Weerawarana, Editors. World ! Wide Web Consortium, 3 August 2005. This version of the WSDL 2.0 specification is ! http://www.w3.org/TR/2005/WD-wsdl20-20050803. The <a href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</a> is available at http://www.w3.org/TR/wsdl20.</dd> <dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd> <cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a></cite>, S. Bradner, *************** *** 1070,1094 **** <div class="div2"> ! <h3><a name="N10754"></a>B.1 Changes Since Candidate Recommendation</h3> ! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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><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</d><td>Added resolution to issue cr1 - changed ActionMismatch to ProblemAction</td></tr></table> </div> <div class="div2"> ! <h3><a name="N1075E"></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="N10768"></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="N10772"></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="N1077C"></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> --- 1033,1057 ---- <div class="div2"> ! <h3><a name="N67414"></a>B.1 Changes Since Candidate Recommendation</h3> ! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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><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 polcy</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="N67424"></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="N67434"></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="N67444"></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="N67454"></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 Tuesday, 22 November 2005 21:34:15 UTC