2004/ws/addressing ws-addr-soap.html,1.42,1.43 ws-addr-core.html,1.37,1.38

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

Modified Files:
	ws-addr-soap.html ws-addr-core.html 
Log Message:
Sync HTML with the XML

Index: ws-addr-soap.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -C2 -d -r1.42 -r1.43
*** ws-addr-soap.html	24 Oct 2005 05:04:50 -0000	1.42
--- ws-addr-soap.html	8 Nov 2005 06:18:58 -0000	1.43
***************
*** 57,60 ****
--- 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>&nbsp;&copy;&nbsp;@@@@&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</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>
***************
*** 66,71 ****
          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>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notation"> Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#s12feature">SOAP 1.2 Addressing 1.0 Feature</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#s12featurename">Feature Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#s12featuredesc">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#s12featureprops">Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;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>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#s12modulename">Module Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#s12moduledesc">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#additionalinfoset">Additional Infoset Items</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.4 <a href="#bindrefp">Binding Message Addressing Properies</a><br>&nbsp;&nbsp;&nbsp;&nbsp;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>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#s11extname">Extension Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#s11extdesc">Description</a><br>5. <a href="#faults">Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#N10324">SOAP 1.2 Fault Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#N10376">SOAP 1.1 Fault Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.3 <a href="#faultdetailelements">Fault Detail Elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.1 <a href="#N103E0">Problem Header</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.2 <a href="#N10404">Problem Header QName</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.3 <a href="#N10428">Problem IRI</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.4 <a href="#N1044C">Problem Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.5 <a href="#N1488">Retry After</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.4 <a href="#soapfaults">Predefined Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1 <a href="#invalidmapfault"> Invalid Addressing Header</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.1 <a href="#N104D1">wsa:InvalidAddress</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.2 <a href="#N104DA">wsa:InvalidEPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.3 <a href="#N104E3">wsa:InvalidCardinality</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.4 <a href="#N104EC">wsa:MissingAddressInEPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.5 <a href="#N104F5">wsa:DuplicateMessageID</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.6 <a href="#N104FE">wsa:ActionMismatch</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.2 < href="#missingmapfault"> Message Addressing Header Required</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.3 <a href="#destinationfault"> Destination Unreachable</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.4 <a href="#actionfault"> Action Not Supported</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.5 <a href="#unavailablefault"> Endpoint Unavailable</a><br>6. <a href="#securityconsiderations">Security Considerations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#N10584">Establishing EPR Trust</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#N10596">Additional Security Considerations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.3 <a href="#N105A8">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>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N10741">Changes Since Candidate Recommendation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N1074B">Changes Since Last Call Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N10755">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.4 <a href="#N1075F">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.5 <a href="#N10769">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>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notation"> Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#s12feature">SOAP 1.2 Addressing 1.0 Feature</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#s12featurename">Feature Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#s12featuredesc">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#s12featureprops">Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;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>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#s12modulename">Module Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#s12moduledesc">Description</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#additionalinfoset">Additional Infoset Items</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.4 <a href="#bindrefp">Binding Message Addressing Properies</a><br>&nbsp;&nbsp;&nbsp;&nbsp;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>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#s11extname">Extension Name</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.2 <a href="#s11extdesc">Description</a><br>5. <a href="#faults">Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.1 <a href="#N10334">SOAP 1.2 Fault Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.2 <a href="#N10386">SOAP 1.1 Fault Binding</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.3 <a href="#faultdetailelements">Fault Detail Elements</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.1 <a href="#N103F0">Problem Header</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.2 <a href="#N10414">Problem Header QName</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.3 <a href="#N10438">Problem IRI</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.4 <a href="#N1045C">Problem Action</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.3.5 <a href="#N1498">Retry After</a><br>&nbsp;&nbsp;&nbsp;&nbsp;5.4 <a href="#soapfaults">Predefined Faults</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1 <a href="#invalidmapfault"> Invalid Addressing Header</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.1 <a href="#N104E1">wsa:InvalidAddress</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.2 <a href="#N104EA">wsa:InvalidEPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.3 <a href="#N104F3">wsa:InvalidCardinality</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.4 <a href="#N104FC">wsa:MissingAddressInEPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.5 <a href="#N10505">wsa:DuplicateMessageID</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.1.6 <a href="#N1050E">wsa:ActionMismatch</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.2 < href="#missingmapfault"> Message Addressing Header Required</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.3 <a href="#destinationfault"> Destination Unreachable</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.4 <a href="#actionfault"> Action Not Supported</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;5.4.5 <a href="#unavailablefault"> Endpoint Unavailable</a><br>6. <a href="#securityconsiderations">Security Considerations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.1 <a href="#N10594">Establishing EPR Trust</a><br>&nbsp;&nbsp;&nbsp;&nbsp;6.2 <a href="#N105A6">Additional Security Considerations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;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>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N10754">Changes Since Candidate Recommendation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N1075E">Changes Since Last Call Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N10768">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.4 <a href="#N10772">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.5 <a href="#N1077C">Changes Since Submission</a><br></p></div><hr><div class="body">
      <div class="div1">
        
