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

WWW/2002/ws/ra/edcopies wseventing.html,1.92,1.93 wseventing.xml,1.84,1.85

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 02 Oct 2009 16:01:21 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MtkZN-0005aV-SP@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv21391

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


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -d -r1.84 -r1.85
--- wseventing.xml	2 Oct 2009 15:50:32 -0000	1.84
+++ wseventing.xml	2 Oct 2009 16:01:19 -0000	1.85
@@ -710,6 +710,18 @@
      </gitem>
 
      <gitem>
+      <label> Subscription </label>
+      <def>
+       <p>
+        A registration of interest in receiving Notification messages from 
+        an Event Source.  Subscriptions may be created, renewed, expired 
+        or cancelled.  A Subscription is "active" when it has been created 
+        but has not been expired or cancelled.
+       </p>
+      </def>
+     </gitem>
+
+     <gitem>
       <label> Subscriber </label>
       <def>
        <p>
@@ -1156,11 +1168,12 @@
      If the event source chooses not to accept a subscription due
      to the content of the Subscribe message, then the 
      event source MUST generate a 
-     wse:SubscribeRequestInvalid fault. If the event source
+     SOAP 1.1 Server fault or a SOAP 1.2 Receiver
+     fault. If the event source
      does not accept this subscription due to an internal processing
      reason and not due to the specific content of the Subscribe
      message, then the event source MUST
-     generate a wse:EventSourceUnableToProcess fault.
+     generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault.
     </p>
 
     <p>
@@ -1339,8 +1352,8 @@
     </p>
 
     <p>
-     If the subscription is not valid, the request MUST fail and the 
-     subscription manager MUST generate a wse:InvalidSubscription fault.
+     If the subscription is not active, the request MUST fail and the 
+     subscription manager MAY generate a wse:UnknownSubscription fault.
     </p>
 
     <p>
@@ -1382,8 +1395,8 @@
     <p>
      If the subscription manager chooses not to renew this
      subscription, the request MUST fail, and the subscription manager
-     MUST generate a wse:UnableToRenew fault indicating that the
-     renewal was not accepted.
+     MUST generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault 
+     indicating that the renewal was not accepted.
     </p>
 
     <p>
@@ -1500,7 +1513,7 @@
     </p>
 
     <p>
-     If the subscription is valid and has not expired, the
+     If the subscription is active, the
      subscription manager MUST reply with a response of the following
      form:
     </p>
@@ -1517,6 +1530,11 @@
     </example>
 
     <p>
+     If the subscription is not active, the request MUST fail and the 
+     subscription manager MAY generate a wse:UnknownSubscription fault. 
+    </p>
+
+    <p>
      Components of the outline listed above are constrained as for
      a response to a renew request (see <specref ref="Renew"/>).
      Other components of the outline above are not further
@@ -1658,6 +1676,11 @@
     </example>
 
     <p>
+     If the subscription is not active, the request MUST fail and the 
+     subscription manager MAY generate a wse:UnknownSubscription fault. 
+    </p>
+
+    <p>
      Components of the outline listed above are not further
      constrained by this specification.
     </p>
@@ -2043,8 +2066,8 @@
    <div2 id="FaultDetailRetryElement">
     <head>Fault Detail RetryAfter Element</head>
     <p>
-     The following element is used to convey additional information in 
-     the faults.
+     The following element MAY be used to convey additional information in 
+     the detail element of a fault.
     </p>
     
     <glist>   
@@ -2212,156 +2235,6 @@
     </table>
    </div2>
 
