- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 08 Feb 2011 00:57:15 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/test
In directory hutz:/tmp/cvs-serv14721
Modified Files:
scenario.html scenario.xml
Log Message:
Fix some xpath expressions
Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/test/scenario.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- scenario.xml 5 Feb 2011 00:23:33 -0000 1.7
+++ scenario.xml 8 Feb 2011 00:57:13 -0000 1.8
@@ -1694,9 +1694,9 @@
<item>
<p>
Filter in dialect 'http://www.w3.org/2010/08/ws-evt/Dialects/XPath10'
- that selects those events that apply to tag
- 234b6840-de3d-11df-85ca-0800200c9a66 (Kerry).
- (TBD - add exact filter expression)
+ that selects those events that apply to the animal named 'Kerry':
+ <phrase/>
+ //*[local-name='Name']/node()='Kerry'
</p>
</item>
<item>
@@ -1712,8 +1712,8 @@
<p>
The messaging sequence for this test is identical to that of the
Basic Test. The difference between this test and the Basic Test is
- that only Notifications applying to tag
- 234b6840-de3d-11df-85ca-0800200c9a66 are received by the Event Sink.
+ that only Notifications applying to the animal named 'Kerry'
+ are received by the Event Sink.
</p>
</div3>
@@ -1733,8 +1733,8 @@
</item>
<item>
<p>
- Receipt of one or more unwrapped Notifications for the tag
- 234b6840-de3d-11df-85ca-0800200c9a66 by the Event Sink.
+ Receipt of one or more unwrapped Notifications for the animal
+ named 'Kerry' by the Event Sink.
</p>
</item>
<item>
@@ -1795,9 +1795,9 @@
<item>
<p>
Filter in dialect 'http://www.w3.org/2010/08/ws-evt/Dialects/XPath20'
- that selects those events that apply to tag
- 32675b90-de3d-11df-85ca-0800200c9a66 (Oscar).
- (TBD - add exact filter expression)
+ that selects those events that apply to the animal named 'Oscar':
+ <phrase/>
+ //*[local-name='Name']/node()='Oscar'
</p>
</item>
<item>
@@ -1813,8 +1813,8 @@
<p>
The messaging sequence for this test is identical to that of the
Basic Test. The difference between this test and the Basic Test is
- that only Notifications applying to tag
- 32675b90-de3d-11df-85ca-0800200c9a66 are received by the Event Sink.
+ that only Notifications applying to the animal named 'Oscar'
+ are received by the Event Sink.
</p>
</div3>
@@ -1834,8 +1834,8 @@
</item>
<item>
<p>
- Receipt of one or more unwrapped Notifications for the tag
- 32675b90-de3d-11df-85ca-0800200c9a66 by the Event Sink.
+ Receipt of one or more unwrapped Notifications for the animal
+ named 'Oscar' by the Event Sink.
</p>
</item>
<item>
Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/test/scenario.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- scenario.html 5 Feb 2011 00:23:33 -0000 1.7
+++ scenario.html 8 Feb 2011 00:57:13 -0000 1.8
@@ -70,38 +70,38 @@
5.6 <a href="#iddiv2x1x1204">Renew Test</a><br/>
5.7 <a href="#iddiv2x1x1274">SubscriptionEnd Test</a><br/>
5.8 <a href="#iddiv2x1x1336">Filter Test - XPath 1.0</a><br/>
- 5.9 <a href="#iddiv2x1x1388">Filter Test - XPath 2.0</a><br/>
- 5.10 <a href="#iddiv2x1x1440">Non-Addressable Event Sink Test</a><br/>
-6 <a href="#iddiv1x1x1504">WS-Transfer/WS-Fragment Tests</a><br/>
- 6.1 <a href="#iddiv2x1x1509">Create Test</a><br/>
- 6.2 <a href="#iddiv2x1x1535">Get Test</a><br/>
- 6.3 <a href="#iddiv2x1x1561">Fragment Get Test</a><br/>
- 6.4 <a href="#iddiv2x1x1587">Put Test</a><br/>
- 6.5 <a href="#iddiv2x1x1613">Fragment Put Test</a><br/>
- 6.6 <a href="#iddiv2x1x1888">Delete Test</a><br/>
-7 <a href="#iddiv1x1x1914">WS-Enumeration Tests</a><br/>
- 7.1 <a href="#iddiv2x1x1919">Basic Test</a><br/>
- 7.2 <a href="#iddiv2x1x1974">New Empty Enumeration Test</a><br/>
- 7.3 <a href="#iddiv2x1x2027">Optimized Enumeration Test</a><br/>
- 7.4 <a href="#iddiv2x1x2069">MaxCharacters Test</a><br/>
- 7.5 <a href="#iddiv2x1x2131">MaxTime Test</a><br/>
- 7.6 <a href="#iddiv2x1x2189">Duration Expiration Test</a><br/>
- 7.7 <a href="#iddiv2x1x2243">Specific Time Expiration Test</a><br/>
- 7.8 <a href="#iddiv2x1x2292">Best Effort Expiration Test</a><br/>
- 7.9 <a href="#iddiv2x1x2339">GetStatus Test</a><br/>
- 7.10 <a href="#iddiv2x1x2388">Renew Test</a><br/>
- 7.11 <a href="#iddiv2x1x2437">Release Test</a><br/>
- 7.12 <a href="#iddiv2x1x2486">EnumerationEnd Test</a><br/>
- 7.13 <a href="#iddiv2x1x2541">Filter Test - XPath 1.0</a><br/>
- 7.14 <a href="#iddiv2x1x2598">Filter Test - XPath 2.0</a><br/>
+ 5.9 <a href="#iddiv2x1x1390">Filter Test - XPath 2.0</a><br/>
+ 5.10 <a href="#iddiv2x1x1444">Non-Addressable Event Sink Test</a><br/>
+6 <a href="#iddiv1x1x1508">WS-Transfer/WS-Fragment Tests</a><br/>
+ 6.1 <a href="#iddiv2x1x1513">Create Test</a><br/>
+ 6.2 <a href="#iddiv2x1x1539">Get Test</a><br/>
+ 6.3 <a href="#iddiv2x1x1565">Fragment Get Test</a><br/>
+ 6.4 <a href="#iddiv2x1x1591">Put Test</a><br/>
+ 6.5 <a href="#iddiv2x1x1617">Fragment Put Test</a><br/>
+ 6.6 <a href="#iddiv2x1x1892">Delete Test</a><br/>
+7 <a href="#iddiv1x1x1918">WS-Enumeration Tests</a><br/>
+ 7.1 <a href="#iddiv2x1x1923">Basic Test</a><br/>
+ 7.2 <a href="#iddiv2x1x1978">New Empty Enumeration Test</a><br/>
+ 7.3 <a href="#iddiv2x1x2031">Optimized Enumeration Test</a><br/>
+ 7.4 <a href="#iddiv2x1x2073">MaxCharacters Test</a><br/>
+ 7.5 <a href="#iddiv2x1x2135">MaxTime Test</a><br/>
+ 7.6 <a href="#iddiv2x1x2193">Duration Expiration Test</a><br/>
+ 7.7 <a href="#iddiv2x1x2247">Specific Time Expiration Test</a><br/>
+ 7.8 <a href="#iddiv2x1x2296">Best Effort Expiration Test</a><br/>
+ 7.9 <a href="#iddiv2x1x2343">GetStatus Test</a><br/>
+ 7.10 <a href="#iddiv2x1x2392">Renew Test</a><br/>
+ 7.11 <a href="#iddiv2x1x2441">Release Test</a><br/>
+ 7.12 <a href="#iddiv2x1x2490">EnumerationEnd Test</a><br/>
+ 7.13 <a href="#iddiv2x1x2545">Filter Test - XPath 1.0</a><br/>
+ 7.14 <a href="#iddiv2x1x2602">Filter Test - XPath 2.0</a><br/>
8 <a href="#wsdl">WSDL</a><br/>
- 8.1 <a href="#iddiv2x1x2659">Event Source WSDL</a><br/>
- 8.2 <a href="#iddiv2x1x2664">Notification WSDL</a><br/>
+ 8.1 <a href="#iddiv2x1x2663">Event Source WSDL</a><br/>
+ 8.2 <a href="#iddiv2x1x2668">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="#iddiv2x1x2703">Normative References</a><br/>
+ 12.1 <a href="#iddiv2x1x2707">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/>
@@ -756,31 +756,31 @@
no EndTo EPR
</p></li><li><p>
Filter in dialect 'http://www.w3.org/2010/08/ws-evt/Dialects/XPath10'
- that selects those events that apply to tag
- 234b6840-de3d-11df-85ca-0800200c9a66 (Kerry).
- (TBD - add exact filter expression)
+ that selects those events that apply to the animal named 'Kerry':
+ <br/>
+ //*[local-name='Name']/node()='Kerry'
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1355" id="iddiv3x1x1355"/>5.8.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1357" id="iddiv3x1x1357"/>5.8.1 Sequence</h4><p>
The messaging sequence for this test is identical to that of the
Basic Test. The difference between this test and the Basic Test is
- that only Notifications applying to tag
- 234b6840-de3d-11df-85ca-0800200c9a66 are received by the Event Sink.
+ that only Notifications applying to the animal named 'Kerry'
+ are received by the Event Sink.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1360" id="iddiv3x1x1360"/>5.8.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1362" id="iddiv3x1x1362"/>5.8.2 Success Criteria</h4><ul><li><p>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
- Receipt of one or more unwrapped Notifications for the tag
- 234b6840-de3d-11df-85ca-0800200c9a66 by the Event Sink.
+ Receipt of one or more unwrapped Notifications for the animal
+ named 'Kerry' by the Event Sink.
</p></li><li><p>
Receipt of a valid Unsubscribe message by the Subscription Manager.
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1379" id="iddiv3x1x1379"/>5.8.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1381" id="iddiv3x1x1381"/>5.8.3 Conformance</h4><p>
Because this test involves the use of the optional wse:Filter
element there are a number of failure cases that fall within the
boundaries of conforming behavior.
@@ -793,7 +793,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1388" id="iddiv2x1x1388"/>5.9 Filter Test - XPath 2.0</h3><p>
+<h3><a name="iddiv2x1x1390" id="iddiv2x1x1390"/>5.9 Filter Test - XPath 2.0</h3><p>
This test verifies the ability of the Event Source/Subscription
Manager to correctly implement XPath 2.0 filters. The initial
Subscribe request has the following features:
@@ -803,31 +803,31 @@
no EndTo EPR
</p></li><li><p>
Filter in dialect 'http://www.w3.org/2010/08/ws-evt/Dialects/XPath20'
- that selects those events that apply to tag
- 32675b90-de3d-11df-85ca-0800200c9a66 (Oscar).
- (TBD - add exact filter expression)
+ that selects those events that apply to the animal named 'Oscar':
+ <br/>
+ //*[local-name='Name']/node()='Oscar'
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1407" id="iddiv3x1x1407"/>5.9.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1411" id="iddiv3x1x1411"/>5.9.1 Sequence</h4><p>
The messaging sequence for this test is identical to that of the
Basic Test. The difference between this test and the Basic Test is
- that only Notifications applying to tag
- 32675b90-de3d-11df-85ca-0800200c9a66 are received by the Event Sink.
+ that only Notifications applying to the animal named 'Oscar'
+ are received by the Event Sink.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1412" id="iddiv3x1x1412"/>5.9.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1416" id="iddiv3x1x1416"/>5.9.2 Success Criteria</h4><ul><li><p>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
- Receipt of one or more unwrapped Notifications for the tag
- 32675b90-de3d-11df-85ca-0800200c9a66 by the Event Sink.
+ Receipt of one or more unwrapped Notifications for the animal
+ named 'Oscar' by the Event Sink.
</p></li><li><p>
Receipt of a valid Unsubscribe message by the Subscription Manager.
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1431" id="iddiv3x1x1431"/>5.9.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1435" id="iddiv3x1x1435"/>5.9.3 Conformance</h4><p>
Because this test involves the use of the optional wse:Filter element
there are a number of failure cases that fall within the boundaries
of conforming behavior.
@@ -840,7 +840,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1440" id="iddiv2x1x1440"/>5.10 Non-Addressable Event Sink Test</h3><p>
+<h3><a name="iddiv2x1x1444" id="iddiv2x1x1444"/>5.10 Non-Addressable Event Sink Test</h3><p>
This test verifies the ability to subscribe and receive notifications
in an environment in which the Event Sink cannot accept connections
from systems outside its network (i.e. the Event Sink is
@@ -861,7 +861,7 @@
the MakeConnection anonymous URI (e.g.
http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=550e8400-e29b-11d4-a716-446655440000).
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1464" id="iddiv3x1x1464"/>5.11 Sequence</h4><p>
+<h4><a name="iddiv3x1x1468" id="iddiv3x1x1468"/>5.11 Sequence</h4><p>
The following diagram illustrates the sequence of messages for the
Non-Addressable Event Sink Test.
</p><img src="scenario/non_addressable_event_sink.jpg"/><p>
@@ -870,7 +870,7 @@
SubscribeResponse and UnsubscribeResponse are both transmitted on
the back-channel of their corresponding requests.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1476" id="iddiv3x1x1476"/>5.12 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1480" id="iddiv3x1x1480"/>5.12 Success Criteria</h4><ul><li><p>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
@@ -902,27 +902,27 @@
elicit a wsa:ActionNotSupported fault response or some other,
unspecified behavior.
</p></div></div><div class="div1">
-<h2><a name="iddiv1x1x1504" id="iddiv1x1x1504"/>6 WS-Transfer/WS-Fragment Tests</h2><p>
+<h2><a name="iddiv1x1x1508" id="iddiv1x1x1508"/>6 WS-Transfer/WS-Fragment Tests</h2><p>
This section describes the tests for WS-Transfer and WS-Fragment.
</p><div class="div2">
-<h3><a name="iddiv2x1x1509" id="iddiv2x1x1509"/>6.1 Create Test</h3><p>
+<h3><a name="iddiv2x1x1513" id="iddiv2x1x1513"/>6.1 Create Test</h3><p>
This test will verifies the ability to create a new Animal/Tag
in the service. The Create message will contain the initial
representation of the new Animal/Tag.
</p><div class="div3">
-<h4><a name="iddiv3x1x1515" id="iddiv3x1x1515"/>6.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1519" id="iddiv3x1x1519"/>6.1.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1520" id="iddiv3x1x1520"/>6.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1524" id="iddiv3x1x1524"/>6.1.2 Success Criteria</h4><ul><li><p>
Receipt of a valid Create message by the service.
</p></li><li><p>
Receipt of a valid CreateResponse message by the client.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1530" id="iddiv3x1x1530"/>6.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1534" id="iddiv3x1x1534"/>6.1.3 Conformance</h4><p>
A conforming service MUST respond to the Create request with a
CreateResponse message.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1535" id="iddiv2x1x1535"/>6.2 Get Test</h3><p>
+<h3><a name="iddiv2x1x1539" id="iddiv2x1x1539"/>6.2 Get Test</h3><p>
This test verifies the ability of a client to retrieve the
current representation of an Animal/Tag. The endpoint to which
this test is executed against may be any valid endpoint created
@@ -931,20 +931,20 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1541" id="iddiv3x1x1541"/>6.2.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1545" id="iddiv3x1x1545"/>6.2.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1546" id="iddiv3x1x1546"/>6.2.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1550" id="iddiv3x1x1550"/>6.2.2 Success Criteria</h4><ul><li><p>
Receipt of a valid Get message by the service.
</p></li><li><p>
Receipt of a valid GetResponse message by the service.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1556" id="iddiv3x1x1556"/>6.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1560" id="iddiv3x1x1560"/>6.2.3 Conformance</h4><p>
A conforming service MUST respond to the Get request with a
GetResponse message containing the current representation of
the Animal/Tag.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1561" id="iddiv2x1x1561"/>6.3 Fragment Get Test</h3><p>
+<h3><a name="iddiv2x1x1565" id="iddiv2x1x1565"/>6.3 Fragment Get Test</h3><p>
This test verifies the ability of a client to retrieve a subset of the
current representation of an Animal/Tag. The endpoint to which
this test is executed against may be any valid endpoint created
@@ -953,22 +953,22 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1567" id="iddiv3x1x1567"/>6.3.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1571" id="iddiv3x1x1571"/>6.3.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1572" id="iddiv3x1x1572"/>6.3.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1576" id="iddiv3x1x1576"/>6.3.2 Success Criteria</h4><ul><li><p>
Receipt of a valid Get message containing the WS-Fragment Dialect IRI
by the service.
</p></li><li><p>
Receipt of a valid GetResponse message by the service.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1582" id="iddiv3x1x1582"/>6.3.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1586" id="iddiv3x1x1586"/>6.3.3 Conformance</h4><p>
The Get request uses the WS-Fragment Dialect IRI
and asks for a subset of the representation using XPath 1.0.
A conforming service MUST either respond with a wst:UnknownDialect
fault or return just the requested data.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1587" id="iddiv2x1x1587"/>6.4 Put Test</h3><p>
+<h3><a name="iddiv2x1x1591" id="iddiv2x1x1591"/>6.4 Put Test</h3><p>
This test verifies the ability of a client to update the current
representation of an Animal/Tag. The endpoint to which this test
is executed against may be any valid endpoint created during the
@@ -977,19 +977,19 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1593" id="iddiv3x1x1593"/>6.4.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1597" id="iddiv3x1x1597"/>6.4.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1598" id="iddiv3x1x1598"/>6.4.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1602" id="iddiv3x1x1602"/>6.4.2 Success Criteria</h4><ul><li><p>
Receipt of a valid Put message by the service.
</p></li><li><p>
Receipt of a valid PutResponse message by the client.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1608" id="iddiv3x1x1608"/>6.4.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1612" id="iddiv3x1x1612"/>6.4.3 Conformance</h4><p>
A conforming service MUST respond to the Put request with a
PutResponse message.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1613" id="iddiv2x1x1613"/>6.5 Fragment Put Test</h3><p>
+<h3><a name="iddiv2x1x1617" id="iddiv2x1x1617"/>6.5 Fragment Put Test</h3><p>
This test verifies the ability of a client to update a portion of the
current representation of an Animal/Tag. The endpoint to which this test
is executed against may be any valid endpoint created during the
@@ -998,12 +998,12 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1619" id="iddiv3x1x1619"/>6.5.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1623" id="iddiv3x1x1623"/>6.5.1 Sequence</h4><p>
In this test the client issues a series of Put requests to update
the representation of an Animal/Tag. After each request the client
will issue a Get to verify that the update was successful.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1624" id="iddiv3x1x1624"/>6.5.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1628" id="iddiv3x1x1628"/>6.5.2 Success Criteria</h4><ul><li><p>
Receipt of a valid Put message using the WS-Fragment Dialect IRI
by the service.
</p></li><li><p>
@@ -1013,14 +1013,14 @@
</p></li><li><p>
Receipt of a valid GetResponse message by the client.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1640" id="iddiv3x1x1640"/>6.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1644" id="iddiv3x1x1644"/>6.5.3 Conformance</h4><p>
A conforming service MUST respond to the Put request with either a
wst:UnknownDialect fault or return a PutResponse message. A
conforming service MUST also respond to the subsequent Get request
with a GetResponse message containing the new representation of the
Animal/Tag - or with no change if the Put was rejected.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1645" id="iddiv3x1x1645"/>6.5.4 Variations</h4><p>
+<h4><a name="iddiv3x1x1649" id="iddiv3x1x1649"/>6.5.4 Variations</h4><p>
Except when noted,
the following variations use this Animal representation as
an example guide for what each variation is expected to produce:
@@ -1146,7 +1146,7 @@
Result: New Entry is added to History array <br/>
History array needs to be empty before test starts
</p></li></ol></div></div><div class="div2">
-<h3><a name="iddiv2x1x1888" id="iddiv2x1x1888"/>6.6 Delete Test</h3><p>
+<h3><a name="iddiv2x1x1892" id="iddiv2x1x1892"/>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
@@ -1155,33 +1155,33 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1894" id="iddiv3x1x1894"/>6.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1898" id="iddiv3x1x1898"/>6.6.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1899" id="iddiv3x1x1899"/>6.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1903" id="iddiv3x1x1903"/>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="iddiv3x1x1909" id="iddiv3x1x1909"/>6.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1913" id="iddiv3x1x1913"/>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="iddiv1x1x1914" id="iddiv1x1x1914"/>7 WS-Enumeration Tests</h2><p>
+<h2><a name="iddiv1x1x1918" id="iddiv1x1x1918"/>7 WS-Enumeration Tests</h2><p>
This section describes the tests for WS-Enumeration.
</p><div class="div2">
-<h3><a name="iddiv2x1x1919" id="iddiv2x1x1919"/>7.1 Basic Test</h3><p>
+<h3><a name="iddiv2x1x1923" id="iddiv2x1x1923"/>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="iddiv3x1x1935" id="iddiv3x1x1935"/>7.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1939" id="iddiv3x1x1939"/>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="iddiv3x1x1945" id="iddiv3x1x1945"/>7.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1949" id="iddiv3x1x1949"/>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>
@@ -1200,7 +1200,7 @@
Receipt of a valid EnumerateResponse message with EndOfSequence
element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1967" id="iddiv3x1x1967"/>7.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1971" id="iddiv3x1x1971"/>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.
@@ -1208,7 +1208,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="iddiv2x1x1974" id="iddiv2x1x1974"/>7.2 New Empty Enumeration Test</h3><p>
+<h3><a name="iddiv2x1x1978" id="iddiv2x1x1978"/>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
@@ -1216,11 +1216,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="iddiv3x1x1993" id="iddiv3x1x1993"/>7.2.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1997" id="iddiv3x1x1997"/>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="iddiv3x1x1998" id="iddiv3x1x1998"/>7.2.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2002" id="iddiv3x1x2002"/>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>
@@ -1239,7 +1239,7 @@
Receipt of a valid EnumerateResponse message with
EndOfSequence element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2020" id="iddiv3x1x2020"/>7.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2024" id="iddiv3x1x2024"/>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.
@@ -1248,23 +1248,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="iddiv2x1x2027" id="iddiv2x1x2027"/>7.3 Optimized Enumeration Test</h3><p>
+<h3><a name="iddiv2x1x2031" id="iddiv2x1x2031"/>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="iddiv3x1x2040" id="iddiv3x1x2040"/>7.3.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2044" id="iddiv3x1x2044"/>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="iddiv3x1x2050" id="iddiv3x1x2050"/>7.3.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2054" id="iddiv3x1x2054"/>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="iddiv3x1x2060" id="iddiv3x1x2060"/>7.3.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2064" id="iddiv3x1x2064"/>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.
@@ -1276,7 +1276,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="iddiv2x1x2069" id="iddiv2x1x2069"/>7.4 MaxCharacters Test</h3><p>
+<h3><a name="iddiv2x1x2073" id="iddiv2x1x2073"/>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
@@ -1286,11 +1286,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="iddiv3x1x2097" id="iddiv3x1x2097"/>7.4.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2101" id="iddiv3x1x2101"/>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="iddiv3x1x2102" id="iddiv3x1x2102"/>7.4.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2106" id="iddiv3x1x2106"/>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>
@@ -1311,7 +1311,7 @@
Receipt of a valid EnumerateResponse message with EndOfSequence
element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2124" id="iddiv3x1x2124"/>7.4.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2128" id="iddiv3x1x2128"/>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.
@@ -1320,7 +1320,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="iddiv2x1x2131" id="iddiv2x1x2131"/>7.5 MaxTime Test</h3><p>
+<h3><a name="iddiv2x1x2135" id="iddiv2x1x2135"/>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
@@ -1330,13 +1330,13 @@
</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="iddiv3x1x2156" id="iddiv3x1x2156"/>7.5.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2160" id="iddiv3x1x2160"/>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="iddiv3x1x2166" id="iddiv3x1x2166"/>7.5.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2170" id="iddiv3x1x2170"/>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>
@@ -1348,7 +1348,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="iddiv3x1x2182" id="iddiv3x1x2182"/>7.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2186" id="iddiv3x1x2186"/>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.
@@ -1357,20 +1357,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="iddiv2x1x2189" id="iddiv2x1x2189"/>7.6 Duration Expiration Test</h3><p>
+<h3><a name="iddiv2x1x2193" id="iddiv2x1x2193"/>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="iddiv3x1x2208" id="iddiv3x1x2208"/>7.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2212" id="iddiv3x1x2212"/>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="iddiv3x1x2218" id="iddiv3x1x2218"/>7.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2222" id="iddiv3x1x2222"/>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>
@@ -1383,7 +1383,7 @@
Receipt of a wsen:InvalidEnumerationContext fault by the
data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2234" id="iddiv3x1x2234"/>7.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2238" id="iddiv3x1x2238"/>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.
@@ -1395,18 +1395,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="iddiv2x1x2243" id="iddiv2x1x2243"/>7.7 Specific Time Expiration Test</h3><p>
+<h3><a name="iddiv2x1x2247" id="iddiv2x1x2247"/>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="iddiv3x1x2262" id="iddiv3x1x2262"/>7.7.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2266" id="iddiv3x1x2266"/>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="iddiv3x1x2267" id="iddiv3x1x2267"/>7.7.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2271" id="iddiv3x1x2271"/>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>
@@ -1419,7 +1419,7 @@
Receipt of a wsen:InvalidEnumerationContext fault by the
data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2283" id="iddiv3x1x2283"/>7.7.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2287" id="iddiv3x1x2287"/>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.
@@ -1433,7 +1433,7 @@
request with a wsen:UnsupportedExpirationValue fault or a
wsen:UnsupportedExpirationType fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2292" id="iddiv2x1x2292"/>7.8 Best Effort Expiration Test</h3><p>
+<h3><a name="iddiv2x1x2296" id="iddiv2x1x2296"/>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:
@@ -1441,11 +1441,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="iddiv3x1x2311" id="iddiv3x1x2311"/>7.8.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2315" id="iddiv3x1x2315"/>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="iddiv3x1x2316" id="iddiv3x1x2316"/>7.8.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2320" id="iddiv3x1x2320"/>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>
@@ -1458,7 +1458,7 @@
Receipt of a wsen:InvalidEnumerationContext fault by the
data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2332" id="iddiv3x1x2332"/>7.8.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2336" id="iddiv3x1x2336"/>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
@@ -1468,18 +1468,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="iddiv2x1x2339" id="iddiv2x1x2339"/>7.9 GetStatus Test</h3><p>
+<h3><a name="iddiv2x1x2343" id="iddiv2x1x2343"/>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="iddiv3x1x2355" id="iddiv3x1x2355"/>7.9.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2359" id="iddiv3x1x2359"/>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="iddiv3x1x2365" id="iddiv3x1x2365"/>7.9.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2369" id="iddiv3x1x2369"/>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>
@@ -1491,7 +1491,7 @@
</p></li><li><p>
Receipt of valid GetStatusResponse message by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2381" id="iddiv3x1x2381"/>7.9.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2385" id="iddiv3x1x2385"/>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>
@@ -1499,18 +1499,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="iddiv2x1x2388" id="iddiv2x1x2388"/>7.10 Renew Test</h3><p>
+<h3><a name="iddiv2x1x2392" id="iddiv2x1x2392"/>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="iddiv3x1x2404" id="iddiv3x1x2404"/>7.10.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2408" id="iddiv3x1x2408"/>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="iddiv3x1x2414" id="iddiv3x1x2414"/>7.10.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2418" id="iddiv3x1x2418"/>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>
@@ -1522,7 +1522,7 @@
</p></li><li><p>
Receipt of valid RenewResponse message by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2430" id="iddiv3x1x2430"/>7.10.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2434" id="iddiv3x1x2434"/>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>
@@ -1530,7 +1530,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="iddiv2x1x2437" id="iddiv2x1x2437"/>7.11 Release Test</h3><p>
+<h3><a name="iddiv2x1x2441" id="iddiv2x1x2441"/>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
@@ -1538,11 +1538,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="iddiv3x1x2453" id="iddiv3x1x2453"/>7.11.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2457" id="iddiv3x1x2457"/>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="iddiv3x1x2463" id="iddiv3x1x2463"/>7.11.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2467" id="iddiv3x1x2467"/>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>
@@ -1554,7 +1554,7 @@
</p></li><li><p>
Receipt of valid ReleaseResponse message by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2479" id="iddiv3x1x2479"/>7.11.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2483" id="iddiv3x1x2483"/>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>
@@ -1562,7 +1562,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="iddiv2x1x2486" id="iddiv2x1x2486"/>7.12 EnumerationEnd Test</h3><p>
+<h3><a name="iddiv2x1x2490" id="iddiv2x1x2490"/>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
@@ -1577,11 +1577,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="iddiv3x1x2507" id="iddiv3x1x2507"/>7.12.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2511" id="iddiv3x1x2511"/>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="iddiv3x1x2517" id="iddiv3x1x2517"/>7.12.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2521" id="iddiv3x1x2521"/>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>
@@ -1590,7 +1590,7 @@
</p></li><li><p>
Receipt of valid EnumerationEnd message by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2530" id="iddiv3x1x2530"/>7.12.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2534" id="iddiv3x1x2534"/>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.
@@ -1605,7 +1605,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="iddiv2x1x2541" id="iddiv2x1x2541"/>7.13 Filter Test - XPath 1.0</h3><p>
+<h3><a name="iddiv2x1x2545" id="iddiv2x1x2545"/>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:
@@ -1616,11 +1616,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="iddiv3x1x2560" id="iddiv3x1x2560"/>7.13.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2564" id="iddiv3x1x2564"/>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="iddiv3x1x2565" id="iddiv3x1x2565"/>7.13.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2569" id="iddiv3x1x2569"/>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>
@@ -1639,7 +1639,7 @@
Receipt of a valid EnumerateResponse message with
EndOfSequence element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2587" id="iddiv3x1x2587"/>7.13.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2591" id="iddiv3x1x2591"/>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
@@ -1660,7 +1660,7 @@
filter will never evaluate to true for the lifetime of
the enumeration.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x2598" id="iddiv2x1x2598"/>7.14 Filter Test - XPath 2.0</h3><p>
+<h3><a name="iddiv2x1x2602" id="iddiv2x1x2602"/>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:
@@ -1671,11 +1671,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="iddiv3x1x2617" id="iddiv3x1x2617"/>7.14.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x2621" id="iddiv3x1x2621"/>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="iddiv3x1x2622" id="iddiv3x1x2622"/>7.14.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x2626" id="iddiv3x1x2626"/>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>
@@ -1694,7 +1694,7 @@
Receipt of a valid EnumerateResponse message with EndOfSequence
element by the data consumer
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x2644" id="iddiv3x1x2644"/>7.14.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x2648" id="iddiv3x1x2648"/>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
@@ -1716,10 +1716,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="iddiv2x1x2659" id="iddiv2x1x2659"/>8.1 Event Source WSDL</h3><p>
+<h3><a name="iddiv2x1x2663" id="iddiv2x1x2663"/>8.1 Event Source WSDL</h3><p>
TBD
</p></div><div class="div2">
-<h3><a name="iddiv2x1x2664" id="iddiv2x1x2664"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x2668" id="iddiv2x1x2668"/>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>
@@ -1759,7 +1759,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="iddiv2x1x2703" id="iddiv2x1x2703"/>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="iddiv2x1x2707" id="iddiv2x1x2707"/>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 Tuesday, 8 February 2011 00:57:18 UTC