WWW/2002/ws/ra/edcopies wsenum.html,1.162,1.163 wsenum.xml,1.153,1.154 wseventing.html,1.227,1.228 wseventing.xml,1.219,1.220

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

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


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.219
retrieving revision 1.220
diff -u -d -r1.219 -r1.220
--- wseventing.xml	16 Feb 2011 05:25:11 -0000	1.219
+++ wseventing.xml	16 Feb 2011 05:44:56 -0000	1.220
@@ -1126,8 +1126,17 @@
        <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 MUST generate a 
+        If an event source detects this condition during the processing
+        of the Subscribe request it MUST generate a 
         wse:EmptyFilter fault in response to the Subscribe request message.
+        If, after the SubscribeResponse message has been sent, the
+        event source determines that the filter will never evaluate to true 
+        for the lifetime of the subscription, or if there is an error within 
+        the filter expression, the subscription MUST be terminated. In 
+        this case if an EndTo was provided, then a SubscriptionEnd message 
+        MUST be sent with a Status value of
+        "http://www.w3.org/&wsevt.nsprefix;/ws-evt/SourceCancelling".
+
        </p>
       </def>
      </gitem>
@@ -5288,6 +5297,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12063">12063</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/02/15 </td>
+      <td> DD </td>
+      <td> Added resolution of issue
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11949">11949</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.227
retrieving revision 1.228
diff -u -d -r1.227 -r1.228
--- wseventing.html	16 Feb 2011 05:25:11 -0000	1.227
+++ wseventing.html	16 Feb 2011 05:44:56 -0000	1.228
@@ -74,26 +74,26 @@
 &nbsp;&nbsp;&nbsp;6.11 <a href="#NoDeliveryMechanismEstablished">NoDeliveryMechanismEstablished</a><br/>
 &nbsp;&nbsp;&nbsp;6.12 <a href="#CannotProcessFilter">CannotProcessFilter</a><br/>
 7 <a href="#Security">Security Considerations</a><br/>
-&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x2137">Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2x1x2146">Subscriptions</a><br/>
-&nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2x1x2151">Endpoint Verification</a><br/>
+&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x2139">Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;7.2 <a href="#iddiv2x1x2148">Subscriptions</a><br/>
+&nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2x1x2153">Endpoint Verification</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="#iddiv2x1x2177">EventSource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2x1x2301">SubscriptionManager Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2x1x2179">EventSource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2x1x2303">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="#iddiv2x1x2364">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2x1x2524">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2366">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2x1x2526">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="#iddiv3x1x2674">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3x1x2722">Bindings for Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4x1x2727">Binding for Unwrapped Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4x1x2748">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3x1x2676">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3x1x2724">Bindings for Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4x1x2729">Binding for Unwrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4x1x2750">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="#iddiv3x1x2775">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3x1x2777">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/>
@@ -661,8 +661,17 @@
        </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 MUST generate a 
+        If an event source detects this condition during the processing
+        of the Subscribe request it MUST generate a 
         wse:EmptyFilter fault in response to the Subscribe request message.
+        If, after the SubscribeResponse message has been sent, the
+        event source determines that the filter will never evaluate to true 
+        for the lifetime of the subscription, or if there is an error within 
+        the filter expression, the subscription MUST be terminated. In 
+        this case if an EndTo was provided, then a SubscriptionEnd message 
+        MUST be sent with a Status value of
+        "http://www.w3.org/2002/ws/ra/edcopies/ws-evt/SourceCancelling".
+
        </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/2002/ws/ra/edcopies/ws-evt/Dialects/XPath10".
        </p><p>
@@ -1455,7 +1464,7 @@
     urged to perform a security analysis to determine their particular 
     threat profile and the appropriate responses to those threats.
    </p><div class="div2">
-<h3><a name="iddiv2x1x2137" id="iddiv2x1x2137"/>7.1 Notifications</h3><p>
+<h3><a name="iddiv2x1x2139" id="iddiv2x1x2139"/>7.1 Notifications</h3><p>
      The information contained in Notifications might be sensitive. In 
      such cases it is advisable to authenticate and authorize subscribers 
      as part of the processing of the Subscribe request. Note that an 
@@ -1476,7 +1485,7 @@
      and trace the origin of such attempts. Additionally, the 
      authorization of Subscribers reduces the pool of potential attackers.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x2146" id="iddiv2x1x2146"/>7.2 Subscriptions</h3><p>
+<h3><a name="iddiv2x1x2148" id="iddiv2x1x2148"/>7.2 Subscriptions</h3><p>
      Once created, subscriptions ought to be treated as protected 
      resources. Renew, GetStatus, and Unsubscribe requests ought to be 
      authenticated and authorized (for example, the identity of the 
@@ -1491,7 +1500,7 @@
      the identities of these entities are discovered and verified) 
      are particular to individual deployments.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x2151" id="iddiv2x1x2151"/>7.3 Endpoint Verification</h3><p>
+<h3><a name="iddiv2x1x2153" id="iddiv2x1x2153"/>7.3 Endpoint Verification</h3><p>
      Implementations that perform validity checks on the EPRs used in 
      WS-Eventing (wse:NotifyTo, wse:EndTo) are advised that such checks 
      can be misused to obtain information about a target network. For 
