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

WWW/2002/ws/ra/edcopies wsenum.html,1.95,1.96 wseventing.html,1.138,1.139 wsmex.html,1.89,1.90 wst.html,1.88,1.89

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 01 Dec 2009 23:55:39 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1NFcZH-0003bX-QX@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv13767

Modified Files:
	wsenum.html wseventing.html wsmex.html wst.html 
Log Message:
8201


Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.88
retrieving revision 1.89
diff -u -d -r1.88 -r1.89
--- wst.html	17 Nov 2009 22:05:23 -0000	1.88
+++ wst.html	1 Dec 2009 23:55:37 -0000	1.89
@@ -58,12 +58,12 @@
 &nbsp;&nbsp;&nbsp;5.3 <a href="#PutDenied">PutDenied</a><br/>
 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_1343">TransferResource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2_1_1413">TransferResourceFactory Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2_1_1341">TransferResource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2_1_1411">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_1466">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_1639">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_1464">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_1637">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="#changelog">Change Log</a><br/>
@@ -237,14 +237,13 @@
      however receivers of those messages MUST support those OPTIONAL
      elements and attributes, unless other behavior is explicitly defined
      by this specification.
-    </p><p>
-     A compliant SOAP Node that implements a resource MUST
-     provide the Get operation as defined in this specification, and MAY provide
-     the Put and Delete operations.
     </p></div></div><div class="div1">
 <h2><a name="resourceOperations" id="resourceOperations"/>3 Resource Operations</h2><div class="div2">
-<h3><a name="Get" id="Get"/>3.1 Get</h3><p>This specification defines one Web service operation (Get) for fetching a
-one-time snapshot of the representation of a resource.</p><p>The Get request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
+<h3><a name="Get" id="Get"/>3.1 Get</h3><p>
+         This specification defines one Web service operation (Get) for 
+         fetching a one-time snapshot of the representation of a resource.
+         This operation MUST be supported by compliant WS-Transfer resources.
+        </p><p>The Get request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-tra/Get
 
 <b>[Body]</b>
@@ -360,8 +359,9 @@
   &lt;/xxx:Customer&gt;</pre></div></div></div><div class="div2">
 <h3><a name="Put" id="Put"/>3.2 Put</h3><p>
          This specification defines one Web service operation (Put) for 
-         updating a resource by providing a replacement representation. A 
-         resource MAY accept updates that provide different XML 
+         updating a resource by providing a replacement representation. 
+         This operation MAY be supported by compliant WS-Transfer resources.
+         A resource MAY accept updates that provide different XML 
          representations than that returned by the resource; in such a 
          case, the semantics of the update operation is defined by
          the resource.
@@ -513,8 +513,11 @@
     &lt;wst:PutResponse/&gt;
   &lt;/s:Body&gt;
 &lt;/s:Envelope&gt; </pre></div></div></div><div class="div2">
-<h3><a name="Delete" id="Delete"/>3.3 Delete</h3><p>This specification defines one Web service operation (Delete) for deleting
-a resource in its entirety.</p><p>The Delete request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
+<h3><a name="Delete" id="Delete"/>3.3 Delete</h3><p>
+         This specification defines one Web service operation (Delete) for 
+         deleting a resource in its entirety.
+         This operation MAY be supported by compliant WS-Transfer resources.
+        </p><p>The Delete request message MUST be of the following form:</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-tra/Delete
 
 <b>[Body]</b>
@@ -605,8 +608,12 @@
   &lt;/s:Body&gt;
 &lt;/s:Envelope&gt; </pre></div></div></div></div><div class="div1">
 <h2><a name="Resource_Factory_Operations" id="Resource_Factory_Operations"/>4 Resource Factory Operations</h2><div class="div2">
