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

WWW/2002/ws/ra/test scenario.html,1.13,1.14 scenario.xml,1.13,1.14

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 22 Mar 2011 23:50:50 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1Q2BLe-0006CK-AM@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/test
In directory hutz:/tmp/cvs-serv23710

Modified Files:
	scenario.html scenario.xml 
Log Message:
Updates from Nathan for MaxTime test


Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/test/scenario.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- scenario.xml	17 Feb 2011 00:48:45 -0000	1.13
+++ scenario.xml	22 Mar 2011 23:50:48 -0000	1.14
@@ -2955,14 +2955,10 @@
         <head>Sequence</head>
 
         <p>
-          The following diagram illustrates the sequence of messages for the 
-          MaxTime Test.  Note that the data source is not able to assemble 
-          the second EnumerateResponse message before the duration 
-          specified in the MaxTime element has passed.
+          The messaging sequence for this test is identical to that of the 
+          Basic Test. 
         </p>
 
-        <graphic source='scenario/enum_maxtime_test.jpg'/>
-
       </div3>
 
       <div3>
@@ -2989,7 +2985,34 @@
           </item>
           <item>
             <p>
-              Receipt of a wsen:TimedOut fault by the data consumer
+             Receipt of valid EnumerateResponse message with zero items and 
+             with Items/@Reason equal to 
+             http://www.w3.org/2010/08/ws-enu/TimedOut by 
+             the data consumer
+            </p>
+          </item>
+          <item>
+            <p>
+             Receipt of one or more valid Enumerate messages with 
+             EnumerationContext element by the data source 
+            </p>
+          </item>
+          <item>
+            <p>
+             Receipt of one or more valid EnumerateResponse messages with 
+             one item by the data consumer 
+            </p>
+          </item>
+          <item>
+            <p>
+             Receipt of a valid Enumerate message with EnumerationContext 
+             element by the data source 
+            </p>
+          </item>
+          <item>
+            <p>
+             Receipt of a valid EnumerateResponse message with EndOfSequence 
+             element by the data consumer 
             </p>
           </item>
         </ulist>
@@ -4206,6 +4229,13 @@
        Add the sce:Scenario header and the sce:EndTime element
       </td>
      </tr>
+     <tr>
+      <td> 2011/03/22 </td>
+      <td> DD </td>
+      <td> 
+       Updates from Nathan
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/test/scenario.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- scenario.html	17 Feb 2011 00:48:45 -0000	1.13
+++ scenario.html	22 Mar 2011 23:50:48 -0000	1.14
@@ -85,23 +85,23 @@
 &nbsp;&nbsp;&nbsp;7.3 <a href="#iddiv2x1x2037">Optimized Enumeration Test</a><br/>
 &nbsp;&nbsp;&nbsp;7.4 <a href="#iddiv2x1x2079">MaxCharacters Test</a><br/>
 &nbsp;&nbsp;&nbsp;7.5 <a href="#iddiv2x1x2141">MaxTime Test</a><br/>
