WWW/2002/ws/ra/edcopies wsenum.html,1.156,1.157 wsenum.xml,1.147,1.148 wsevd.html,1.23,1.24 wseventing.html,1.222,1.223 wseventing.xml,1.214,1.215 wsfrag.html,1.79,1.80 wsfrag.xml,1.76,1.77 wsmex.html,1.149,1.150 wsmex.xml,1.139,1.140 wssa.html,1.12,1.13 wst.html,1.135,1.136 wst.xml,1.133,1.134

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

Modified Files:
	wsenum.html wsenum.xml wsevd.html wseventing.html 
	wseventing.xml wsfrag.html wsfrag.xml wsmex.html wsmex.xml 
	wssa.html wst.html wst.xml 
Log Message:
11899


Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.133
retrieving revision 1.134
diff -u -d -r1.133 -r1.134
--- wst.xml	2 Feb 2011 00:36:28 -0000	1.133
+++ wst.xml	7 Feb 2011 23:51:03 -0000	1.134
@@ -1465,27 +1465,6 @@
     is defined for the fault.<phrase/>
    </p>
    
-   <p>
-    For SOAP 1.2, the <kw>[Code]</kw> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p>
-    
-   <table id="soapver" border="1">
-    <tbody>
-     <tr>
-      <th> SOAP Version </th>
-      <th> Sender </th>
-      <th> Receiver </th>
-     </tr>
-     <tr>
-      <td> SOAP 1.2 </td>
-      <td> s12:Sender </td>
-      <td> s12:Receiver </td>
-     </tr>
-    </tbody>
-   </table>
-   
    <p>The properties above bind to a SOAP 1.2 fault as follows:</p>
    <example>
     <eg>&lt;s12:Envelope&gt;
@@ -2984,6 +2963,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/02/07 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.222
retrieving revision 1.223
diff -u -d -r1.222 -r1.223
--- wseventing.html	2 Feb 2011 00:44:31 -0000	1.222
+++ wseventing.html	7 Feb 2011 23:51:02 -0000	1.223
@@ -74,26 +74,26 @@
 &nbsp;&nbsp;&nbsp;6.11 <a href="#NoDeliveryMechanismEstablished">NoDeliveryMechanismEstablished</a><br/>
 &nbsp;&nbsp;&nbsp;6.12 <a href="#CannotProcessFilter">CannotProcessFilter</a><br/>
 7 <a href="#Security">Security Considerations</a><br/>
-&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x2142">Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2x1x2151">Subscriptions</a><br/>
-&nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2x1x2156">Endpoint Verification</a><br/>
+&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x2107">Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2x1x2116">Subscriptions</a><br/>
+&nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2x1x2121">Endpoint Verification</a><br/>
 8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
 9 <a href="#metadata">WS-Eventing Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2x1x2182">EventSource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2x1x2306">SubscriptionManager Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2x1x2147">EventSource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2x1x2271">SubscriptionManager Assertion</a><br/>
 10 <a href="#acks">Acknowledgements</a><br/>
 11 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2369">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2x1x2529">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2334">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2x1x2494">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
 &nbsp;&nbsp;&nbsp;A.1 <a href="#ETypes">Event Types &amp; Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3x1x2679">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3x1x2727">Bindings for Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4x1x2732">Binding for Unwrapped Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4x1x2753">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3x1x2644">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3x1x2692">Bindings for Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4x1x2697">Binding for Unwrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4x1x2718">Binding for Wrapped Notifications</a><br/>
 &nbsp;&nbsp;&nbsp;A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3x1x2780">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3x1x2745">Retrieving Notification WSDLs</a><br/>
 B <a href="#Schema">XML Schema</a><br/>
 C <a href="#WSDL">WSDL</a><br/>
 D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -1322,11 +1322,7 @@
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/fault">http://www.w3.org/2002/ws/ra/edcopies/ws-evt/fault</a></pre></div></div><p>
     The definitions of faults in this section use the following properties:
    </p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element 