-<h3><a name="Factory_Create" id="Factory_Create"/>4.1 Create</h3><p>This specification defines one Web service operation (Create) for creating
-    a resource and providing its initial representation. In some cases, the
+<h3><a name="Factory_Create" id="Factory_Create"/>4.1 Create</h3><p>
+         This specification defines one Web service operation (Create) for 
+         creating a resource and providing its initial representation. 
+         This operation MAY be supported by compliant WS-Transfer resource
+         factories.
+         In some cases, the
     initial representation MAY constitute the representation of a logical
     constructor for the resource and can thus differ structurally from the
     representation returned by Get or the one required by Put. This is because
@@ -892,7 +899,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="iddiv2_1_1343" id="iddiv2_1_1343"/>7.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1341" id="iddiv2_1_1341"/>7.1 TransferResource Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-Transfer specification's definition of a Transfer Resource
      is through the use of the Web Services
@@ -960,7 +967,7 @@
          the Global Element Declaration (GED) or type of this resource.  This 
          QName can be used in order to retrieve the schema of the resource.
         </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1413" id="iddiv2_1_1413"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1411" id="iddiv2_1_1411"/>7.2 TransferResourceFactory Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-Transfer specification's definition of a Transfer Resource Factory
      is through the use of the Web Services
@@ -1032,7 +1039,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1466" id="iddiv2_1_1466"/>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_1464" id="iddiv2_1_1464"/>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.
@@ -1100,7 +1107,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_1639" id="iddiv2_1_1639"/>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_1637" id="iddiv2_1_1637"/>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.
@@ -1321,4 +1328,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8184">8184</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8179">8179</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</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=8280">8280</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.138
retrieving revision 1.139
diff -u -d -r1.138 -r1.139
--- wseventing.html	17 Nov 2009 22:05:22 -0000	1.138
+++ wseventing.html	1 Dec 2009 23:55:37 -0000	1.139
@@ -75,22 +75,22 @@
 &nbsp;&nbsp;&nbsp;7.2 <a href="#AccessControl">Access Control</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="#iddiv2_1_2126">EventSource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2193">SubscriptionManager Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2124">EventSource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2191">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_2264">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2385">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2262">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2383">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_2691">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2712">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_2717">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_2735">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_2710">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_2715">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_2733">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_2762">Retrieving Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2783">Multiple Event Information Metadata Sections</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2760">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2781">Multiple Event Information Metadata Sections</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/>
@@ -481,7 +481,9 @@
    </p><div class="div2">
 <h3><a name="Subscribe" id="Subscribe"/>4.1 Subscribe</h3><p>
      To create a subscription, a subscriber sends a request message
-     of the following form to an event source:
+     to an event source.  This operation MUST be supported by
+     compliant event sources.
+     The message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-evt/Subscribe
 
@@ -827,11 +829,11 @@
      <a href="#Table4">Example 4-1</a>).
     </p></div><div class="div2">
 <h3><a name="Renew" id="Renew"/>4.2 Renew</h3><p>
-     To update the expiration for a subscription, subscription
-     managers MUST support requests to renew subscriptions.
-    </p><p>
-     To renew a subscription, the subscriber sends a request of the
-     following form to the subscription manager:
+     To update, or renew, the expiration for a subscription, a
+     subscriber sends a Renew request message to the subscription
+     manager.
+     This operation MUST be supported by compliant subscription managers.
+     The Renew request message message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-evt/Renew
 
@@ -942,7 +944,9 @@
     </p></div><div class="div2">
 <h3><a name="GetStatus" id="GetStatus"/>4.3 GetStatus</h3><p>
      To get the status of a subscription, the subscriber sends a
-     request of the following form to the subscription manager:
+     GetStatus request message to the subscription manager.
+     This operation MUST be supported by compliant subscription managers.
+     The GetStatus request MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-evt/GetStatus
 
@@ -1047,8 +1051,9 @@
      with the subscription.
     </p><p>
      To explicitly delete a subscription, a subscriber 