***************
*** 405,415 ****
          
  <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 the
!           ReplyTo or FaultTo 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 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>
        
--- 406,414 ----
          
  <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>
        
***************
*** 445,454 ****
              <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 identical to the value of the
!                 wsa:Action header, or be empty. The latter case supports the ability to obscure the
!                 wsa:Action header through SOAP-level security mechanisms, without requiring
!                 otherwise unnecessary transport-level security. Failure to have an identical value,
!                 or an empty 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>
            
--- 444,452 ----
              <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>
            
***************
*** 473,476 ****
--- 471,481 ----
  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>
***************
*** 485,489 ****
        <div class="div2">
          
! <h3><a name="N10324"></a>5.1 SOAP 1.2 Fault Binding</h3>
          <p>The fault properties bind to a SOAP 1.2 fault as follows:</p>
          <dl>
--- 490,494 ----
        <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>
***************
*** 557,561 ****
        <div class="div2">
          
! <h3><a name="N10376"></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>
--- 562,566 ----
        <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>
***************
*** 631,635 ****
          <div class="div3">
            
! <h4><a name="N103E0"></a>5.3.1 Problem Header</h4>
            <p> The following describes the &lt;wsa:ProblemHeader&gt; element:</p>
            <dl>
--- 636,640 ----
          <div class="div3">
            
! <h4><a name="N103F0"></a>5.3.1 Problem Header</h4>
            <p> The following describes the &lt;wsa:ProblemHeader&gt; element:</p>
            <dl>
***************
*** 651,655 ****
          <div class="div3">
            
! <h4><a name="N10404"></a>5.3.2 Problem Header QName</h4>
            <p> The following describes the &lt;wsa:ProblemHeaderQName&gt; element:</p>
            <dl>
--- 656,660 ----
          <div class="div3">
            
! <h4><a name="N10414"></a>5.3.2 Problem Header QName</h4>
            <p> The following describes the &lt;wsa:ProblemHeaderQName&gt; element:</p>
            <dl>
***************
*** 670,674 ****
          <div class="div3">
            
! <h4><a name="N10428"></a>5.3.3 Problem IRI</h4>
            <p> The following describes the &lt;wsa:ProblemIRI&gt; element:</p>
            <dl>
--- 675,679 ----
          <div class="div3">
            
! <h4><a name="N10438"></a>5.3.3 Problem IRI</h4>
            <p> The following describes the &lt;wsa:ProblemIRI&gt; element:</p>
            <dl>
***************
*** 689,693 ****
          <div class="div3">
            
! <h4><a name="N1044C"></a>5.3.4 Problem Action</h4>
            <p> The following describes the &lt;wsa:ProblemAction&gt; element:</p>
            <dl>
--- 694,698 ----
          <div class="div3">
            
! <h4><a name="N1045C"></a>5.3.4 Problem Action</h4>
            <p> The following describes the &lt;wsa:ProblemAction&gt; element:</p>
            <dl>
***************
*** 720,724 ****
          <div class="div3">
            
! <h4><a name="N10488"></a>5.3.5 Retry After</h4>
            <p> The following describes the &lt;wsa:RetryAfter&gt; element:</p>
            <dl>
--- 725,729 ----
          <div class="div3">
            
! <h4><a name="N10498"></a>5.3.5 Retry After</h4>
            <p> The following describes the &lt;wsa:RetryAfter&gt; element:</p>
            <dl>
***************
*** 768,787 ****
            <div class="div4">
              
! <h5><a name="N104D1"></a>5.4.1.1 wsa:InvalidAddress</h5>
              <p>Specifies that an [address] was invalid.</p>
            </div>
            <div class="div4">
              
! <h5><a name="N104DA"></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="N104E3"></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="N104EC"></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>
--- 773,792 ----
            <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>
***************
*** 789,793 ****
            <div class="div4">
              
! <h5><a name="N104F5"></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>
--- 794,798 ----
            <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>
***************
*** 795,799 ****
            <div class="div4">
              
! <h5><a name="N104FE"></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 &lt;wsa:ProblemAction&gt;
--- 800,804 ----
            <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 &lt;wsa:ProblemAction&gt;
***************
*** 896,900 ****
        <div class="div2">
          