-    is defined for the fault.<br/></p><p>
-    For SOAP 1.2, the <b>[Code]</b> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p><a name="soapver" id="soapver"/><table border="1"><tbody><tr><th> SOAP Version </th><th> Sender </th><th> Receiver </th></tr><tr><td> SOAP 1.2 </td><td> s12:Sender </td><td> s12:Receiver </td></tr></tbody></table><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
+    is defined for the fault.<br/></p><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
   &lt;s12:Header&gt;
     &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
     &lt;!-- Headers elided for brevity. --&gt;
@@ -1451,7 +1447,7 @@
     urged to perform a security analysis to determine their particular 
     threat profile and the appropriate responses to those threats.
    </p><div class="div2">
-<h3><a name="iddiv2x1x2142" id="iddiv2x1x2142"/>7.1 Notifications</h3><p>
+<h3><a name="iddiv2x1x2107" id="iddiv2x1x2107"/>7.1 Notifications</h3><p>
      The information contained in Notifications might be sensitive. In 
      such cases it is advisable to authenticate and authorize subscribers 
      as part of the processing of the Subscribe request. Note that an 
@@ -1472,7 +1468,7 @@
      and trace the origin of such attempts. Additionally, the 
      authorization of Subscribers reduces the pool of potential attackers.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x2151" id="iddiv2x1x2151"/>7.2 Subscriptions</h3><p>
+<h3><a name="iddiv2x1x2116" id="iddiv2x1x2116"/>7.2 Subscriptions</h3><p>
      Once created, subscriptions ought to be treated as protected 
      resources. Renew, GetStatus, and Unsubscribe requests ought to be 
      authenticated and authorized (for example, the identity of the 
@@ -1487,7 +1483,7 @@
      the identities of these entities are discovered and verified) 
      are particular to individual deployments.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x2156" id="iddiv2x1x2156"/>7.3 Endpoint Verification</h3><p>
+<h3><a name="iddiv2x1x2121" id="iddiv2x1x2121"/>7.3 Endpoint Verification</h3><p>
      Implementations that perform validity checks on the EPRs used in 
      WS-Eventing (wse:NotifyTo, wse:EndTo) are advised that such checks 
      can be misused to obtain information about a target network. For 
@@ -1538,7 +1534,7 @@
     that indicate a particular security mechanism used to protect
     the WS-Eventing operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2x1x2182" id="iddiv2x1x2182"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2x1x2147" id="iddiv2x1x2147"/>9.1 EventSource Assertion</h3><p>
      Services indicate support for the WS-Eventing's definition 
      of an event source through the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1650,7 +1646,7 @@
      (10) - (12) contains the EventDescription data that describes the 
      syntax of the events that this event source might send.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x2306" id="iddiv2x1x2306"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2x1x2271" id="iddiv2x1x2271"/>9.2 SubscriptionManager Assertion</h3><p>
      Services indicate support for the
      WS-Eventing's definition of a subscription manager 
      through the use of the Web Services
@@ -1721,7 +1717,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2369" id="iddiv2x1x2369"/>11.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+<h3><a name="iddiv2x1x2334" id="iddiv2x1x2334"/>11.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
          WS-I Profile, Basic Profile Version 1.2
         </cite></a>
         , R. Chumbley, et al, Editors.
@@ -1783,7 +1779,7 @@
        , E. Christensen, et al., Editors.
        World Wide Web Consortium (W3C), 15 March 2001
       Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x2529" id="iddiv2x1x2529"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+<h3><a name="iddiv2x1x2494" id="iddiv2x1x2494"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
         OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
         Web Services Make Connection (WS-MakeConnection)
        </cite></a>
@@ -1861,7 +1857,7 @@
      serve as a description of the Event Type used in 
      <a href="#Table1">Example 2-1</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x2669" id="idexamplex1x2669"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wsevd:EventDescriptions 
+<div class="exampleHeader"><a name="idexamplex1x2634" id="idexamplex1x2634"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wsevd:EventDescriptions 
 (02)        targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)        xmlns:wsevd="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch"&gt;
@@ -1882,7 +1878,7 @@
      (GED) for this Event Type is defined on line (08) as being of type 
      "{http://www.example.org/oceanwatch}:WindReportType". 
     </p><div class="div3">