@@ -1542,7 +1551,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="iddiv2x1x2177" id="iddiv2x1x2177"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2x1x2179" id="iddiv2x1x2179"/>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 -
@@ -1654,7 +1663,7 @@
      (10) - (12) contains the EventDescription data that describes the 
      syntax of the events that this event source might send.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x2301" id="iddiv2x1x2301"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2x1x2303" id="iddiv2x1x2303"/>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
@@ -1725,7 +1734,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="iddiv2x1x2364" id="iddiv2x1x2364"/>11.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+<h3><a name="iddiv2x1x2366" id="iddiv2x1x2366"/>11.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
          WS-I Profile, Basic Profile Version 1.2
         </cite></a>
         , R. Chumbley, et al, Editors.
@@ -1787,7 +1796,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="iddiv2x1x2524" id="iddiv2x1x2524"/>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="iddiv2x1x2526" id="iddiv2x1x2526"/>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>
@@ -1865,7 +1874,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="idexamplex1x2664" id="idexamplex1x2664"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wsevd:EventDescriptions 
+<div class="exampleHeader"><a name="idexamplex1x2666" id="idexamplex1x2666"/>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;
@@ -1886,7 +1895,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="iddiv3x1x2674" id="iddiv3x1x2674"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x2676" id="iddiv3x1x2676"/>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>.
@@ -1933,7 +1942,7 @@
 (10) &lt;/mex:GetMetadataResponse&gt; </pre></div></div><p><a href="#mexEVD">Example A-4</a> shows how the Event Descriptions metadata
       might appear within a GetMetadataResponse message.
      </p></div><div class="div3">
-<h4><a name="iddiv3x1x2722" id="iddiv3x1x2722"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x2724" id="iddiv3x1x2724"/>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 
@@ -1945,7 +1954,7 @@
       Format, implementations MAY provide a Notification WSDL (see below) 
       that explicitly describes the notification operations. 
      </p><div class="div4">
-<h5><a name="iddiv4x1x2727" id="iddiv4x1x2727"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2729" id="iddiv4x1x2729"/>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>
@@ -1960,7 +1969,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="iddiv4x1x2748" id="iddiv4x1x2748"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2750" id="iddiv4x1x2750"/>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>
@@ -1986,7 +1995,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="idexamplex1x2769" id="idexamplex1x2769"/>Example A-5: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexamplex1x2771" id="idexamplex1x2771"/>Example A-5: 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/"
@@ -2021,7 +2030,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="iddiv3x1x2775" id="iddiv3x1x2775"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3x1x2777" id="iddiv3x1x2777"/>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>.
@@ -2773,4 +2782,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12051">12051</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11698">11698</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11894">11894</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12063">12063</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=12063">12063</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11949">11949</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.162
retrieving revision 1.163
diff -u -d -r1.162 -r1.163
--- wsenum.html	16 Feb 2011 05:36:19 -0000	1.162
+++ wsenum.html	16 Feb 2011 05:44:56 -0000	1.163
@@ -67,15 +67,15 @@
 &nbsp;&nbsp;&nbsp;5.9 <a href="#EmptyFilter">EmptyFilter</a><br/>
 &nbsp;&nbsp;&nbsp;5.10 <a href="#MaxElementsMustBeZero">MaxElementsMustBeZero</a><br/>
 6 <a href="#Security">Security Considerations</a><br/>
-&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2x1x1872">Creating Enumeration Contexts</a><br/>
-&nbsp;&nbsp;&nbsp;6.2 <a href="#iddiv2x1x1877">Protecting Enumeration Contexts</a><br/>
-&nbsp;&nbsp;&nbsp;6.3 <a href="#iddiv2x1x1884">Endpoint Verification</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2x1x1874">Creating Enumeration Contexts</a><br/>
+&nbsp;&nbsp;&nbsp;6.2 <a href="#iddiv2x1x1879">Protecting Enumeration Contexts</a><br/>
+&nbsp;&nbsp;&nbsp;6.3 <a href="#iddiv2x1x1886">Endpoint Verification</a><br/>
 7 <a href="#metadata">WS-Enumeration Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x1904">Enumeration Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;7.1 <a href="#iddiv2x1x1906">Enumeration Assertion</a><br/>
 8 <a href="#acks">Acknowledgements</a><br/>
 9 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2x1x2024">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2x1x2236">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2x1x2026">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2x1x2238">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
 B <a href="#WSDL">WSDL</a><br/>
@@ -514,8 +514,17 @@
        </p><p>
         It is possible for a Enumerate request to contain a filter that
         will never evaluate to true for the lifetime of the enumeration.
-        If a data source detects this condition it MUST generate a
+        If a data source detects this condition during the processing
+        of the Enumerate request it MUST generate a
         wsen:EmptyFilter fault in response to the Enumerate request message.
