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

WWW/2002/ws/ra/edcopies wsenum.html,1.42,1.43 wsenum.xml,1.33,1.34 wseventing.html,1.55,1.56 wseventing.xml,1.47,1.48

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 04 Jun 2009 20:38:57 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MCJiD-00040f-Ie@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv15317

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
Log Message:
6916


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -d -r1.47 -r1.48
--- wseventing.xml	4 Jun 2009 20:30:22 -0000	1.47
+++ wseventing.xml	4 Jun 2009 20:38:55 -0000	1.48
@@ -886,7 +886,7 @@
        <p>
         If the event source does not support the requested
         delivery mode, the request MUST fail, and the event source
-        MAY generate a wse:DeliveryModeRequestedUnavailable fault
+        MUST generate a wse:DeliveryModeRequestedUnavailable fault
         indicating that the requested delivery mode is not
         supported.
        </p>
@@ -974,7 +974,7 @@
        <p>
         If the expiration time is either a zero duration or a
         specific time that occurs in the past according to the event
-        source, then the request MUST fail, and the event source MAY
+        source, then the request MUST fail, and the event source MUST
         generate a wse:InvalidExpirationTime fault indicating that an
         invalid expiration time was requested.
        </p>
@@ -984,7 +984,7 @@
         available, and so are only able to accept durations as
         expirations. If such a source receives a Subscribe request
         containing a specific time expiration, then the request MAY
-        fail; if so, the event source MAY generate a
+        fail; if so, the event source MUST generate a
         wse:UnsupportedExpirationType fault indicating that an
         unsupported expiration type was requested.
        </p>
@@ -1002,7 +1002,7 @@
         notification MUST NOT be sent to the event sink. Implied
         value is an expression that always returns true. If the event
         source does not support filtering, then a request that
-        specifies a filter MUST fail, and the event source MAY
+        specifies a filter MUST fail, and the event source MUST
         generate a wse:FilteringNotSupported fault indicating that
         filtering is not supported.
        </p>
@@ -1010,7 +1010,7 @@
        <p>
         If the event source supports filtering but cannot honor
         the requested filtering, the request MUST fail, and the event
-        source MAY generate a wse:FilteringRequestedUnavailable fault
+        source MUST generate a wse:FilteringRequestedUnavailable fault
         indicating that the requested filter dialect is not
         supported.
        </p>
@@ -1018,7 +1018,7 @@
        <p>
         It is possible for a Subscribe request to contain a filter that 
         will never evaluate to true for the lifetime of the Subscription. 
-        If an Event Source detects this condition it MAY generate a 
+        If an Event Source detects this condition it MUST generate a 
         wse:EmptyFilter fault in response to the Subscribe request message.
        </p>
       </def>
@@ -1114,7 +1114,7 @@
      wsa:Address IRI.
      Detecting these errors during Subscribe processing will lessen the chances
      of the subscriber creating an unusable subscription.  If this check is
-     performed and a problem is detected then the event source MAY generate
+     performed and a problem is detected then the event source MUST generate
      a wse:UnusableEPR fault rather than returning the SubscribeResponse 
      message.
     </p>
@@ -1193,7 +1193,7 @@
 
     <p>
      If the event source chooses not to accept a subscription, the
-     request MUST fail, and the event source MAY generate a
+     request MUST fail, and the event source MUST generate a
      wse:EventSourceUnableToProcess fault indicating that the request
      was not accepted.
     </p>
@@ -1411,7 +1411,7 @@
     <p>
      If the subscription manager chooses not to renew this
      subscription, the request MUST fail, and the subscription manager
-     MAY generate a wse:UnableToRenew fault indicating that the
+     MUST generate a wse:UnableToRenew fault indicating that the
      renewal was not accepted.
     </p>
 
@@ -2366,7 +2366,7 @@
     <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 MAY generate the following fault
+     or subscription manager MUST generate the following fault
      indicating that the request is invalid:
     </p>
 
@@ -3666,6 +3666,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6955">6955</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/06/04 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6916">6916</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -d -r1.55 -r1.56
--- wseventing.html	4 Jun 2009 20:30:22 -0000	1.55
+++ wseventing.html	4 Jun 2009 20:38:55 -0000	1.56
@@ -507,7 +507,7 @@
        </p><p>
         If the event source does not support the requested
         delivery mode, the request MUST fail, and the event source
-        MAY generate a wse:DeliveryModeRequestedUnavailable fault
+        MUST generate a wse:DeliveryModeRequestedUnavailable fault
         indicating that the requested delivery mode is not
         supported.
        </p></dd><dt class="label"><b>[Body]</b>/wse:Subscribe/wse:Delivery/@Mode="http://www.w3.org/2009/02/ws-evt/DeliveryModes/Push"