-<h4><a name="iddiv3x1x2679" id="iddiv3x1x2679"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x2644" id="iddiv3x1x2644"/>A.1.1 Retrieving Event Descriptions</h4><p>
       Although there are many ways in which an event source can make its 
       EventDescriptions available, this specification RECOMMENDS the use of 
       the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1929,7 +1925,7 @@
 (10) &lt;/mex:GetMetadataResponse&gt; </pre></div></div><p><a href="#mexEVD">Example A-4</a> shows how the Event Descriptions metadata
       might appear within a GetMetadataResponse message.
      </p></div><div class="div3">
-<h4><a name="iddiv3x1x2727" id="iddiv3x1x2727"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x2692" id="iddiv3x1x2692"/>A.1.2 Bindings for Event Descriptions</h4><p>
       For any Notification Format it MUST be possible to determine how a 
       given wsevd:eventType will appear on the wire as a notification in a 
       subscription created with that format. The following sections define 
@@ -1941,7 +1937,7 @@
       Format, implementations MAY provide a Notification WSDL (see below) 
       that explicitly describes the notification operations. 
      </p><div class="div4">
-<h5><a name="iddiv4x1x2732" id="iddiv4x1x2732"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2697" id="iddiv4x1x2697"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
        The information about an Event Type contained in the wsevd:eventType 
        element binds to a Unwrapped Notification for that type as follows:
       </p><ul><li><p>
@@ -1956,7 +1952,7 @@
          event being transmitted. If the @element attribute is absent then
          the <b>[Body]</b> property has no children.
         </p></li></ul></div><div class="div4">
-<h5><a name="iddiv4x1x2753" id="iddiv4x1x2753"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2718" id="iddiv4x1x2718"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
        The information about an Event Type contained in the eventType element 
        binds to a Wrapped Notification for that type as follows: 
       </p><ul><li><p>
@@ -1982,7 +1978,7 @@
      successful Subscribe request that used a particular Format IRI. The 
      following is an example of a Notification WSDL: 
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexamplex1x2774" id="idexamplex1x2774"/>Example A-5: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexamplex1x2739" id="idexamplex1x2739"/>Example A-5: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
 (02)                   targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)                   xmlns:xs="http://www.w3.org/2001/XMLSchema"
 (04)                   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -2017,7 +2013,7 @@
 (33)     &lt;/wsdl:operation&gt;
 (34)   &lt;/wsdl:binding&gt;
 (35) &lt;/wsdl:definitions&gt;</pre></div></div><div class="div3">
-<h4><a name="iddiv3x1x2780" id="iddiv3x1x2780"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3x1x2745" id="iddiv3x1x2745"/>A.2.1 Retrieving Notification WSDLs</h4><p>
       Although there are many ways in which an event source can make 
       Notification WSDLs available, this specification RECOMMENDS the use of 
       the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -2764,4 +2760,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11551">11551</a></td></tr><tr><td> 2011/01/26 </td><td> DD </td><td> Added resolution of issue
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11874">11874</a></td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</a></td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11703">11703</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=11703">11703</a></td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</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.147
retrieving revision 1.148
diff -u -d -r1.147 -r1.148
--- wsenum.xml	2 Feb 2011 00:36:27 -0000	1.147
+++ wsenum.xml	7 Feb 2011 23:51:02 -0000	1.148
@@ -1804,27 +1804,6 @@
     is defined for the fault.<phrase/>
    </p>
    
-   <p>
-    For SOAP 1.2, the <kw>[Code]</kw> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p>
-   
-   <table id="soapver" border="1">
-    <tbody>
-     <tr>
-      <th> SOAP Version </th>
-      <th> Sender </th>
-      <th> Receiver </th>
-     </tr>
-     <tr>
-      <td> SOAP 1.2 </td>
-      <td> s12:Sender </td>
-      <td> s12:Receiver </td>
-     </tr>
-    </tbody>
-   </table>
-   
    <p>The properties above bind to a SOAP 1.2 fault as follows:</p>
    <example>
     <eg>&lt;s12:Envelope&gt;
