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

WWW/2002/ws/ra/edcopies wseventing.html,1.84,1.85 wseventing.xml,1.75,1.76

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 22 Sep 2009 22:01:15 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MqDQB-0008RI-9J@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv32344

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


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -d -r1.75 -r1.76
--- wseventing.xml	15 Sep 2009 19:43:09 -0000	1.75
+++ wseventing.xml	22 Sep 2009 22:01:13 -0000	1.76
@@ -1339,6 +1339,11 @@
     </p>
 
     <p>
+     If the subscription is not valid, the request MUST fail and the 
+     subscription manager MUST generate a wse:InvalidSubscription fault.
+    </p>
+
+    <p>
      If the subscription manager accepts a request to renew a
      subscription, it MUST reply with a response of the following
      form:
@@ -2467,6 +2472,39 @@
     </table>
    </div2>
 
+   <div2 id="InvalidSubscription">
+    <head>InvalidSubscription</head>
+
+    <p>
+     This fault is generated when a request specifies a subscription
+     that is not valid.
+    </p>
+
+    <table border="1">
+     <tbody>
+      <tr>
+       <td><kw>[Code]</kw></td>
+       <td>s12:Sender</td>
+      </tr>
+
+      <tr>
+       <td><kw>[Subcode]</kw></td>
+       <td>wse:InvalidSubscription</td>
+      </tr>
+
+      <tr>
+       <td><kw>[Reason]</kw></td>
+       <td>the subscription is not valid.</td>
+      </tr>
+
+      <tr>
+       <td><kw>[Detail]</kw></td>
+       <td><emph>none</emph></td>
+      </tr>
+     </tbody>
+    </table>
+   </div2>
+
   </div1>
 
   <div1 id="Security">
@@ -4112,6 +4150,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/09/22 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7698">7698</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -d -r1.84 -r1.85
--- wseventing.html	15 Sep 2009 19:43:09 -0000	1.84
+++ wseventing.html	22 Sep 2009 22:01:13 -0000	1.85
@@ -72,6 +72,7 @@
 &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/>
 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/>
@@ -82,13 +83,13 @@
 </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_2463">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2477">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_2482">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_2500">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2515">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2529">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_2534">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_2552">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_2527">Retrieving Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2541">Multiple Event Information Metadata Sections</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2579">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2593">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/>
@@ -811,6 +812,9 @@
      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.
+    </p><p>
      If the subscription manager accepts a request to renew a
      subscription, it MUST reply with a response of the following
      form:
@@ -1351,7 +1355,11 @@
 <h3><a name="UnusableEPR" id="UnusableEPR"/>6.12 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><div class="div1">
+    </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>
+     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">
 <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
@@ -1689,7 +1697,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_2455" id="idexample_1_2455"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2507" id="idexample_1_2507"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
 (02)        targetNamepace="http://www.example.org/oceanwatch/notifications"
 (03)        xmlns:wse="http://www.w3.org/2009/02/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch"&gt;
@@ -1709,7 +1717,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_2463" id="iddiv3_1_2463"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2515" id="iddiv3_1_2515"/>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>.
@@ -1720,7 +1728,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_2477" id="iddiv3_1_2477"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2529" id="iddiv3_1_2529"/>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 
@@ -1732,7 +1740,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_2482" id="iddiv4_1_2482"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2534" id="iddiv4_1_2534"/>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>
@@ -1746,7 +1754,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_2500" id="iddiv4_1_2500"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2552" id="iddiv4_1_2552"/>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>
@@ -1770,7 +1778,7 @@
      successful Subscribe request that used a particular Format URI. The 
      following is an example of a Notification WSDL: 
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2521" id="idexample_1_2521"/>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_2573" id="idexample_1_2573"/>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/"
@@ -1805,7 +1813,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_2527" id="iddiv3_1_2527"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2579" id="iddiv3_1_2579"/>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>.
@@ -1821,7 +1829,7 @@
       Format URI/@Identifier, there MUST NOT exist more than one 
       Notification WSDL document. 
      </p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2541" id="iddiv2_1_2541"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2593" id="iddiv2_1_2593"/>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 
@@ -2320,4 +2328,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6401">6401</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</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=6533">6533</a></td></tr><tr><td> 2009/09/22 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7698">7698</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 22 September 2009 22:01:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 September 2009 22:01:26 GMT