@@ -553,7 +553,7 @@
        </p><p>
         If the expiration time is either a zero duration or a
         specific time that occurs in the past according to the event
-        source, then the request MUST fail, and the event source MAY
+        source, then the request MUST fail, and the event source MUST
         generate a wse:InvalidExpirationTime fault indicating that an
         invalid expiration time was requested.
        </p><p>
@@ -561,7 +561,7 @@
         available, and so are only able to accept durations as
         expirations. If such a source receives a Subscribe request
         containing a specific time expiration, then the request MAY
-        fail; if so, the event source MAY generate a
+        fail; if so, the event source MUST generate a
         wse:UnsupportedExpirationType fault indicating that an
         unsupported expiration type was requested.
        </p></dd><dt class="label"><b>[Body]</b>/wse:Subscribe/wse:Filter </dt><dd><p>
@@ -572,19 +572,19 @@
         notification MUST NOT be sent to the event sink. Implied
         value is an expression that always returns true. If the event
         source does not support filtering, then a request that
-        specifies a filter MUST fail, and the event source MAY
+        specifies a filter MUST fail, and the event source MUST
         generate a wse:FilteringNotSupported fault indicating that
         filtering is not supported.
        </p><p>
         If the event source supports filtering but cannot honor
         the requested filtering, the request MUST fail, and the event
-        source MAY generate a wse:FilteringRequestedUnavailable fault
+        source MUST generate a wse:FilteringRequestedUnavailable fault
         indicating that the requested filter dialect is not
         supported.
        </p><p>
         It is possible for a Subscribe request to contain a filter that 
         will never evaluate to true for the lifetime of the Subscription. 
-        If an Event Source detects this condition it MAY generate a 
+        If an Event Source detects this condition it MUST generate a 
         wse:EmptyFilter fault in response to the Subscribe request message.
        </p></dd><dt class="label"><a name="Dialect" id="Dialect"/><b>[Body]</b>/wse:Subscribe/wse:Filter/@Dialect </dt><dd><p>
         Implied value is "http://www.w3.org/TR/1999/REC-xpath-19991116".
@@ -628,7 +628,7 @@
      wsa:Address IRI.
      Detecting these errors during Subscribe processing will lessen the chances
      of the subscriber creating an unusable subscription.  If this check is
-     performed and a problem is detected then the event source MAY generate
+     performed and a problem is detected then the event source MUST generate
      a wse:UnusableEPR fault rather than returning the SubscribeResponse 
      message.
     </p><p>
@@ -675,7 +675,7 @@
      constrained by this specification.
     </p><p>
      If the event source chooses not to accept a subscription, the
-     request MUST fail, and the event source MAY generate a
+     request MUST fail, and the event source MUST generate a
      wse:EventSourceUnableToProcess fault indicating that the request
      was not accepted.
     </p><p><a href="#Table4">Example 4-1</a> lists another hypothetical request to create a
@@ -837,7 +837,7 @@
        </p></dd></dl><p>
      If the subscription manager chooses not to renew this
      subscription, the request MUST fail, and the subscription manager
-     MAY generate a wse:UnableToRenew fault indicating that the
+     MUST generate a wse:UnableToRenew fault indicating that the
      renewal was not accepted.
     </p><p>
      Other components of the outline above are not further
@@ -1343,7 +1343,7 @@
 <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 MAY generate the following fault
+     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>
@@ -2093,4 +2093,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6429">6429</a></td></tr><tr><td> 2009/05/21 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6674">6674</a></td></tr><tr><td> 2009/05/27 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6906">6906</a></td></tr><tr><td> 2009/06/04 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6955">6955</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=6955">6955</a></td></tr><tr><td> 2009/06/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6916">6916</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.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- wsenum.html	27 May 2009 22:36:17 -0000	1.42
+++ wsenum.html	4 Jun 2009 20:38:55 -0000	1.43
@@ -376,7 +376,7 @@
         If the expiration time is either a zero
         duration or a specific time that occurs in the past according to
         the data source, then the request MUST fail, and the data source
-        MAY generate a wsen:InvalidExpirationTime fault indicating that an 
+        MUST generate a wsen:InvalidExpirationTime fault indicating that an 
         invalid expiration time was requested.
        </p><p>
         Some data sources may not have a "wall time"
@@ -397,17 +397,17 @@
         desired.
        </p><p>
         If the data source does not support
-        filtering, the request MUST fail, and the data source MAY generate
+        filtering, the request MUST fail, and the data source MUST generate
         a wsen:FilteringNotSupported fault.
        </p><p>
         If the data source supports filtering but
         cannot honor the requested filter dialect, the request MUST fail,
-        and the data source MAY generate a 
+        and the data source MUST generate a 
         wsen:FilterDialectRequestUnavailable fault.
        </p><p>
         If the data source supports filtering and the
         requested dialect but cannot process the requested filter content,
