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

WWW/2002/ws/ra/edcopies wseventing.html,1.181,1.182 wseventing.xml,1.174,1.175

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 27 Apr 2010 12:32:34 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1O6jxq-0000q4-Tc@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv3043

Modified Files:
	wseventing.html wseventing.xml 
Log Message:
8832


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.174
retrieving revision 1.175
diff -u -d -r1.174 -r1.175
--- wseventing.xml	24 Apr 2010 02:16:48 -0000	1.174
+++ wseventing.xml	27 Apr 2010 12:32:32 -0000	1.175
@@ -829,6 +829,32 @@
     at the application layer.
    </p>
 
+   <p>
+    A subscription can become invalid for any reason including:
+   </p>
+
+   <olist>
+    <item> <p>Subscription deleted (via Unsubscribe)</p> </item>
+    <item> <p>Subscription expired</p> </item>
+    <item> <p>Subscription ended (via SubscriptionEnd)</p> </item>
+   </olist>
+
+   <p>
+    In addition, the Event Source/Subscription Manager MAY cancel a 
+    subscription at any time, as necessary.
+   </p>
+   
+   <p>
+    When processing a Renew, GetStatus or Unsubscribe operation, a 
+    Subscription Manager MUST generate an wse:UnknownSubscription fault if 
+    it determines that the subscription is invalid.
+   </p>
+
+   <p>
+    Once a Subscriber determines that a subscription is invalid, it MUST 
+    NOT issue any more WSEventing request messages using that subscription.
+   </p>
+
    <div2 id="Subscribe">
     <head>Subscribe</head>
 
@@ -1433,7 +1459,7 @@
     <p>
      If the request message reaches a conformant implementation of 
      WS-Eventing and the message refers to an unknown subscription, then the 
-     implemention MUST generate a wse:UnknownSubscription fault.
+     implementation MUST generate a wse:UnknownSubscription fault.
     </p>
 
     <p>
@@ -1609,7 +1635,7 @@
     <p>
      If the request message reaches a conformant implementation of
      WS-Eventing and the message refers to an unknown subscription, then the
-     implemention MUST generate a wse:UnknownSubscription fault.
+     implementation MUST generate a wse:UnknownSubscription fault.
     </p>
 
     <p>
@@ -1755,7 +1781,7 @@
     <p>
      If the request message reaches a conformant implementation of
      WS-Eventing and the message refers to an unknown subscription, then the
-     implemention MUST generate a wse:UnknownSubscription fault.
+     implementation MUST generate a wse:UnknownSubscription fault.
     </p>
 
     <p>
@@ -5025,6 +5051,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9543">9543</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/04/27 </td>
+      <td> DD </td>
+      <td> Added resolution of issue
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8832">8832</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.181
retrieving revision 1.182
diff -u -d -r1.181 -r1.182
--- wseventing.html	24 Apr 2010 02:16:48 -0000	1.181
+++ wseventing.html	27 Apr 2010 12:32:32 -0000	1.182
@@ -76,21 +76,21 @@
 &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_2176">EventSource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2279">SubscriptionManager Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2194">EventSource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2297">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_2353">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2500">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2371">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2518">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_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_2752">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2707">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2744">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_2749">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_2770">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_2779">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2797">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/>
@@ -489,6 +489,18 @@
     messages defined herein are delivered using the quality of
     service of the underlying transport(s) and on a best-effort basis
     at the application layer.
+   </p><p>
+    A subscription can become invalid for any reason including:
+   </p><ol class="enumar"><li><p>Subscription deleted (via Unsubscribe)</p></li><li><p>Subscription expired</p></li><li><p>Subscription ended (via SubscriptionEnd)</p></li></ol><p>
+    In addition, the Event Source/Subscription Manager MAY cancel a 
+    subscription at any time, as necessary.
+   </p><p>
+    When processing a Renew, GetStatus or Unsubscribe operation, a 
+    Subscription Manager MUST generate an wse:UnknownSubscription fault if 
+    it determines that the subscription is invalid.
+   </p><p>
+    Once a Subscriber determines that a subscription is invalid, it MUST 
+    NOT issue any more WSEventing request messages using that subscription.
    </p><div class="div2">
 <h3><a name="Subscribe" id="Subscribe"/>4.1 Subscribe</h3><p>
      To create a subscription, a subscriber sends a Subscribe request message