-&nbsp;&nbsp;&nbsp;7.6 <a href="#iddiv2x1x2199">Duration Expiration Test</a><br/>
-&nbsp;&nbsp;&nbsp;7.7 <a href="#iddiv2x1x2253">Specific Time Expiration Test</a><br/>
-&nbsp;&nbsp;&nbsp;7.8 <a href="#iddiv2x1x2302">Best Effort Expiration Test</a><br/>
-&nbsp;&nbsp;&nbsp;7.9 <a href="#iddiv2x1x2349">GetStatus Test</a><br/>
-&nbsp;&nbsp;&nbsp;7.10 <a href="#iddiv2x1x2398">Renew Test</a><br/>
-&nbsp;&nbsp;&nbsp;7.11 <a href="#iddiv2x1x2447">Release Test</a><br/>
-&nbsp;&nbsp;&nbsp;7.12 <a href="#iddiv2x1x2496">EnumerationEnd Test</a><br/>
-&nbsp;&nbsp;&nbsp;7.13 <a href="#iddiv2x1x2551">Filter Test - XPath 1.0</a><br/>
-&nbsp;&nbsp;&nbsp;7.14 <a href="#iddiv2x1x2608">Filter Test - XPath 2.0</a><br/>
+&nbsp;&nbsp;&nbsp;7.6 <a href="#iddiv2x1x2206">Duration Expiration Test</a><br/>
+&nbsp;&nbsp;&nbsp;7.7 <a href="#iddiv2x1x2260">Specific Time Expiration Test</a><br/>
+&nbsp;&nbsp;&nbsp;7.8 <a href="#iddiv2x1x2309">Best Effort Expiration Test</a><br/>
+&nbsp;&nbsp;&nbsp;7.9 <a href="#iddiv2x1x2356">GetStatus Test</a><br/>
+&nbsp;&nbsp;&nbsp;7.10 <a href="#iddiv2x1x2405">Renew Test</a><br/>
+&nbsp;&nbsp;&nbsp;7.11 <a href="#iddiv2x1x2454">Release Test</a><br/>
+&nbsp;&nbsp;&nbsp;7.12 <a href="#iddiv2x1x2503">EnumerationEnd Test</a><br/>
+&nbsp;&nbsp;&nbsp;7.13 <a href="#iddiv2x1x2558">Filter Test - XPath 1.0</a><br/>
+&nbsp;&nbsp;&nbsp;7.14 <a href="#iddiv2x1x2615">Filter Test - XPath 2.0</a><br/>
 8 <a href="#wsdl">WSDL</a><br/>
-&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2x1x2669">Event Source WSDL</a><br/>
-&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2x1x2674">Notification WSDL</a><br/>
+&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2x1x2676">Event Source WSDL</a><br/>
+&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2x1x2681">Notification WSDL</a><br/>
 9 <a href="#evd">EventDescriptions</a><br/>
 10 <a href="#xsd">Schemas</a><br/>
 11 <a href="#acks">Acknowledgements</a><br/>
 12 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2713">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2720">Normative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
 B <a href="#changelog">Change Log</a><br/>
@@ -1337,12 +1337,10 @@
         The subsequent Enumerate requests have the following salient features:
       </p><ul><li><p>EnumerationContext element that was provided by the data source</p></li></ul><div class="div3">
 <h4><a name="iddiv3x1x2166" id="iddiv3x1x2166"/>7.5.1 Sequence</h4><p>
-          The following diagram illustrates the sequence of messages for the 
-          MaxTime Test.  Note that the data source is not able to assemble 
-          the second EnumerateResponse message before the duration 
-          specified in the MaxTime element has passed.
-        </p><img src="scenario/enum_maxtime_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x2176" id="iddiv3x1x2176"/>7.5.2 Success Criteria</h4><ul><li><p>
+          The messaging sequence for this test is identical to that of the 
+          Basic Test. 
+        </p></div><div class="div3">
+<h4><a name="iddiv3x1x2171" id="iddiv3x1x2171"/>7.5.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element 
               by the data source
             </p></li><li><p>
@@ -1352,9 +1350,24 @@
               Receipt of one valid Enumerate message with 
               EnumerationContext element and MaxTime element by the data source
             </p></li><li><p>
-              Receipt of a wsen:TimedOut fault by the data consumer
+             Receipt of valid EnumerateResponse message with zero items and 
+             with Items/@Reason equal to 
+             http://www.w3.org/2010/08/ws-enu/TimedOut by 
+             the data consumer
+            </p></li><li><p>
+             Receipt of one or more valid Enumerate messages with 
+             EnumerationContext element by the data source 
+            </p></li><li><p>
+             Receipt of one or more valid EnumerateResponse messages with 
+             one item by the data consumer 
+            </p></li><li><p>
+             Receipt of a valid Enumerate message with EnumerationContext 
+             element by the data source 
+            </p></li><li><p>
+             Receipt of a valid EnumerateResponse message with EndOfSequence 
+             element by the data consumer 
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2192" id="iddiv3x1x2192"/>7.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2199" id="iddiv3x1x2199"/>7.5.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing 
           this test due to its inability to support the optional 
           wsen:MaxTime element.
