WWW/2002/ws/ra/edcopies wsenum.html,1.32,1.33 wsenum.xml,1.23,1.24 wseventing.html,1.42,1.43 wseventing.xml,1.33,1.34 wsmex.html,1.34,1.35 wsmex.xml,1.24,1.25 wsrt.html,1.30,1.31 wsrt.xml,1.19,1.20 wst.html,1.31,1.32 wst.xml,1.27,1.28

Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv8568

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
	wsmex.html wsmex.xml wsrt.html wsrt.xml wst.html wst.xml 
Log Message:
Issue 6739 - Compliance section mismatch

Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- wst.xml	21 Apr 2009 00:40:40 -0000	1.27
+++ wst.xml	22 Apr 2009 13:04:34 -0000	1.28
@@ -413,33 +413,43 @@
 
       <div2 id="compliance">
         <head>Compliance</head>
-        <p>An implementation is not compliant with this specification if it fails to
-     satisfy one or more of the MUST or REQUIRED level requirements defined
-     herein. A SOAP Node MUST NOT use the XML namespace identifier for this
-     specification (listed in <specref ref="xmlnamespaces"/>) within
-     SOAP envelopes unless it is compliant with this specification.</p>
-        <p>Specifically, a compliant SOAP Node that implements a resource MUST
-     provide the Get operation as defined in this specification, and MAY provide
-     the Put and Delete operations.</p>
-        <p>Normative text within this specification takes precedence over normative
-     outlines, which in turn takes precedence over the XML Schema and WSDL
-     descriptions.</p>
-     <p>
-     In any given
-     request-response message exchange, the responses generated by the service
-     server MUST use the same WS-Addressing namespace binding that was used in the
-     request.</p>
+        
+        <p>
+          An implementation is not compliant with this specification if it fails to
+          satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+          A SOAP Node MUST NOT use the XML namespace identifier for this specification
+          (listed in <specref ref="namespaces"/>) within SOAP Envelopes unless it is compliant
+          with this specification. 
+        </p>
+        
+        <p>
+          Normative text within this specification takes precedence over the XML Schema
+          and WSDL descriptions, which in turn take precedence over outlines, which in
+          turn take precedence over examples. 
+        </p>
+        
+        <p>
+          All messages defined by this specification MUST be sent to a Web service that
+          is addressable by an EPR [WS-Addressing]. 
+        </p>
+        
+        <p>
+          Specifically, a compliant SOAP Node that implements a resource MUST
+           provide the Get operation as defined in this specification, and MAY provide
+           the Put and Delete operations.
+        </p>
+
+         <p>
+          In any given
+          request-response message exchange, the responses generated by the service
+          server MUST use the same WS-Addressing namespace binding that was used in the
+          request.
+         </p>
       </div2>
     </div1>
     <div1 id="resourceOperations">
       <head>Resource Operations</head>
 
-      <p>
-       All messages defined by this specification MUST be sent
-       to a Web service that is addressable by an EPR
-       <bibref ref="AddrCore"/>.
-      </p>
-
       <div2 id="Get">
         <head>Get</head>
         <p>This specification defines one Web service operation (Get) for fetching a
@@ -1592,6 +1602,13 @@
          <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6730">6730</loc>
         </td>
        </tr>
+        <tr>
+          <td> 2009/04/22 </td>
+          <td> KW </td>
+          <td> Added resolution of issue 
+            <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</loc>
+          </td>
+        </tr>
       </tbody>
      </table>
     </div1>

Index: wsrt.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -r1.19 -r1.20
--- wsrt.xml	5 Apr 2009 19:31:04 -0000	1.19
+++ wsrt.xml	22 Apr 2009 13:04:34 -0000	1.20
@@ -655,16 +655,24 @@
     <head>Compliance</head>
  
     <p>
-     An endpoint is not compliant with this specification if it
-     fails to satisfy one or more of the MUST or REQUIRED level requirements
-     defined herein.
+    An implementation is not compliant with this specification if it fails to
+    satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+    A SOAP Node MUST NOT use the XML namespace identifier for this specification
+     (listed in <specref ref="namespaces"/>) within SOAP Envelopes unless it is compliant
+    with this specification. 
     </p>
-    
+     
+     <p>
+    Normative text within this specification takes precedence over the XML Schema
+    and WSDL descriptions, which in turn take precedence over outlines, which in
+    turn take precedence over examples. 
+     </p>
+     
     <p>