-        the request MUST fail, and the data source MAY generate a 
+        the request MUST fail, and the data source MUST generate a 
         wsen:CannotProcessFilter fault.
        </p></dd><dt class="label"><a name="Dialect" id="Dialect"/><b>[Body]</b>/wsen:Enumerate/wsen:Filter/@Dialect </dt><dd><p>
         Implied value is
@@ -447,7 +447,7 @@
      wsa:Address IRI.
      Detecting these errors during Enumerate processing will lessen the chances
      of the consumer creating an unusable enumeration.  If this check is
-     performed and a problem is detected then the event source MAY generate
+     performed and a problem is detected then the event source MUST generate
      a wsen:UnusableEPR fault rather than returning the EnumerateResponse.
      message.
     </p><p>
@@ -580,7 +580,8 @@
         returned in a Pull response), or because it has been Released, or
         because it has expired, or because the data source has had to
         invalidate the context, then the data source SHOULD fail the
-        request, and MAY generate the a wsen:InvalidEnumerationContext fault.
+        request, and if so, MUST generate the a wsen:InvalidEnumerationContext 
+        fault.
        </p><p>
         Note that the data source may not be able to
         determine that an enumeration context is not valid, especially if
@@ -808,7 +809,8 @@
         returned in a Pull response), or because it has been Released, or
         because it has expired, or because the data source has had to
         invalidate the context, then the data source SHOULD fail the
-        request, and MAY generate a wsen:InvalidEnumerationContext fault.
+        request, and if so, MUST generate a wsen:InvalidEnumerationContext 
+        fault.
        </p></dd></dl><p>
      Other components of the outline above are not
      further constrained by this specification.
@@ -1661,4 +1663,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6696">6696</a></td></tr><tr><td> 2009/05/21 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6674">6674</a></td></tr><tr><td> 2009/05/26 </td><td> KW </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6920">6920</a></td></tr><tr><td> 2009/05/27 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6906">6906</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=6906">6906</a></td></tr><tr><td> 2009/06/04 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6916">6916</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -d -r1.33 -r1.34
--- wsenum.xml	27 May 2009 22:36:17 -0000	1.33
+++ wsenum.xml	4 Jun 2009 20:38:55 -0000	1.34
@@ -646,7 +646,7 @@
         If the expiration time is either a zero
         duration or a specific time that occurs in the past according to
         the data source, then the request MUST fail, and the data source
-        MAY generate a wsen:InvalidExpirationTime fault indicating that an 
+        MUST generate a wsen:InvalidExpirationTime fault indicating that an 
         invalid expiration time was requested.
        </p>
 
@@ -678,21 +678,21 @@
        </p>
        <p>
         If the data source does not support
-        filtering, the request MUST fail, and the data source MAY generate
+        filtering, the request MUST fail, and the data source MUST generate
         a wsen:FilteringNotSupported fault.
        </p>
 
        <p>
         If the data source supports filtering but
         cannot honor the requested filter dialect, the request MUST fail,
-        and the data source MAY generate a 
+        and the data source MUST generate a 
         wsen:FilterDialectRequestUnavailable fault.
        </p>
 
        <p>
         If the data source supports filtering and the
         requested dialect but cannot process the requested filter content,
-        the request MUST fail, and the data source MAY generate a 
+        the request MUST fail, and the data source MUST generate a 
         wsen:CannotProcessFilter fault.
        </p>
 
@@ -776,7 +776,7 @@
      wsa:Address IRI.
      Detecting these errors during Enumerate processing will lessen the chances
      of the consumer creating an unusable enumeration.  If this check is
-     performed and a problem is detected then the event source MAY generate
+     performed and a problem is detected then the event source MUST generate
      a wsen:UnusableEPR fault rather than returning the EnumerateResponse.
      message.
     </p>
@@ -972,7 +972,8 @@
         returned in a Pull response), or because it has been Released, or
         because it has expired, or because the data source has had to
         invalidate the context, then the data source SHOULD fail the
-        request, and MAY generate the a wsen:InvalidEnumerationContext fault.
+        request, and if so, MUST generate the a wsen:InvalidEnumerationContext 
+        fault.
        </p>
 
        <p>
@@ -1314,7 +1315,8 @@
         returned in a Pull response), or because it has been Released, or
         because it has expired, or because the data source has had to
         invalidate the context, then the data source SHOULD fail the
-        request, and MAY generate a wsen:InvalidEnumerationContext fault.
+        request, and if so, MUST generate a wsen:InvalidEnumerationContext 
+        fault.
        </p>
 
       </def>
@@ -2883,6 +2885,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6906">6906</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/06/04 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6916">6916</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Thursday, 4 June 2009 20:39:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 4 June 2009 20:39:03 GMT