@@ -4002,6 +3981,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/02/07 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -d -r1.76 -r1.77
--- wsfrag.xml	2 Feb 2011 00:36:27 -0000	1.76
+++ wsfrag.xml	7 Feb 2011 23:51:02 -0000	1.77
@@ -1664,27 +1664,6 @@
     is defined for the fault.<phrase/>
    </p>
     
-   <p>
-    For SOAP 1.2, the <kw>[Code]</kw> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p>
-   
-   <table id="soapver" border="1">
-    <tbody>
-     <tr>
-      <th> SOAP Version </th>
-      <th> Sender </th>
-      <th> Receiver </th>
-     </tr>
-     <tr>
-      <td> SOAP 1.2 </td>
-      <td> s12:Sender </td>
-      <td> s12:Receiver </td>
-     </tr>
-    </tbody>
-   </table>
-    
    <p>The properties above bind to a SOAP 1.2 fault as follows:</p>
    <example>
     <eg>&lt;s12:Envelope&gt;
@@ -2479,6 +2458,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/02/07 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -d -r1.79 -r1.80
--- wsfrag.html	2 Feb 2011 00:36:27 -0000	1.79
+++ wsfrag.html	7 Feb 2011 23:51:02 -0000	1.80
@@ -67,10 +67,10 @@
 &nbsp;&nbsp;&nbsp;9.2 <a href="#InvalidExpression">InvalidExpression</a><br/>
 &nbsp;&nbsp;&nbsp;9.3 <a href="#UnsupportedMode">UnsupportedMode</a><br/>
 10 <a href="#metadata">WS-Fragment Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2x1x1900">Fragment Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2x1x1865">Fragment Assertion</a><br/>
 11 <a href="#acks">Acknowledgements</a><br/>
 12 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x1963">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x1928">Normative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
 B <a href="#changelog">Change Log</a><br/>
@@ -790,11 +790,7 @@
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-fra/fault">http://www.w3.org/2002/ws/ra/edcopies/ws-fra/fault</a></pre></div></div><p>
     The definitions of faults in this section use the following properties:
    </p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element 
-    is defined for the fault.<br/></p><p>
-    For SOAP 1.2, the <b>[Code]</b> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p><a name="soapver" id="soapver"/><table border="1"><tbody><tr><th> SOAP Version </th><th> Sender </th><th> Receiver </th></tr><tr><td> SOAP 1.2 </td><td> s12:Sender </td><td> s12:Receiver </td></tr></tbody></table><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
+    is defined for the fault.<br/></p><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
   &lt;s12:Header&gt;
     &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
     &lt;!-- Headers elided for brevity. --&gt;
@@ -860,7 +856,7 @@
     doing so the endpoint is indicating that the corresponding WS-Fragment
     features are supported by that endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2x1x1900" id="iddiv2x1x1900"/>10.1 Fragment Assertion</h3><p>
+<h3><a name="iddiv2x1x1865" id="iddiv2x1x1865"/>10.1 Fragment Assertion</h3><p>
      Services indicate their support for the WS-Fragment specification through 
      the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -924,7 +920,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2x1x1963" id="iddiv2x1x1963"/>12.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+<h3><a name="iddiv2x1x1928" id="iddiv2x1x1928"/>12.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
          WS-I Profile, Basic Profile Version 1.2
         </cite></a>
         , R. Chumbley, et al, Editors.
@@ -1124,4 +1120,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9558">9558</a></td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9717">9717</a></td></tr><tr><td> 2010/11/19 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8284">8284</a></td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</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=11882">11882</a></td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</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.135
retrieving revision 1.136
diff -u -d -r1.135 -r1.136
--- wst.html	2 Feb 2011 00:36:28 -0000	1.135
+++ wst.html	7 Feb 2011 23:51:02 -0000	1.136
@@ -60,15 +60,15 @@
 &nbsp;&nbsp;&nbsp;6.3 <a href="#PutDenied">PutDenied</a><br/>
 &nbsp;&nbsp;&nbsp;6.4 <a href="#UnknownResource">UnknownResource</a><br/>
 7 <a href="#Security_Considerations">Security Considerations</a><br/>