-     Normative text within this specification takes precedence
-     over the XML Schema and WSDL descriptions, which in turn take 
-     precedence over outlines, which in turn take precedence over examples.
+    All messages defined by this specification MUST be sent to a Web service that
+    is addressable by an EPR [WS-Addressing]. 
     </p>
+
    </div2>
   </div1>
 
@@ -678,12 +686,6 @@
     representations.
    </p>
 
-   <p>
-    All messages defined by this specification MUST be sent
-    to a Web service that is addressable by an EPR
-    <bibref ref="AddrCore"/>.
-   </p>
-
    <div2 id="fragments">
     <head>Fragments</head>
  
@@ -3807,6 +3809,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/04/22 </td>
+      <td> KW </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- wseventing.html	21 Apr 2009 00:04:40 -0000	1.42
+++ wseventing.html	22 Apr 2009 13:04:34 -0000	1.43
@@ -414,19 +414,21 @@
         renew, and/or delete subscriptions on behalf of an event source.
        </p></dd></dl></div><div class="div2">
 <h3><a name="compliance" id="compliance"/>3.5 Compliance</h3><p>
-     An implementation is not compliant with this specification if
-     it fails to satisfy one or more of the MUST or REQUIRED level
-     requirements defined herein. A SOAP Node MUST NOT use the XML
-     namespace identifier for this specification (listed in 
-     <a href="#namespaces"><b>3.3 XML Namespaces</b></a>) within SOAP Envelopes unless
-     it is compliant with this specification.
+     An implementation is not compliant with this specification if it fails to
+     satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+     A SOAP Node MUST NOT use the XML namespace identifier for this specification
+     (listed in <a href="#namespaces"><b>3.3 XML Namespaces</b></a>) within SOAP Envelopes unless it is compliant
+     with this specification. 
+    </p><p>
+     Normative text within this specification takes precedence over the XML Schema
+     and WSDL descriptions, which in turn take precedence over outlines, which in
+     turn take precedence over examples. 
+    </p><p>
+     All messages defined by this specification MUST be sent to a Web service that
+     is addressable by an EPR [WS-Addressing]. 
     </p><p>
      SOAP is not a requirement for using the constructs defined in
      this specification.
-    </p><p>
-     Normative text within this specification takes precedence over
-     normative outlines, which in turn takes precedence over the XML
-     Schema and WSDL descriptions.
     </p></div></div><div class="div1">
 <h2><a name="SubMsgs" id="SubMsgs"/>4 Subscription Messages</h2><p>
     To create, renew, and delete subscriptions, subscribers send
@@ -454,10 +456,6 @@
     messages defined herein are delivered using the quality of
     service of the underlying transport(s) and on a best-effort basis
     at the application layer.
-   </p><p>
-    All messages defined by this specification MUST be sent
-    to a Web service that is addressable by an EPR
-    <a href="#AddrCore">[WS-Addressing]</a>.
    </p><div class="div2">
 <h3><a name="Subscribe" id="Subscribe"/>4.1 Subscribe</h3><p>
      To create a subscription, a subscriber sends a request message
@@ -1968,4 +1966,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</a></td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6727">6727</a></td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6725">6725</a></td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6715">6715</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6715">6715</a></td></tr><tr><td> 2009/04/22 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsrt.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.html,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -d -r1.30 -r1.31
--- wsrt.html	5 Apr 2009 19:31:04 -0000	1.30
+++ wsrt.html	22 Apr 2009 13:04:34 -0000	1.31
@@ -371,23 +371,24 @@
      with the value "1".
     </p></div><div class="div2">
 <h3><a name="compliance" id="compliance"/>3.5 Compliance</h3><p>
-     An endpoint is not compliant with this specification if it
-     fails to satisfy one or more of the MUST or REQUIRED level requirements
-     defined herein.
+    An implementation is not compliant with this specification if it fails to
+    satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+    A SOAP Node MUST NOT use the XML namespace identifier for this specification
+     (listed in <a href="#namespaces"><b>3.2 XML Namespaces</b></a>) within SOAP Envelopes unless it is compliant
+    with this specification. 
     </p><p>