! <h3><a name="N10584"></a>6.1 Establishing EPR Trust</h3>
          
          <p>There are many mechanisms that could be used to supply proof that a
--- 901,905 ----
        <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
***************
*** 921,925 ****
        <div class="div2">
          
! <h3><a name="N10596"></a>6.2 Additional Security Considerations</h3>
          
          <p>The wsa:isReferenceParameter attribute is only meaningful on SOAP
--- 926,930 ----
        <div class="div2">
          
! <h3><a name="N105A6"></a>6.2 Additional Security Considerations</h3>
          
          <p>The wsa:isReferenceParameter attribute is only meaningful on SOAP
***************
*** 938,942 ****
        <div class="div2">
          
! <h3><a name="N105A8"></a>6.3 Additional Considerations for SOAP Intermediaries</h3>
          
          <p>To avoid breaking signatures, intermediaries MUST NOT change the XML
--- 943,947 ----
        <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
***************
*** 974,978 ****
          <p>Endpoints MAY accept and respond to messages which contain no WSA headers.</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">
        
***************
*** 1063,1087 ****
        <div class="div2">
          
! <h3><a name="N10741"></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-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="N1074B"></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="N10755"></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="N1075F"></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="N10769"></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>
--- 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>

Index: ws-addr-core.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-core.html,v
retrieving revision 1.37
retrieving revision 1.38
diff -C2 -d -r1.37 -r1.38
*** ws-addr-core.html	17 Oct 2005 18:47:56 -0000	1.37
--- ws-addr-core.html	8 Nov 2005 06:18:58 -0000	1.38
***************
*** 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 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>
--- 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>
***************
*** 57,60 ****
--- 57,62 ----
              <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>&nbsp;&copy;&nbsp;@@@@&nbsp;<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>&reg;</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>
***************
*** 70,75 ****
          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>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notation">Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#namespaces">Namespaces</a><br>2. <a href="#eprs">Endpoint References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#eprinfomodel">Information Model for Endpoint References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#eprinfoset">Endpoint Reference XML Infoset Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#eprcomp">Endpoint Reference Comparison</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#eprlifecycle">Endpoint Reference Lifecycle</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.5 <a href="#eprextensibility">Endpoint Reference Extensibility</a><br>3. <a href="#msgaddrprops">Message Addressing Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#abstractmaps">Abstract Property Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#msgaddrpropsinfoset">XML Infoset Representation of MessageAddressing Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#compiri">Comparing IRIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#formreplymsg">Formulating a Reply Message</a><br>4. <a href="#securityconsiderations">Security Considerations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;4.1 <a href="#N66963">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>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N67324">Changes Since Candidate Recommendation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N67334">Changes Since Last Call Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N67344">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.4 <a href="#N67354">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.5 <a href="#N67364">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>&nbsp;&nbsp;&nbsp;&nbsp;1.1 <a href="#notation">Notational Conventions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;1.2 <a href="#namespaces">Namespaces</a><br>2. <a href="#eprs">Endpoint References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.1 <a href="#eprinfomodel">Information Model for Endpoint References</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.2 <a href="#eprinfoset">Endpoint Reference XML Infoset Representation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.3 <a href="#eprcomp">Endpoint Reference Comparison</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.4 <a href="#eprlifecycle">Endpoint Reference Lifecycle</a><br>&nbsp;&nbsp;&nbsp;&nbsp;2.5 <a href="#eprextensibility">Endpoint Reference Extensibility</a><br>3. <a href="#msgaddrprops">Message Addressing Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.1 <a href="#abstractmaps">Abstract Property Definitions</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.2 <a href="#msgaddrpropsinfoset">XML Infoset Representation of MessageAddressing Properties</a><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3.2.1 <a href="#compiri">Comparing IRIs</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.3 <a href="#sendmsgepr">Sending a Message to an EPR</a><br>&nbsp;&nbsp;&nbsp;&nbsp;3.4 <a href="#formreplymsg">Formulating a Reply Message</a><br>4. <a href="#securityconsiderations">Security Considerations</a><br>&nbsp;&nbsp;&nbsp;&nbsp;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>&nbsp;&nbsp;&nbsp;&nbsp;B.1 <a href="#N1071E">Changes Since Candidate Recommendation</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.2 <a href="#N10728">Changes Since Last Call Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.3 <a href="#N10732">Changes Since Second Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.4 <a href="#N1073C">Changes Since First Working Draft</a><br>&nbsp;&nbsp;&nbsp;&nbsp;B.5 <a href="#N10746">Changes Since Submission</a><br></p></div><hr><div class="body">
          <div class="div1">
              
***************
*** 93,97 ****
                  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) &lt;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 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) &lt;S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"      