@@ -872,7 +884,7 @@
     </p><p>
      If the request message reaches a conformant implementation of 
      WS-Eventing and the message refers to an unknown subscription, then the 
-     implemention MUST generate a wse:UnknownSubscription fault.
+     implementation MUST generate a wse:UnknownSubscription fault.
     </p><p>
      If the subscription manager chooses not to renew this
      subscription, the request MUST fail, and the subscription manager
@@ -999,7 +1011,7 @@
     </p><p>
      If the request message reaches a conformant implementation of
      WS-Eventing and the message refers to an unknown subscription, then the
-     implemention MUST generate a wse:UnknownSubscription fault.
+     implementation MUST generate a wse:UnknownSubscription fault.
     </p><p>
      This operation is safe; it will not result in any side effect
      imputable to the requester. This means that in case of an underlying
@@ -1102,7 +1114,7 @@
     </p><p>
      If the request message reaches a conformant implementation of
      WS-Eventing and the message refers to an unknown subscription, then the
-     implemention MUST generate a wse:UnknownSubscription fault.
+     implementation MUST generate a wse:UnknownSubscription fault.
     </p><p><a href="#Table10">Example 4-7</a> lists a hypothetical request to delete the
      subscription created in <a href="#Table5">Example 4-2</a>.
     </p><div class="exampleOuter">
@@ -1532,7 +1544,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_2176" id="iddiv2_1_2176"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2194" id="iddiv2_1_2194"/>9.1 EventSource Assertion</h3><p>
      Services indicate support for the WS-Eventing's definition 
      of an event source through the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1615,7 +1627,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_2279" id="iddiv2_1_2279"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2297" id="iddiv2_1_2297"/>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
@@ -1695,7 +1707,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_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>
+<h3><a name="iddiv2_1_2371" id="iddiv2_1_2371"/>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.
@@ -1752,7 +1764,7 @@
        , E. Christensen, et al., Editors.
        World Wide Web Consortium (W3C), 15 March 2001
       Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2500" id="iddiv2_1_2500"/>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_2518" id="iddiv2_1_2518"/>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>
@@ -1851,7 +1863,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_2679" id="idexample_1_2679"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wsevd:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2697" id="idexample_1_2697"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wsevd:EventDescriptions 
 (02)        targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)        xmlns:wsevd="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch"&gt;
@@ -1871,7 +1883,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_2689" id="iddiv3_1_2689"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2707" id="iddiv3_1_2707"/>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>.
@@ -1909,7 +1921,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_2726" id="iddiv3_1_2726"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2744" id="iddiv3_1_2744"/>A.1.2 Bindings for Event Descriptions</h4><p>
       For any Notification Format it MUST be possible to determine how a 
       given wsevd:eventType will appear on the wire as a notification in a 
       subscription created with that format. The following sections define 
@@ -1921,7 +1933,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_2731" id="iddiv4_1_2731"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2749" id="iddiv4_1_2749"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
        The information about an Event Type contained in the wsevd:eventType 
        element binds to a Unwrapped Notification for that type as follows:
       </p><ul><li><p>
@@ -1936,7 +1948,7 @@
          event being transmitted. If the @element attribute is absent then
          the <b>[Body]</b> property has no children.
         </p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2752" id="iddiv4_1_2752"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2770" id="iddiv4_1_2770"/>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>
@@ -1962,7 +1974,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_2773" id="idexample_1_2773"/>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_2791" id="idexample_1_2791"/>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/"
@@ -1997,7 +2009,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_2779" id="iddiv3_1_2779"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2797" id="iddiv3_1_2797"/>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>.
@@ -2689,4 +2701,5 @@
        <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><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</a></td></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9543">9543</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=9543">9543</a></td></tr><tr><td> 2010/04/27 </td><td> DD </td><td> Added resolution of issue
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8832">8832</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 27 April 2010 12:32:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 April 2010 12:32:38 GMT