-     Normative text within this specification takes precedence
-     over the XML Schema and WSDL descriptions, which in turn take 
-     precedence over outlines, which in turn take precedence over examples.
+    Normative text within this specification takes precedence over the XML Schema
+    and WSDL descriptions, which in turn take precedence over outlines, which in
+    turn take precedence over examples. 
+     </p><p>
+    All messages defined by this specification MUST be sent to a Web service that
+    is addressable by an EPR [WS-Addressing]. 
     </p></div></div><div class="div1">
 <h2><a name="Transferextensions" id="Transferextensions"/>4 Extensions to WS-Transfer</h2><p>
     WS-Transfer defines operations to Get, Put, Create and
     Delete representations of resources. WS-ResourceTransfer extends these
     operations to add the capability to operate on fragments of the resource
     representations.
-   </p><p>
-    All messages defined by this specification MUST be sent
-    to a Web service that is addressable by an EPR
-    <a href="#AddrCore">[WS-Addressing]</a>.
    </p><div class="div2">
 <h3><a name="fragments" id="fragments"/>4.1 Fragments</h3><p>
      Since an EPR refers to a resource as a whole, techniques
@@ -2155,4 +2156,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a></td></tr><tr><td> 2009/03/12 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6548">6548</a></td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a></td></tr><tr><td> 2009/03/24 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</a></td></tr><tr><td> 2009/04/22 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -d -r1.31 -r1.32
--- wst.html	21 Apr 2009 00:40:40 -0000	1.31
+++ wst.html	22 Apr 2009 13:04:34 -0000	1.32
@@ -195,24 +195,30 @@
      of a corresponding SOAP Header with a soap:mustUnderstand attribute
      with the value "1".
     </p></div><div class="div2">
-<h3><a name="compliance" id="compliance"/>2.5 Compliance</h3><p>An implementation is not compliant with this specification if it fails to
-     satisfy one or more of the MUST or REQUIRED level requirements defined
-     herein. A SOAP Node MUST NOT use the XML namespace identifier for this
-     specification (listed in <a href="#xmlnamespaces">Table 2-1</a>) within
-     SOAP envelopes unless it is compliant with this specification.</p><p>Specifically, a compliant SOAP Node that implements a resource MUST
-     provide the Get operation as defined in this specification, and MAY provide
-     the Put and Delete operations.</p><p>Normative text within this specification takes precedence over normative
-     outlines, which in turn takes precedence over the XML Schema and WSDL
-     descriptions.</p><p>
-     In any given
-     request-response message exchange, the responses generated by the service
-     server MUST use the same WS-Addressing namespace binding that was used in the
-     request.</p></div></div><div class="div1">
-<h2><a name="resourceOperations" id="resourceOperations"/>3 Resource Operations</h2><p>
-       All messages defined by this specification MUST be sent
-       to a Web service that is addressable by an EPR
-       <a href="#AddrCore">[WS-Addressing]</a>.
-      </p><div class="div2">
+<h3><a name="compliance" id="compliance"/>2.5 Compliance</h3><p>
+          An implementation is not compliant with this specification if it fails to
+          satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+          A SOAP Node MUST NOT use the XML namespace identifier for this specification
+          (listed in <a href="#namespaces"><b>2.2 XML Namespaces</b></a>) within SOAP Envelopes unless it is compliant
+          with this specification. 
+        </p><p>
+          Normative text within this specification takes precedence over the XML Schema
+          and WSDL descriptions, which in turn take precedence over outlines, which in
+          turn take precedence over examples. 
+        </p><p>
+          All messages defined by this specification MUST be sent to a Web service that
+          is addressable by an EPR [WS-Addressing]. 
+        </p><p>
+          Specifically, a compliant SOAP Node that implements a resource MUST
+           provide the Get operation as defined in this specification, and MAY provide
+           the Put and Delete operations.
+        </p><p>
+          In any given
+          request-response message exchange, the responses generated by the service
+          server MUST use the same WS-Addressing namespace binding that was used in the
+          request.
+         </p></div></div><div class="div1">
+<h2><a name="resourceOperations" id="resourceOperations"/>3 Resource Operations</h2><div class="div2">
 <h3><a name="Get" id="Get"/>3.1 Get</h3><p>This specification defines one Web service operation (Get) for fetching a
 one-time snapshot of the representation of a resource.</p><p>The Get request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/02/ws-tra/Get
@@ -966,4 +972,5 @@
          <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a></td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue 
          <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a></td></tr><tr><td> 2009/03/24 </td><td> DD </td><td> Added resolution of issue 
          <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</a></td></tr><tr><td> 2009/04/20 </td><td> DD </td><td> Added resolution of issue 