-&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x1322">Protecting Resources</a><br/>
-&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2x1x1327">Protecting Resource Factories</a><br/>
+&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x1287">Protecting Resources</a><br/>
+&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2x1x1292">Protecting Resource Factories</a><br/>
 8 <a href="#metadata">WS-Transfer Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2x1x1345">TransferResource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2x1x1427">TransferResourceFactory Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2x1x1310">TransferResource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2x1x1392">TransferResourceFactory Assertion</a><br/>
 9 <a href="#acks">Acknowledgements</a><br/>
 10 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2x1x1501">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;10.2 <a href="#iddiv2x1x1687">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2x1x1466">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;10.2 <a href="#iddiv2x1x1652">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
 B <a href="#WSDL">WSDL</a><br/>
@@ -891,11 +891,7 @@
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-tra/fault">http://www.w3.org/2002/ws/ra/edcopies/ws-tra/fault</a></pre></div></div><p>
     The definitions of faults in this section use the following properties:
    </p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element 
-    is defined for the fault.<br/></p><p>
-    For SOAP 1.2, the <b>[Code]</b> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p><a name="soapver" id="soapver"/><table border="1"><tbody><tr><th> SOAP Version </th><th> Sender </th><th> Receiver </th></tr><tr><td> SOAP 1.2 </td><td> s12:Sender </td><td> s12:Receiver </td></tr></tbody></table><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
+    is defined for the fault.<br/></p><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
   &lt;s12:Header&gt;
     &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
     &lt;!-- Headers elided for brevity. --&gt;
@@ -975,7 +971,7 @@
     to perform a security analysis to determine their particular threat 
     profile and the appropriate responses to those threats.
    </p><div class="div2">
-<h3><a name="iddiv2x1x1322" id="iddiv2x1x1322"/>7.1 Protecting Resources</h3><p>
+<h3><a name="iddiv2x1x1287" id="iddiv2x1x1287"/>7.1 Protecting Resources</h3><p>
      Both resources and the information that makes up their representation 
      might be sensitive. In these cases, it is advisable for resource 
      managers to authenticate and authorize clients attempting Get, Put, 
@@ -984,7 +980,7 @@
      ought to have the appropriate authenticity, integrity, and 
      confidentiality measures applied.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x1327" id="iddiv2x1x1327"/>7.2 Protecting Resource Factories</h3><p>
+<h3><a name="iddiv2x1x1292" id="iddiv2x1x1292"/>7.2 Protecting Resource Factories</h3><p>
      In cases where resources and/or the information that makes up their 
      representation are sensitive so, too, are the services that create 
      these resources. In such cases it is advisable for resource factories 
@@ -1017,7 +1013,7 @@
     that indicate a particular security mechanism used to protect
     the WS-Transfer operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2x1x1345" id="iddiv2x1x1345"/>8.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2x1x1310" id="iddiv2x1x1310"/>8.1 TransferResource Assertion</h3><p>
      Services indicate support for the
      WS-Transfer's definition of a Transfer Resource
      through the use of the Web Services
@@ -1083,7 +1079,7 @@
          WS-Transfer message exchanges. Any metadata that appears is scoped 
          to the operations and features of the WS-Transfer specification.
         </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x1427" id="iddiv2x1x1427"/>8.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2x1x1392" id="iddiv2x1x1392"/>8.2 TransferResourceFactory Assertion</h3><p>
      Services indicate support for
      WS-Transfer's definition of a Transfer Resource Factory
      through the use of the Web Services
@@ -1161,7 +1157,7 @@
       Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>10 References</h2><div class="div2">
-<h3><a name="iddiv2x1x1501" id="iddiv2x1x1501"/>10.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+<h3><a name="iddiv2x1x1466" id="iddiv2x1x1466"/>10.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
          WS-I Profile, Basic Profile Version 1.2
         </cite></a>
         , R. Chumbley, et al, Editors.