-     sends a request of the following form to the subscription
-     manager:
+     sends an Unsubscribe request message to the subscription manager.
+     This operation MUST be supported by compliant subscription managers.
+     The Unsubscribe request message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-evt/Unsubscribe
 
@@ -1131,11 +1136,14 @@
 (16) &lt;/s12:Envelope&gt;</pre></div></div></div><div class="div2">
 <h3><a name="SubscriptionEnd" id="SubscriptionEnd"/>4.5 Subscription End</h3><p>
      If the event source terminates a subscription unexpectedly,
-     SubscriptionEnd SOAP message SHOULD be sent to
+     a SubscriptionEnd SOAP message SHOULD be sent to
      the endpoint reference indicated when the subscription was
      created (see <a href="#Subscribe"><b>4.1 Subscribe</b></a>). 
      This endpoint reference MUST refer to an endpoint that supports the 
-     SubscriptionEndPortType portType.
+     SubscriptionEndPortType portType.  Support for including the
+     EndTo EPR in a Subscribe request message
+     (and implicitly the sending of the SubscriptionEnd message)
+     MUST be supported by compliant event sources.
      The message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-evt/SubscriptionEnd
@@ -1493,7 +1501,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="iddiv2_1_2126" id="iddiv2_1_2126"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2124" id="iddiv2_1_2124"/>9.1 EventSource Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-Eventing specification's definition of an event source 
      is through the use of the Web Services
@@ -1552,7 +1560,7 @@
          When present, this OPTIONAL parameter indicates support for the 
          specified event delivery format name URI.
         </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2193" id="iddiv2_1_2193"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2191" id="iddiv2_1_2191"/>9.2 SubscriptionManager Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-Eventing specification's definition of a subscription manager 
      is through the use of the Web Services
@@ -1637,7 +1645,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2264" id="iddiv2_1_2264"/>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_2262" id="iddiv2_1_2262"/>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.
@@ -1684,7 +1692,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_2385" id="iddiv2_1_2385"/>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_2383" id="iddiv2_1_2383"/>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>
@@ -1875,7 +1883,7 @@
      serve as a description of the Event Type used in 
      <a href="#Table1">Example 2-1</a> and <a href="#EDExample">Example A-1</a>. 
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2681" id="idexample_1_2681"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2679" id="idexample_1_2679"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
 (02)        targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)        xmlns:wse="http://www.w3.org/2009/09/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch"&gt;
@@ -1895,7 +1903,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_2691" id="iddiv3_1_2691"/>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>.
@@ -1906,7 +1914,7 @@
       be equal to the value of its wse:EventDescriptions/@targetNamespace. An 
       event source MUST NOT have more than one EventDescriptions document.
      </p></div><div class="div3">
-<h4><a name="iddiv3_1_2712" id="iddiv3_1_2712"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2710" id="iddiv3_1_2710"/>A.1.2 Bindings for Event Descriptions</h4><p>
       For any Notification Format it SHOULD 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 
@@ -1918,7 +1926,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_2717" id="iddiv4_1_2717"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2715" id="iddiv4_1_2715"/>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>
@@ -1932,7 +1940,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_2735" id="iddiv4_1_2735"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2733" id="iddiv4_1_2733"/>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>
@@ -1956,7 +1964,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_2756" id="idexample_1_2756"/>Example A-3: 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_2754" id="idexample_1_2754"/>Example A-3: 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/"
@@ -1991,7 +1999,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_2762" id="iddiv3_1_2762"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2760" id="iddiv3_1_2760"/>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>.
@@ -2007,7 +2015,7 @@
       Format IRI/@Identifier, there MUST NOT exist more than one 
       Notification WSDL document. 
      </p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2783" id="iddiv2_1_2783"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2781" id="iddiv2_1_2781"/>A.3 Multiple Event Information Metadata Sections</h3><p>
      When WS-MetadataExchange is used to retrieve metadata about an event 
      source, recipients of mex:Metadata elements that contain Metadata 
      Sections with both the 