-         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6730">6730</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+         <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6730">6730</a></td></tr><tr><td> 2009/04/22 </td><td> KW </td><td> Added resolution of issue 
+            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -d -r1.24 -r1.25
--- wsmex.xml	8 Apr 2009 00:21:19 -0000	1.24
+++ wsmex.xml	22 Apr 2009 13:04:34 -0000	1.25
@@ -453,7 +453,7 @@
   <div1 id="Notation">
    <head>Notation</head>
    
-   <div2 id="Namespaces">
+   <div2 id="namespaces">
     <head>XML Namespaces</head>
 
     <p>
@@ -676,13 +676,22 @@
     <head>Compliance</head>
     
     <p>
-     An implementation is not compliant with this specification if it 
-     fails to satisfy one or more of the MUST or REQUIRED level 
-     requirements defined herein. A SOAP Node MUST NOT use the XML 
-     namespace identifier for this specification (listed in 
-     <specref ref='Conventions'/>) within XML documents, SOAP Envelopes, 
-     and <bibref ref='AddrCore'/> endpoint 
-     references unless it is compliant with this specification.
+     An implementation is not compliant with this specification if it fails to
+     satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+     A SOAP Node MUST NOT use the XML namespace identifier for this specification
+     (listed in <specref ref="namespaces"/>) within SOAP Envelopes unless it is compliant
+     with this specification. 
+    </p>
+    
+    <p>
+     Normative text within this specification takes precedence over the XML Schema
+     and WSDL descriptions, which in turn take precedence over outlines, which in
+     turn take precedence over examples. 
+    </p>
+    
+    <p>
+     All messages defined by this specification MUST be sent to a Web service that
+     is addressable by an EPR [WS-Addressing]. 
     </p>
     
     <p>
@@ -695,20 +704,6 @@
      and access specifications (e.g. HTTP, WS-ResourceFramework).
     </p>
 
-    <p>
-     Normative text within this specification takes precedence over 
-     outlines, which in turn take precedence over the XML Schema 
-     <bibref ref='Schema1'/>,<bibref ref='Schema2'/> and 
-     <bibref ref='WSDL11'/> descriptions (if any), which in turn 
-     take precedence over examples.
-    </p>
-
-    <p>
-     All messages defined by this specification MUST be sent
-     to a Web service that is addressable by an EPR
-     <bibref ref="AddrCore"/>.
-    </p>
-
    </div2>
   </div1>
  
@@ -1942,6 +1937,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6728">6728</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/04/22 </td>
+      <td> KW </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -d -r1.32 -r1.33
--- wsenum.html	8 Apr 2009 00:20:00 -0000	1.32
+++ wsenum.html	22 Apr 2009 13:04:34 -0000	1.33
@@ -264,16 +264,18 @@
          specification
         </p></dd></dl></div><div class="div2">
 <h3><a name="compliance" id="compliance"/>2.5 Compliance</h3><p>
-      An implementation is not compliant with this
-      specification if it fails to satisfy one or more of the MUST or
-      REQUIRED level requirements defined herein. A SOAP Node MUST NOT
-      use the XML namespace identifier for this specification (listed in
-      <a href="#namespaces"><b>2.3 XML Namespaces</b></a>) within SOAP Envelopes unless
-      it is compliant with this specification.
+      An implementation is not compliant with this specification if it fails to
+      satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+      A SOAP Node MUST NOT use the XML namespace identifier for this specification
+      (listed in <a href="#namespaces"><b>2.3 XML Namespaces</b></a>) within SOAP Envelopes unless it is compliant
+      with this specification. 
      </p><p>
-      Normative text within this specification takes
-      precedence over normative outlines, which in turn takes precedence
-      over the XML Schema and WSDL descriptions.
+      Normative text within this specification takes precedence over the XML Schema
+      and WSDL descriptions, which in turn take precedence over outlines, which in
+      turn take precedence over examples. 
+     </p><p>
+      All messages defined by this specification MUST be sent to a Web service that
+      is addressable by an EPR [WS-Addressing]. 
      </p></div></div><div class="div1">
 <h2><a name="EnumMsgs" id="EnumMsgs"/>3 Enumeration Messages</h2><p>
     Enumeration contexts represent a specific
@@ -317,10 +319,6 @@
    </p><p>
     In addition, the data source MAY invalidate an
     enumeration context at any time, as necessary.