@@ -1363,20 +1376,20 @@
           are required to be supported by the data source, there are no 
           allowable failure cases.
         </p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2199" id="iddiv2x1x2199"/>7.6 Duration Expiration Test</h3><p>
+<h3><a name="iddiv2x1x2206" id="iddiv2x1x2206"/>7.6 Duration Expiration Test</h3><p>
         This test verifies the correct implementation of the expiration 
         feature on the data source.  The initial Enumerate message has 
         the following salient features:
       </p><ul><li><p>NewContext element</p></li><li><p>Expires element with a short expiration time as xs:duration</p></li></ul><p>
         The second Enumerate request has the following salient features:
       </p><ul><li><p>EnumerationContext element that was provided by the data source</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x2218" id="iddiv3x1x2218"/>7.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2225" id="iddiv3x1x2225"/>7.6.1 Sequence</h4><p>
           The following diagram illustrates the sequence of messages for 
           the Duration Expiration Test.  Note that the data source waits 
           until the expiration time has passed before sending the 
           second Enumerate request.
         </p><img src="scenario/enum_expires_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x2228" id="iddiv3x1x2228"/>7.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2235" id="iddiv3x1x2235"/>7.6.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element 
               and Expires element by the data source
             </p></li><li><p>
@@ -1389,7 +1402,7 @@
               Receipt of a wsen:InvalidEnumerationContext fault by the 
               data consumer
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2244" id="iddiv3x1x2244"/>7.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2251" id="iddiv3x1x2251"/>7.6.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing 
           this test due to its inability to support the optional 
           wsen:Expires element with a value of type xs:duration.
@@ -1401,18 +1414,18 @@
           A conforming data source MAY respond to the initial Enumerate 
           request with a wsen:UnsupportedExpirationValue fault.
         </p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2253" id="iddiv2x1x2253"/>7.7 Specific Time Expiration Test</h3><p>
+<h3><a name="iddiv2x1x2260" id="iddiv2x1x2260"/>7.7 Specific Time Expiration Test</h3><p>
         This test verifies the correct implementation of the expiration 
         feature on the data source.  The initial Enumerate message has 
         the following salient features:
       </p><ul><li><p>NewContext element</p></li><li><p>Expires element with a short expiration time as xs:dateTime</p></li></ul><p>
         The second Enumerate request has the following salient features:
       </p><ul><li><p>EnumerationContext element that was provided by the data source</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x2272" id="iddiv3x1x2272"/>7.7.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2279" id="iddiv3x1x2279"/>7.7.1 Sequence</h4><p>
           The messaging sequence for this test is identical to that of 
           the Duration Expiration Test.
         </p></div><div class="div3">
-<h4><a name="iddiv3x1x2277" id="iddiv3x1x2277"/>7.7.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2284" id="iddiv3x1x2284"/>7.7.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element 
               and Expires element by the data source
             </p></li><li><p>
@@ -1425,7 +1438,7 @@
               Receipt of a wsen:InvalidEnumerationContext fault by the 
               data consumer
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2293" id="iddiv3x1x2293"/>7.7.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2300" id="iddiv3x1x2300"/>7.7.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing 
           this test due to its inability to support the optional 
           wsen:Expires element with a value of type xs:datetime.
@@ -1439,7 +1452,7 @@
           request with a wsen:UnsupportedExpirationValue fault or a 
           wsen:UnsupportedExpirationType fault.
         </p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2302" id="iddiv2x1x2302"/>7.8 Best Effort Expiration Test</h3><p>
+<h3><a name="iddiv2x1x2309" id="iddiv2x1x2309"/>7.8 Best Effort Expiration Test</h3><p>
         This test verifies the correct implementation of the "best effort 
         expiration feature on the data source.  The initial Enumerate 
         message has the following salient features:
