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

Fw: WWW/2002/ws/ra/edcopies wseventing.html,1.70,1.71 wseventing.xml,1.61,1.62

From: Doug Davis <dug@us.ibm.com>
Date: Wed, 5 Aug 2009 17:52:47 -0400
To: public-ws-resource-access@w3.org
Message-ID: <OFE5B65A18.D997302E-ON85257609.0077C792-85257609.007837F1@us.ibm.com>
just so no one is surprised - I noticed that a few faults still said 
something like "this fault is sent..." rather than "this fault is 
generated" - so I fixed those too - and this was in wseventing, wst and 
wsrt.   If this is a concern let me know and we can discuss. 

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
The more I'm around some people, the more I like my dog.
----- Forwarded by Doug Davis/Raleigh/IBM on 08/05/2009 05:48 PM -----

Doug Davis via cvs-syncmail <cvsmail@w3.org> 
Sent by: public-ws-resource-access-notifications-request@w3.org
08/05/2009 05:46 PM

To
public-ws-resource-access-notifications@w3.org
cc

Subject
WWW/2002/ws/ra/edcopies wseventing.html,1.70,1.71 wseventing.xml,1.61,1.62






Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv15576

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


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -d -r1.61 -r1.62
--- wseventing.xml               5 Aug 2009 21:00:49 -0000 1.61
+++ wseventing.xml               5 Aug 2009 21:46:53 -0000 1.62
@@ -1128,10 +1128,14 @@
     </p>
 
     <p>
-     If the event source chooses not to accept a subscription, the
-     request MUST fail, and the event source MUST generate a
-     wse:EventSourceUnableToProcess fault indicating that the request
-     was not accepted.
+     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
+     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.
     </p>
 
     <p>
@@ -2033,7 +2037,7 @@
     <head>InvalidExpirationTime</head>
 
     <p>
-     This fault is sent when a Subscribe request specifies an
+     This fault is generated when a Subscribe request specifies an
      expiration time that is in the past or an expiration duration of
      zero.
     </p>
@@ -2067,7 +2071,7 @@
     <head>UnsupportedExpirationType</head>
 
     <p>
-     This fault is sent when a Subscribe request specifies an
+     This fault is generated when a Subscribe request specifies an
      expiration time and the event source is only capable of accepting
      expiration durations; for instance, if the event source does not
      have access to absolute time.
@@ -2102,7 +2106,7 @@
     <head>FilteringNotSupported</head>
 
     <p>
-     This fault is sent when a Subscribe request contains a filter
+     This fault is generated when a Subscribe request contains a filter
      and the event source does not support filtering.
     </p>
 
@@ -2135,7 +2139,7 @@
     <head>FilteringRequestedUnavailable</head>
 
     <p>
-     This fault is sent when a Subscribe request specifies a filter
+     This fault is generated when a Subscribe request specifies a filter
      dialect that the event source does not support. Optionally, this
      fault may contain a list of supported filter dialect URIs in the
      Detail property.
@@ -2171,11 +2175,47 @@
     </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 sent when the event source is not capable of
+     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>
@@ -2215,7 +2255,7 @@
     <head>UnableToRenew</head>
 
     <p>
-     This fault is sent when the event source is not capable of
+     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>
@@ -2289,7 +2329,7 @@
     <head>DeliveryFormatRequestUnavailable</head>
 
     <p>
-     This fault is sent when a Subscribe request specifies a delivery 
+     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 URIs in the 
      Detail property.
@@ -3621,6 +3661,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159
">7159</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/08/05 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7205
">7205</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -d -r1.70 -r1.71
--- wseventing.html              5 Aug 2009 21:00:49 -0000 1.70
+++ wseventing.html              5 Aug 2009 21:46:53 -0000 1.71
@@ -65,12 +65,13 @@
 &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="#EventSourceUnableToProcess">EventSourceUnableToProcess</a><br/>
