W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > March 2010

WWW/2002/ws/ra/edcopies wsenum.html,1.124,1.125 wsenum.xml,1.115,1.116 wseventing.html,1.173,1.174 wseventing.xml,1.166,1.167 wsmex.html,1.113,1.114 wsmex.xml,1.100,1.101 wst.html,1.114,1.115 wst.xml,1.111,1.112

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 30 Mar 2010 23:40:00 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1Nwl2O-00012z-K3@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv3923

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
	wsmex.html wsmex.xml wst.html wst.xml 
Log Message:
9266


Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -d -r1.111 -r1.112
--- wst.xml	16 Mar 2010 19:49:32 -0000	1.111
+++ wst.xml	30 Mar 2010 23:39:58 -0000	1.112
@@ -197,7 +197,7 @@
             </def>
           </gitem>
           <gitem>
-            <label>Resource factory</label>
+            <label>Resource Factory</label>
             <def>
               <p>A Web service that is capable of creating new resources using the
          Create operation defined in this specification.</p>
@@ -1645,12 +1645,12 @@
    <head>WS-Transfer Metadata</head>
 
    <p>
-    An endpoint MAY indicate that it supports WS-Transfer, or its features,
+    An endpoint MAY indicate its support of WS-Transfer, or its features,
     by including the WS-Transfer TransferResource or TransferResourceFactory
     Policy assertions within its WSDL. By
     doing so the endpoint is indicating that the corresponding WS-Transfer