@@ -1447,11 +1460,11 @@
           with @BestEffort=true</p></li></ul><p>
         The second Enumerate request has the following salient features:
       </p><ul><li><p>EnumerationContext element that was provided by the data source</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x2321" id="iddiv3x1x2321"/>7.8.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2328" id="iddiv3x1x2328"/>7.8.1 Sequence</h4><p>
           The messaging sequence for this test is identical to that of 
           the Duration Expiration Test.
         </p></div><div class="div3">
-<h4><a name="iddiv3x1x2326" id="iddiv3x1x2326"/>7.8.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2333" id="iddiv3x1x2333"/>7.8.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element and 
               Expires element by the data source
             </p></li><li><p>
@@ -1464,7 +1477,7 @@
               Receipt of a wsen:InvalidEnumerationContext fault by the 
               data consumer
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2342" id="iddiv3x1x2342"/>7.8.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2349" id="iddiv3x1x2349"/>7.8.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing 
           this test due to its inability to support the optional 
           wsen:Expires element with a value of type xs:duration or with 
@@ -1474,18 +1487,18 @@
           are required to be supported by the data source, there are no 
           allowable failure cases.
         </p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2349" id="iddiv2x1x2349"/>7.9 GetStatus Test</h3><p>
+<h3><a name="iddiv2x1x2356" id="iddiv2x1x2356"/>7.9 GetStatus Test</h3><p>
         This test verifies the ability of a data consumer to get the 
         status of an existing enumeration.  The initial Enumerate request 
         has the following salient features:
       </p><ul><li><p>NewContext element</p></li></ul><p>
         The GetStatus message has the following salient features:
       </p><ul><li><p>EnumerationContext element that was provided by the data source</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x2365" id="iddiv3x1x2365"/>7.9.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2372" id="iddiv3x1x2372"/>7.9.1 Sequence</h4><p>
           The following diagram illustrates the sequence of messages for 
           the GetStatus Test.
         </p><img src="scenario/enum_getstatus_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x2375" id="iddiv3x1x2375"/>7.9.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2382" id="iddiv3x1x2382"/>7.9.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element 
               by the data source
             </p></li><li><p>
@@ -1497,7 +1510,7 @@
             </p></li><li><p>
               Receipt of valid GetStatusResponse message by the data consumer
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2391" id="iddiv3x1x2391"/>7.9.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2398" id="iddiv3x1x2398"/>7.9.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing 
           this test due to its inability to support the GetStatus operation.
         </p><p>
@@ -1505,18 +1518,18 @@
           are required to be supported by the data source, there are no 
           allowable failure cases.
         </p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2398" id="iddiv2x1x2398"/>7.10 Renew Test</h3><p>
+<h3><a name="iddiv2x1x2405" id="iddiv2x1x2405"/>7.10 Renew Test</h3><p>
         This test verifies the ability of a data consumer to renew an 
         existing enumeration.  The initial Enumerate request has the 
         following salient features:
       </p><ul><li><p>NewContext element</p></li></ul><p>
         The Renew message has the following salient features:
       </p><ul><li><p>EnumerationContext element that was provided by the data source</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x2414" id="iddiv3x1x2414"/>7.10.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2421" id="iddiv3x1x2421"/>7.10.1 Sequence</h4><p>
           The following diagram illustrates the sequence of messages for the 
           Renew Test.
         </p><img src="scenario/enum_renew_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x2424" id="iddiv3x1x2424"/>7.10.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2431" id="iddiv3x1x2431"/>7.10.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element 
               by the data source
             </p></li><li><p>
@@ -1528,7 +1541,7 @@
             </p></li><li><p>
               Receipt of valid RenewResponse message by the data consumer
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2440" id="iddiv3x1x2440"/>7.10.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2447" id="iddiv3x1x2447"/>7.10.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing 
           this test due to its inability to support the Renew operation.
         </p><p>
