- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 14 Jan 2011 16:40:31 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv24947
Modified Files:
scenario.html scenario.xml
Log Message:
For nathan
Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- scenario.xml 9 Jan 2011 21:10:05 -0000 1.15
+++ scenario.xml 14 Jan 2011 16:40:29 -0000 1.16
@@ -412,9 +412,9 @@
Name: Kerry <phrase/>
Birthdate: 05/22/2008 <phrase/>
Gender: Female <phrase/>
- Family: ... <phrase/>
- Genus: ... <phrase/>
- Species: ... <phrase/>
+ Family: Delphinidae <phrase/>
+ Genus: Orcinus <phrase/>
+ Species: orca <phrase/>
</p>
</item>
[...1344 lines suppressed...]
+ </div3>
+ </div2>
+
</div1>
<div1 id="wsdl">
@@ -2529,6 +3803,13 @@
an array and something with an attribute to test frag stuf
</td>
</tr>
+ <tr>
+ <td> 2011/01/14 </td>
+ <td> NB </td>
+ <td>
+ Added initial Enum section
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- scenario.html 9 Jan 2011 21:10:05 -0000 1.15
+++ scenario.html 14 Jan 2011 16:40:29 -0000 1.16
@@ -80,15 +80,28 @@
6.5 <a href="#iddiv2x1x1555">Fragment Put Test</a><br/>
6.6 <a href="#iddiv2x1x1587">Delete Test</a><br/>
7 <a href="#iddiv1x1x1613">WS-Enumeration Tests</a><br/>
- 7.1 <a href="#iddiv2x1x1618">xxx Test</a><br/>
+ 7.1 <a href="#iddiv2x1x1618">Basic Test</a><br/>
+ 7.2 <a href="#iddiv2x1x1673">New Empty Enumeration Test</a><br/>
+ 7.3 <a href="#iddiv2x1x1726">Optimized Enumeration Test</a><br/>
+ 7.4 <a href="#iddiv2x1x1768">MaxCharacters Test</a><br/>
+ 7.5 <a href="#iddiv2x1x1830">MaxTime Test</a><br/>
+ 7.6 <a href="#iddiv2x1x1888">Duration Expiration Test</a><br/>
+ 7.7 <a href="#iddiv2x1x1942">Specific Time Expiration Test</a><br/>
+ 7.8 <a href="#iddiv2x1x1991">Best Effort Expiration Test</a><br/>
+ 7.9 <a href="#iddiv2x1x2038">GetStatus Test</a><br/>
+ 7.10 <a href="#iddiv2x1x2087">Renew Test</a><br/>
+ 7.11 <a href="#iddiv2x1x2136">Release Test</a><br/>
+ 7.12 <a href="#iddiv2x1x2185">EnumerationEnd Test</a><br/>
+ 7.13 <a href="#iddiv2x1x2232">Filter Test - XPath 1.0</a><br/>
+ 7.14 <a href="#iddiv2x1x2289">Filter Test - XPath 2.0</a><br/>
8 <a href="#wsdl">WSDL</a><br/>
- 8.1 <a href="#iddiv2x1x1645">Event Source WSDL</a><br/>
- 8.2 <a href="#iddiv2x1x1650">Notification WSDL</a><br/>
+ 8.1 <a href="#iddiv2x1x2350">Event Source WSDL</a><br/>
+ 8.2 <a href="#iddiv2x1x2355">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/>
- 12.1 <a href="#iddiv2x1x1677">Normative References</a><br/>
+ 12.1 <a href="#iddiv2x1x2382">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/>
@@ -181,16 +194,16 @@
Name: Kerry <br/>
Birthdate: 05/22/2008 <br/>
Gender: Female <br/>
- Family: ... <br/>
- Genus: ... <br/>
- Species: ... <br/></p></li><li><p>
+ Family: Delphinidae <br/>
+ Genus: Orcinus <br/>
+ Species: orca <br/></p></li><li><p>
ID: -- system defined -- <br/>
Name: Oscar <br/>
Birthdate: 03/01/2010 <br/>
Gender: Male <br/>
- Family: ... <br/>
- Genus: ... <br/>
- Species: ... <br/></p></li></ul></div><div class="div2">
+ Family: Balaenopteridae <br/>
+ Genus: Megaptera <br/>
+ Species: novaeangliae <br/></p></li></ul></div><div class="div2">
<h3><a name="evt_description" id="evt_description"/>3.2 Event Description</h3><p>
The location of the tags is expressed in GPS coordinates using the GPS
eXchange Format, an XML schema designed as a common GPS data format
@@ -961,25 +974,555 @@
DeleteResponse message.
</p></div></div></div><div class="div1">
<h2><a name="iddiv1x1x1613" id="iddiv1x1x1613"/>7 WS-Enumeration Tests</h2><p>
- ...
+ This section describes the tests for WS-Enumeration.
</p><div class="div2">
-<h3><a name="iddiv2x1x1618" id="iddiv2x1x1618"/>7.1 xxx Test</h3><p>
- This test ....
- </p><div class="div3">
-<h4><a name="iddiv3x1x1624" id="iddiv3x1x1624"/>7.1.1 Sequence</h4><p>
- ...
- </p></div><div class="div3">
-<h4><a name="iddiv3x1x1629" id="iddiv3x1x1629"/>7.1.2 Success Criteria</h4><ul><li><p>
- ...
- </p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1636" id="iddiv3x1x1636"/>7.1.3 Conformance</h4><p>
- ...
- </p></div></div></div><div class="div1">
+<h3><a name="iddiv2x1x1618" id="iddiv2x1x1618"/>7.1 Basic Test</h3><p>
+ This test verifies the ability to enumerate instances of a resource
+ using the default behavior. The initial Enumerate request has the
+ following salient features:
+ </p><ul><li><p>NewContext element</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="iddiv3x1x1634" id="iddiv3x1x1634"/>7.1.1 Sequence</h4><p>
+ The following diagram illustrates the sequence of messages for the
+ Basic Test.
+ </p><img src="images/enum_basic_test.jpg"/></div><div class="div3">
+<h4><a name="iddiv3x1x1644" id="iddiv3x1x1644"/>7.1.2 Success Criteria</h4><ul><li><p>
+ Receipt of valid Enumerate message with NewContext element by the
+ data source
+ </p></li><li><p>
+ Receipt of a valid EnumerateResponse message with EnumerationContext
+ element and with one item 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="iddiv3x1x1666" id="iddiv3x1x1666"/>7.1.3 Conformance</h4><p>
+ A conforming data source MAY NOT be capable of implementing this
+ test due to its inability to return items in response to an
+ Enumerate request that also created a new enumeration.
+ </p><p>
+ A conforming data source MAY respond to the initial Enumerate
+ request with a wsen:MaxElementsMustBeZero fault.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x1673" id="iddiv2x1x1673"/>7.2 New Empty Enumeration Test</h3><p>
+ This test verifies the ability to create a new enumeration without
+ retrieving any of the data items in the first EnumerateResponse
+ message. The initial Enumerate request has the following salient
+ features:
+ </p><ul><li><p>NewContext element</p></li><li><p>MaxElements element equal to 0</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="iddiv3x1x1692" id="iddiv3x1x1692"/>7.2.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="iddiv3x1x1697" id="iddiv3x1x1697"/>7.2.2 Success Criteria</h4><ul><li><p>
+ Receipt of valid Enumerate message with NewContext element and
+ MaxElements equal to 0 by the data source
+ </p></li><li><p>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element and with no items 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="iddiv3x1x1719" id="iddiv3x1x1719"/>7.2.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:MaxElements element.
+ </p><p>
+ Because this test involves only operations and elements that
+ are required to be supported by the data source, there are
+ no allowable failure cases.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x1726" id="iddiv2x1x1726"/>7.3 Optimized Enumeration Test</h3><p>
+ This test verifies the ability to enumerate an entire set of
+ instances of a resource with just one Enumerate message. The
+ Enumerate request has the following salient features:
+ </p><ul><li><p>NewContext element</p></li><li><p>MaxElements element with large value</p></li></ul><div class="div3">
+<h4><a name="iddiv3x1x1739" id="iddiv3x1x1739"/>7.3.1 Sequence</h4><p>
+ The following diagram illustrates the sequence of messages for
+ the Optimized Enumeration Test.
+ </p><img src="images/enum_optimized_test.jpg"/></div><div class="div3">
+<h4><a name="iddiv3x1x1749" id="iddiv3x1x1749"/>7.3.2 Success Criteria</h4><ul><li><p>
+ Receipt of valid Enumerate message with NewContext element and
+ MaxElements equal to large number by the data source
+ </p></li><li><p>
+ Receipt of a valid EnumerateResponse message with all Items
+ and EndOfSequence element by the data consumer
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x1759" id="iddiv3x1x1759"/>7.3.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:MaxElements element.
+ </p><p>
+ A conforming data source MAY NOT be capable of implementing this
+ test due to its inability to return items in response to an
+ Enumerate request that also created a new enumeration.
+ </p><p>
+ A conforming data source MAY respond to the initial Enumerate
+ request with a wsen:MaxElementsMustBeZero fault.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x1768" id="iddiv2x1x1768"/>7.4 MaxCharacters Test</h3><p>
+ This test verifies the ability of a data consumer to limit the
+ size of the items returned from an enumeration using the
+ wsen:MaxCharacters element. The initial Enumerate request has
+ the following salient features:
+ </p><ul><li><p>NewContext element</p></li><li><p>MaxElements element with large value</p></li><li><p>MaxCharacters element with a value slightly bigger than
+ one returned item</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><li><p>MaxElements element with a large value</p></li><li><p>MaxCharacters element with a value slightly bigger than
+ one returned item</p></li></ul><div class="div3">
+<h4><a name="iddiv3x1x1796" id="iddiv3x1x1796"/>7.4.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="iddiv3x1x1801" id="iddiv3x1x1801"/>7.4.2 Success Criteria</h4><ul><li><p>
+ Receipt of valid Enumerate message with NewContext element,
+ MaxElements element and MaxCharacters element by the data source
+ </p></li><li><p>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element and with one item by the data consumer
+ </p></li><li><p>
+ Receipt of one or more valid Enumerate messages with
+ EnumerationContext element, MaxElements element and
+ MaxCharacters 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, MaxElements element and MaxCharacters 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="iddiv3x1x1823" id="iddiv3x1x1823"/>7.4.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:MaxElements
+ element or the optional wsen:MaxCharacters element.
+ </p><p>
+ Because this test involves only operations and elements that
+ are required to be supported by the data source, there are no
+ allowable failure cases.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x1830" id="iddiv2x1x1830"/>7.5 MaxTime Test</h3><p>
+ This test verifies the ability of a data consumer to limit the
+ amount of time it takes for the data source to assemble an
+ EnumerateResponse using the wsen:MaxTime element. The initial
+ Enumerate request has the following salient features:
+ </p><ul><li><p>NewContext element</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><li><p>MaxTime element with a very low value </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="iddiv3x1x1855" id="iddiv3x1x1855"/>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.
+
+ <img src="images/enum_maxtime_test.jpg"/></p></div><div class="div3">
+<h4><a name="iddiv3x1x1865" id="iddiv3x1x1865"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element and with one item by the data consumer
+ </p></li><li><p>
+ 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
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x1881" id="iddiv3x1x1881"/>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.
+ </p><p>
+ Because this test involves only operations and elements that
+ are required to be supported by the data source, there are no
+ allowable failure cases.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x1888" id="iddiv2x1x1888"/>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="iddiv3x1x1907" id="iddiv3x1x1907"/>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.
+
+ <img src="images/enum_expires_test.jpg"/></p></div><div class="div3">
+<h4><a name="iddiv3x1x1917" id="iddiv3x1x1917"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element and with one item by the data consumer
+ </p></li><li><p>
+ Receipt of valid Enumerate message with EnumerationContext
+ element by the data source
+ </p></li><li><p>
+ Receipt of a wsen:InvalidEnumerationContext fault by the
+ data consumer
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x1933" id="iddiv3x1x1933"/>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.
+ </p><p>
+ A conforming data source MAY NOT be capable of implementing this
+ test due to its inability to grant an expiration time that
+ matches the specified value in the Enumerate request.
+ </p><p>
+ 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="iddiv2x1x1942" id="iddiv2x1x1942"/>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="iddiv3x1x1961" id="iddiv3x1x1961"/>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="iddiv3x1x1966" id="iddiv3x1x1966"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element and with one item by the data consumer
+ </p></li><li><p>
+ Receipt of valid Enumerate message with EnumerationContext
+ element by the data source
+ </p></li><li><p>
+ Receipt of a wsen:InvalidEnumerationContext fault by the
+ data consumer
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x1982" id="iddiv3x1x1982"/>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.
+ </p><p>
+ A conforming data source MAY NOT be capable of implementing
+ this test due to its inability to grant an expiration time
+ that matches the specified value in the Enumerate request, or to
+ its inability to support specific expiration time values.
+ </p><p>
+ A conforming data source MAY respond to the initial Enumerate
+ request with a wsen:UnsupportedExpirationValue fault or a
+ wsen:UnsupportedExpirationType fault.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x1991" id="iddiv2x1x1991"/>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:
+ </p><ul><li><p>NewContext element</p></li><li><p>Expires element with a short expiration time as xs:duration
+ 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="iddiv3x1x2010" id="iddiv3x1x2010"/>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="iddiv3x1x2015" id="iddiv3x1x2015"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element and with one item by the data consumer
+ </p></li><li><p>
+ Receipt of valid Enumerate message with EnumerationContext
+ element by the data source
+ </p></li><li><p>
+ Receipt of a wsen:InvalidEnumerationContext fault by the
+ data consumer
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x2031" id="iddiv3x1x2031"/>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
+ the @BestEffort attribute.
+ </p><p>
+ Because this test involves only operations and elements that
+ are required to be supported by the data source, there are no
+ allowable failure cases.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x2038" id="iddiv2x1x2038"/>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="iddiv3x1x2054" id="iddiv3x1x2054"/>7.9.1 Sequence</h4><p>
+ The following diagram illustrates the sequence of messages for
+ the GetStatus Test.
+
+ <img src="images/enum_getstatus_test.jpg"/></p></div><div class="div3">
+<h4><a name="iddiv3x1x2064" id="iddiv3x1x2064"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element by the data consumer
+ </p></li><li><p>
+ Receipt of valid GetStatus message with EnumerationContext
+ element by the data source
+ </p></li><li><p>
+ Receipt of valid GetStatusResponse message by the data consumer
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x2080" id="iddiv3x1x2080"/>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>
+ Because this test involves only operations and elements that
+ are required to be supported by the data source, there are no
+ allowable failure cases.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x2087" id="iddiv2x1x2087"/>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="iddiv3x1x2103" id="iddiv3x1x2103"/>7.10.1 Sequence</h4><p>
+ The following diagram illustrates the sequence of messages for the
+ Renew Test.
+
+ <img src="images/enum_renew_test.jpg"/></p></div><div class="div3">
+<h4><a name="iddiv3x1x2113" id="iddiv3x1x2113"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element by the data consumer
+ </p></li><li><p>
+ Receipt of valid Renew message with EnumerationContext element
+ by the data source
+ </p></li><li><p>
+ Receipt of valid RenewResponse message by the data consumer
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x2129" id="iddiv3x1x2129"/>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>
+ A conforming data source MAY choose not to renew the enumeration
+ 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="iddiv2x1x2136" id="iddiv2x1x2136"/>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
+ salient features:
+ </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="iddiv3x1x2152" id="iddiv3x1x2152"/>7.11.1 Sequence</h4><p>
+ The following diagram illustrates the sequence of messages for
+ the Release Test.
+
+ <img src="images/enum_release_test.jpg"/></p></div><div class="div3">
+<h4><a name="iddiv3x1x2162" id="iddiv3x1x2162"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element by the data consumer
+ </p></li><li><p>
+ Receipt of valid Release message with EnumerationContext
+ element by the data source
+ </p></li><li><p>
+ Receipt of valid ReleaseResponse message by the data consumer
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x2178" id="iddiv3x1x2178"/>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>
+ Because this test involves only operations and elements that
+ are required to be supported by the data source, there are no
+ allowable failure cases.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x2185" id="iddiv2x1x2185"/>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
+ salient features:
+ </p><ul><li><p>NewContext element</p></li><li><p>EndTo element containing an EPR for the data consumer</p></li></ul><div class="div3">
+<h4><a name="iddiv3x1x2198" id="iddiv3x1x2198"/>7.12.1 Sequence</h4><p>
+ The following diagram illustrates the sequence of messages for
+ the EnumerationEnd Test.
+
+ <img src="images/enum_enumerationend_test.jpg"/></p></div><div class="div3">
+<h4><a name="iddiv3x1x2208" id="iddiv3x1x2208"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element by the data consumer
+ </p></li><li><p>
+ Receipt of valid EnumerationEnd message by the data consumer
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x2221" id="iddiv3x1x2221"/>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.
+ </p><p>
+ A conforming data source MAY NOT be capable of implementing
+ this test due to its inability to support the use of the EndTo EPR.
+ </p><p>
+ A conforming data source MAY respond to the initial Enumerate
+ request with a wsen:EndToNotSupported fault.
+ </p><p>
+ A conforming data source MAY respond to the initial Enumerate
+ 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="iddiv2x1x2232" id="iddiv2x1x2232"/>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:
+ </p><ul><li><p>NewContext element</p></li><li><p>
+ Filter element with @Dialect equal to
+ 'http://www.w3.org/2010/08/ws-enu/Dialects/XPath10'
+ (actual filter expression TBD)
+ </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="iddiv3x1x2251" id="iddiv3x1x2251"/>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="iddiv3x1x2256" id="iddiv3x1x2256"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element and with one item 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="iddiv3x1x2278" id="iddiv3x1x2278"/>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
+ 'http://www.w3.org/2010/08/ws-enu/Dialects/XPath10'.
+ </p><p>
+ A conforming data source MAY NOT be capable of implementing this
+ test due to its inability to support filtering, to process the
+ filter dialect 'http://www.w3.org/2010/08/ws-enu/Dialects/XPath10',
+ or to process the filter content.
+ </p><p>
+ A conforming data source MAY respond to the initial Enumerate
+ request with a wsen:FilteringNotSupported fault, a
+ wsen:FilterDialectRequestedUnavailable fault, or a
+ wsen:CannotProcessFilter fault.
+ </p><p>
+ A conforming data source MAY respond to the initial Enumerate
+ request with a wsen:EmptyFilter fault if it detects that the
+ filter will never evaluate to true for the lifetime of
+ the enumeration.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x2289" id="iddiv2x1x2289"/>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:
+ </p><ul><li><p>NewContext element</p></li><li><p>
+ Filter element with @Dialect equal to
+ 'http://www.w3.org/2010/08/ws-enu/Dialects/XPath20'
+ (actual filter expression TBD)
+ </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="iddiv3x1x2308" id="iddiv3x1x2308"/>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="iddiv3x1x2313" id="iddiv3x1x2313"/>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>
+ Receipt of a valid EnumerateResponse message with
+ EnumerationContext element and with one item 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="iddiv3x1x2335" id="iddiv3x1x2335"/>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
+ 'http://www.w3.org/2010/08/ws-enu/Dialects/XPath20'.
+ </p><p>
+ A conforming data source MAY NOT be capable of implementing this
+ test due to its inability to support filtering, to process the
+ filter dialect 'http://www.w3.org/2010/08/ws-enu/Dialects/XPath20',
+ or to process the filter content.
+ </p><p>
+ A conforming data source MAY respond to the initial Enumerate
+ request with a wsen:FilteringNotSupported fault, a
+ wsen:FilterDialectRequestedUnavailable fault, or a
+ wsen:CannotProcessFilter fault.
+ </p><p>
+ A conforming data source MAY respond to the initial Enumerate
+ request with a wsen:EmptyFilter fault if it detects that the
+ filter will never evaluate to true for the lifetime of
+ the enumeration.
+ </p></div></div></div><div class="div1">
<h2><a name="wsdl" id="wsdl"/>8 WSDL</h2><div class="div2">
-<h3><a name="iddiv2x1x1645" id="iddiv2x1x1645"/>8.1 Event Source WSDL</h3><p>
+<h3><a name="iddiv2x1x2350" id="iddiv2x1x2350"/>8.1 Event Source WSDL</h3><p>
TBD
</p></div><div class="div2">
-<h3><a name="iddiv2x1x1650" id="iddiv2x1x1650"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x2355" id="iddiv2x1x2355"/>8.2 Notification WSDL</h3><p>
TBD
</p></div></div><div class="div1">
<h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
@@ -1019,7 +1562,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="iddiv2x1x1677" id="iddiv2x1x1677"/>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="iddiv2x1x2382" id="iddiv2x1x2382"/>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.
@@ -1138,4 +1681,6 @@
Add a history section to each animal so we can track medical
history or just make notes about the animal. Really, we need
an array and something with an attribute to test frag stuf
+ </td></tr><tr><td> 2011/01/14 </td><td> NB </td><td>
+ Added initial Enum section
</td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Friday, 14 January 2011 16:40:35 UTC