***************
*** 280,284 ****
                                  Reference parameters are provided by the issuer of the endpoint
                                  reference and are assumed to be opaque to other users of an endpoint
!                                 refernce. The binding of reference parameters to messages depends
                                  upon the protocol binding used to interact with the endpoint -
                                      Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] describes the
--- 282,286 ----
                                  Reference parameters are provided by the issuer of the endpoint
                                  reference and are assumed to be opaque to other users of an endpoint
!                                 reference. The binding of reference parameters to messages depends
                                  upon the protocol binding used to interact with the endpoint -
                                      Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] describes the
***************
*** 419,423 ****
                      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>
  &lt;wsa:EndpointReference xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"&gt;
--- 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>
  &lt;wsa:EndpointReference xmlns:wsa="http://www.w3.org/@@@@/@@/addressing"&gt;
***************
*** 512,516 ****
                          <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%">&nbsp;</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>
--- 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">&nbsp;</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>
***************
*** 632,636 ****
                              <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%">&nbsp;</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>
--- 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">&nbsp;</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>
***************
*** 711,715 ****
              <div class="div2">
                  
! <h3><a name="formreplymsg"></a>3.3 Formulating a Reply Message</h3>
                  <p>This section specifies the WS-Addressing-specific rules for creating a reply or
                      fault message related to another message.</p>
--- 713,742 ----
              <div class="div2">
                  
! <h3><a name="sendmsgepr"></a>3.3 Sending a Message to an EPR</h3>
!                 <p>This section describes the process of constructing a message in accordance to an EPR.</p>
!                 <ol>
!                     <li>
!                         <p>If the EPR's [address] property is
!                             "http://www.w3.org/@@@@/@@/addressing/none" the message is discarded, if not
!                             then populate the message's message addressing properties:</p>
!                         <ul>
!                             <li>
!                                 <p>[action]: this property is required, but is not populated from the EPR.</p>
!                             </li>
!                             <li>
!                                 <p>[destination]: this property takes the value of the 
!                                     EPR's [address] property.</p>
!                             </li>
!                              <li>
!                                 <p>[reference parameters]: this property takes the value of the
!                                     selected EPR's [reference parameters] property</p>
!                             </li>
!                         </ul>
!                     </li>
!                 </ol>
!             </div>
!             <div class="div2">
!                 
! <h3><a name="formreplymsg"></a>3.4 Formulating a Reply Message</h3>
                  <p>This section specifies the WS-Addressing-specific rules for creating a reply or
                      fault message related to another message.</p>
***************
*** 745,757 ****
                      </li>
                      <li>
!                         <p>If the selected EPR's [address] property is
!                             "http://www.w3.org/@@@@/@@/addressing/none" the reply message is discarded, if not
!                             then populate the reply message's message addressing properties:</p>
                          <ul>
                              <li>
-                                 <p>[destination]: this property takes the value of the selected
-                                     EPR's [address] property.</p>
-                             </li>
-                             <li>
                                  <p>[relationship]: this property MUST include a pair of IRIs as
                                      follows; the relationship type is the predefined reply URI
--- 772,778 ----
                      </li>
                      <li>
!                         <p>Send the message according to the previous section, but also including:</p>
                          <ul>
                              <li>
                                  <p>[relationship]: this property MUST include a pair of IRIs as
                                      follows; the relationship type is the predefined reply URI
***************
*** 761,775 ****
                                      property</p>
                              </li>
-                             <li>
-                                 <p>[reference parameters]: this property takes the value of the
-                                     selected EPR's [reference parameters] property</p>
-                             </li>
                          </ul>
                      </li>
                  </ol>
                  <p>The following example illustrates a message containing message addressing
                      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>
  &lt;S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
--- 782,793 ----
                                      property</p>
                              </li>
                          </ul>
                      </li>
+                     
                  </ol>
                  <p>The following example illustrates a message containing message addressing
                      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>
  &lt;S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope"
***************
*** 813,817 ****
                  <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>
  &lt;S: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>
  &lt;S:Envelope
***************
*** 893,897 ****
              <div class="div2">
                  
! <h3><a name="N66963"></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="N105B5"></a>4.1 Additional Security Considerations</h3>
                  
                  <p>To prevent information disclosure, EPR issuers should not put sensitive information
***************
*** 1000,1014 ****
              <div class="div2">
                  
! <h3><a name="N67324"></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-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="N67334"></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="N67344"></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="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
***************
*** 1019,1028 ****
              <div class="div2">
                  
! <h3><a name="N67354"></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="N67364"></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="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>

Received on Tuesday, 8 November 2005 06:19:16 UTC