@@ -1536,7 +1549,7 @@
           and instead respond to the Renew request with a SOAP 1.1 Server 
           fault or a SOAP 1.2 Receiver fault.
         </p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2447" id="iddiv2x1x2447"/>7.11 Release Test</h3><p>
+<h3><a name="iddiv2x1x2454" id="iddiv2x1x2454"/>7.11 Release Test</h3><p>
         This test verifies the ability of a data consumer to release 
         an existing enumeration before its data items have all been 
         retrieved.  The initial Enumerate request has the following 
@@ -1544,11 +1557,11 @@
       </p><ul><li><p>NewContext element</p></li></ul><p>
         The Release message has the following salient features:
       </p><ul><li><p>EnumerationContext element that was provided by the data source</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x2463" id="iddiv3x1x2463"/>7.11.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2470" id="iddiv3x1x2470"/>7.11.1 Sequence</h4><p>
           The following diagram illustrates the sequence of messages for 
           the Release Test.
         </p><img src="scenario/enum_release_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x2473" id="iddiv3x1x2473"/>7.11.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2480" id="iddiv3x1x2480"/>7.11.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element 
               by the data source
             </p></li><li><p>
@@ -1560,7 +1573,7 @@
             </p></li><li><p>
               Receipt of valid ReleaseResponse message by the data consumer
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2489" id="iddiv3x1x2489"/>7.11.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2496" id="iddiv3x1x2496"/>7.11.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing this 
           test due to its inability to support the Release operation.
         </p><p>
@@ -1568,7 +1581,7 @@
           are required to be supported by the data source, there are no 
           allowable failure cases.
         </p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2496" id="iddiv2x1x2496"/>7.12 EnumerationEnd Test</h3><p>
+<h3><a name="iddiv2x1x2503" id="iddiv2x1x2503"/>7.12 EnumerationEnd Test</h3><p>
         This test verifies the ability of a data source to send a 
         notification to a data consumer if it terminates the enumeration 
         unexpectedly.  The initial Enumerate request has the following 
@@ -1583,11 +1596,11 @@
        in this element must be less than the expires time specified in the
        Enumerate request message used to create the enumeration.
       </p><div class="div3">
-<h4><a name="iddiv3x1x2517" id="iddiv3x1x2517"/>7.12.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2524" id="iddiv3x1x2524"/>7.12.1 Sequence</h4><p>
           The following diagram illustrates the sequence of messages for 
           the EnumerationEnd Test.
         </p><img src="scenario/enum_enumerationend_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x2527" id="iddiv3x1x2527"/>7.12.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2534" id="iddiv3x1x2534"/>7.12.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element 
               and EndTo element by the data source
             </p></li><li><p>
@@ -1596,7 +1609,7 @@
             </p></li><li><p>
               Receipt of valid EnumerationEnd message by the data consumer
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2540" id="iddiv3x1x2540"/>7.12.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2547" id="iddiv3x1x2547"/>7.12.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing 
           this test due to its inability to support the optional 
           wsen:EndTo element or the EnumerationEndPortType portType.
@@ -1611,7 +1624,7 @@
           request with a wsen:UnusableEPR  fault if it checks the validity 
           of the EndTo EPR and detects a problem.
         </p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2551" id="iddiv2x1x2551"/>7.13 Filter Test - XPath 1.0</h3><p>
+<h3><a name="iddiv2x1x2558" id="iddiv2x1x2558"/>7.13 Filter Test - XPath 1.0</h3><p>
         This test verifies the ability of the data source to correctly 
         implement XPath 1.0 filters. The initial Enumerate request has 
         the following salient features:
@@ -1622,11 +1635,11 @@
           </p></li></ul><p>
         The subsequent Enumerate requests have the following salient features:
       </p><ul><li><p>EnumerationContext element that was provided by the data source</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x2570" id="iddiv3x1x2570"/>7.13.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2577" id="iddiv3x1x2577"/>7.13.1 Sequence</h4><p>
           The messaging sequence for this test is identical to that of 
           the Basic Test.
         </p></div><div class="div3">