-    operations are supported by that endpoint even though they do not
-    explicitly appear in its WSDL
+    operations are supported by that endpoint even though they are implicit
+    and do not explicitly appear in its WSDL
     (i.e. the WS-Transfer operations do not appear in the WSDL that MAY be 
     retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
    </p>
@@ -1667,7 +1667,7 @@
    <p>
     This WS-Transfer WSDL can be annotated to indicate any endpoint
     specific metadata that might be needed by clients interacting with
-    this service's WS-Transfer operations.   
+    the WS-Transfer operations.   
     For example, the WSDL might have policy assertions
     that indicate a particular security mechanism used to protect
     the WS-Transfer operations supported by this endpoint.
@@ -1686,34 +1686,6 @@
 
     <p>
      This specification defines a policy assertion (wst:TransferResource).
-     The wst:TransferResource policy assertion applies to the endpoint 
-     policy subject.
-    </p>
-
-    <p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
-     wsdl20:binding. 
-    </p>
-
-    <p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-Transfer is REQUIRED to communicate with the
-     subject and that the subject is a WS-Transfer Resource.
-    </p>
-    
-    <p>
-     In order to indicate that the subject supports WS-Transfer
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p>
-
-    <p>
      The normative outline of this assertion is:
     </p>
 
@@ -1741,9 +1713,13 @@
       <label> /wst:TransferResource </label>
        <def>
         <p>
-         This policy assertion specifies that WS-Transfer protocol MUST be 
-         used when communicating with this endpoint and that the subject is a 
-         Transfer Resource. This assertion has Endpoint Policy Subject.  Unless 
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is a Transfer
+         resource
+         and the WS-Transfer protocol MUST
+         be used when communicating with this endpoint.
+         
+         Unless 
          support for OPTIONAL operations is explicitly indicated by either 
          the PutOperationSupported or DeleteOperationSupported parameters only 
          the Get operation is supported.
@@ -1852,34 +1828,6 @@
     <p>
      This specification defines a policy assertion 
      (wst:TransferResourceFactory).
-     The wst:TransferResourceFactory policy assertion applies to the endpoint 
-     policy subject.
-    </p>
-
-    <p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
-     wsdl20:binding.
-    </p>
-
-    <p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-Transfer is REQUIRED to communicate with the
-     subject and that the subject is a WS-Transfer Resource Factory. 
-    </p>
-    
-    <p>
-     In order to indicate that the subject supports WS-Transfer
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p>
-
-    <p>
      The normative outline of this assertion is:
     </p>
 
@@ -1903,9 +1851,11 @@
       <label> /wst:TransferResourceFactory </label>
        <def>
         <p>
-         This policy assertion specifies that WS-Transfer Create operation 
-         MUST be used when communicating with this endpoint. This assertion 
-         has Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is a resource 
+         factory
+         and the WS-Transfer protocol MUST
+         be used when communicating with this endpoint.
         </p>
        </def>
      </gitem>
@@ -2892,6 +2842,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/03/30 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.173
retrieving revision 1.174
diff -u -d -r1.173 -r1.174
--- wseventing.html	30 Mar 2010 22:20:57 -0000	1.173
+++ wseventing.html	30 Mar 2010 23:39:58 -0000	1.174
@@ -77,20 +77,20 @@
 8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
 9 <a href="#metadata">WS-Eventing Metadata</a><br/>
 &nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2176">EventSource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2287">SubscriptionManager Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2279">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="#iddiv2_1_2369">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2503">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2353">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2487">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="#iddiv3_1_2705">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2742">Bindings for Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2747">Binding for Unwrapped Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2765">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2689">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2726">Bindings for Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2731">Binding for Unwrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2749">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="#iddiv3_1_2792">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2776">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/>
@@ -1502,11 +1502,12 @@
     message.
    </p></div><div class="div1">
 <h2><a name="metadata" id="metadata"/>9 WS-Eventing Metadata</h2><p>
-    An endpoint MAY indicate that it supports WS-Eventing, or its features,
+    An endpoint MAY indicate its support of WS-Eventing, or its features,
     by including the WS-Eventing EventSource or SubscriptionManager Policy 
     assertions within its WSDL. By
     doing so the endpoint is indicating that the corresponding WS-Eventing
-    operations are supported by that endpoint even though they do not
+    operations are supported by that endpoint even though they are implicit
+    and do not
     explicitly appear in its WSDL (ie. the WS-Eventing operations do not
     appear in the WSDL that MAY be retrievable by using WS-MetadataExchange
     GetWSDL to that endpoint).
@@ -1520,7 +1521,7 @@
    </p><p>
     This WS-Eventing WSDL can be annotated to indicate any endpoint
     specific metadata that might be needed by clients interacting with
-    this service's WS-Eventing operations.   For example, the WSDL MAY 
+    the WS-Eventing operations.   For example, the WSDL MAY 
     have policy assertions
     that indicate a particular security mechanism used to protect
     the WS-Eventing operations supported by this endpoint.
@@ -1531,26 +1532,7 @@
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
      Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
     </p><p>
-     This specification defines a policy assertion (wse:EventSource).  The
-     wse:EventSource policy assertion applies to the endpoint policy subject.
-    </p><p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl:portType,
-     wsdl11:port or
-     wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:interface,
-     wsdl20:endpoint or wsdl20:binding. 
-    </p><p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-Eventing is REQUIRED to communicate with the
-     subject and that the subject is a WS-Eventing event source. 
-    </p><p>
-     In order to indicate that the subject supports WS-Eventing
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p><p>
+     This specification defines a policy assertion (wse:EventSource). 
      The normative outline of this assertion is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wse:EventSource ...&gt;
   &lt;wse:DateTimeSupported .../&gt; ?
@@ -1570,9 +1552,10 @@
      The following describes additional, normative constraints on the
      outline listed above:
     </p><dl><dt class="label"> /wse:EventSource </dt><dd><p>
-         A policy assertion that specifies that WS-Eventing protocol MUST be 
-         used when communicating with this endpoint and that the subject is 
-         an event source. This assertion has Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is an event source
+         and the WS-Eventing protocol MUST
+         be used when communicating with this endpoint.
         </p></dd><dt class="label"> /wse:EventSource/wse:DateTimeSupported </dt><dd><p>
          When present, this OPTIONAL parameter indicates support for 
          expiration time expressed as specific time (rather than duration).
@@ -1626,7 +1609,7 @@
      Note: The WS-RA WG is interested in Last Call feedback on the use
      of nested policy expressions.
     </p></div><div class="div2">
-<h3><a name="iddiv2_1_2287" id="iddiv2_1_2287"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2279" id="iddiv2_1_2279"/>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
@@ -1634,26 +1617,6 @@
      Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
     </p><p>
      This specification defines a policy assertion (wse:SubscriptionManager).
-     The wse:SubscriptionManager policy assertion applies to the endpoint 
-     policy subject.
-    </p><p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl:portType,
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
-     wsdl20:binding. 
-    </p><p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-Eventing is REQUIRED to communicate with the
-     subject and that the subject is a WS-Eventing subscription manager.
-    </p><p>
-     In order to indicate that the subject supports WS-Eventing
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p><p>
      The normative outline of this assertion is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wse:SubscriptionManager ...&gt;
   &lt;wse:DateTimeSupported .../&gt; ?
@@ -1665,9 +1628,11 @@
      The following describes additional, normative constraints on the
      outline listed above:
     </p><dl><dt class="label"> /wse:SubscriptionManager </dt><dd><p>
-         A policy assertion that specifies that WS-Eventing protocol MUST be 
-         used when communicating with this endpoint and that the subject is 
-         a subscription manager. This assertion has Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is an subscription
+         manager
+         and the WS-Eventing protocol MUST
+         be used when communicating with this endpoint.
         </p></dd><dt class="label"> /wse:SubscriptionManager/wse:DateTimeSupported </dt><dd><p>
          When present, this OPTIONAL parameter indicates support for 
          expiration time expressed as specific time (rather than duration).
@@ -1724,7 +1689,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="iddiv2_1_2369" id="iddiv2_1_2369"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2353" id="iddiv2_1_2353"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.
@@ -1776,7 +1741,7 @@
        , A. Vedamuthu, et al., Editors.
        World Wide Web Consortium (W3C), 4 September 2007.
       Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2503" id="iddiv2_1_2503"/>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="iddiv2_1_2487" id="iddiv2_1_2487"/>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>
@@ -1880,7 +1845,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="idexample_1_2695" id="idexample_1_2695"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wsevd:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2679" id="idexample_1_2679"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wsevd:EventDescriptions 
 (02)        targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)        xmlns:wse="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch"&gt;