@@ -2608,4 +2616,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8276">8276</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8277">8277</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8285">8285</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=8285">8285</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -d -r1.95 -r1.96
--- wsenum.html	17 Nov 2009 21:00:39 -0000	1.95
+++ wsenum.html	1 Dec 2009 23:55:37 -0000	1.96
@@ -67,11 +67,11 @@
 &nbsp;&nbsp;&nbsp;4.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
 5 <a href="#Security">Security Considerations</a><br/>
 6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_1902">Enumeration Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_1900">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_1991">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2177">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_1989">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2175">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/>
@@ -359,7 +359,8 @@
     and refreshed on every PullResponse or RenewResponse.
    </p><div class="div2">
 <h3><a name="Enumerate" id="Enumerate"/>3.1 Enumerate</h3><p>
-     Data sources MUST support the Enumerate operation to start an enumeration.
+     This specification defines the Enumerate operation to start an enumeration.
+     This operation MUST be supported by compliant data sources.
      A data source MAY provide other mechanisms for starting an enumeration and
      receiving an enumeration context.
     </p><p>
@@ -621,9 +622,10 @@
      below.
     </p></div><div class="div2">
 <h3><a name="Pull" id="Pull"/>3.2 Pull</h3><p>
-     The Pull operation is initiated by sending a
-     Pull request message to the data source. The Pull request message
-     MUST be of the following form:
+     The Pull operation is initiated by sending a Pull request message to 
+     the data source. 
+     This operation MUST be supported by compliant data sources.
+     The Pull request message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-enu/Pull
 
@@ -825,11 +827,10 @@
      the enumeration context is no longer needed. 
     </p></div><div class="div2">
 <h3><a name="Renew" id="Renew"/>3.3 Renew</h3><p>
-     Data sources MUST support requests to renew
-     enumerations.
-    </p><p>
-     To renew an enumeration, the consumer sends a
-     request of the following form to the data source:
+     To update, or renew, the expiration for an enumeration, a Renew
+     request message is sent to the data source.
+     This operation MUST be supported by compliant data sources.
+     The Renew request message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-enu/Renew
 
@@ -885,8 +886,9 @@
     </p></div><div class="div2">
 <h3><a name="GetStatus" id="GetStatus"/>3.4 GetStatus</h3><p>
      To get the status of an enumeration, the
-     consumer sends a request of the following form to the data
-     source:
+     consumer sends a GetStatus request message to the data source.
+     This operation MUST be supported by compliant data sources.
+     The message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-enu/GetStatus
 
@@ -924,8 +926,9 @@
     </p></div><div class="div2">
 <h3><a name="Release" id="Release"/>3.5 Release</h3><p>
      The Release operation is initiated by sending a
-     Release request message to the data source. The Release request
-     message MUST be of the following form:
+     Release request message to the data source. 
+     This operation MUST be supported by compliant data sources.
+     The Release request message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-enu/Release
 
@@ -1011,8 +1014,11 @@
      If the data source terminates an enumeration
      unexpectedly, the data source SHOULD send an EnumerationEnd SOAP
      message to the endpoint reference indicated when the enumeration
-     was created (see <a href="#Enumerate"><b>3.1 Enumerate</b></a>). The message MUST be of the
-     following form:
+     was created (see <a href="#Enumerate"><b>3.1 Enumerate</b></a>). 
+     Support for including the EndTo EPR in a Enumerate request message
+     (and implicitly the sending of the EnumerationEnd message) MUST
+     be supported by compliant data sources.
+     The message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-enu/EnumerationEnd
 