-<h4><a name="iddiv3x1x2575" id="iddiv3x1x2575"/>7.13.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2582" id="iddiv3x1x2582"/>7.13.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element 
               and Filter element by the data source
             </p></li><li><p>
@@ -1645,7 +1658,7 @@
               Receipt of a valid EnumerateResponse message with 
               EndOfSequence element by the data consumer
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2597" id="iddiv3x1x2597"/>7.13.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2604" id="iddiv3x1x2604"/>7.13.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing 
           this test due to its inability to support the optional wsen:Filter 
           element or the @Dialect 
@@ -1666,7 +1679,7 @@
           filter will never evaluate to true for the lifetime of 
           the enumeration.
         </p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2608" id="iddiv2x1x2608"/>7.14 Filter Test - XPath 2.0</h3><p>
+<h3><a name="iddiv2x1x2615" id="iddiv2x1x2615"/>7.14 Filter Test - XPath 2.0</h3><p>
         This test verifies the ability of the data source to correctly 
         implement XPath 2.0 filters. The initial Enumerate request has 
         the following salient features:
@@ -1677,11 +1690,11 @@
           </p></li></ul><p>
         The subsequent Enumerate requests have the following salient features:
       </p><ul><li><p>EnumerationContext element that was provided by the data source</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x2627" id="iddiv3x1x2627"/>7.14.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2634" id="iddiv3x1x2634"/>7.14.1 Sequence</h4><p>
           The messaging sequence for this test is identical to that of the 
           Basic Test.
         </p></div><div class="div3">
-<h4><a name="iddiv3x1x2632" id="iddiv3x1x2632"/>7.14.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2639" id="iddiv3x1x2639"/>7.14.2 Success Criteria</h4><ul><li><p>
               Receipt of valid Enumerate message with NewContext element 
               and Filter element by the data source
             </p></li><li><p>
@@ -1700,7 +1713,7 @@
               Receipt of a valid EnumerateResponse message with EndOfSequence 
               element by the data consumer
             </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2654" id="iddiv3x1x2654"/>7.14.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2661" id="iddiv3x1x2661"/>7.14.3 Conformance</h4><p>
           A conforming data consumer MAY NOT be capable of implementing 
           this test due to its inability to support the optional 
           wsen:Filter element or the @Dialect 
@@ -1722,10 +1735,10 @@
           the enumeration.
         </p></div></div></div><div class="div1">
 <h2><a name="wsdl" id="wsdl"/>8 WSDL</h2><div class="div2">
-<h3><a name="iddiv2x1x2669" id="iddiv2x1x2669"/>8.1 Event Source WSDL</h3><p>
+<h3><a name="iddiv2x1x2676" id="iddiv2x1x2676"/>8.1 Event Source WSDL</h3><p>
      TBD
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x2674" id="iddiv2x1x2674"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x2681" id="iddiv2x1x2681"/>8.2 Notification WSDL</h3><p>
      Available here:
     <a href="http://www.w3.org/2002/ws/ra/test/scenario/scenarioSink.wsdl">http://www.w3.org/2002/ws/ra/test/scenario/scenarioSink.wsdl</a></p></div></div><div class="div1">
 <h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
@@ -1765,7 +1778,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="References" id="References"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2713" id="iddiv2x1x2713"/>12.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="iddiv2x1x2720" id="iddiv2x1x2720"/>12.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.
@@ -1892,4 +1905,6 @@
        Updated frag xpath to not need prefix namespace mapping
       </td></tr><tr><td> 2011/02/04 </td><td> DD </td><td> 
        Add the sce:Scenario header and the sce:EndTime element
+      </td></tr><tr><td> 2011/03/22 </td><td> DD </td><td> 
+       Updates from Nathan
       </td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 22 March 2011 23:50:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 March 2011 23:50:53 GMT