-   <div2 id="SubscribeRequestInvalid">
-    <head>SubscribeRequestInvalid</head>
-
-    <p>
-     This fault is generated when the event source is not capable of
-     fulfilling a Subscribe request due to the content of the Subscribe
-     request message.
-    </p>
-
-    <table border="1">
-     <tbody>
-      <tr>
-       <td><kw>[Code]</kw></td>
-       <td>s12:Receiver</td>
-      </tr>
-
-      <tr>
-       <td><kw>[Subcode]</kw></td>
-       <td>wse:SubscribeRequestInvalid</td>
-      </tr>
-
-      <tr>
-       <td><kw>[Reason]</kw></td>
-       <td>
-        <emph>Text explaining the failure.</emph>
-       </td>
-      </tr>
-
-      <tr>
-       <td><kw>[Detail]</kw></td>
-       <td></td>
-      </tr>
-     </tbody>
-    </table>
-   </div2>
-
-   <div2 id="EventSourceUnableToProcess">
-    <head>EventSourceUnableToProcess</head>
-
-    <p>
-     This fault is generated when the event source is not capable of
-     fulfilling a Subscribe request for local reasons unrelated to the
-     specific request.
-    </p>
-
-    <table border="1">
-     <tbody>
-      <tr>
-       <td><kw>[Code]</kw></td>
-       <td>s12:Receiver</td>
-      </tr>
-
-      <tr>
-       <td><kw>[Subcode]</kw></td>
-       <td>wse:EventSourceUnableToProcess</td>
-      </tr>
-
-      <tr>
-       <td><kw>[Reason]</kw></td>
-       <td>
-        <emph>Text explaining the failure; e.g., "The event
-        source has too many subscribers".</emph>
-       </td>
-      </tr>
-
-      <tr>
-       <td><kw>[Detail]</kw></td>
-       <td>
-       &lt;wse:RetryAfter&gt; ? 
-       <emph>(Optional)</emph>
-       </td>
-      </tr>
-     </tbody>
-    </table>
-   </div2>
-
-   <div2 id="UnableToRenew">
-    <head>UnableToRenew</head>
-
-    <p>
-     This fault is generated when the event source is not capable of
-     fulfilling a Renew request for local reasons unrelated to the
-     specific request.
-    </p>
-
-    <table border="1">
-    <tbody>
-      <tr>
-       <td><kw>[Code]</kw></td>
-       <td>s12:Receiver</td>
-      </tr>
-
-      <tr>
-       <td><kw>[Subcode]</kw></td>
-       <td>wse:UnableToRenew</td>
-      </tr>
-
-      <tr>
-       <td><kw>[Reason]</kw></td>
-       <td>
-        <emph>Text explaining the failure; e.g., "The event
-        source has too many subscribers".</emph>
-       </td>
-      </tr>
-      <tr>
-       <td><kw>[Detail]</kw></td>
-       <td>
-        &lt;wse:RetryAfter&gt; ? 
-        <emph>(Optional)</emph>
-       </td>
-      </tr>
-     </tbody>
-    </table>
-   </div2>
-   
-   <div2 id="InvalidMessage">
-    <head>InvalidMessage</head>
-
-    <p>
-     If a request message does not comply with the corresponding
-     outline listed above, the request MUST fail and the event source
-     or subscription manager MUST generate the following fault
-     indicating that the request is invalid:
-    </p>
-
-    <table border="1">
-     <tbody>
-      <tr>
-       <td><kw>[Code]</kw></td>
-       <td>s12:Sender</td>
-      </tr>
-
-      <tr>
-       <td><kw>[Subcode]</kw></td>
-       <td>wse:InvalidMessage</td>
-      </tr>
-
-      <tr>
-       <td><kw>[Reason]</kw></td>
-       <td>The message is not valid and cannot be processed.</td>
-      </tr>
-
-      <tr>
-       <td><kw>[Detail]</kw></td>
-       <td><emph>The invalid message</emph></td>
-      </tr>
-     </tbody>
-    </table>
-   </div2>
-
    <div2 id="DeliveryFormatRequestedUnavailable">
     <head>DeliveryFormatRequestUnavailable</head>
 
@@ -2472,12 +2345,12 @@
     </table>
    </div2>
 
-   <div2 id="InvalidSubscription">
-    <head>InvalidSubscription</head>
+   <div2 id="UnknownSubscription">
+    <head>UnknownSubscription</head>
 
     <p>
      This fault is generated when a request specifies a subscription
-     that is not valid.
+     that is not active.
     </p>
 
     <table border="1">
@@ -2489,12 +2362,12 @@
 
       <tr>
        <td><kw>[Subcode]</kw></td>
-       <td>wse:InvalidSubscription</td>
+       <td>wse:UnknownSubscription</td>
       </tr>
 
       <tr>
        <td><kw>[Reason]</kw></td>
-       <td>the subscription is not valid.</td>
+       <td>the subscription is not active.</td>
       </tr>
 
       <tr>
@@ -4226,6 +4099,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/02 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7554">7554</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -d -r1.92 -r1.93
--- wseventing.html	2 Oct 2009 15:50:32 -0000	1.92
+++ wseventing.html	2 Oct 2009 16:01:19 -0000	1.93
@@ -65,14 +65,10 @@
 &nbsp;&nbsp;&nbsp;6.3 <a href="#UnsupportedExpirationType">UnsupportedExpirationType</a><br/>
 &nbsp;&nbsp;&nbsp;6.4 <a href="#FilteringNotSupported">FilteringNotSupported</a><br/>
 &nbsp;&nbsp;&nbsp;6.5 <a href="#FilteringRequestedUnavailable">FilteringRequestedUnavailable</a><br/>