@@ -1900,7 +1865,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="iddiv3_1_2705" id="iddiv3_1_2705"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2689" id="iddiv3_1_2689"/>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>.
@@ -1938,7 +1903,7 @@
       representation is the Event Description metadata. The data can be
       retrieved via an HTTP GET to the specified URL.
      </p></div><div class="div3">
-<h4><a name="iddiv3_1_2742" id="iddiv3_1_2742"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2726" id="iddiv3_1_2726"/>A.1.2 Bindings for Event Descriptions</h4><p>
       For any Notification Format it MUST be possible to determine how a 
       given wse:eventType will appear on the wire as a notification in a 
       subscription created with that format. The following sections define 
@@ -1950,7 +1915,7 @@
       Format, implementations MAY provide a Notification WSDL (see below) 
       that explicitly describes the notification operations. 
      </p><div class="div4">
-<h5><a name="iddiv4_1_2747" id="iddiv4_1_2747"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2731" id="iddiv4_1_2731"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
        The information about an Event Type contained in the wse:eventType 
        element binds to a Unwrapped Notification for that type as follows:
       </p><ul><li><p>
@@ -1964,7 +1929,7 @@
          of the wse:eventType element corresponding to the type of the 
          event being transmitted.
         </p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2765" id="iddiv4_1_2765"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2749" id="iddiv4_1_2749"/>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>
@@ -1988,7 +1953,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="idexample_1_2786" id="idexample_1_2786"/>Example A-4: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2770" id="idexample_1_2770"/>Example A-4: 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/"
@@ -2023,7 +1988,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="iddiv3_1_2792" id="iddiv3_1_2792"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2776" id="iddiv3_1_2776"/>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>.
@@ -2712,4 +2677,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9320">9320</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</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=9031">9031</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</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.114
retrieving revision 1.115
diff -u -d -r1.114 -r1.115
--- wst.html	16 Mar 2010 19:49:32 -0000	1.114
+++ wst.html	30 Mar 2010 23:39:58 -0000	1.115
@@ -60,11 +60,11 @@
 6 <a href="#Security_Considerations">Security Considerations</a><br/>
 7 <a href="#metadata">WS-Transfer Metadata</a><br/>
 &nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2_1_1370">TransferResource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2_1_1460">TransferResourceFactory Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2_1_1452">TransferResourceFactory Assertion</a><br/>
 8 <a href="#acks">Acknowledgements</a><br/>
 9 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_1533">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_1706">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_1517">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_1690">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/>
@@ -136,7 +136,7 @@
                 and can be represented by an XML Information Set.
                 The representation can be retrieved using the Get operation 
                 and can be manipulated using the Put and Delete operations.
-              </p></dd><dt class="label">Resource factory</dt><dd><p>A Web service that is capable of creating new resources using the
+              </p></dd><dt class="label">Resource Factory</dt><dd><p>A Web service that is capable of creating new resources using the
          Create operation defined in this specification.</p></dd></dl></div><div class="div2">
 <h3><a name="namespaces" id="namespaces"/>2.2 XML Namespaces</h3><p>
      The XML Namespace URI that MUST be used by implementations of this
@@ -942,12 +942,12 @@
      of this specification. That said, care SHOULD be taken to ensure that
      minimal state is saved prior to any authenticating sequences.</p></li></ul></div><div class="div1">
 <h2><a name="metadata" id="metadata"/>7 WS-Transfer Metadata</h2><p>
-    An endpoint MAY indicate that it supports WS-Transfer, or its features,
+    An endpoint MAY indicate its support of WS-Transfer, or its features,
     by including the WS-Transfer TransferResource or TransferResourceFactory
     Policy assertions within its WSDL. By
     doing so the endpoint is indicating that the corresponding WS-Transfer