+        If, after the EnumerateResponse message has been sent, the
+        data source determines that the filter will never evaluate to true 
+        for the lifetime of the enumeration, or if there is an error within 
+        the filter expression, the enumeration MUST be terminated. In this 
+        case if an EndTo was provided, then a EnumerationEnd message MUST 
+        be sent with a Reason value of
+        "http://www.w3.org/2002/ws/ra/edcopies/ws-evt/SourceCancelling".
+
        </p></dd><dt class="label"><a name="Dialect" id="Dialect"/><b>[Body]</b>/wsen:Enumerate/wsen:NewContext/wsen:Filter/@Dialect </dt><dd><p>
         Implied value is
         "http://www.w3.org/2002/ws/ra/edcopies/ws-enu/Dialects/XPath10".
@@ -1226,7 +1235,7 @@
     a security analysis to determine their particular threat profile and 
     the appropriate responses to those threats.
    </p><div class="div2">
-<h3><a name="iddiv2x1x1872" id="iddiv2x1x1872"/>6.1 Creating Enumeration Contexts</h3><p>
+<h3><a name="iddiv2x1x1874" id="iddiv2x1x1874"/>6.1 Creating Enumeration Contexts</h3><p>
      An enumeration represents a logical cursor through a sequence of 
      data items. If the information in these items is sensitive, it is 
      advisable to for Data Sources to authenticate and authorize Consumers 
@@ -1237,7 +1246,7 @@
      the time the Enumerate request is processed or varies during the 
      lifetime of the enumeration.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x1877" id="iddiv2x1x1877"/>6.2 Protecting Enumeration Contexts</h3><p>
+<h3><a name="iddiv2x1x1879" id="iddiv2x1x1879"/>6.2 Protecting Enumeration Contexts</h3><p>
      Once created, it is advisable to treat Enumeration Contexts as 
      protected resources. Renew, GetStatus, and Release requests ought to 
      be authenticated and authorized (for example, the identity of the 
@@ -1259,7 +1268,7 @@
      Data Sources are advised to authenticate and authorize clients 
      sending Enumerate requests.
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x1884" id="iddiv2x1x1884"/>6.3 Endpoint Verification</h3><p>
+<h3><a name="iddiv2x1x1886" id="iddiv2x1x1886"/>6.3 Endpoint Verification</h3><p>
      Data Source implementations that perform validity checks on the 
      EndTo EPR used in the Enumerate request are advised that such checks 
      can be misused to obtain information about a target network. For 
@@ -1301,7 +1310,7 @@
     that indicate a particular security mechanism used to protect 
     the WS-Enumeration operations supported by this endpoint. 
    </p><div class="div2">
-<h3><a name="iddiv2x1x1904" id="iddiv2x1x1904"/>7.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2x1x1906" id="iddiv2x1x1906"/>7.1 Enumeration Assertion</h3><p>
      Services indicate support for the WS-Enumeration's definition of a 
      data source through the use of the Web Services 
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy - 
@@ -1416,7 +1425,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2024" id="iddiv2x1x2024"/>9.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
+<h3><a name="iddiv2x1x2026" id="iddiv2x1x2026"/>9.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"/>BP12</dt><dd><a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
          WS-I Profile, Basic Profile Version 1.2
         </cite></a>
         , R. Chumbley, et al, Editors.
@@ -1498,7 +1507,7 @@
        , A. Berglund, et al., Editors.
        World Wide Web Consortium (W3C), 23 January 2007. 
       Available at <a href="http://www.w3.org/TR/xpath20/">http://www.w3.org/TR/xpath20/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2x1x2236" id="iddiv2x1x2236"/>9.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+<h3><a name="iddiv2x1x2238" id="iddiv2x1x2238"/>9.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
         W3C Working Group Draft, "Web Services Metadata Exchange
           (WS-MetadataExchange) 1.1"
        </cite></a>
@@ -2097,4 +2106,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12051">12051</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11894">11894</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12063">12063</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11990">11990</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=11990">11990</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11949">11949</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.153
retrieving revision 1.154
diff -u -d -r1.153 -r1.154
--- wsenum.xml	16 Feb 2011 05:36:19 -0000	1.153
+++ wsenum.xml	16 Feb 2011 05:44:56 -0000	1.154
@@ -858,8 +858,17 @@
        <p>
         It is possible for a Enumerate request to contain a filter that
         will never evaluate to true for the lifetime of the enumeration.
-        If a data source detects this condition it MUST generate a
+        If a data source detects this condition during the processing
+        of the Enumerate request it MUST generate a
         wsen:EmptyFilter fault in response to the Enumerate request message.
+        If, after the EnumerateResponse message has been sent, the
+        data source determines that the filter will never evaluate to true 
+        for the lifetime of the enumeration, or if there is an error within 
+        the filter expression, the enumeration MUST be terminated. In this 
+        case if an EndTo was provided, then a EnumerationEnd message MUST 
+        be sent with a Reason value of
+        "http://www.w3.org/&wsenu.nsprefix;/ws-evt/SourceCancelling".
+
        </p>
 
       </def>
@@ -4028,6 +4037,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11990">11990</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/02/15 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11949">11949</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Received on Wednesday, 16 February 2011 05:45:00 UTC