@@ -1263,7 +1269,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="iddiv2_1_1902" id="iddiv2_1_1902"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_1900" id="iddiv2_1_1900"/>6.1 Enumeration Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the 
      WS-Enumeration specification is through the use of the Web Services 
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy - 
@@ -1359,7 +1365,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1991" id="iddiv2_1_1991"/>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_1989" id="iddiv2_1_1989"/>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. 
@@ -1431,7 +1437,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_2177" id="iddiv2_1_2177"/>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_2175" id="iddiv2_1_2175"/>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>
@@ -1932,4 +1938,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8158">8158</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</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=8280">8280</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</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.89
retrieving revision 1.90
diff -u -d -r1.89 -r1.90
--- wsmex.html	1 Dec 2009 22:23:50 -0000	1.89
+++ wsmex.html	1 Dec 2009 23:55:37 -0000	1.90
@@ -55,7 +55,7 @@
 5 <a href="#web-services-metadata">Web Services Metadata</a><br/>
 6 <a href="#Retrieving-Metadata">Retrieving Metadata</a><br/>
 &nbsp;&nbsp;&nbsp;6.1 <a href="#WS-Transfer-Get">WS-Transfer Get</a><br/>
-&nbsp;&nbsp;&nbsp;6.2 <a href="#Get-Metadata">Get Metadata</a><br/>
+&nbsp;&nbsp;&nbsp;6.2 <a href="#GetMetadata">Get Metadata</a><br/>
 7 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
 8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br/>
 9 <a href="#ImplicitWSDL">Exposing WSDL for Operations Implicitly Defined by a Policy Assertion</a><br/>
@@ -491,7 +491,7 @@
     resources. A Web service endpoint MAY also support direct retrieval 
     of metadata by requesters using a GetMetadata operation directed 
     to the Web service endpoint itself, as described in 
-    <a href="#Get-Metadata"><b>6.2 Get Metadata</b></a>.
+    <a href="#GetMetadata"><b>6.2 Get Metadata</b></a>.
    </p><p>
     A metadata resource MAY support other operations defined by 
     <a href="#WS-Transfer">[WS-Transfer]</a>, such as Put (e.g. to allow update of 
@@ -551,7 +551,7 @@
     This specification defines the following values for Dialect; 
     other specifications SHOULD define values for Dialect for their 
     metadata format(s).
-   </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy <a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex-all </td><td> None.  [Defined in this specification for use in GetMetadata requests.  See <a href="#Get-Metadata"><b>6.2 Get Metadata</b></a>.] </td></tr></tbody></table><p>
+   </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy <a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr><tr><td> http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex-all </td><td> None.  [Defined in this specification for use in GetMetadata requests.  See <a href="#GetMetadata"><b>6.2 Get Metadata</b></a>.] </td></tr></tbody></table><p>
     If there is more than one metadata unit with the same Dialect, e.g., 
     more than one XML Schema document, including them all, one per 
     Metadata Section, is explicitly encouraged.
@@ -630,11 +630,11 @@
      <a href="#XMLSchema2">[XMLSchema - Part 2]</a>, <a href="#WSDL11">[WSDL11]</a>, 
      <a href="#wspolicy">[WS-Policy]</a>) for which a Dialect value is defined.
     </p></div><div class="div2">
-<h3><a name="Get-Metadata" id="Get-Metadata"/>6.2 Get Metadata</h3><p>
+<h3><a name="GetMetadata" id="GetMetadata"/>6.2 Get Metadata</h3><p>
      A requester MAY send a GetMetadata request message to an endpoint to 
      retrieve the metadata associated with that endpoint.
-     A service endpoint MAY 
-     support the GetMetadata request. Observe that, in the case where 
+     This operation MAY be supported by compliant service endpoints.
+     Observe that, in the case where 
      a service endpoint is also a <a href="#WS-Transfer">[WS-Transfer]</a> resource, 
      the <a href="#WS-Transfer">[WS-Transfer]</a> Get operation allows requesters to 
      retrieve the resource representation associated with that endpoint 
@@ -1360,4 +1360,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8291">8291</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8203">8203</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=8203">8203</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 1 December 2009 23:55:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 December 2009 23:55:42 GMT