-&nbsp;&nbsp;&nbsp;6.7 <a href="#UnableToRenew">UnableToRenew</a><br/>
-&nbsp;&nbsp;&nbsp;6.8 <a href="#InvalidMessage">InvalidMessage</a><br/>
-&nbsp;&nbsp;&nbsp;6.9 <a 
href="#DeliveryFormatRequestedUnavailable">DeliveryFormatRequestUnavailable</a><br/>
-&nbsp;&nbsp;&nbsp;6.10 <a href="#EmptyFilter">EmptyFilter</a><br/>
-&nbsp;&nbsp;&nbsp;6.11 <a href="#UnusableEPR">UnusableEPR</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/>
 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/>
@@ -634,10 +635,14 @@
      Other components of the outline above are not further
      constrained by this specification.
     </p><p>
-     If the event source chooses not to accept a subscription, the
-     request MUST fail, and the event source MUST generate a
-     wse:EventSourceUnableToProcess fault indicating that the request
-     was not accepted.
+     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
+     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.
     </p><p><a href="#Table4">Example 4-1</a> lists another hypothetical 
request to create a
      subscription.
     </p><div class="exampleOuter">
@@ -1246,22 +1251,22 @@
         Optional extensibility attributes that do not affect processing.
        </p></dd></dl></div><div class="div2">
 <h3><a name="InvalidExpirationTime" id="InvalidExpirationTime"/>6.2 
InvalidExpirationTime</h3><p>
-     This fault is sent when a Subscribe request specifies an
+     This fault is generated when a Subscribe request specifies an
      expiration time that is in the past or an expiration duration of
      zero.
     </p><table 
border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:InvalidExpirationTime</td></tr><tr><td><b>[Reason]</b></td><td>The 
expiration time requested is 
invalid.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div 
class="div2">
 <h3><a name="UnsupportedExpirationType" 
id="UnsupportedExpirationType"/>6.3 UnsupportedExpirationType</h3><p>
-     This fault is sent when a Subscribe request specifies an
+     This fault is generated when a Subscribe request specifies an
      expiration time and the event source is only capable of accepting
      expiration durations; for instance, if the event source does not
      have access to absolute time.
     </p><table 
border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnsupportedExpirationType</td></tr><tr><td><b>[Reason]</b></td><td>Only 
expiration durations are 
supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div 
class="div2">
 <h3><a name="FilteringNotSupported" id="FilteringNotSupported"/>6.4 
FilteringNotSupported</h3><p>
-     This fault is sent when a Subscribe request contains a filter
+     This fault is generated when a Subscribe request contains a filter
      and the event source does not support filtering.
     </p><table 
border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>Filtering 
is not 
supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div 
class="div2">
 <h3><a name="FilteringRequestedUnavailable" 
id="FilteringRequestedUnavailable"/>6.5 
FilteringRequestedUnavailable</h3><p>
-     This fault is sent when a Subscribe request specifies a filter
+     This fault is generated when a Subscribe request specifies a filter
      dialect that the event source does not support. Optionally, this
      fault may contain a list of supported filter dialect URIs in the
      Detail property.
@@ -1269,42 +1274,47 @@
         &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="EventSourceUnableToProcess" 
id="EventSourceUnableToProcess"/>6.6 EventSourceUnableToProcess</h3><p>
-     This fault is sent when the event source is not capable of
+<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.7 UnableToRenew</h3><p>
-     This fault is sent when the event source is not capable of
+<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.8 
InvalidMessage</h3><p>
+<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.9 
DeliveryFormatRequestUnavailable</h3><p>
-     This fault is sent when a Subscribe request specifies a delivery 
+<h3><a name="DeliveryFormatRequestedUnavailable" 
id="DeliveryFormatRequestedUnavailable"/>6.10 
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 URIs in the 
      Detail property.
     </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.10 EmptyFilter</h3><p>
+<h3><a name="EmptyFilter" id="EmptyFilter"/>6.11 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.11 UnusableEPR</h3><p>
+<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">
@@ -2047,4 +2057,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6692
">6692</a></td></tr><tr><td> 2009/08/04 </td><td> DD </td><td> Added 
resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7136
">7136</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added 
resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6432
">6432</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added 
resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159
">7159</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=7159
">7159</a></td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added 
resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7205
">7205</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 5 August 2009 21:53:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:09 GMT