-   </p><p>
-    All messages defined by this specification MUST be sent
-    to a Web service that is addressable by an EPR 
-    <a href="#AddrCore">[WS-Addressing]</a>.
    </p><div class="div2">
 <h3><a name="Enumerate" id="Enumerate"/>3.1 Enumerate</h3><p>
      All data sources MUST support some operation
@@ -1642,4 +1640,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a></td></tr><tr><td> 2009/03/24 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</a></td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6499">6499</a></td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6726">6726</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6726">6726</a></td></tr><tr><td> 2009/04/22 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- wsenum.xml	8 Apr 2009 00:20:00 -0000	1.23
+++ wsenum.xml	22 Apr 2009 13:04:34 -0000	1.24
@@ -489,20 +489,26 @@
 
     <div2 id="compliance">
      <head>Compliance</head>
-
+     
      <p>
-      An implementation is not compliant with this
-      specification if it fails to satisfy one or more of the MUST or
-      REQUIRED level requirements defined herein. A SOAP Node MUST NOT
-      use the XML namespace identifier for this specification (listed in
-      <specref ref="namespaces"/>) within SOAP Envelopes unless
-      it is compliant with this specification.
+      An implementation is not compliant with this specification if it fails to
+      satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+      A SOAP Node MUST NOT use the XML namespace identifier for this specification
+      (listed in <specref ref="namespaces"/>) within SOAP Envelopes unless it is compliant
+      with this specification. 
      </p>
+     
      <p>
-      Normative text within this specification takes
-      precedence over normative outlines, which in turn takes precedence
-      over the XML Schema and WSDL descriptions.
+      Normative text within this specification takes precedence over the XML Schema
+      and WSDL descriptions, which in turn take precedence over outlines, which in
+      turn take precedence over examples. 
      </p>
+     
+     <p>
+      All messages defined by this specification MUST be sent to a Web service that
+      is addressable by an EPR [WS-Addressing]. 
+     </p>
+     
     </div2>
 
   </div1>
@@ -559,12 +565,6 @@
     enumeration context at any time, as necessary.
    </p>
 
-   <p>
-    All messages defined by this specification MUST be sent
-    to a Web service that is addressable by an EPR 
-    <bibref ref="AddrCore"/>.
-   </p>
-
    <div2 id="Enumerate">
     <head>Enumerate</head>
 
@@ -2793,6 +2793,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6726">6726</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/04/22 </td>
+      <td> KW </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -d -r1.34 -r1.35
--- wsmex.html	8 Apr 2009 00:21:19 -0000	1.34
+++ wsmex.html	22 Apr 2009 13:04:34 -0000	1.35
@@ -47,7 +47,7 @@
 &nbsp;&nbsp;&nbsp;2.1 <a href="#Requirements">Requirements</a><br/>
 &nbsp;&nbsp;&nbsp;2.2 <a href="#Example">Example</a><br/>
 3 <a href="#Notation">Notation</a><br/>
-&nbsp;&nbsp;&nbsp;3.1 <a href="#Namespaces">XML Namespaces</a><br/>
+&nbsp;&nbsp;&nbsp;3.1 <a href="#namespaces">XML Namespaces</a><br/>
 &nbsp;&nbsp;&nbsp;3.2 <a href="#Conventions">Notational Conventions</a><br/>
 &nbsp;&nbsp;&nbsp;3.3 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br/>
 &nbsp;&nbsp;&nbsp;3.4 <a href="#Compliance">Compliance</a><br/>
@@ -332,7 +332,7 @@
      <a href="#GetMexReq">Example 2-3</a> was directed.
     </p></div></div><div class="div1">
 <h2><a name="Notation" id="Notation"/>3 Notation</h2><div class="div2">
-<h3><a name="Namespaces" id="Namespaces"/>3.1 XML Namespaces</h3><p>
+<h3><a name="namespaces" id="namespaces"/>3.1 XML Namespaces</h3><p>
      The XML namespace URI that MUST be used by implementations of this 
      specification is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/02/ws-mex">http://www.w3.org/2009/02/ws-mex</a></pre></div></div><p><a href="#XMLNS">Table 3-1</a> lists XML namespaces that are used in this 
@@ -408,13 +408,18 @@
      with the value "1".
     </p></div><div class="div2">
 <h3><a name="Compliance" id="Compliance"/>3.4 Compliance</h3><p>