@@ -1234,7 +1230,7 @@
        , P. Biron, A. Malhotra, Editors.
        World Wide Web Consortium (W3C), 28 October 2004.
       Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x1687" id="iddiv2x1x1687"/>10.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
+<h3><a name="iddiv2x1x1652" id="iddiv2x1x1652"/>10.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
        W3C Working Group Draft, "Web Services Fragment (WS-Fragment) 1.0"
       </cite></a>
       , D. Davis, et al., Editors.
@@ -1598,4 +1594,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11202">11202</a></td></tr><tr><td> 2010/11/16 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11210">11210</a></td></tr><tr><td> 2010/11/19 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8284">8284</a></td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</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=11882">11882</a></td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</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.139
retrieving revision 1.140
diff -u -d -r1.139 -r1.140
--- wsmex.xml	2 Feb 2011 00:36:27 -0000	1.139
+++ wsmex.xml	7 Feb 2011 23:51:02 -0000	1.140
@@ -2602,27 +2602,6 @@
     is defined for the fault.<phrase/>
    </p>
    
-   <p>
-    For SOAP 1.2, the <kw>[Code]</kw> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p>
-    
-   <table id="soapver" border="1">
-    <tbody>
-     <tr>
-      <th> SOAP Version </th>
-      <th> Sender </th>
-      <th> Receiver </th>
-     </tr>
-     <tr>
-      <td> SOAP 1.2 </td>
-      <td> s12:Sender </td>
-      <td> s12:Receiver </td>
-     </tr>
-    </tbody>
-   </table>
-   
    <p>The properties above bind to a SOAP 1.2 fault as follows:</p>
    <example>
     <eg>&lt;s12:Envelope&gt;
@@ -4371,6 +4350,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/02/07 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.156
retrieving revision 1.157
diff -u -d -r1.156 -r1.157
--- wsenum.html	2 Feb 2011 00:36:26 -0000	1.156
+++ wsenum.html	7 Feb 2011 23:51:02 -0000	1.157
@@ -68,15 +68,15 @@
 &nbsp;&nbsp;&nbsp;5.10 <a href="#EmptyFilter">EmptyFilter</a><br/>
 &nbsp;&nbsp;&nbsp;5.11 <a href="#MaxElementsMustBeZero">MaxElementsMustBeZero</a><br/>
 6 <a href="#Security">Security Considerations</a><br/>
-&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2x1x1911">Creating Enumeration Contexts</a><br/>
-&nbsp;&nbsp;&nbsp;6.2 <a href="#iddiv2x1x1916">Protecting Enumeration Contexts</a><br/>
-&nbsp;&nbsp;&nbsp;6.3 <a href="#iddiv2x1x1923">Endpoint Verification</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2x1x1876">Creating Enumeration Contexts</a><br/>
+&nbsp;&nbsp;&nbsp;6.2 <a href="#iddiv2x1x1881">Protecting Enumeration Contexts</a><br/>
+&nbsp;&nbsp;&nbsp;6.3 <a href="#iddiv2x1x1888">Endpoint Verification</a><br/>
 7 <a href="#metadata">WS-Enumeration Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x1943">Enumeration Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x1908">Enumeration Assertion</a><br/>
 8 <a href="#acks">Acknowledgements</a><br/>
 9 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2x1x2063">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2x1x2275">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2x1x2028">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2x1x2240">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
 B <a href="#WSDL">WSDL</a><br/>
@@ -1094,11 +1094,7 @@
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-enu/fault">http://www.w3.org/2002/ws/ra/edcopies/ws-enu/fault</a></pre></div></div><p>
     The definitions of faults in this section use the following properties:
    </p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element 
-    is defined for the fault.<br/></p><p>
-    For SOAP 1.2, the <b>[Code]</b> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p><a name="soapver" id="soapver"/><table border="1"><tbody><tr><th> SOAP Version </th><th> Sender </th><th> Receiver </th></tr><tr><td> SOAP 1.2 </td><td> s12:Sender </td><td> s12:Receiver </td></tr></tbody></table><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
+    is defined for the fault.<br/></p><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
   &lt;s12:Header&gt;
     &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
     &lt;!-- Headers elided for brevity. --&gt;
