- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 31 Jan 2011 19:48:57 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv31462
Modified Files:
scenario.html scenario.xml
Log Message:
more frag stuff
Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- scenario.xml 31 Jan 2011 19:36:02 -0000 1.22
+++ scenario.xml 31 Jan 2011 19:48:55 -0000 1.23
@@ -2302,7 +2302,7 @@
<p>
Mode: Remove
Expression: //sce:Entry[1]/@Date <phrase/>
- Value: -
+ Value: - <phrase/>
Result: Date attribute is removed
</p>
</item>
@@ -2335,7 +2335,7 @@
<item>
<p>
Mode: Replace
- Expression: //sce:Entry[0] <phrase/>
+ Expression: //sce:History/sce:Entry[0] <phrase/>
Value: <sce:Entry> ... </sce:Entry> <phrase/>
Result: Entry is added to the History array <phrase/>
History array needs to be empty before test starts
@@ -2381,7 +2381,7 @@
<p>
Mode: Remove
Expression: //sce:Entry <phrase/>
- Value: -
+ Value: - <phrase/>
Result: All Entry elements are removed <phrase/>
History array needs to have one Entry
</p>
@@ -2390,7 +2390,7 @@
<p>
Mode: Remove
Expression: //sce:Entry <phrase/>
- Value: -
+ Value: - <phrase/>
Result: All Entry elements are removed <phrase/>
History array needs to have more than one Entry
</p>
@@ -2399,11 +2399,32 @@
<p>
Mode: Remove
Expression: //sce:Entry[1] <phrase/>
- Value: -
+ Value: - <phrase/>
Result: Just first Entry is removed <phrase/>
History array needs to have more than one Entry
</p>
</item>
+
+ <!-- stuff beyond what the table in the spec says -->
+ <item>
+ <p>
+ Mode: InsertBefore
+ Expression: //sce:History/sce:Entry <phrase/>
+ Value: <sce:Entry> ... </sce:Entry> <phrase/>
+ Result: New Entry is added to History array <phrase/>
+ History array needs to be empty before test starts
+ </p>
+ </item>
+ <item>
+ <p>
+ Mode: InsertAfter
+ Expression: //sce:History/sce:Entry <phrase/>
+ Value: <sce:Entry> ... </sce:Entry> <phrase/>
+ Result: New Entry is added to History array <phrase/>
+ History array needs to be empty before test starts
+ </p>
+ </item>
+
</ulist>
</div3>
</div2>
Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- scenario.html 31 Jan 2011 19:36:02 -0000 1.22
+++ scenario.html 31 Jan 2011 19:48:55 -0000 1.23
@@ -77,30 +77,30 @@
6.3 <a href="#iddiv2x1x1540">Fragment Get Test</a><br/>
6.4 <a href="#iddiv2x1x1566">Put Test</a><br/>
6.5 <a href="#iddiv2x1x1592">Fragment Put Test</a><br/>
- 6.6 <a href="#iddiv2x1x1781">Delete Test</a><br/>
-7 <a href="#iddiv1x1x1807">WS-Enumeration Tests</a><br/>
- 7.1 <a href="#iddiv2x1x1812">Basic Test</a><br/>
- 7.2 <a href="#iddiv2x1x1867">New Empty Enumeration Test</a><br/>
- 7.3 <a href="#iddiv2x1x1920">Optimized Enumeration Test</a><br/>
- 7.4 <a href="#iddiv2x1x1962">MaxCharacters Test</a><br/>
- 7.5 <a href="#iddiv2x1x2024">MaxTime Test</a><br/>
- 7.6 <a href="#iddiv2x1x2082">Duration Expiration Test</a><br/>
- 7.7 <a href="#iddiv2x1x2136">Specific Time Expiration Test</a><br/>
- 7.8 <a href="#iddiv2x1x2185">Best Effort Expiration Test</a><br/>
- 7.9 <a href="#iddiv2x1x2232">GetStatus Test</a><br/>
- 7.10 <a href="#iddiv2x1x2281">Renew Test</a><br/>
- 7.11 <a href="#iddiv2x1x2330">Release Test</a><br/>
- 7.12 <a href="#iddiv2x1x2379">EnumerationEnd Test</a><br/>
- 7.13 <a href="#iddiv2x1x2426">Filter Test - XPath 1.0</a><br/>
- 7.14 <a href="#iddiv2x1x2483">Filter Test - XPath 2.0</a><br/>
+ 6.6 <a href="#iddiv2x1x1808">Delete Test</a><br/>
+7 <a href="#iddiv1x1x1834">WS-Enumeration Tests</a><br/>
+ 7.1 <a href="#iddiv2x1x1839">Basic Test</a><br/>
+ 7.2 <a href="#iddiv2x1x1894">New Empty Enumeration Test</a><br/>
+ 7.3 <a href="#iddiv2x1x1947">Optimized Enumeration Test</a><br/>
+ 7.4 <a href="#iddiv2x1x1989">MaxCharacters Test</a><br/>
+ 7.5 <a href="#iddiv2x1x2051">MaxTime Test</a><br/>
+ 7.6 <a href="#iddiv2x1x2109">Duration Expiration Test</a><br/>
+ 7.7 <a href="#iddiv2x1x2163">Specific Time Expiration Test</a><br/>
+ 7.8 <a href="#iddiv2x1x2212">Best Effort Expiration Test</a><br/>
+ 7.9 <a href="#iddiv2x1x2259">GetStatus Test</a><br/>
+ 7.10 <a href="#iddiv2x1x2308">Renew Test</a><br/>
+ 7.11 <a href="#iddiv2x1x2357">Release Test</a><br/>
+ 7.12 <a href="#iddiv2x1x2406">EnumerationEnd Test</a><br/>
+ 7.13 <a href="#iddiv2x1x2453">Filter Test - XPath 1.0</a><br/>
+ 7.14 <a href="#iddiv2x1x2510">Filter Test - XPath 2.0</a><br/>
8 <a href="#wsdl">WSDL</a><br/>
- 8.1 <a href="#iddiv2x1x2544">Event Source WSDL</a><br/>
- 8.2 <a href="#iddiv2x1x2549">Notification WSDL</a><br/>
+ 8.1 <a href="#iddiv2x1x2571">Event Source WSDL</a><br/>
+ 8.2 <a href="#iddiv2x1x2576">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="#iddiv2x1x2588">Normative References</a><br/>
+ 12.1 <a href="#iddiv2x1x2615">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/>
@@ -1047,7 +1047,7 @@
</p></li><li><p>
Mode: Remove
Expression: //sce:Entry[1]/@Date <br/>
- Value: -
+ Value: - <br/>
Result: Date attribute is removed
</p></li><li><p>
Mode: Add
@@ -1068,7 +1068,7 @@
Result: First Entry is replaced
</p></li><li><p>
Mode: Replace
- Expression: //sce:Entry[0] <br/>
+ Expression: //sce:History/sce:Entry[0] <br/>
Value: <sce:Entry> ... </sce:Entry> <br/>
Result: Entry is added to the History array <br/>
History array needs to be empty before test starts
@@ -1099,23 +1099,35 @@
</p></li><li><p>
Mode: Remove
Expression: //sce:Entry <br/>
- Value: -
+ Value: - <br/>
Result: All Entry elements are removed <br/>
History array needs to have one Entry
</p></li><li><p>
Mode: Remove
Expression: //sce:Entry <br/>
- Value: -
+ Value: - <br/>
Result: All Entry elements are removed <br/>
History array needs to have more than one Entry
</p></li><li><p>
Mode: Remove
Expression: //sce:Entry[1] <br/>
- Value: -
+ Value: - <br/>
Result: Just first Entry is removed <br/>
History array needs to have more than one Entry
+ </p></li><li><p>
+ Mode: InsertBefore
+ Expression: //sce:History/sce:Entry <br/>
+ Value: <sce:Entry> ... </sce:Entry> <br/>
+ Result: New Entry is added to History array <br/>
+ History array needs to be empty before test starts
+ </p></li><li><p>
+ Mode: InsertAfter
+ Expression: //sce:History/sce:Entry <br/>
+ Value: <sce:Entry> ... </sce:Entry> <br/>
+ Result: New Entry is added to History array <br/>
+ History array needs to be empty before test starts
</p></li></ul></div></div><div class="div2">
-<h3><a name="iddiv2x1x1781" id="iddiv2x1x1781"/>6.6 Delete Test</h3><p>
+<h3><a name="iddiv2x1x1808" id="iddiv2x1x1808"/>6.6 Delete Test</h3><p>
This test verifies the ability of a client to delete an Animal/Tag.
The endpoint to which this test
is executed against may be any valid endpoint created during the
@@ -1124,33 +1136,33 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1787" id="iddiv3x1x1787"/>6.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1814" id="iddiv3x1x1814"/>6.6.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1792" id="iddiv3x1x1792"/>6.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1819" id="iddiv3x1x1819"/>6.6.2 Success Criteria</h4><ul><li><p>
Receipt of a valid Delete message by the service.
</p></li><li><p>
Receipt of a valid DeleteResponse message by the client.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1802" id="iddiv3x1x1802"/>6.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1829" id="iddiv3x1x1829"/>6.6.3 Conformance</h4><p>
A conforming service MUST respond to the Delete request with a
DeleteResponse message.
</p></div></div></div><div class="div1">
-<h2><a name="iddiv1x1x1807" id="iddiv1x1x1807"/>7 WS-Enumeration Tests</h2><p>
+<h2><a name="iddiv1x1x1834" id="iddiv1x1x1834"/>7 WS-Enumeration Tests</h2><p>
This section describes the tests for WS-Enumeration.
</p><div class="div2">
-<h3><a name="iddiv2x1x1812" id="iddiv2x1x1812"/>7.1 Basic Test</h3><p>
+<h3><a name="iddiv2x1x1839" id="iddiv2x1x1839"/>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="iddiv3x1x1828" id="iddiv3x1x1828"/>7.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1855" id="iddiv3x1x1855"/>7.1.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for the
Basic Test.
</p><img src="scenario/enum_basic_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x1838" id="iddiv3x1x1838"/>7.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1865" id="iddiv3x1x1865"/>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>
@@ -1169,7 +1181,7 @@
Receipt of a valid EnumerateResponse message with EndOfSequence
element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1860" id="iddiv3x1x1860"/>7.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1887" id="iddiv3x1x1887"/>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.
@@ -1177,7 +1189,7 @@
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="iddiv2x1x1867" id="iddiv2x1x1867"/>7.2 New Empty Enumeration Test</h3><p>
+<h3><a name="iddiv2x1x1894" id="iddiv2x1x1894"/>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
@@ -1185,11 +1197,11 @@
</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="iddiv3x1x1886" id="iddiv3x1x1886"/>7.2.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1913" id="iddiv3x1x1913"/>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="iddiv3x1x1891" id="iddiv3x1x1891"/>7.2.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1918" id="iddiv3x1x1918"/>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>
@@ -1208,7 +1220,7 @@
Receipt of a valid EnumerateResponse message with
EndOfSequence element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1913" id="iddiv3x1x1913"/>7.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1940" id="iddiv3x1x1940"/>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.
@@ -1217,23 +1229,23 @@
are required to be supported by the data source, there are
no allowable failure cases.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1920" id="iddiv2x1x1920"/>7.3 Optimized Enumeration Test</h3><p>
+<h3><a name="iddiv2x1x1947" id="iddiv2x1x1947"/>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="iddiv3x1x1933" id="iddiv3x1x1933"/>7.3.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1960" id="iddiv3x1x1960"/>7.3.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for
the Optimized Enumeration Test.
</p><img src="scenario/enum_optimized_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x1943" id="iddiv3x1x1943"/>7.3.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1970" id="iddiv3x1x1970"/>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="iddiv3x1x1953" id="iddiv3x1x1953"/>7.3.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1980" id="iddiv3x1x1980"/>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.
@@ -1245,7 +1257,7 @@
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="iddiv2x1x1962" id="iddiv2x1x1962"/>7.4 MaxCharacters Test</h3><p>
+<h3><a name="iddiv2x1x1989" id="iddiv2x1x1989"/>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
@@ -1255,11 +1267,11 @@
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="iddiv3x1x1990" id="iddiv3x1x1990"/>7.4.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2017" id="iddiv3x1x2017"/>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="iddiv3x1x1995" id="iddiv3x1x1995"/>7.4.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2022" id="iddiv3x1x2022"/>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>
@@ -1280,7 +1292,7 @@
Receipt of a valid EnumerateResponse message with EndOfSequence
element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2017" id="iddiv3x1x2017"/>7.4.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2044" id="iddiv3x1x2044"/>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.
@@ -1289,7 +1301,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="iddiv2x1x2024" id="iddiv2x1x2024"/>7.5 MaxTime Test</h3><p>
+<h3><a name="iddiv2x1x2051" id="iddiv2x1x2051"/>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
@@ -1299,14 +1311,14 @@
</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="iddiv3x1x2049" id="iddiv3x1x2049"/>7.5.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2076" id="iddiv3x1x2076"/>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="scenario/enum_maxtime_test.jpg"/></p></div><div class="div3">
-<h4><a name="iddiv3x1x2059" id="iddiv3x1x2059"/>7.5.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2086" id="iddiv3x1x2086"/>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>
@@ -1318,7 +1330,7 @@
</p></li><li><p>
Receipt of a wsen:TimedOut fault by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2075" id="iddiv3x1x2075"/>7.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2102" id="iddiv3x1x2102"/>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.
@@ -1327,21 +1339,21 @@
are required to be supported by the data source, there are no
allowable failure cases.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2082" id="iddiv2x1x2082"/>7.6 Duration Expiration Test</h3><p>
+<h3><a name="iddiv2x1x2109" id="iddiv2x1x2109"/>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="iddiv3x1x2101" id="iddiv3x1x2101"/>7.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2128" id="iddiv3x1x2128"/>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="scenario/enum_expires_test.jpg"/></p></div><div class="div3">
-<h4><a name="iddiv3x1x2111" id="iddiv3x1x2111"/>7.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2138" id="iddiv3x1x2138"/>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>
@@ -1354,7 +1366,7 @@
Receipt of a wsen:InvalidEnumerationContext fault by the
data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2127" id="iddiv3x1x2127"/>7.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2154" id="iddiv3x1x2154"/>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.
@@ -1366,18 +1378,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="iddiv2x1x2136" id="iddiv2x1x2136"/>7.7 Specific Time Expiration Test</h3><p>
+<h3><a name="iddiv2x1x2163" id="iddiv2x1x2163"/>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="iddiv3x1x2155" id="iddiv3x1x2155"/>7.7.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2182" id="iddiv3x1x2182"/>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="iddiv3x1x2160" id="iddiv3x1x2160"/>7.7.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2187" id="iddiv3x1x2187"/>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>
@@ -1390,7 +1402,7 @@
Receipt of a wsen:InvalidEnumerationContext fault by the
data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2176" id="iddiv3x1x2176"/>7.7.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2203" id="iddiv3x1x2203"/>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.
@@ -1404,7 +1416,7 @@
request with a wsen:UnsupportedExpirationValue fault or a
wsen:UnsupportedExpirationType fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2185" id="iddiv2x1x2185"/>7.8 Best Effort Expiration Test</h3><p>
+<h3><a name="iddiv2x1x2212" id="iddiv2x1x2212"/>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:
@@ -1412,11 +1424,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="iddiv3x1x2204" id="iddiv3x1x2204"/>7.8.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2231" id="iddiv3x1x2231"/>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="iddiv3x1x2209" id="iddiv3x1x2209"/>7.8.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2236" id="iddiv3x1x2236"/>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>
@@ -1429,7 +1441,7 @@
Receipt of a wsen:InvalidEnumerationContext fault by the
data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2225" id="iddiv3x1x2225"/>7.8.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2252" id="iddiv3x1x2252"/>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
@@ -1439,19 +1451,19 @@
are required to be supported by the data source, there are no
allowable failure cases.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2232" id="iddiv2x1x2232"/>7.9 GetStatus Test</h3><p>
+<h3><a name="iddiv2x1x2259" id="iddiv2x1x2259"/>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="iddiv3x1x2248" id="iddiv3x1x2248"/>7.9.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2275" id="iddiv3x1x2275"/>7.9.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for
the GetStatus Test.
<img src="scenario/enum_getstatus_test.jpg"/></p></div><div class="div3">
-<h4><a name="iddiv3x1x2258" id="iddiv3x1x2258"/>7.9.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2285" id="iddiv3x1x2285"/>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>
@@ -1463,7 +1475,7 @@
</p></li><li><p>
Receipt of valid GetStatusResponse message by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2274" id="iddiv3x1x2274"/>7.9.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2301" id="iddiv3x1x2301"/>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>
@@ -1471,19 +1483,19 @@
are required to be supported by the data source, there are no
allowable failure cases.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2281" id="iddiv2x1x2281"/>7.10 Renew Test</h3><p>
+<h3><a name="iddiv2x1x2308" id="iddiv2x1x2308"/>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="iddiv3x1x2297" id="iddiv3x1x2297"/>7.10.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2324" id="iddiv3x1x2324"/>7.10.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for the
Renew Test.
<img src="scenario/enum_renew_test.jpg"/></p></div><div class="div3">
-<h4><a name="iddiv3x1x2307" id="iddiv3x1x2307"/>7.10.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2334" id="iddiv3x1x2334"/>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>
@@ -1495,7 +1507,7 @@
</p></li><li><p>
Receipt of valid RenewResponse message by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2323" id="iddiv3x1x2323"/>7.10.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2350" id="iddiv3x1x2350"/>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>
@@ -1503,7 +1515,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="iddiv2x1x2330" id="iddiv2x1x2330"/>7.11 Release Test</h3><p>
+<h3><a name="iddiv2x1x2357" id="iddiv2x1x2357"/>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
@@ -1511,12 +1523,12 @@
</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="iddiv3x1x2346" id="iddiv3x1x2346"/>7.11.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2373" id="iddiv3x1x2373"/>7.11.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for
the Release Test.
<img src="scenario/enum_release_test.jpg"/></p></div><div class="div3">
-<h4><a name="iddiv3x1x2356" id="iddiv3x1x2356"/>7.11.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2383" id="iddiv3x1x2383"/>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>
@@ -1528,7 +1540,7 @@
</p></li><li><p>
Receipt of valid ReleaseResponse message by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2372" id="iddiv3x1x2372"/>7.11.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2399" id="iddiv3x1x2399"/>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>
@@ -1536,18 +1548,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="iddiv2x1x2379" id="iddiv2x1x2379"/>7.12 EnumerationEnd Test</h3><p>
+<h3><a name="iddiv2x1x2406" id="iddiv2x1x2406"/>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="iddiv3x1x2392" id="iddiv3x1x2392"/>7.12.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2419" id="iddiv3x1x2419"/>7.12.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for
the EnumerationEnd Test.
<img src="scenario/enum_enumerationend_test.jpg"/></p></div><div class="div3">
-<h4><a name="iddiv3x1x2402" id="iddiv3x1x2402"/>7.12.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2429" id="iddiv3x1x2429"/>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>
@@ -1556,7 +1568,7 @@
</p></li><li><p>
Receipt of valid EnumerationEnd message by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2415" id="iddiv3x1x2415"/>7.12.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2442" id="iddiv3x1x2442"/>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.
@@ -1571,7 +1583,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="iddiv2x1x2426" id="iddiv2x1x2426"/>7.13 Filter Test - XPath 1.0</h3><p>
+<h3><a name="iddiv2x1x2453" id="iddiv2x1x2453"/>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:
@@ -1582,11 +1594,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="iddiv3x1x2445" id="iddiv3x1x2445"/>7.13.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2472" id="iddiv3x1x2472"/>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="iddiv3x1x2450" id="iddiv3x1x2450"/>7.13.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2477" id="iddiv3x1x2477"/>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>
@@ -1605,7 +1617,7 @@
Receipt of a valid EnumerateResponse message with
EndOfSequence element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2472" id="iddiv3x1x2472"/>7.13.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2499" id="iddiv3x1x2499"/>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
@@ -1626,7 +1638,7 @@
filter will never evaluate to true for the lifetime of
the enumeration.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2483" id="iddiv2x1x2483"/>7.14 Filter Test - XPath 2.0</h3><p>
+<h3><a name="iddiv2x1x2510" id="iddiv2x1x2510"/>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:
@@ -1637,11 +1649,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="iddiv3x1x2502" id="iddiv3x1x2502"/>7.14.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2529" id="iddiv3x1x2529"/>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="iddiv3x1x2507" id="iddiv3x1x2507"/>7.14.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2534" id="iddiv3x1x2534"/>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>
@@ -1660,7 +1672,7 @@
Receipt of a valid EnumerateResponse message with EndOfSequence
element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2529" id="iddiv3x1x2529"/>7.14.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2556" id="iddiv3x1x2556"/>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
@@ -1682,10 +1694,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="iddiv2x1x2544" id="iddiv2x1x2544"/>8.1 Event Source WSDL</h3><p>
+<h3><a name="iddiv2x1x2571" id="iddiv2x1x2571"/>8.1 Event Source WSDL</h3><p>
TBD
</p></div><div class="div2">
-<h3><a name="iddiv2x1x2549" id="iddiv2x1x2549"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x2576" id="iddiv2x1x2576"/>8.2 Notification WSDL</h3><p>
Available here:
<a href="http://www.w3.org/2011/01/scenario/scenarioSink.wsdl">http://www.w3.org/2011/01/scenario/scenarioSink.wsdl</a></p></div></div><div class="div1">
<h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
@@ -1725,7 +1737,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="iddiv2x1x2588" id="iddiv2x1x2588"/>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="iddiv2x1x2615" id="iddiv2x1x2615"/>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.
Received on Monday, 31 January 2011 19:48:59 UTC