-    operations are supported by that endpoint even though they do not
-    explicitly appear in its WSDL
+    operations are supported by that endpoint even though they are implicit
+    and do not explicitly appear in its WSDL
     (i.e. the WS-Transfer operations do not appear in the WSDL that MAY be 
     retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
    </p><p>
@@ -960,7 +960,7 @@
    </p><p>
     This WS-Transfer WSDL can be annotated to indicate any endpoint
     specific metadata that might be needed by clients interacting with
-    this service's WS-Transfer operations.   
+    the WS-Transfer operations.   
     For example, the WSDL might have policy assertions
     that indicate a particular security mechanism used to protect
     the WS-Transfer operations supported by this endpoint.
@@ -973,26 +973,6 @@
      Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
     </p><p>
      This specification defines a policy assertion (wst:TransferResource).
-     The wst:TransferResource policy assertion applies to the endpoint 
-     policy subject.
-    </p><p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
-     wsdl20:binding. 
-    </p><p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-Transfer is REQUIRED to communicate with the
-     subject and that the subject is a WS-Transfer Resource.
-    </p><p>
-     In order to indicate that the subject supports WS-Transfer
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p><p>
      The normative outline of this assertion is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wst:TransferResource ...&gt;
   &lt;wst:PutOperationSupported .../&gt; ?
@@ -1007,9 +987,13 @@
      The following describes additional, normative constraints on the
      outline listed above:
     </p><dl><dt class="label"> /wst:TransferResource </dt><dd><p>
-         This policy assertion specifies that WS-Transfer protocol MUST be 
-         used when communicating with this endpoint and that the subject is a 
-         Transfer Resource. This assertion has Endpoint Policy Subject.  Unless 
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is a Transfer
+         resource
+         and the WS-Transfer protocol MUST
+         be used when communicating with this endpoint.
+         
+         Unless 
          support for OPTIONAL operations is explicitly indicated by either 
          the PutOperationSupported or DeleteOperationSupported parameters only 
          the Get operation is supported.
@@ -1046,7 +1030,7 @@
      Note: The WS-RA WG is interested in Last Call feedback on the use
      of nested policy expressions.
     </p></div><div class="div2">
-<h3><a name="iddiv2_1_1460" id="iddiv2_1_1460"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1452" id="iddiv2_1_1452"/>7.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
@@ -1055,26 +1039,6 @@
     </p><p>
      This specification defines a policy assertion 
      (wst:TransferResourceFactory).
-     The wst:TransferResourceFactory policy assertion applies to the endpoint 
-     policy subject.
-    </p><p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
-     wsdl20:binding.
-    </p><p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-Transfer is REQUIRED to communicate with the
-     subject and that the subject is a WS-Transfer Resource Factory. 
-    </p><p>
-     In order to indicate that the subject supports WS-Transfer
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p><p>
      The normative outline of this assertion is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wst:TransferResourceFactory ...&gt;
   &lt;wst:Dialect URI="<em>xs:anyURI</em>" ...&gt;
@@ -1085,9 +1049,11 @@
      The following describes additional, normative constraints on the
      outline listed above:
     </p><dl><dt class="label"> /wst:TransferResourceFactory </dt><dd><p>
-         This policy assertion specifies that WS-Transfer Create operation 
-         MUST be used when communicating with this endpoint. This assertion 
-         has Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is a resource 
+         factory
+         and the WS-Transfer protocol MUST
+         be used when communicating with this endpoint.
         </p></dd><dt class="label"> /wst:TransferResourceFactory/wst:Dialect </dt><dd><p>
          When present, this OPTIONAL parameter indicates support for the 
          specified Dialect IRI.
@@ -1136,7 +1102,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="iddiv2_1_1533" id="iddiv2_1_1533"/>9.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_1517" id="iddiv2_1_1517"/>9.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.
@@ -1204,7 +1170,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="iddiv2_1_1706" id="iddiv2_1_1706"/>9.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="iddiv2_1_1690" id="iddiv2_1_1690"/>9.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.
@@ -1569,4 +1535,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9032">9032</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</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=8198">8198</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</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.100
retrieving revision 1.101
diff -u -d -r1.100 -r1.101
--- wsmex.xml	30 Mar 2010 22:20:57 -0000	1.100
+++ wsmex.xml	30 Mar 2010 23:39:58 -0000	1.101
@@ -2035,7 +2035,8 @@
     An endpoint MAY indicate that it supports a specific feature by 
     including the feature's policy assertion within its WSDL. By doing so, 
     the endpoint is indicating that feature operations are 
-    supported by that endpoint even though they do not explicitly appear in 
+    supported by that endpoint even though they are implicit
+    and do not explicitly appear in 
     its WSDL.  An example of this is an endpoint that indicates the use 
     of WS-Transfer <bibref ref="WS-Transfer"/> by the use of the 
     wst:TransferResource WS-Policy <bibref ref="wspolicy"/> assertion.
@@ -2288,13 +2289,13 @@
    <head>WS-MetadataExchange Metadata</head>
 
    <p>
-    An endpoint MAY indicate that it supports WS-MetadataExchange, or its 
+    An endpoint MAY indicate its support of WS-MetadataExchange, or its 
     features,
     by including the MetadataExchange Policy assertion within its WSDL. By
     doing so the endpoint is indicating that the corresponding 
     WS-MetadataExchange
-    operations are supported by that endpoint even though they do not
-    explicitly appear in its WSDL 
+    operations are supported by that endpoint even though they are implicit
+    and do not explicitly appear in its WSDL 
     (i.e. the WS-MetadataExchange operations do not appear in the WSDL that 
     MAY be retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
    </p>
@@ -2310,7 +2311,7 @@
    <p>
     The WS-MetadataExchange WSDL can be annotated to indicate any endpoint
     specific metadata that might be needed by clients interacting with
-    this service's WS-MetadataExchange operations.  For example, the WSDL 
+    the WS-MetadataExchange operations.  For example, the WSDL 
     MAY have policy assertions that
     indicate a particular security mechanism used to protect the
     WS-MetadataExchange operations supported by this endpoint.
@@ -2328,34 +2329,6 @@
 
     <p>
      This specification defines a policy assertion (mex:MetadataExchange).  
-     The mex:MetadataExchange policy assertion applies to the endpoint 
-     policy subject.
-    </p>
-
-    <p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl11:portType, 
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
-     wsdl20:binding. 
-    </p>
-
-    <p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-MetadataExchange is REQUIRED to communicate with 
-     the subject and that the subject supports WS-MetadataExchange. 
-    </p>
-    
-    <p>
-     In order to indicate that the subject supports WS-MetadataExchange
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p>
-
-    <p>
      The normative outline of this assertion is:
     </p>
 
@@ -2384,9 +2357,10 @@
       <label> /mex:MetadataExchange </label>
        <def>
         <p>
-         This policy assertion specifies that WS-MetadataExchange protocol 
-         MUST be used when communicating with this service endpoint. This 
-         assertion has Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that 
+         the WS-MetadataExchange protocol MUST
+         be used when communicating with this endpoint.
         </p>
        </def>
      </gitem>
@@ -3478,6 +3452,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/03/30 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.124
retrieving revision 1.125
diff -u -d -r1.124 -r1.125
--- wsenum.html	30 Mar 2010 20:49:31 -0000	1.124
+++ wsenum.html	30 Mar 2010 23:39:57 -0000	1.125
@@ -72,8 +72,8 @@
 &nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_2023">Enumeration Assertion</a><br/>
 7 <a href="#acks">Acknowledgements</a><br/>
 8 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_2138">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2324">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_2130">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2316">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/>
@@ -1287,12 +1287,12 @@
       authenticating sequences.
      </p></li></ul></div><div class="div1">
 <h2><a name="metadata" id="metadata"/>6 WS-Enumeration Metadata</h2><p>
-    An endpoint MAY indicate that it supports WS-Enumeration, or its features,
+    An endpoint MAY indicate its support of WS-Enumeration, or its features,
     by including the WS-Enumeration DataSource Policy assertion within its 
     WSDL. By
     doing so the endpoint is indicating that the corresponding WS-Enumeration
-    operations are supported by that endpoint even though they do not
-    explicitly appear in its WSDL
+    operations are supported by that endpoint even though they are implicit
+    and do not explicitly appear in its WSDL
     (i.e. the WS-Enumeration operations do not appear in the WSDL that MAY 
     be retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
    </p><p>
@@ -1304,7 +1304,7 @@
    </p><p>
     This WS-Enumeration WSDL can be annotated to indicate any endpoint 
     specific metadata that might be needed by clients interacting with 
-    this service's WS-Enumeration operations.   For example, the WSDL MAY 
+    the WS-Enumeration operations.   For example, the WSDL MAY 
     have policy assertions 
     that indicate a particular security mechanism used to protect 
     the WS-Enumeration operations supported by this endpoint. 
@@ -1315,28 +1315,7 @@
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy - 
      Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications. 
     </p><p>
-     This specification defines a policy assertion 
-     (wsenu:DataSource).  The 
-     wsenu:DataSource policy assertion applies to the 
-     endpoint policy subject.
-    </p><p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl11:portType, 
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint 
-     or wsdl20:binding. 
-    </p><p>
-     The meaning of this assertion, when present in a policy 
-     alternative, is that WS-Enumeration is REQUIRED to communicate with the 
-     subject and that the subject is a WS-Enumeration data source.
-    </p><p>
-     In order to indicate that the subject supports WS-Enumeration 
-     but does not require its use, an additional policy alternative SHOULD 
-     be provided which does not contain this assertion. The compact 
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional 
-     attribute) provided by WS-Policy MAY be used to indicate two policy 
-     alternatives, one which contains the policy assertion, and another 
-     which does not. 
-    </p><p>
+     This specification defines a policy assertion (wsenu:DataSource).  
      The normative outline of this assertion is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;wsenu:DataSource ...&gt;
  &lt;wsenu:FilterDialect URI="<em>xs:anyURI</em>" ...&gt; 
@@ -1352,9 +1331,10 @@
      The following describes additional, normative constraints on the 
      outline listed above:
     </p><dl><dt class="label"> /wsenu:DataSource </dt><dd><p>
-         A policy assertion that specifies that WS-Enumeration protocol MUST 
-         be used when communicating with this endpoint. This assertion has 
-         Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is a data source
+         and the WS-Enumeration protocol MUST 
+         be used when communicating with this endpoint. 
         </p></dd><dt class="label"> /wsenu:DataSource/wsenu:FilterDialect </dt><dd><p>
          When present, this OPTIONAL parameter indicates support for the 
          specified Filter Dialect IRI.
@@ -1432,7 +1412,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2138" id="iddiv2_1_2138"/>8.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2130" id="iddiv2_1_2130"/>8.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author. 
@@ -1504,7 +1484,7 @@
        , J. Clark, S. DeRose, Editors.
        World Wide Web Consortium (W3C), 16 November 1999. 
       Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2324" id="iddiv2_1_2324"/>8.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="iddiv2_1_2316" id="iddiv2_1_2316"/>8.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>
@@ -2128,4 +2108,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9095">9095</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=9095">9095</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</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.115
retrieving revision 1.116
diff -u -d -r1.115 -r1.116
--- wsenum.xml	30 Mar 2010 20:49:31 -0000	1.115
+++ wsenum.xml	30 Mar 2010 23:39:58 -0000	1.116
@@ -2409,12 +2409,12 @@
    <head>WS-Enumeration Metadata</head>
 
    <p>
-    An endpoint MAY indicate that it supports WS-Enumeration, or its features,
+    An endpoint MAY indicate its support of WS-Enumeration, or its features,
     by including the WS-Enumeration DataSource Policy assertion within its 
     WSDL. By
     doing so the endpoint is indicating that the corresponding WS-Enumeration
-    operations are supported by that endpoint even though they do not
-    explicitly appear in its WSDL
+    operations are supported by that endpoint even though they are implicit
+    and do not explicitly appear in its WSDL
     (i.e. the WS-Enumeration operations do not appear in the WSDL that MAY 
     be retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
    </p>
@@ -2430,7 +2430,7 @@
    <p>
     This WS-Enumeration WSDL can be annotated to indicate any endpoint 
     specific metadata that might be needed by clients interacting with 
-    this service's WS-Enumeration operations.   For example, the WSDL MAY 
+    the WS-Enumeration operations.   For example, the WSDL MAY 
     have policy assertions 
     that indicate a particular security mechanism used to protect 
     the WS-Enumeration operations supported by this endpoint. 
@@ -2447,36 +2447,7 @@
     </p>
  
     <p>
-     This specification defines a policy assertion 
-     (wsenu:DataSource).  The 
-     wsenu:DataSource policy assertion applies to the 
-     endpoint policy subject.
-    </p>
- 
-    <p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl11:portType, 
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint 
-     or wsdl20:binding. 
-    </p>
-
-    <p>
-     The meaning of this assertion, when present in a policy 
-     alternative, is that WS-Enumeration is REQUIRED to communicate with the 
-     subject and that the subject is a WS-Enumeration data source.
-    </p>
-
-    <p>
-     In order to indicate that the subject supports WS-Enumeration 
-     but does not require its use, an additional policy alternative SHOULD 
-     be provided which does not contain this assertion. The compact 
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional 
-     attribute) provided by WS-Policy MAY be used to indicate two policy 
-     alternatives, one which contains the policy assertion, and another 
-     which does not. 
-    </p>
-
-    <p>
+     This specification defines a policy assertion (wsenu:DataSource).  
      The normative outline of this assertion is:
     </p>
 
@@ -2505,9 +2476,10 @@
       <label> /wsenu:DataSource </label>
        <def>
         <p>
-         A policy assertion that specifies that WS-Enumeration protocol MUST 
-         be used when communicating with this endpoint. This assertion has 
-         Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is a data source
+         and the WS-Enumeration protocol MUST 
+         be used when communicating with this endpoint. 
         </p>
        </def>
      </gitem>
@@ -4017,6 +3989,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9095">9095</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/03/30 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -d -r1.113 -r1.114
--- wsmex.html	30 Mar 2010 22:20:57 -0000	1.113
+++ wsmex.html	30 Mar 2010 23:39:58 -0000	1.114
@@ -72,8 +72,8 @@
 12 <a href="#bootstrapping">Boostrapping Metadata Retrieval</a><br/>
 13 <a href="#acks">Acknowledgements</a><br/>
 14 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;14.1 <a href="#iddiv2_1_1773">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;14.2 <a href="#iddiv2_1_1946">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;14.1 <a href="#iddiv2_1_1765">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;14.2 <a href="#iddiv2_1_1938">Informative 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/>
@@ -1225,7 +1225,8 @@
     An endpoint MAY indicate that it supports a specific feature by 
     including the feature's policy assertion within its WSDL. By doing so, 
     the endpoint is indicating that feature operations are 
-    supported by that endpoint even though they do not explicitly appear in 
+    supported by that endpoint even though they are implicit
+    and do not explicitly appear in 
     its WSDL.  An example of this is an endpoint that indicates the use 
     of WS-Transfer <a href="#WS-Transfer">[WS-Transfer]</a> by the use of the 
     wst:TransferResource WS-Policy <a href="#wspolicy">[WS-Policy]</a> assertion.
@@ -1397,13 +1398,13 @@
       replay of application messages.
      </p></li></ul></div><div class="div1">
 <h2><a name="metadata" id="metadata"/>11 WS-MetadataExchange Metadata</h2><p>
-    An endpoint MAY indicate that it supports WS-MetadataExchange, or its 
+    An endpoint MAY indicate its support of WS-MetadataExchange, or its 
     features,
     by including the MetadataExchange Policy assertion within its WSDL. By
     doing so the endpoint is indicating that the corresponding 
     WS-MetadataExchange
-    operations are supported by that endpoint even though they do not
-    explicitly appear in its WSDL 
+    operations are supported by that endpoint even though they are implicit
+    and do not explicitly appear in its WSDL 
     (i.e. the WS-MetadataExchange operations do not appear in the WSDL that 
     MAY be retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
    </p><p>
@@ -1415,7 +1416,7 @@
    </p><p>
     The WS-MetadataExchange WSDL can be annotated to indicate any endpoint
     specific metadata that might be needed by clients interacting with
-    this service's WS-MetadataExchange operations.  For example, the WSDL 
+    the WS-MetadataExchange operations.  For example, the WSDL 
     MAY have policy assertions that
     indicate a particular security mechanism used to protect the
     WS-MetadataExchange operations supported by this endpoint.
@@ -1427,26 +1428,6 @@
      Attachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a> specifications.
     </p><p>
      This specification defines a policy assertion (mex:MetadataExchange).  
-     The mex:MetadataExchange policy assertion applies to the endpoint 
-     policy subject.
-    </p><p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl11:portType, 
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
-     wsdl20:binding. 
-    </p><p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-MetadataExchange is REQUIRED to communicate with 
-     the subject and that the subject supports WS-MetadataExchange. 
-    </p><p>
-     In order to indicate that the subject supports WS-MetadataExchange
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p><p>
      The normative outline of this assertion is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;mex:MetadataExchange ...&gt;
   &lt;mex:GetMetadataSupported ...&gt;
@@ -1462,9 +1443,10 @@
      The following describes additional, normative constraints on the
      outline listed above:
     </p><dl><dt class="label"> /mex:MetadataExchange </dt><dd><p>
-         This policy assertion specifies that WS-MetadataExchange protocol 
-         MUST be used when communicating with this service endpoint. This 
-         assertion has Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that 
+         the WS-MetadataExchange protocol MUST
+         be used when communicating with this endpoint.
         </p></dd><dt class="label"> /mex:MetadataExchange/mex:GetMetadataSupported </dt><dd><p>
          When present, this OPTIONAL parameter indicates that the 
          GetMetadata operation is supported by this endpoint.  
@@ -1588,7 +1570,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="References" id="References"/>14 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1773" id="iddiv2_1_1773"/>14.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_1765" id="iddiv2_1_1765"/>14.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.
@@ -1655,7 +1637,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="iddiv2_1_1946" id="iddiv2_1_1946"/>14.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_1938" id="iddiv2_1_1938"/>14.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
         OASIS Standard, "Web Services Secure Conversation
           (WS-SecureConversation) 1.4"
        </cite></a>
@@ -1983,4 +1965,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8289">8289</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</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=9031">9031</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</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.166
retrieving revision 1.167
diff -u -d -r1.166 -r1.167
--- wseventing.xml	30 Mar 2010 22:20:57 -0000	1.166
+++ wseventing.xml	30 Mar 2010 23:39:58 -0000	1.167
@@ -2677,11 +2677,12 @@
    <head>WS-Eventing Metadata</head>
 
    <p>
-    An endpoint MAY indicate that it supports WS-Eventing, or its features,
+    An endpoint MAY indicate its support of WS-Eventing, or its features,
     by including the WS-Eventing EventSource or SubscriptionManager Policy 
     assertions within its WSDL. By
     doing so the endpoint is indicating that the corresponding WS-Eventing
-    operations are supported by that endpoint even though they do not
+    operations are supported by that endpoint even though they are implicit
+    and do not
     explicitly appear in its WSDL (ie. the WS-Eventing operations do not
     appear in the WSDL that MAY be retrievable by using WS-MetadataExchange
     GetWSDL to that endpoint).
@@ -2699,7 +2700,7 @@
    <p>
     This WS-Eventing WSDL can be annotated to indicate any endpoint
     specific metadata that might be needed by clients interacting with
-    this service's WS-Eventing operations.   For example, the WSDL MAY 
+    the WS-Eventing operations.   For example, the WSDL MAY 
     have policy assertions
     that indicate a particular security mechanism used to protect
     the WS-Eventing operations supported by this endpoint.
@@ -2716,34 +2717,7 @@
     </p>
 
     <p>
-     This specification defines a policy assertion (wse:EventSource).  The
-     wse:EventSource policy assertion applies to the endpoint policy subject.
-    </p>
-
-    <p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl:portType,
-     wsdl11:port or
-     wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:interface,
-     wsdl20:endpoint or wsdl20:binding. 
-    </p>
-
-    <p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-Eventing is REQUIRED to communicate with the
-     subject and that the subject is a WS-Eventing event source. 
-    </p>
-
-    <p>
-     In order to indicate that the subject supports WS-Eventing
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p>
-
-    <p>
+     This specification defines a policy assertion (wse:EventSource). 
      The normative outline of this assertion is:
     </p>
 
@@ -2776,9 +2750,10 @@
       <label> /wse:EventSource </label>
        <def>
         <p>
-         A policy assertion that specifies that WS-Eventing protocol MUST be 
-         used when communicating with this endpoint and that the subject is 
-         an event source. This assertion has Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is an event source
+         and the WS-Eventing protocol MUST
+         be used when communicating with this endpoint.
         </p>
        </def>
      </gitem>
@@ -2916,34 +2891,6 @@
 
     <p>
      This specification defines a policy assertion (wse:SubscriptionManager).
-     The wse:SubscriptionManager policy assertion applies to the endpoint 
-     policy subject.
-    </p>
-
-    <p>
-     For WSDL 1.1, these assertions MAY be attached to wsdl:portType,
-     wsdl11:port or wsdl11:binding. 
-     For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
-     wsdl20:binding. 
-    </p>
-
-    <p>
-     The meaning of this assertion, when present in a policy
-     alternative, is that WS-Eventing is REQUIRED to communicate with the
-     subject and that the subject is a WS-Eventing subscription manager.
-    </p>
-
-    <p>
-     In order to indicate that the subject supports WS-Eventing
-     but does not require its use, an additional policy alternative SHOULD
-     be provided which does not contain this assertion. The compact
-     authoring style for an OPTIONAL policy assertion (the wsp:Optional
-     attribute) provided by WS-Policy MAY be used to indicate two policy
-     alternatives, one which contains the policy assertion, and another
-     which does not.
-    </p>
-
-    <p>
      The normative outline of this assertion is:
     </p>
 
@@ -2968,9 +2915,11 @@
       <label> /wse:SubscriptionManager </label>
        <def>
         <p>
-         A policy assertion that specifies that WS-Eventing protocol MUST be 
-         used when communicating with this endpoint and that the subject is 
-         a subscription manager. This assertion has Endpoint Policy Subject.
+         This policy assertion has Endpoint Policy Subject. When present in a
+         policy alternative, it indicates that the subject is an subscription
+         manager
+         and the WS-Eventing protocol MUST
+         be used when communicating with this endpoint.
         </p>
        </def>
      </gitem>
@@ -5046,6 +4995,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/03/30 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Tuesday, 30 March 2010 23:40:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 30 March 2010 23:40:12 GMT