@@ -1219,7 +1215,7 @@
     a security analysis to determine their particular threat profile and 
     the appropriate responses to those threats.
    </p><div class="div2">
-<h3><a name="iddiv2x1x1911" id="iddiv2x1x1911"/>6.1 Creating Enumeration Contexts</h3><p>
+<h3><a name="iddiv2x1x1876" id="iddiv2x1x1876"/>6.1 Creating Enumeration Contexts</h3><p>
      An enumeration represents a logical cursor through a sequence of 
      data items. If the information in these items is sensitive, it is 
      advisable to for Data Sources to authenticate and authorize Consumers 
@@ -1230,7 +1226,7 @@
      the time the Enumerate request is processed or varies during the 
      lifetime of the enumeration.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x1916" id="iddiv2x1x1916"/>6.2 Protecting Enumeration Contexts</h3><p>
+<h3><a name="iddiv2x1x1881" id="iddiv2x1x1881"/>6.2 Protecting Enumeration Contexts</h3><p>
      Once created, it is advisable to treat Enumeration Contexts as 
      protected resources. Renew, GetStatus, and Release requests ought to 
      be authenticated and authorized (for example, the identity of the 
@@ -1252,7 +1248,7 @@
      Data Sources are advised to authenticate and authorize clients 
      sending Enumerate requests.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x1923" id="iddiv2x1x1923"/>6.3 Endpoint Verification</h3><p>
+<h3><a name="iddiv2x1x1888" id="iddiv2x1x1888"/>6.3 Endpoint Verification</h3><p>
      Data Source implementations that perform validity checks on the 
      EndTo EPR used in the Enumerate request are advised that such checks 
      can be misused to obtain information about a target network. For 
@@ -1294,7 +1290,7 @@
     that indicate a particular security mechanism used to protect 
     the WS-Enumeration operations supported by this endpoint. 
    </p><div class="div2">
-<h3><a name="iddiv2x1x1943" id="iddiv2x1x1943"/>7.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2x1x1908" id="iddiv2x1x1908"/>7.1 Enumeration Assertion</h3><p>
      Services indicate support for the WS-Enumeration's definition of a 
      data source through the use of the Web Services 
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy - 
@@ -1409,7 +1405,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2063" id="iddiv2x1x2063"/>9.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+<h3><a name="iddiv2x1x2028" id="iddiv2x1x2028"/>9.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
          WS-I Profile, Basic Profile Version 1.2
         </cite></a>
         , R. Chumbley, et al, Editors.
@@ -1491,7 +1487,7 @@
        , A. Berglund, et al., Editors.
        World Wide Web Consortium (W3C), 23 January 2007. 
       Available at <a href="http://www.w3.org/TR/xpath20/">http://www.w3.org/TR/xpath20/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x2275" id="iddiv2x1x2275"/>9.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+<h3><a name="iddiv2x1x2240" id="iddiv2x1x2240"/>9.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
         W3C Working Group Draft, "Web Services Metadata Exchange
           (WS-MetadataExchange) 1.1"
        </cite></a>
@@ -2084,4 +2080,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10960">10960</a></td></tr><tr><td> 2010/11/19 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8284">8284</a></td></tr><tr><td> 2011/01/11 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11696">11696</a></td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</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=11882">11882</a></td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file


Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.149
retrieving revision 1.150
diff -u -d -r1.149 -r1.150
--- wsmex.html	2 Feb 2011 00:36:27 -0000	1.149
+++ wsmex.html	7 Feb 2011 23:51:02 -0000	1.150
@@ -73,13 +73,13 @@
 &nbsp;&nbsp;&nbsp;10.1 <a href="#UnsupportedMetadata">UnsupportedMetadata</a><br/>
 &nbsp;&nbsp;&nbsp;10.2 <a href="#InvalidMetadata">UnknownDialect</a><br/>
 11 <a href="#Security">Security Considerations</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2053">Metadata and Security Bootstrapping</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2018">Metadata and Security Bootstrapping</a><br/>
 12 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2074">MetadataExchange Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2039">MetadataExchange Assertion</a><br/>
 13 <a href="#bootstrapping">Bootstrapping Metadata Retrieval</a><br/>
 14 <a href="#acks">Acknowledgements</a><br/>
 15 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;15.1 <a href="#iddiv2x1x2330">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;15.1 <a href="#iddiv2x1x2295">Normative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
 B <a href="#Appendix-B">WSDL</a><br/>
@@ -1569,11 +1569,7 @@
    </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-mex/fault">http://www.w3.org/2002/ws/ra/edcopies/ws-mex/fault</a></pre></div></div><p>
     The definitions of faults in this section use the following properties:
    </p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element 
-    is defined for the fault.<br/></p><p>
-    For SOAP 1.2, the <b>[Code]</b> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p><a name="soapver" id="soapver"/><table border="1"><tbody><tr><th> SOAP Version </th><th> Sender </th><th> Receiver </th></tr><tr><td> SOAP 1.2 </td><td> s12:Sender </td><td> s12:Receiver </td></tr></tbody></table><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
+    is defined for the fault.<br/></p><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s12:Envelope&gt;
   &lt;s12:Header&gt;
     &lt;wsa:Action&gt; <b>[Action]</b> &lt;/wsa:Action&gt;
     &lt;!-- Headers elided for brevity. --&gt;
@@ -1649,7 +1645,7 @@
     security analysis to determine their particular threat profile and the 
     appropriate responses to those threats.
    </p><div class="div2">
-<h3><a name="iddiv2x1x2053" id="iddiv2x1x2053"/>11.1 Metadata and Security Bootstrapping</h3><p>
+<h3><a name="iddiv2x1x2018" id="iddiv2x1x2018"/>11.1 Metadata and Security Bootstrapping</h3><p>
      There are cases in which the metadata used to describe a service might 
      be considered sensitive information. In these cases it is advisable 
      for services to authenticate and authorize consumers as part of the 
@@ -1687,7 +1683,7 @@
     indicate a particular security mechanism used to protect the
     WS-MetadataExchange operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2x1x2074" id="iddiv2x1x2074"/>12.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2x1x2039" id="iddiv2x1x2039"/>12.1 MetadataExchange Assertion</h3><p>
      Services indicate support for the WS-MetadataExchange specification 
      through the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1910,7 +1906,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="References" id="References"/>15 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2330" id="iddiv2x1x2330"/>15.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+<h3><a name="iddiv2x1x2295" id="iddiv2x1x2295"/>15.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
          WS-I Profile, Basic Profile Version 1.2
         </cite></a>
         , R. Chumbley, et al, Editors.
@@ -2465,4 +2461,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11849">11849</a></td></tr><tr><td> 2011/01/26 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11867">11867</a></td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11850">11850</a></td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</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=11882">11882</a></td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</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.214
retrieving revision 1.215
diff -u -d -r1.214 -r1.215
--- wseventing.xml	2 Feb 2011 00:44:31 -0000	1.214
+++ wseventing.xml	7 Feb 2011 23:51:02 -0000	1.215
@@ -2099,27 +2099,6 @@
     is defined for the fault.<phrase/>
    </p>
    
-   <p>
-    For SOAP 1.2, the <kw>[Code]</kw> property MUST be either
-    "Sender" or "Receiver". These properties are serialized
-    into text XML as follows:
-   </p>
-   
-   <table id="soapver" border="1">
-    <tbody>
-     <tr>
-      <th> SOAP Version </th>
-      <th> Sender </th>
-      <th> Receiver </th>
-     </tr>
-     <tr>
-      <td> SOAP 1.2 </td>
-      <td> s12:Sender </td>
-      <td> s12:Receiver </td>
-     </tr>
-    </tbody>
-   </table>
-   
    <p>The properties above bind to a SOAP 1.2 fault as follows:</p>
    <example>
     <eg>&lt;s12:Envelope&gt;
@@ -5252,6 +5231,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11703">11703</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/02/07 </td>
+      <td> DD </td>
+      <td> Added resolution of issue
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Received on Monday, 7 February 2011 23:51:07 UTC