-&nbsp;&nbsp;&nbsp;6.6 <a href="#SubscribeRequestInvalid">SubscribeRequestInvalid</a><br/>
-&nbsp;&nbsp;&nbsp;6.7 <a href="#EventSourceUnableToProcess">EventSourceUnableToProcess</a><br/>
-&nbsp;&nbsp;&nbsp;6.8 <a href="#UnableToRenew">UnableToRenew</a><br/>
-&nbsp;&nbsp;&nbsp;6.9 <a href="#InvalidMessage">InvalidMessage</a><br/>
-&nbsp;&nbsp;&nbsp;6.10 <a href="#DeliveryFormatRequestedUnavailable">DeliveryFormatRequestUnavailable</a><br/>
-&nbsp;&nbsp;&nbsp;6.11 <a href="#EmptyFilter">EmptyFilter</a><br/>
-&nbsp;&nbsp;&nbsp;6.12 <a href="#UnusableEPR">UnusableEPR</a><br/>
-&nbsp;&nbsp;&nbsp;6.13 <a href="#InvalidSubscription">InvalidSubscription</a><br/>
+&nbsp;&nbsp;&nbsp;6.6 <a href="#DeliveryFormatRequestedUnavailable">DeliveryFormatRequestUnavailable</a><br/>
+&nbsp;&nbsp;&nbsp;6.7 <a href="#EmptyFilter">EmptyFilter</a><br/>
+&nbsp;&nbsp;&nbsp;6.8 <a href="#UnusableEPR">UnusableEPR</a><br/>
+&nbsp;&nbsp;&nbsp;6.9 <a href="#UnknownSubscription">UnknownSubscription</a><br/>
 7 <a href="#Security">Security Considerations</a><br/>
 &nbsp;&nbsp;&nbsp;7.1 <a href="#MessageSecurity">Message Security</a><br/>
 &nbsp;&nbsp;&nbsp;7.2 <a href="#AccessControl">Access Control</a><br/>
@@ -80,18 +76,18 @@
 9 <a href="#policy">WS-Eventing Policy Assertion(s)</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_2232">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2340">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2039">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2147">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_2646">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2662">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_2667">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_2685">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2453">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2469">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_2474">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_2492">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_2712">Retrieving Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2728">Multiple Event Information Metadata Sections</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2519">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2535">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/>
@@ -420,6 +416,11 @@
        </p></dd><dt class="label"> Notification </dt><dd><p>
         A one-way message sent to indicate that an event, or events,
         have occurred.
+       </p></dd><dt class="label"> Subscription </dt><dd><p>
+        A registration of interest in receiving Notification messages from 
+        an Event Source.  Subscriptions may be created, renewed, expired 
+        or cancelled.  A Subscription is "active" when it has been created 
+        but has not been expired or cancelled.
        </p></dd><dt class="label"> Subscriber </dt><dd><p>
         A Web service that sends requests to create, renew, and/or
         delete subscriptions.
@@ -670,11 +671,12 @@
      If the event source chooses not to accept a subscription due
      to the content of the Subscribe message, then the 
      event source MUST generate a 
-     wse:SubscribeRequestInvalid fault. If the event source
+     SOAP 1.1 Server fault or a SOAP 1.2 Receiver
+     fault. If the event source
      does not accept this subscription due to an internal processing
      reason and not due to the specific content of the Subscribe
      message, then the event source MUST
-     generate a wse:EventSourceUnableToProcess fault.
+     generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault.
     </p><p><a href="#Table4">Example 4-1</a> lists another hypothetical request to create a
      subscription.
     </p><div class="exampleOuter">
@@ -814,8 +816,8 @@
      of the outline above are not further constrained by this
      specification.
     </p><p>
-     If the subscription is not valid, the request MUST fail and the 
-     subscription manager MUST generate a wse:InvalidSubscription fault.
+     If the subscription is not active, the request MUST fail and the 
+     subscription manager MAY generate a wse:UnknownSubscription fault.
     </p><p>
      If the subscription manager accepts a request to renew a
      subscription, it MUST reply with a response of the following
@@ -838,8 +840,8 @@
        </p></dd></dl><p>
      If the subscription manager chooses not to renew this
      subscription, the request MUST fail, and the subscription manager
