- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 13 Feb 2006 17:01:54 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv24071
Modified Files:
ws-addr-core.html ws-addr-soap.html ws-addr-wsdl.html
Log Message:
Updated to sync with XML
Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.33
retrieving revision 1.34
diff -C2 -d -r1.33 -r1.34
*** ws-addr-wsdl.html 9 Feb 2006 11:42:51 -0000 1.33
--- ws-addr-wsdl.html 13 Feb 2006 17:01:51 -0000 1.34
***************
*** 1,15 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
! "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
! <html lang="en-US" xmlns="http://www.w3.org/1999/xhtml" xml:lang=
! "en-US">
! <head>
! <meta name="generator" content=
! "HTML Tidy for Linux/x86 (vers 1 September 2005), see www.w3.org" />
! <meta http-equiv="Content-Type" content=
! "text/html; charset=utf-8" />
! <title>Web Services Addressing 1.0 - WSDL Binding</title>
[...3683 lines suppressed...]
! <div class="div2">
!
! <h3><a name="N68806"></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="N68816"></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="N68826"></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>
! </div>
! </div>
! </div>
! </body></html>
\ No newline at end of file
Index: ws-addr-core.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -C2 -d -r1.40 -r1.41
*** ws-addr-core.html 9 Feb 2006 11:42:51 -0000 1.40
--- ws-addr-core.html 13 Feb 2006 17:01:51 -0000 1.41
***************
*** 1,15 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
! "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
! <html lang="en-US" xmlns="http://www.w3.org/1999/xhtml" xml:lang=
! "en-US">
! <head>
! <meta name="generator" content=
! "HTML Tidy for Linux/x86 (vers 1 September 2005), see www.w3.org" />
! <meta http-equiv="Content-Type" content=
! "text/html; charset=utf-8" />
! <title>Web Services Addressing 1.0 - Core</title>
[...2869 lines suppressed...]
! Added the note from David Hull at
! http://lists.w3.org/Archives/Public/public-ws-addressing/2005Mar/0254.html
! per teleconference March 28, 2005</td></tr><tr><td>2005-03-21 @ 22:36</td><td>mgudgin</td><td>Incorporated resolution of issue 50 into Section 3.2</td></tr><tr><td>2005-03-21 @ 22:06</td><td>mgudgin</td><td>Updated with resolution to issue 54</td></tr><tr><td>2005-03-21 @ 20:47</td><td>mgudgin</td><td>Removed parenthetical statement '(and opaquely)' from description of [action] property in Section 3 per resolution on 2005-03-21 telcon</td></tr><tr><td>2005-03-21 @ 16:39</td><td>mgudgin</td><td>s/that value/that the value in description of [action] property in Section 3</td></tr><tr><td>2005-03-21 @ 16:37</td><td>mgudgin</td><td>Split paragraph 2 in Section 3 into two seperate paragraphs</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-02 @ 21:18</td><td>mhadley</td><td>Added rsolution to issue 4</td></tr><tr><td>2005-03-02 @ 20:30</td><td>mhadley</td><td>Added 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-03-02 @ 14:07</td><td>mhadley</td><td>Added issue 52 resolution.</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 @ 21:42</td><td>mhadley</td><td>Added issue 48 resolution</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 @ 14:34</td><td>mgudgin</td><td>
! Added new section 2.5: Endpoint Reference Extensibility per resolution of issue i042</td></tr><tr><td>2005-02-17 @ 16:16</td><td>mhadley</td><td>Added resolution to issue 44</td></tr><tr><td>2005-02-15 @ 22:53</td><td>mhadley</td><td>Added resolution to issue 46</td></tr></table>
! </div>
! <div class="div2">
!
! <h3><a name="N67429"></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="N67439"></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>
! </div>
! </div>
! </div>
! </body></html>
\ No newline at end of file
Index: ws-addr-soap.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.html,v
retrieving revision 1.44
retrieving revision 1.45
diff -C2 -d -r1.44 -r1.45
*** ws-addr-soap.html 22 Nov 2005 21:33:42 -0000 1.44
--- ws-addr-soap.html 13 Feb 2006 17:01:51 -0000 1.45
***************
*** 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">
--- 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="#soaphdrvtransport">Relationship between SOAP Headers and transport-level properties</a><br>4. <a href="#s11ext">SOAP 1.1 Addressing 1.0 Extension</a><br> 4.1 <a href="#s11extname">Extension Name</a><br> 4.2 <a href="#s11extdesc">Description</a><br>5. <a href="#addressesinsoap">Addresses in SOAP</a><br> 5.1 <a href="#anonaddress">Use of Anonymous Address in SOAP</a><br> 5.1.1 <a href="#N66312">SOAP 1.1/HTTP</a><br> 5.1.2 <a href="#N66321">SOAP 1.2</a><br> 5.2 <a href="#nonanonaddress">Use of Non-Anonymous Addresses in SOAP</a><br> 5.2.1 <a href="#N66343">SOAP 1.1/HTTP</a><br> 5.2.2 <a href="#N66352">SOAP 1.2</a><br>6. <a href="#faults">Faults</a><br> 6.1 <a href=#N66416">SOAP 1.2 Fault Binding</a><br> 6.2 <a href="#N66498">SOAP 1.1 Fault Binding</a><br> 6.3 <a href="#faultdetailelements">Fault Detail Elements</a><br> 6.3.1 <a href="#N66604">Problem Header</a><br> 6.3.2 <a href="#N66640">Problem Header QName</a><br> 6.3.3 <a href="#N66676">Problem IRI</a><br> 6.3.4 <a href="#N66712">Problem Action</a><br> 6.3.5 <a href="#N66772">Retry After</a><br> 6.4 <a href="#soapfaults">Predefined Faults</a><br> 6.4.1 <a href="#invalidmapfault"> Invalid Addressing Header</a><br> 6.4.1.1 <a href="#N66845">wsa:InvalidAddress</a><br>   6.4.1.2 <a href="#N66854">wsa:InvalidEPR</a><br> 6.4.1.3 <a href="#N66863">wsa:InvalidCardinality</a><br> 6.4.1.4 <a href="#N66872">wsa:MissingAddressInEPR</a><br> 6.4.1.5 <a href="#N66881">wsa:DuplicateMessageID</a><br> 6.4.1.6 <a href="#N66890">wsa:ActionMismatch</a><br> 6.4.1.7 <a href="#N66899">wsa:OnlyAnonymousAddressSupported</a><br> 6.4.1.8 <a href="#N66908">wsa:OnlyNonAnonymousAddressSupported</a><br> 6.4.2 <a href="#missingmapfault"> Message Addressing Header Required</a><br> nbsp; 6.4.3 <a href="#destinationfault"> Destination Unreachable</a><br> 6.4.4 <a href="#actionfault"> Action Not Supported</a><br> 6.4.5 <a href="#unavailablefault"> Endpoint Unavailable</a><br>7. <a href="#securityconsiderations">Security Considerations</a><br> 7.1 <a href="#N67044">Establishing EPR Trust</a><br> 7.2 <a href="#N67062">Additional Security Considerations</a><br> 7.3 <a href="#N67080">Additional Considerations for SOAP Intermediaries</a><br>8. <a href="#conformance">Conformance</a><br>9. <a href="#references"> References</a><br></p>
! <h3><a name="appendix" id="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#changelog">Change Log</a> (Non-Normative)<br> B.1 <a href="#N67492">Changes Since Candidate Recommendation</a><br> B.2 <a href="#N67502">Changes Since Last Call Working Draft</a><br> B.3 <a href="#N67512">Changes Since Second Working Draft</a><br> B.4 <a href="#N67522">Changes Since First Working Draft</a><br> B.5 <a href="#N67532">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
***************
*** 83,87 ****
<div class="exampleInner"><pre>
(01) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
! xmlns:wsa="http://www.w3.org/@@@@/@@/addressing">
(02) <S:Header>
(03) <wsa:MessageID>http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA</wsa:MessageID>
--- 83,87 ----
<div class="exampleInner"><pre>
(01) <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
! xmlns:wsa="http://www.w3.org/2005/08/addressing">
(02) <S:Header>
(03) <wsa:MessageID>http://example.com/6B29FC40-CA47-1067-B31D-00DD010662DA</wsa:MessageID>
***************
*** 144,148 ****
<tr>
<td rowspan="1" colspan="1">wsa</td>
! <td rowspan="1" colspan="1"> http://www.w3.org/@@@@/@@/addressing </td>
</tr>
<tr>
--- 144,148 ----
<tr>
<td rowspan="1" colspan="1">wsa</td>
! <td rowspan="1" colspan="1"> http://www.w3.org/2005/08/addressing </td>
</tr>
<tr>
***************
*** 166,170 ****
not a requirement.</p>
<p>All information items defined by this specification are identified by the XML namespace
! URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>] <a href="http://www.w3.org/@@@@/@@/addressing">http://www.w3.org/@@@@/@@/addressing</a>. A
normative XML Schema [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document
can be obtained by dereferencing the XML namespace URI.</p>
--- 166,170 ----
not a requirement.</p>
<p>All information items defined by this specification are identified by the XML namespace
! URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>] <a href="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing</a>. A
normative XML Schema [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document
can be obtained by dereferencing the XML namespace URI.</p>
***************
*** 181,185 ****
<ul>
<li>
! <p>http://www.w3.org/@@@@/@@/addressing/feature</p>
</li>
</ul>
--- 181,185 ----
<ul>
<li>
! <p>http://www.w3.org/2005/08/addressing/feature</p>
</li>
</ul>
***************
*** 200,204 ****
<dl>
! <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/Destination</dt>
<dd>
<p>Corresponds to the abstract [destination] property.</p>
--- 200,204 ----
<dl>
! <dt class="label">http://www.w3.org/2005/08/addressing/feature/Destination</dt>
<dd>
<p>Corresponds to the abstract [destination] property.</p>
***************
*** 206,210 ****
! <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/SourceEndpoint</dt>
<dd>
<p>Corresponds to the abstract [source endpoint] property.</p>
--- 206,210 ----
! <dt class="label">http://www.w3.org/2005/08/addressing/feature/SourceEndpoint</dt>
<dd>
<p>Corresponds to the abstract [source endpoint] property.</p>
***************
*** 212,216 ****
! <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/ReplyEndpoint</dt>
<dd>
<p>Corresponds to the abstract [reply endpoint] property.</p>
--- 212,216 ----
! <dt class="label">http://www.w3.org/2005/08/addressing/feature/ReplyEndpoint</dt>
<dd>
<p>Corresponds to the abstract [reply endpoint] property.</p>
***************
*** 218,222 ****
! <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/FaultEndpoint</dt>
<dd>
<p>Corresponds to the abstract [fault endpoint] property.</p>
--- 218,222 ----
! <dt class="label">http://www.w3.org/2005/08/addressing/feature/FaultEndpoint</dt>
<dd>
<p>Corresponds to the abstract [fault endpoint] property.</p>
***************
*** 224,228 ****
! <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/Action</dt>
<dd>
<p>Corresponds to the abstract [action] property.</p>
--- 224,228 ----
! <dt class="label">http://www.w3.org/2005/08/addressing/feature/Action</dt>
<dd>
<p>Corresponds to the abstract [action] property.</p>
***************
*** 230,234 ****
! <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/MessageID</dt>
<dd>
<p>Corresponds to the abstract [message id] property.</p>
--- 230,234 ----
! <dt class="label">http://www.w3.org/2005/08/addressing/feature/MessageID</dt>
<dd>
<p>Corresponds to the abstract [message id] property.</p>
***************
*** 236,240 ****
! <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/Relationship</dt>
<dd>
<p>Corresponds to the abstract [relationship] property.</p>
--- 236,240 ----
! <dt class="label">http://www.w3.org/2005/08/addressing/feature/Relationship</dt>
<dd>
<p>Corresponds to the abstract [relationship] property.</p>
***************
*** 242,246 ****
! <dt class="label">http://www.w3.org/@@@@/@@/addressing/feature/ReferenceParameters</dt>
<dd>
<p>Corresponds to the abstract [reference parameters] property.</p>
--- 242,246 ----
! <dt class="label">http://www.w3.org/2005/08/addressing/feature/ReferenceParameters</dt>
<dd>
<p>Corresponds to the abstract [reference parameters] property.</p>
***************
*** 254,260 ****
<p>If the http://www.w3.org/2003/05/soap/features/action/Action property of the SOAP Action
feature[<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>] has a value, then the value of the
! http://www.w3.org/@@@@/@@/addressing/feature/Action property of the SOAP 1.2 Addressing 1.0 feature MUST be
identical to it. Failure to have an identical value results in an Invalid Addressing
! Header fault (see <a href="#invalidmapfault"><b>5.4.1 Invalid Addressing Header</b></a>).</p>
</div>
</div>
--- 254,260 ----
<p>If the http://www.w3.org/2003/05/soap/features/action/Action property of the SOAP Action
feature[<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>] has a value, then the value of the
! http://www.w3.org/2005/08/addressing/feature/Action property of the SOAP 1.2 Addressing 1.0 feature MUST be
identical to it. Failure to have an identical value results in an Invalid Addressing
! Header fault (see <a href="#invalidmapfault"><b>6.4.1 Invalid Addressing Header</b></a>).</p>
</div>
</div>
***************
*** 270,274 ****
<ul>
<li>
! <p>http://www.w3.org/@@@@/@@/addressing/module</p>
</li>
</ul>
--- 270,274 ----
<ul>
<li>
! <p>http://www.w3.org/2005/08/addressing/module</p>
</li>
</ul>
***************
*** 291,295 ****
element information items in the message. A message MUST NOT contain more than one wsa:To,
wsa:ReplyTo, wsa:FaultTo, wsa:Action, or wsa:MessageID header targeted at a recipient. A
! recipient MUST generate a wsa:InvalidAddressingHeader (see <a href="#invalidmapfault"><b>5.4.1 Invalid Addressing Header</b></a>) fault if such a message is received.</p>
<div class="note"><p class="prefix"><b>Note:</b></p>
<p>The SOAP processing model dictates that message addressing properties targeted at an
--- 291,295 ----
element information items in the message. A message MUST NOT contain more than one wsa:To,
wsa:ReplyTo, wsa:FaultTo, wsa:Action, or wsa:MessageID header targeted at a recipient. A
! recipient MUST generate a wsa:InvalidAddressingHeader (see <a href="#invalidmapfault"><b>6.4.1 Invalid Addressing Header</b></a>) fault if such a message is received.</p>
<div class="note"><p class="prefix"><b>Note:</b></p>
<p>The SOAP processing model dictates that message addressing properties targeted at an
***************
*** 364,371 ****
<div class="exampleInner"><pre>
<wsa:EndpointReference
! xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"
xmlns:wsaw="http://www.w3.org/2005/03/addressing/wsdl"
xmlns:fabrikam="http://example.com/fabrikam"
! xmlns:wsdli="http://www.w3.org/2005/08/wsdl-instance"
wsdli:wsdlLocation="http://example.com/fabrikam
http://example.com/fabrikam/fabrikam.wsdl">
--- 364,371 ----
<div class="exampleInner"><pre>
<wsa:EndpointReference
! xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:wsaw="http://www.w3.org/2005/03/addressing/wsdl"
xmlns:fabrikam="http://example.com/fabrikam"
! xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
wsdli:wsdlLocation="http://example.com/fabrikam
http://example.com/fabrikam/fabrikam.wsdl">
***************
*** 387,391 ****
<div class="exampleInner"><pre>
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
! xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"
xmlns:fabrikam="http://example.com/fabrikam">
<S:Header>
--- 387,391 ----
<div class="exampleInner"><pre>
<S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
! xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:fabrikam="http://example.com/fabrikam">
<S:Header>
***************
*** 405,414 ****
<div class="div2">
! <h3><a name="soaphttp"></a>3.5 Use of Anonymous Address in SOAP</h3>
! <p>When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified as the address of an EPR, the
! underlying SOAP protocol binding provides a channel to the specified endpoint. Any
! underlying protocol binding supporting the SOAP request-response message exchange pattern
! provides such a channel for response messages. For instance, the SOAP 1.2 HTTP
! 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>
--- 405,415 ----
<div class="div2">
! <h3><a name="soaphdrvtransport"></a>3.5 Relationship between SOAP Headers and transport-level properties</h3>
! <p>Some underlying protocols may support native properties similar to the Message Addressing
! Properties. For example, the reply-to: email header is similar to the [reply endpoint]
! Message Addressing Property. Authors and implementors of bindings should not assume any
! particular correspondence between native properties and Message Addressing Properties. For
! example, if an email message represents only one hop in a multi-hop path, then the
! reply-to: header is likely to differ from the [reply endpoint] address.</p>
</div>
</div>
***************
*** 425,429 ****
<ul>
<li>
! <p>http://www.w3.org/@@@@/@@/addressing/module</p>
</li>
</ul>
--- 426,430 ----
<ul>
<li>
! <p>http://www.w3.org/2005/08/addressing/module</p>
</li>
</ul>
***************
*** 448,452 ****
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>
--- 449,453 ----
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>6.4.1 Invalid Addressing Header</b></a>).</p>
</dd>
***************
*** 456,460 ****
<div class="div1">
! <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>
--- 457,506 ----
<div class="div1">
! <h2><a name="addressesinsoap"></a>5. Addresses in SOAP</h2>
! <div class="div2">
!
! <h3><a name="anonaddress"></a>5.1 Use of Anonymous Address in SOAP</h3>
! <div class="div3">
!
! <h4><a name="N66312"></a>5.1.1 SOAP 1.1/HTTP</h4>
! <p>When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified for the response
! endpoint then there is no change to the SOAP 1.1/ HTTP binding. </p>
! </div>
! <div class="div3">
!
! <h4><a name="N66321"></a>5.1.2 SOAP 1.2</h4>
! <p>When "http://www.w3.org/@@@@/@@/addressing/anonymous" is specified for the response
! endpoint and the request is the request part of a SOAP request-response MEP [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>], then any response MUST be the response part of the same SOAP
! request-response MEP [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>].</p>
! </div>
! </div>
! <div class="div2">
!
! <h3><a name="nonanonaddress"></a>5.2 Use of Non-Anonymous Addresses in SOAP</h3>
! <div class="div3">
!
! <h4><a name="N66343"></a>5.2.1 SOAP 1.1/HTTP</h4>
! <p>When "http://www.w3.org/@@@@/@@/addressing/anonymous" is not specified for the response
! endpoint, then the request SHOULD be part of a binding that supports not returning a
! SOAP envelope in the HTTP response. Any response message SHOULD be sent using a separate
! connection and using the address value specified by response endpoint. Note that other
! specifications MAY define special URIs that have other behaviours (similar to the
! anonymous URI).</p>
! </div>
! <div class="div3">
!
! <h4><a name="N66352"></a>5.2.2 SOAP 1.2</h4>
! <p>When "http://www.w3.org/@@@@/@@/addressing/anonymous" is not specified for the response
! endpoint, then any response SHOULD not be the response part of the same SOAP
! request-response MEP [<cite><a href="#SOAP12-PART2">SOAP 1.2 Part 2: Adjuncts</a></cite>]. For instance, a SOAP 1.2 HTTP
! binding that supports a one-way MEP could put the reply message in a separate one-way
! MEP and a separate HTTP request. As in SOAP 1.1/HTTP, note that other specifications MAY
! define special URIs that have other behaviours (similar to the anonymous URI).</p>
! </div>
! </div>
! </div>
! <div class="div1">
!
! <h2><a name="faults"></a>6. Faults</h2>
<p>The faults defined in this section are generated if the condition stated in the preamble in
each subsection is met.</p>
***************
*** 469,478 ****
<p>The [action] property below designates WS-Addressing fault messages:</p>
<div class="exampleInner"><pre>
! 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,
--- 515,524 ----
<p>The [action] property below designates WS-Addressing fault messages:</p>
<div class="exampleInner"><pre>
! http://www.w3.org/2005/08/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/2005/08/addressing/soap/fault
</pre></div>
<p>The above [action] value SHOULD be used for generic SOAP faults including version mismatch,
***************
*** 490,494 ****
<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>
--- 536,540 ----
<div class="div2">
! <h3><a name="N66416"></a>6.1 SOAP 1.2 Fault Binding</h3>
<p>The fault properties bind to a SOAP 1.2 fault as follows:</p>
<dl>
***************
*** 530,538 ****
</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>
<S:Header>
! <wsa:Action>http://www.w3.org/@@@@/@@/addressing/fault</wsa:Action>
<!-- Headers elided for brevity. -->
</S:Header>
--- 576,584 ----
</dl>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 6-1. </span>Binding of fault properties to SOAP 1.2 messages.</i></p>
<div class="exampleInner"><pre>
<S:Envelope>
<S:Header>
! <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
<!-- Headers elided for brevity. -->
</S:Header>
***************
*** 562,566 ****
<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
--- 608,612 ----
<div class="div2">
! <h3><a name="N66498"></a>6.2 SOAP 1.1 Fault Binding</h3>
<p>The SOAP 1.1 fault is slightly less expressive than the SOAP 1.2 fault and maps only
[Subcode], [Reason] and [Detail]. These the properties bind to a SOAP 1.1 fault as
***************
*** 594,598 ****
<dt class="label">/wsa:FaultDetail</dt>
<dd>
! <p>Zero or more of the elements defined in <a href="#faultdetailelements"><b>5.3 Fault Detail Elements</b></a>.</p>
</dd>
--- 640,644 ----
<dt class="label">/wsa:FaultDetail</dt>
<dd>
! <p>Zero or more of the elements defined in <a href="#faultdetailelements"><b>6.3 Fault Detail Elements</b></a>.</p>
</dd>
***************
*** 608,616 ****
</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>
<S11:Header>
! <wsa:Action>http://www.w3.org/@@@@/@@/addressing/fault</wsa:Action>
<wsa:FaultDetail>[Details]</wsa:FaultDetail>
<!-- Other headers elided for brevity. -->
--- 654,662 ----
</dl>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 6-2. </span>Binding of fault properties to SOAP 1.1 messages.</i></p>
<div class="exampleInner"><pre>
<S11:Envelope>
<S11:Header>
! <wsa:Action>http://www.w3.org/2005/08/addressing/fault</wsa:Action>
<wsa:FaultDetail>[Details]</wsa:FaultDetail>
<!-- Other headers elided for brevity. -->
***************
*** 628,639 ****
<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>
--- 674,685 ----
<div class="div2">
! <h3><a name="faultdetailelements"></a>6.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>6.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="N66604"></a>6.3.1 Problem Header</h4>
<p> The following describes the <wsa:ProblemHeader> 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>
--- 701,705 ----
<div class="div3">
! <h4><a name="N66640"></a>6.3.2 Problem Header QName</h4>
<p> The following describes the <wsa:ProblemHeaderQName> 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>
--- 721,725 ----
<div class="div3">
! <h4><a name="N66676"></a>6.3.3 Problem IRI</h4>
<p> The following describes the <wsa:ProblemIRI> 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>
--- 740,744 ----
<div class="div3">
! <h4><a name="N66712"></a>6.3.4 Problem Action</h4>
<p> The following describes the <wsa:ProblemAction> 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>
--- 771,775 ----
<div class="div3">
! <h4><a name="N66772"></a>6.3.5 Retry After</h4>
<p> The following describes the <wsa:RetryAfter> element:</p>
<dl>
***************
*** 747,756 ****
<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">
! <h4><a name="invalidmapfault"></a>5.4.1 Invalid Addressing Header</h4>
<p>A header representing a WS-Addressing 1.0 Message Addressing Property is invalid and
cannot be processed. The validity failure can be either structural or semantic, e.g. a
--- 793,802 ----
<div class="div2">
! <h3><a name="soapfaults"></a>6.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">
! <h4><a name="invalidmapfault"></a>6.4.1 Invalid Addressing Header</h4>
<p>A header representing a WS-Addressing 1.0 Message Addressing Property is invalid and
cannot be processed. The validity failure can be either structural or semantic, e.g. a
***************
*** 769,788 ****
<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>
--- 815,834 ----
<div class="div4">
! <h5><a name="N66845"></a>6.4.1.1 wsa:InvalidAddress</h5>
<p>Specifies that an [address] was invalid.</p>
</div>
<div class="div4">
! <h5><a name="N66854"></a>6.4.1.2 wsa:InvalidEPR</h5>
<p>Specifies that the invalid header was expected to be an EPR but was not valid.</p>
</div>
<div class="div4">
! <h5><a name="N66863"></a>6.4.1.3 wsa:InvalidCardinality</h5>
<p>Specifies that there was a greater than expected number of the specified header.</p>
</div>
<div class="div4">
! <h5><a name="N66872"></a>6.4.1.4 wsa:MissingAddressInEPR</h5>
<p>Specifies that the invalid header was expected to be an EPR but did not contain an
[address].</p>
***************
*** 790,794 ****
<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>
--- 836,840 ----
<div class="div4">
! <h5><a name="N66881"></a>6.4.1.5 wsa:DuplicateMessageID</h5>
<p>Specifies that the invalid header conveyed a [message id] that was a duplicate of one
already received.</p>
***************
*** 796,800 ****
<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
--- 842,846 ----
<div class="div4">
! <h5><a name="N66890"></a>6.4.1.6 wsa:ActionMismatch</h5>
<p>Specifies that the [action] and SOAPAction for the message did not match, [Details]
MAY contain a <wsa:ProblemAction> element in addition to the
***************
*** 802,809 ****
element.</p>
</div>
</div>
<div class="div3">
! <h4><a name="missingmapfault"></a>5.4.2 Message Addressing Header Required</h4>
<p>A required header representing a Message Addressing Property is absent.</p>
<p> [Code] a QName representing the value S:Sender</p>
--- 848,866 ----
element.</p>
</div>
+ <div class="div4">
+
+ <h5><a name="N66899"></a>6.4.1.7 wsa:OnlyAnonymousAddressSupported</h5>
+ <p>Specifies that the only address supported is the anonymous address.</p>
+ </div>
+ <div class="div4">
+
+ <h5><a name="N66908"></a>6.4.1.8 wsa:OnlyNonAnonymousAddressSupported</h5>
+ <p>Specifies that the anonymous address is not supported, and that only a non-anonymous
+ address will be accepted.</p>
+ </div>
</div>
<div class="div3">
! <h4><a name="missingmapfault"></a>6.4.2 Message Addressing Header Required</h4>
<p>A required header representing a Message Addressing Property is absent.</p>
<p> [Code] a QName representing the value S:Sender</p>
***************
*** 816,820 ****
<div class="div3">
! <h4><a name="destinationfault"></a>5.4.3 Destination Unreachable</h4>
<p>The endpoint identified by the value of [destination] property cannot be reached.</p>
<p> [Code] a QName representing the value S:Sender</p>
--- 873,877 ----
<div class="div3">
! <h4><a name="destinationfault"></a>6.4.3 Destination Unreachable</h4>
<p>The endpoint identified by the value of [destination] property cannot be reached.</p>
<p> [Code] a QName representing the value S:Sender</p>
***************
*** 826,830 ****
<div class="div3">
! <h4><a name="actionfault"></a>5.4.4 Action Not Supported</h4>
<p>The [action] property in the message is not supported at this endpoint.</p>
<p> [Code] a QName representing the value S:Sender</p>
--- 883,887 ----
<div class="div3">
! <h4><a name="actionfault"></a>6.4.4 Action Not Supported</h4>
<p>The [action] property in the message is not supported at this endpoint.</p>
<p> [Code] a QName representing the value S:Sender</p>
***************
*** 836,840 ****
<div class="div3">
! <h4><a name="unavailablefault"></a>5.4.5 Endpoint Unavailable</h4>
<p>The endpoint is unable to process the message at this time either due to some transient
issue or a permanent failure. </p>
--- 893,897 ----
<div class="div3">
! <h4><a name="unavailablefault"></a>6.4.5 Endpoint Unavailable</h4>
<p>The endpoint is unable to process the message at this time either due to some transient
issue or a permanent failure. </p>
***************
*** 852,856 ****
<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
--- 909,913 ----
<div class="div1">
! <h2><a name="securityconsiderations"></a>7. 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
***************
*** 882,886 ****
<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
--- 939,943 ----
<div class="div2">
! <h3><a name="N67044"></a>7.1 Establishing EPR Trust</h3>
<p>There are many mechanisms that could be used to supply proof that a message sender has
authority to represent the [address] of EPRs supplied within the message. Typically such
***************
*** 900,904 ****
<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
--- 957,961 ----
<div class="div2">
! <h3><a name="N67062"></a>7.2 Additional Security Considerations</h3>
<p>The wsa:isReferenceParameter attribute is only meaningful on SOAP headers. Message
processors should consider its appearance elsewhere in a SOAP message as a possible
***************
*** 912,921 ****
<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>
--- 969,978 ----
<div class="div2">
! <h3><a name="N67080"></a>7.3 Additional Considerations for SOAP Intermediaries</h3>
<p>To avoid breaking signatures, intermediaries MUST NOT change the XML representation of
WS-Addressing headers when relaying those headers. Specifically, intermediaries MUST NOT
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/2005/08/addressing/reply",
an intermediary MUST NOT remove it; similarly, if there is no RelationshipType attribute,
an intermediary MUST NOT add one.</p>
***************
*** 924,928 ****
<div class="div1">
! <h2><a name="conformance"></a>7. Conformance</h2>
<p>A SOAP 1.2 message conforms to the SOAP 1.2 Addressing 1.0 Module when it contains headers
from the wsa namespace, and follows all the constraints on message addressing properties
--- 981,985 ----
<div class="div1">
! <h2><a name="conformance"></a>8. Conformance</h2>
<p>A SOAP 1.2 message conforms to the SOAP 1.2 Addressing 1.0 Module when it contains headers
from the wsa namespace, and follows all the constraints on message addressing properties
***************
*** 949,953 ****
<div class="div1">
! <h2><a name="references"></a>8. References</h2>
<dl>
<dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
--- 1006,1010 ----
<div class="div1">
! <h2><a name="references"></a>9. References</h2>
<dl>
<dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
***************
*** 1021,1027 ****
<p>Members of the Working Group are (at the time of writing, and by
alphabetical order):
! Abbie Barbir (Nortel Networks), Rebecca Bergersen (IONA Technologies, Inc.), Andreas Bjärlestam (ERICSSON), Dave Chappell (Sonic Software), Ugo Corda (SeeBeyond Technology Corporation), Francisco Curbera (IBM Corporation), Glen Daniels (Sonic Software), Vikas Deolaliker (Sonoa Systems, Inc.), Paul Downey (BT), Jacques Durand (Fujitsu Limited), Michael Eder (Nokia), Robert Freund (Hitachi, Ltd.), Yaron Goland (BEA Systems, Inc.), Marc Goodner (Microsoft Corporation), Martin Gudgin (Microsoft Corporation), Arun Gupta (Sun Microsystems, Inc.), Hugo Haas (W3C/ERCIM), Marc Hadley (Sun Microsystems, Inc.), David Hull (TIBCO Software, Inc.), Yin-Leng Husband (HP), Anish Karmarkar (Oracle Corporation), Paul Knight (Nortel Networks), Philippe Le Hégaret (W3C/MIT), Amelia Lewis (TIBCO Software, Inc.), Mark Little (Arjuna Technologies Ltd.), Jonathan Marsh (Microsoft Corporation), Jeff Mischkinsky (Oracle Corporation), Nilo Mitra (ERICSSON), Eisaku Nishiyama (Hitachi, Ltd.), Mark Nottingham (BEA Sytems, Inc.), Ales Novy (Systinet Inc.), David Orchard (BEA Systems, Inc.), Mark Peel (Novell, Inc.), Tony Rogers (Computer Associates), Tom Rutt (Fujitsu Limited), Rich Salz (DataPower Technology, Inc.), Davanum Srinivas (Computer Associates), Jiri Tejkl (Systinet Inc.), Steve Vinoski (IONA Technologies, Inc.), Katy Warr (IBM Corporation), Pete Wenzel (SeeBeyond Technology Corporation), Steve Winkler (SAP AG), Ümit Yalçinalp (SAP AG), Prasad Yendluri (webMethods, Inc.).</p>
<p>Previous members of the Working Group were:
! Lisa Bahler (SAIC - Telcordia Technologies), Marc Goodner (SAP AG), Harris Reynolds (webMethods, Inc.), Greg Truty (IBM Corporation).</p>
<p>The people who have contributed to <a href="http://lists.w3.org/Archives/Public/public-ws-addressing/">discussions
on public-ws-addressing@w3.org</a> are also gratefully
--- 1078,1084 ----
<p>Members of the Working Group are (at the time of writing, and by
alphabetical order):
! Abbie Barbir, Andreas Bjärlestam, Dave Chappell, Eran Chinthaka, Francisco Curbera, Glen Daniels, Vikas Deolaliker, Paul Downey, Jacques Durand, Robert Freund, Marc Goodner, Arun Gupta, Hugo Haas, Marc Hadley, David Hull, Yin-Leng Husband, David Illsley, Anish Karmarkar, Paul Knight, Philippe Le Hégaret, Amelia Lewis, Bozhong Lin, Mark Little, Jonathan Marsh, Jeff Mischkinsky, Nilo Mitra, Eisaku Nishiyama, Ales Novy, David Orchard, Gilbert Pilz, Tony Rogers, Tom Rutt, Davanum Srinivas, Jiri Tejkl, Mike Vernal, Steve Vinoski, Katy Warr, Pete Wenzel, Steve Winkler, Ümit Yalçinalp, Prasad Yendluri.</p>
<p>Previous members of the Working Group were:
! Lisa Bahler, Rebecca Bergersen, Ugo Corda, Michael Eder, Yaron Goland, Marc Goodner, Martin Gudgin, Mark Nottingham, Mark Peel, Harris Reynolds, Rich Salz, Davanum Srinivas, Greg Truty.</p>
<p>The people who have contributed to <a href="http://lists.w3.org/Archives/Public/public-ws-addressing/">discussions
on public-ws-addressing@w3.org</a> are also gratefully
***************
*** 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>
--- 1090,1114 ----
<div class="div2">
! <h3><a name="N67492"></a>B.1 Changes Since Candidate Recommendation</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-02-08 @ 07:05</td><td>trogers</td><td>Changed Change Log limit from 20060101 to 20061201</td></tr><tr><td>2006-02-08 @ 06:48</td><td>trogers</td><td>Added the resolution of CR15/i067/i068 - discussion of anonymous/non-anonymous in SOAP 1.1/SOAP 1.2.</td></tr><tr><td>2006-02-08 @ 06:23</td><td>trogers</td><td>Added the resolution of CR14 - stating independence of SOAP headers and transport properties</td></tr><tr><td>2006-02-08 @ 06:13</td><td>trogers</td><td>Added the resolution of CR13 - adding the OnlyAnonymousSupported and OnlyNonAnonymousSupported subsubcodes</td></tr><tr><td>2005-11-22 @ 20:41</td><td>mhadley</td><td>Added issue cr11 resolution, minor editorial teaks to SOAPAction to [action] relationship text</td></tr><tr><td>2005-11-08 @ 05:21</td><td>trogers</td><td>Implemented the resolution of CR7, stating when WSA is engaged.</td></tr><tr><td>2005-11-07 @ 07:18</td><td>mhadley</td><td>Added resolutio to issue cr9, added URI for use with generic SOAP faults</td></tr><tr><td>2005-11-06 @ 12:48</td><td>trogers</td><td>Incorporated the resolution of CR8 by rephrasing the requirements on the SOAPAction HTTP header for SOAP 1.1.</td></tr><tr><td>2005-11-06 @ 12:30</td><td>trogers</td><td>Incorporated the resolution of CR4 by extending the definition of the anonymous URI.</td></tr><tr><td>2005-10-24 @ 05:02</td><td>trogers</td><td>Removed ProblemIRI from InvalidAddress explanation, resolving Issue CR6</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-09-15 @ 19:42</td><td>mhadley</td><td>Added new section for post CR changes</td></tr><tr><td>2005-09-15 @ 18:27</td><td>mhadley</td><td>Added resolution to issue cr1 - changed ActionMismatch to ProblemAction</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N67502"></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="N67512"></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="N67522"></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="N67532"></a>B.5 Changes Since Submission</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-11-24 @ 15:32</td><td>mhadley</td><td>Added note that addressing is backwards compatible with SOAP 1.1</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 22:25</td><td>mhadley</td><td>Removed static change log and added dynamically generated change log from cvs.</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
</div>
Received on Monday, 13 February 2006 17:02:15 UTC