-     An implementation is not compliant with this specification if it 
-     fails to satisfy one or more of the MUST or REQUIRED level 
-     requirements defined herein. A SOAP Node MUST NOT use the XML 
-     namespace identifier for this specification (listed in 
-     <a href="#Conventions"><b>3.2 Notational Conventions</b></a>) within XML documents, SOAP Envelopes, 
-     and <a href="#AddrCore">[WS-Addressing]</a> endpoint 
-     references unless it is compliant with this specification.
+     An implementation is not compliant with this specification if it fails to
+     satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+     A SOAP Node MUST NOT use the XML namespace identifier for this specification
+     (listed in <a href="#namespaces"><b>3.1 XML Namespaces</b></a>) within SOAP Envelopes unless it is compliant
+     with this specification. 
+    </p><p>
+     Normative text within this specification takes precedence over the XML Schema
+     and WSDL descriptions, which in turn take precedence over outlines, which in
+     turn take precedence over examples. 
+    </p><p>
+     All messages defined by this specification MUST be sent to a Web service that
+     is addressable by an EPR [WS-Addressing]. 
     </p><p>
      Support for the GetMetadata operation by a Web service is 
      optional. If metadata about a Web service endpoint is referenced by 
@@ -423,16 +428,6 @@
      Reference MUST refer to a <a href="#WS-Transfer">[WS-Transfer]</a> resource. 
      The referred resource MAY also support other resource management 
      and access specifications (e.g. HTTP, WS-ResourceFramework).
-    </p><p>
-     Normative text within this specification takes precedence over 
-     outlines, which in turn take precedence over the XML Schema 
-     <a href="#Schema1">[XML Schema: Structures]</a>,<a href="#Schema2">[XML Schema: Datatypes]</a> and 
-     <a href="#WSDL11">[WSDL 1.1]</a> descriptions (if any), which in turn 
-     take precedence over examples.
-    </p><p>
-     All messages defined by this specification MUST be sent
-     to a Web service that is addressable by an EPR
-     <a href="#AddrCore">[WS-Addressing]</a>.
     </p></div></div><div class="div1">
 <h2><a name="metadata-resources" id="metadata-resources"/>4 Metadata Resources</h2><p>
     A resource is a Web service that is addressable by an endpoint 
@@ -1118,4 +1113,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6404">6404</a></td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a></td></tr><tr><td> 2009/03/24 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</a></td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6728">6728</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6728">6728</a></td></tr><tr><td> 2009/04/22 </td><td> KW </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -d -r1.33 -r1.34
--- wseventing.xml	21 Apr 2009 00:04:17 -0000	1.33
+++ wseventing.xml	22 Apr 2009 13:04:34 -0000	1.34
@@ -744,14 +744,24 @@
 
    <div2 id="compliance">
     <head>Compliance</head>
-
+    
     <p>
-     An implementation is not compliant with this specification if
-     it fails to satisfy one or more of the MUST or REQUIRED level
-     requirements defined herein. A SOAP Node MUST NOT use the XML
-     namespace identifier for this specification (listed in 
-     <specref ref="namespaces"/>) within SOAP Envelopes unless
-     it is compliant with this specification.
+     An implementation is not compliant with this specification if it fails to
+     satisfy one or more of the MUST or REQUIRED level requirements defined herein.
+     A SOAP Node MUST NOT use the XML namespace identifier for this specification
+     (listed in <specref ref="namespaces"/>) within SOAP Envelopes unless it is compliant
+     with this specification. 
+    </p>
+    
+    <p>
+     Normative text within this specification takes precedence over the XML Schema
+     and WSDL descriptions, which in turn take precedence over outlines, which in
+     turn take precedence over examples. 
+    </p>
+    
+    <p>
+     All messages defined by this specification MUST be sent to a Web service that
+     is addressable by an EPR [WS-Addressing]. 
     </p>
 
     <p>
@@ -759,11 +769,6 @@
      this specification.
     </p>
 
-    <p>
-     Normative text within this specification takes precedence over
-     normative outlines, which in turn takes precedence over the XML
-     Schema and WSDL descriptions.
-    </p>
    </div2>
   </div1>
 
@@ -802,12 +807,6 @@
     at the application layer.
    </p>
 
-   <p>
-    All messages defined by this specification MUST be sent
-    to a Web service that is addressable by an EPR
-    <bibref ref="AddrCore"/>.
-   </p>
-
    <div2 id="Subscribe">
     <head>Subscribe</head>
 
@@ -3412,6 +3411,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6715">6715</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/04/22 </td>
+      <td> KW </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Received on Wednesday, 22 April 2009 13:04:48 UTC