-     MUST generate a wse:UnableToRenew fault indicating that the
-     renewal was not accepted.
+     MUST generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault 
+     indicating that the renewal was not accepted.
     </p><p>
      Other components of the outline above are not further
      constrained by this specification.
@@ -923,7 +925,7 @@
      outline above are not further constrained by this
      specification.
     </p><p>
-     If the subscription is valid and has not expired, the
+     If the subscription is active, the
      subscription manager MUST reply with a response of the following
      form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
@@ -934,6 +936,9 @@
     &lt;wse:Expires&gt;(<em>xs:dateTime</em> | <em>xs:duration</em>)&lt;/wse:Expires&gt; ?
     <em>xs:any</em>*
   &lt;/wse:GetStatusResponse&gt;</pre></div></div><p>
+     If the subscription is not active, the request MUST fail and the 
+     subscription manager MAY generate a wse:UnknownSubscription fault. 
+    </p><p>
      Components of the outline listed above are constrained as for
      a response to a renew request (see <a href="#Renew"><b>4.2 Renew</b></a>).
      Other components of the outline above are not further
@@ -1034,6 +1039,9 @@
   &lt;wse:UnsubscribeResponse ...&gt;
     <em>xs:any</em>*
   &lt;/wse:UnsubscribeResponse&gt;</pre></div></div><p>
+     If the subscription is not active, the request MUST fail and the 
+     subscription manager MAY generate a wse:UnknownSubscription fault. 
+    </p><p>
      Components of the outline listed above are not further
      constrained by this specification.
     </p><p><a href="#Table10">Example 4-7</a> lists a hypothetical request to delete the
@@ -1281,8 +1289,8 @@
   &lt;/s11:Body&gt;
 &lt;/s11:Envelope&gt;</pre></div></div><div class="div2">
 <h3><a name="FaultDetailRetryElement" id="FaultDetailRetryElement"/>6.1 Fault Detail RetryAfter Element</h3><p>
-     The following element is used to convey additional information in 
-     the faults.
+     The following element MAY be used to convey additional information in 
+     the detail element of a fault.
     </p><dl><dt class="label"> /wse:RetryAfter</dt><dd><p>
         This element (whose content is of type xs:unsignedLong) is a suggested 
         minimum duration in milliseconds to wait before retransmitting the message. 
@@ -1314,34 +1322,7 @@
         &lt;wse:SupportedDialect&gt; + 
         <br/><em>Optional; one per filter dialect supported by the
         receiver</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="SubscribeRequestInvalid" id="SubscribeRequestInvalid"/>6.6 SubscribeRequestInvalid</h3><p>
-     This fault is generated when the event source is not capable of
-     fulfilling a Subscribe request due to the content of the Subscribe
-     request message.
-    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Receiver</td></tr><tr><td><b>[Subcode]</b></td><td>wse:SubscribeRequestInvalid</td></tr><tr><td><b>[Reason]</b></td><td><em>Text explaining the failure.</em></td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div><div class="div2">
-<h3><a name="EventSourceUnableToProcess" id="EventSourceUnableToProcess"/>6.7 EventSourceUnableToProcess</h3><p>
-     This fault is generated when the event source is not capable of
-     fulfilling a Subscribe request for local reasons unrelated to the
-     specific request.
-    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Receiver</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EventSourceUnableToProcess</td></tr><tr><td><b>[Reason]</b></td><td><em>Text explaining the failure; e.g., "The event
-        source has too many subscribers".</em></td></tr><tr><td><b>[Detail]</b></td><td>
-       &lt;wse:RetryAfter&gt; ? 
-       <em>(Optional)</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="UnableToRenew" id="UnableToRenew"/>6.8 UnableToRenew</h3><p>
-     This fault is generated when the event source is not capable of
-     fulfilling a Renew request for local reasons unrelated to the
-     specific request.
-    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Receiver</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnableToRenew</td></tr><tr><td><b>[Reason]</b></td><td><em>Text explaining the failure; e.g., "The event
-        source has too many subscribers".</em></td></tr><tr><td><b>[Detail]</b></td><td>
-        &lt;wse:RetryAfter&gt; ? 
-        <em>(Optional)</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="InvalidMessage" id="InvalidMessage"/>6.9 InvalidMessage</h3><p>
-     If a request message does not comply with the corresponding
-     outline listed above, the request MUST fail and the event source
-     or subscription manager MUST generate the following fault
-     indicating that the request is invalid:
-    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:InvalidMessage</td></tr><tr><td><b>[Reason]</b></td><td>The message is not valid and cannot be processed.</td></tr><tr><td><b>[Detail]</b></td><td><em>The invalid message</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"/>6.10 DeliveryFormatRequestUnavailable</h3><p>
+<h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"/>6.6 DeliveryFormatRequestUnavailable</h3><p>
      This fault is generated when a Subscribe request specifies a delivery 
      format that is not supported by the event source. Optionally, this 
      fault MAY contain a list of supported delivery format IRIs in the 
@@ -1349,19 +1330,19 @@
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:DeliveryFormatRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested delivery format is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
         &lt;wse:SupportedDeliveryFormat&gt; +
         <br/><em> Optional, one per delivery format supported by the receiver.</em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="EmptyFilter" id="EmptyFilter"/>6.11 EmptyFilter</h3><p>
+<h3><a name="EmptyFilter" id="EmptyFilter"/>6.7 EmptyFilter</h3><p>
      This fault MAY be generated when an Event Source detects a 
      wse:Subscribe request containing a filter that, for whatever 
      reason, will never evaluate to true.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EmptyFilter</td></tr><tr><td><b>[Reason]</b></td><td>The wse:Filter would result in zero Notifications.</td></tr><tr><td><b>[Detail]</b></td><td><em> The wse:Filter value. </em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="UnusableEPR" id="UnusableEPR"/>6.12 UnusableEPR</h3><p>
+<h3><a name="UnusableEPR" id="UnusableEPR"/>6.8 UnusableEPR</h3><p>
      This fault MAY be generated when an Event Source detects 
      that the wse:NotifyTo or wse:EndTo EPR is unusable.
     </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnusableEPR</td></tr><tr><td><b>[Reason]</b></td><td>An EPR in the Subscribe request message is unusable.</td></tr><tr><td><b>[Detail]</b></td><td><em> The specific EPR that generated the error and why. </em></td></tr></tbody></table></div><div class="div2">
-<h3><a name="InvalidSubscription" id="InvalidSubscription"/>6.13 InvalidSubscription</h3><p>
+<h3><a name="UnknownSubscription" id="UnknownSubscription"/>6.9 UnknownSubscription</h3><p>
      This fault is generated when a request specifies a subscription
-     that is not valid.
-    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:InvalidSubscription</td></tr><tr><td><b>[Reason]</b></td><td>the subscription is not valid.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
+     that is not active.
+    </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnknownSubscription</td></tr><tr><td><b>[Reason]</b></td><td>the subscription is not active.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
 <h2><a name="Security" id="Security"/>7 Security Considerations</h2><div class="div2">
 <h3><a name="MessageSecurity" id="MessageSecurity"/>7.1 Message Security</h3><p>
      It is strongly RECOMMENDED that the communication between
@@ -1504,7 +1485,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_2232" id="iddiv2_1_2232"/>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_2039" id="iddiv2_1_2039"/>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.
@@ -1546,7 +1527,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/">http://www.w3.org/TR/ws-policy/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2340" id="iddiv2_1_2340"/>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_2147" id="iddiv2_1_2147"/>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>
@@ -1736,7 +1717,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_2636" id="idexample_1_2636"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2443" id="idexample_1_2443"/>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;
@@ -1756,7 +1737,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_2646" id="iddiv3_1_2646"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2453" id="iddiv3_1_2453"/>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>.
@@ -1767,7 +1748,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_2662" id="iddiv3_1_2662"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2469" id="iddiv3_1_2469"/>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 
@@ -1779,7 +1760,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_2667" id="iddiv4_1_2667"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2474" id="iddiv4_1_2474"/>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>
@@ -1793,7 +1774,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_2685" id="iddiv4_1_2685"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2492" id="iddiv4_1_2492"/>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>
@@ -1817,7 +1798,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_2706" id="idexample_1_2706"/>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_2513" id="idexample_1_2513"/>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/"
@@ -1852,7 +1833,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_2712" id="iddiv3_1_2712"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2519" id="iddiv3_1_2519"/>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>.
@@ -1868,7 +1849,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_2728" id="iddiv2_1_2728"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2535" id="iddiv2_1_2535"/>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 
@@ -2371,4 +2352,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7698">7698</a></td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6569">6569</a></td></tr><tr><td> 2009/10/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7589">7589</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</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=7426">7426</a></td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7554">7554</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Friday, 2 October 2009 16:01:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 2 October 2009 16:01:27 GMT