- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 31 Dec 2010 13:57:33 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv3397
Modified Files:
scenario.html scenario.xml
Log Message:
add some mex tests
Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- scenario.xml 20 Dec 2010 18:14:56 -0000 1.7
+++ scenario.xml 31 Dec 2010 13:57:31 -0000 1.8
@@ -473,7 +473,8 @@
</item>
<item>
<p>
- A sequence diagram that illustrates the sequence of events in the test.
+ An optional sequence diagram that illustrates the sequence of
+ events in the test.
</p>
</item>
<item>
@@ -501,7 +502,7 @@
</p>
<div2 tocStop='true'>
- <head>GetWSDL Tests</head>
+ <head>GetWSDL Test</head>
<p>
This test verifies the ability to retrieve the WSDL associated with
@@ -546,10 +547,13 @@
</div2>
<div2 tocStop='true'>
- <head>xxx Tests</head>
+ <head>Empty GetMetadata Test</head>
<p>
- This test ....
+ This test verifies the ability to retrieve Metadata using the
+ GetMetadata operation. In this test the GetMetadata request will
+ not contain any child elements. In other words, the client is asking
+ for all available metadata to be returned.
</p>
<div3>
@@ -566,7 +570,12 @@
<ulist>
<item>
<p>
- ...
+ Receipt of a valid (empty) GetMetadata message by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid GetMetadataResponse message by the client.
</p>
</item>
</ulist>
@@ -576,9 +585,247 @@
<head>Conformance</head>
<p>
+ A conforming service MUST respond to the GetMetadata request with
+ a GetMetadataResponse message. The exact Metadata returned, if any,
+ and the content form of the Metadata will vary depending on the
+ availble metadata from the service. At a minimum it is expected
+ that the WSDL of the service MUST be returned.
+ </p>
+ </div3>
+ </div2>
+
+ <div2 tocStop='true'>
+ <head>WSDL GetMetadata Test</head>
+
+ <p>
+ This test verifies the ability to retrieve Metadata using the
+ GetMetadata operation. In this test the client will specifically
+ ask for the WSDL of the service.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <p>
...
</p>
</div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid GetMetadata message, requesting the WSDL,
+ by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid GetMetadataResponse message, containing the
+ WSDL, by the client.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <p>
+ A conforming service MUST respond to the GetMetadata request with
+ a GetMetadataResponse message. The response message MUST contain
+ the WSDL of the service.
+ </p>
+ </div3>
+ </div2>
+
+ <div2 tocStop='true'>
+ <head>Unknown GetMetadata Test</head>
+
+ <p>
+ This test verifies the ability ask for unknown Metadata using the
+ GetMetadata operation. In this test the client will specifically
+ ask for an unknown Metadata type and the service is expected to
+ ignore the request.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <p>
+ ...
+ </p>
+ </div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid GetMetadata message, requesting an unknown Metadata
+ type, by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid GetMetadataResponse message, containing the
+ no Metadata, by the client.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <p>
+ A conforming service MUST respond to the GetMetadata request with
+ a GetMetadataResponse message. The response message MUST contain
+ zero MetadataSection elements.
+ </p>
+ </div3>
+ </div2>
+
+ <div2 tocStop='true'>
+ <head>MultiMetadata GetMetadata Test</head>
+
+ <p>
+ This test verifies the ability ask for multiple types of Metadata at the
+ same time using the GetMetadata operation. In this test the client
+ will specifically ask for multiple types of Metadata (both known and
+ unknown types) and the service is expected to process each type
+ appropriately.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <p>
+ ...
+ </p>
+ </div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid GetMetadata message by the service. The request
+ MUST contain more than one mex:Dialect child element, and MUST
+ contain at least one known and one unknown Metadata Type request.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid GetMetadataResponse message by the client.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <p>
+ A conforming service MUST respond to the GetMetadata request with
+ a GetMetadataResponse message. The response MUST contain the appropriate
+ MetadataSections based on the request.
+ </p>
+ </div3>
+ </div2>
+
+ <div2 tocStop='true'>
+ <head>PutMetadata Test</head>
+
+ <p>
+ This test verifies the ability to update Metadata using the
+ PutMetadata operation.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <p>
+ ...
+ </p>
+ </div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid PutMetadata message by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid PutMetadataResponse message by the client.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <p>
+ A conforming service MUST respond to the PutMetadata request with
+ a PutMetadataResponse message. Each service will decide with type
+ of Metadata it will allow clients to update, as will as the content
+ form.
+ </p>
+ </div3>
+ </div2>
+
+
+ <div2 tocStop='true'>
+ <head>DeleteMetadata Test</head>
+
+ <p>
+ This test verifies the ability to update Metadata using the
+ DeleteMetadata operation.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <p>
+ ...
+ </p>
+ </div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid DeleteMetadata message by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid DeleteMetadataResponse message by the client.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <p>
+ A conforming service MUST respond to the DeleteMetadata request with
+ a DeleteMetadataResponse message. Each service will decide with type
+ of Metadata it will allow clients to delete.
+ </p>
+ </div3>
</div2>
</div1>
@@ -1612,7 +1859,7 @@
</p>
<div2 tocStop='true'>
- <head>xxx Tests</head>
+ <head>xxx Test</head>
<p>
This test ....
@@ -1657,7 +1904,7 @@
</p>
<div2 tocStop='true'>
- <head>xxx Tests</head>
+ <head>xxx Test</head>
<p>
This test ....
Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- scenario.html 20 Dec 2010 18:14:56 -0000 1.7
+++ scenario.html 31 Dec 2010 13:57:31 -0000 1.8
@@ -54,31 +54,36 @@
3.3 <a href="#iddiv2x1x662">Event Timing</a><br/>
3.4 <a href="#iddiv2x1x667">Structure of Test Sections</a><br/>
4 <a href="#iddiv1x1x685">WS-MetadataExchange Tests</a><br/>
- 4.1 <a href="#iddiv2x1x690">GetWSDL Tests</a><br/>
- 4.2 <a href="#iddiv2x1x716">xxx Tests</a><br/>
+ 4.1 <a href="#iddiv2x1x690">GetWSDL Test</a><br/>
+ 4.2 <a href="#iddiv2x1x716">Empty GetMetadata Test</a><br/>
+ 4.3 <a href="#iddiv2x1x742">WSDL GetMetadata Test</a><br/>
+ 4.4 <a href="#iddiv2x1x768">Unknown GetMetadata Test</a><br/>
+ 4.5 <a href="#iddiv2x1x794">MultiMetadata GetMetadata Test</a><br/>
+ 4.6 <a href="#iddiv2x1x820">PutMetadata Test</a><br/>
+ 4.7 <a href="#iddiv2x1x846">DeleteMetadata Test</a><br/>
5 <a href="#wsevt-tests">WS-Eventing Tests</a><br/>
- 5.1 <a href="#iddiv2x1x745">Basic Test</a><br/>
- 5.2 <a href="#iddiv2x1x802">Wrapped Notifications</a><br/>
- 5.3 <a href="#iddiv2x1x854">Duration Expiration Test</a><br/>
- 5.4 <a href="#iddiv2x1x909">Specific Time Expiration Test</a><br/>
- 5.5 <a href="#iddiv2x1x961">Best Effort Expiration Test</a><br/>
- 5.6 <a href="#iddiv2x1x1013">Renew Test</a><br/>
- 5.7 <a href="#iddiv2x1x1083">SubscriptionEnd Test</a><br/>
- 5.8 <a href="#iddiv2x1x1137">Filter Test - XPath 1.0</a><br/>
- 5.9 <a href="#iddiv2x1x1189">Filter Test - XPath 2.0</a><br/>
- 5.10 <a href="#iddiv2x1x1241">Non-Addressable Event Sink Test</a><br/>
-6 <a href="#iddiv1x1x1305">WS-Transfer/WS-Fragment Tests</a><br/>
- 6.1 <a href="#iddiv2x1x1310">xxx Tests</a><br/>
-7 <a href="#iddiv1x1x1333">WS-Enumeration Tests</a><br/>
- 7.1 <a href="#iddiv2x1x1338">xxx Tests</a><br/>
+ 5.1 <a href="#iddiv2x1x878">Basic Test</a><br/>
+ 5.2 <a href="#iddiv2x1x935">Wrapped Notifications</a><br/>
+ 5.3 <a href="#iddiv2x1x987">Duration Expiration Test</a><br/>
+ 5.4 <a href="#iddiv2x1x1042">Specific Time Expiration Test</a><br/>
+ 5.5 <a href="#iddiv2x1x1094">Best Effort Expiration Test</a><br/>
+ 5.6 <a href="#iddiv2x1x1146">Renew Test</a><br/>
+ 5.7 <a href="#iddiv2x1x1216">SubscriptionEnd Test</a><br/>
+ 5.8 <a href="#iddiv2x1x1270">Filter Test - XPath 1.0</a><br/>
+ 5.9 <a href="#iddiv2x1x1322">Filter Test - XPath 2.0</a><br/>
+ 5.10 <a href="#iddiv2x1x1374">Non-Addressable Event Sink Test</a><br/>
+6 <a href="#iddiv1x1x1438">WS-Transfer/WS-Fragment Tests</a><br/>
+ 6.1 <a href="#iddiv2x1x1443">xxx Test</a><br/>
+7 <a href="#iddiv1x1x1466">WS-Enumeration Tests</a><br/>
+ 7.1 <a href="#iddiv2x1x1471">xxx Test</a><br/>
8 <a href="#wsdl">WSDL</a><br/>
- 8.1 <a href="#iddiv2x1x1365">Event Source WSDL</a><br/>
- 8.2 <a href="#iddiv2x1x1370">Notification WSDL</a><br/>
+ 8.1 <a href="#iddiv2x1x1498">Event Source WSDL</a><br/>
+ 8.2 <a href="#iddiv2x1x1503">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="#iddiv2x1x1397">Normative References</a><br/>
+ 12.1 <a href="#iddiv2x1x1530">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/>
@@ -203,7 +208,8 @@
An overview that describes the purpose of the test and the
salient features of the messages that are exchanged.
</p></li><li><p>
- A sequence diagram that illustrates the sequence of events in the test.
+ An optional sequence diagram that illustrates the sequence of
+ events in the test.
</p></li><li><p>
A list of criteria used to judge the success of the test.
</p></li><li><p>
@@ -214,7 +220,7 @@
<h2><a name="iddiv1x1x685" id="iddiv1x1x685"/>4 WS-MetadataExchange Tests</h2><p>
...
</p><div class="div2">
-<h3><a name="iddiv2x1x690" id="iddiv2x1x690"/>4.1 GetWSDL Tests</h3><p>
+<h3><a name="iddiv2x1x690" id="iddiv2x1x690"/>4.1 GetWSDL Test</h3><p>
This test verifies the ability to retrieve the WSDL associated with
a WS-MetadataExchange compliant service.
</p><div class="div3">
@@ -232,17 +238,124 @@
WSDL of the service or no child elements at all as children of
the GetWSDLResponse element.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x716" id="iddiv2x1x716"/>4.2 xxx Tests</h3><p>
- This test ....
+<h3><a name="iddiv2x1x716" id="iddiv2x1x716"/>4.2 Empty GetMetadata Test</h3><p>
+ This test verifies the ability to retrieve Metadata using the
+ GetMetadata operation. In this test the GetMetadata request will
+ not contain any child elements. In other words, the client is asking
+ for all available metadata to be returned.
</p><div class="div3">
<h4><a name="iddiv3x1x722" id="iddiv3x1x722"/>4.2.1 Sequence</h4><p>
...
</p></div><div class="div3">
<h4><a name="iddiv3x1x727" id="iddiv3x1x727"/>4.2.2 Success Criteria</h4><ul><li><p>
- ...
+ Receipt of a valid (empty) GetMetadata message by the service.
+ </p></li><li><p>
+ Receipt of a valid GetMetadataResponse message by the client.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x734" id="iddiv3x1x734"/>4.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x737" id="iddiv3x1x737"/>4.2.3 Conformance</h4><p>
+ A conforming service MUST respond to the GetMetadata request with
+ a GetMetadataResponse message. The exact Metadata returned, if any,
+ and the content form of the Metadata will vary depending on the
+ availble metadata from the service. At a minimum it is expected
+ that the WSDL of the service MUST be returned.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x742" id="iddiv2x1x742"/>4.3 WSDL GetMetadata Test</h3><p>
+ This test verifies the ability to retrieve Metadata using the
+ GetMetadata operation. In this test the client will specifically
+ ask for the WSDL of the service.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x748" id="iddiv3x1x748"/>4.3.1 Sequence</h4><p>
+ ...
+ </p></div><div class="div3">
+<h4><a name="iddiv3x1x753" id="iddiv3x1x753"/>4.3.2 Success Criteria</h4><ul><li><p>
+ Receipt of a valid GetMetadata message, requesting the WSDL,
+ by the service.
+ </p></li><li><p>
+ Receipt of a valid GetMetadataResponse message, containing the
+ WSDL, by the client.
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x763" id="iddiv3x1x763"/>4.3.3 Conformance</h4><p>
+ A conforming service MUST respond to the GetMetadata request with
+ a GetMetadataResponse message. The response message MUST contain
+ the WSDL of the service.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x768" id="iddiv2x1x768"/>4.4 Unknown GetMetadata Test</h3><p>
+ This test verifies the ability ask for unknown Metadata using the
+ GetMetadata operation. In this test the client will specifically
+ ask for an unknown Metadata type and the service is expected to
+ ignore the request.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x774" id="iddiv3x1x774"/>4.4.1 Sequence</h4><p>
...
+ </p></div><div class="div3">
+<h4><a name="iddiv3x1x779" id="iddiv3x1x779"/>4.4.2 Success Criteria</h4><ul><li><p>
+ Receipt of a valid GetMetadata message, requesting an unknown Metadata
+ type, by the service.
+ </p></li><li><p>
+ Receipt of a valid GetMetadataResponse message, containing the
+ no Metadata, by the client.
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x789" id="iddiv3x1x789"/>4.4.3 Conformance</h4><p>
+ A conforming service MUST respond to the GetMetadata request with
+ a GetMetadataResponse message. The response message MUST contain
+ zero MetadataSection elements.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x794" id="iddiv2x1x794"/>4.5 MultiMetadata GetMetadata Test</h3><p>
+ This test verifies the ability ask for multiple types of Metadata at the
+ same time using the GetMetadata operation. In this test the client
+ will specifically ask for multiple types of Metadata (both known and
+ unknown types) and the service is expected to process each type
+ appropriately.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x800" id="iddiv3x1x800"/>4.5.1 Sequence</h4><p>
+ ...
+ </p></div><div class="div3">
+<h4><a name="iddiv3x1x805" id="iddiv3x1x805"/>4.5.2 Success Criteria</h4><ul><li><p>
+ Receipt of a valid GetMetadata message by the service. The request
+ MUST contain more than one mex:Dialect child element, and MUST
+ contain at least one known and one unknown Metadata Type request.
+ </p></li><li><p>
+ Receipt of a valid GetMetadataResponse message by the client.
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x815" id="iddiv3x1x815"/>4.5.3 Conformance</h4><p>
+ A conforming service MUST respond to the GetMetadata request with
+ a GetMetadataResponse message. The response MUST contain the appropriate
+ MetadataSections based on the request.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x820" id="iddiv2x1x820"/>4.6 PutMetadata Test</h3><p>
+ This test verifies the ability to update Metadata using the
+ PutMetadata operation.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x826" id="iddiv3x1x826"/>4.6.1 Sequence</h4><p>
+ ...
+ </p></div><div class="div3">
+<h4><a name="iddiv3x1x831" id="iddiv3x1x831"/>4.6.2 Success Criteria</h4><ul><li><p>
+ Receipt of a valid PutMetadata message by the service.
+ </p></li><li><p>
+ Receipt of a valid PutMetadataResponse message by the client.
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x841" id="iddiv3x1x841"/>4.6.3 Conformance</h4><p>
+ A conforming service MUST respond to the PutMetadata request with
+ a PutMetadataResponse message. Each service will decide with type
+ of Metadata it will allow clients to update, as will as the content
+ form.
+ </p></div></div><div class="div2">
+<h3><a name="iddiv2x1x846" id="iddiv2x1x846"/>4.7 DeleteMetadata Test</h3><p>
+ This test verifies the ability to update Metadata using the
+ DeleteMetadata operation.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x852" id="iddiv3x1x852"/>4.7.1 Sequence</h4><p>
+ ...
+ </p></div><div class="div3">
+<h4><a name="iddiv3x1x857" id="iddiv3x1x857"/>4.7.2 Success Criteria</h4><ul><li><p>
+ Receipt of a valid DeleteMetadata message by the service.
+ </p></li><li><p>
+ Receipt of a valid DeleteMetadataResponse message by the client.
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x867" id="iddiv3x1x867"/>4.7.3 Conformance</h4><p>
+ A conforming service MUST respond to the DeleteMetadata request with
+ a DeleteMetadataResponse message. Each service will decide with type
+ of Metadata it will allow clients to delete.
</p></div></div></div><div class="div1">
<h2><a name="wsevt-tests" id="wsevt-tests"/>5 WS-Eventing Tests</h2><p>
This section describes the tests for WS-Eventing except for those
@@ -250,15 +363,15 @@
affect only the process of developing one or more of the components
of a WS-Eventing-based system.
</p><div class="div2">
-<h3><a name="iddiv2x1x745" id="iddiv2x1x745"/>5.1 Basic Test</h3><p>
+<h3><a name="iddiv2x1x878" id="iddiv2x1x878"/>5.1 Basic Test</h3><p>
This test verifies the ability to subscribe and receive notifications.
The initial Subscribe request has the following features:
</p><ul><li><p>expiration time chose by Event Source/Subscription Manager</p></li><li><p>no EndTo EPR</p></li><li><p>no Filters</p></li><li><p>unwrapped notifications</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x764" id="iddiv3x1x764"/>5.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x897" id="iddiv3x1x897"/>5.1.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for the
Basic Test.
</p><img src="images/basic_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x774" id="iddiv3x1x774"/>5.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x907" id="iddiv3x1x907"/>5.1.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.
@@ -269,7 +382,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x793" id="iddiv3x1x793"/>5.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x926" id="iddiv3x1x926"/>5.1.3 Conformance</h4><p>
Because this test involves only operations and elements that are
required, there are no allowable failure cases.
</p><p>
@@ -280,16 +393,16 @@
An implementation that is unable to support this test does not
conform to WS-Eventing.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x802" id="iddiv2x1x802"/>5.2 Wrapped Notifications</h3><p>
+<h3><a name="iddiv2x1x935" id="iddiv2x1x935"/>5.2 Wrapped Notifications</h3><p>
This test verifies the simple ability to subscribe and receive
wrapped notifications. The initial Subscribe request has the
following features:
</p><ul><li><p>expiration time chosen by Event Source/Subscription Manager</p></li><li><p>no EndTo EPR</p></li><li><p>no Filters</p></li><li><p>wrapped notifications</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x821" id="iddiv3x1x821"/>5.2.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x954" id="iddiv3x1x954"/>5.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="iddiv3x1x826" id="iddiv3x1x826"/>5.2.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x959" id="iddiv3x1x959"/>5.2.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.
@@ -300,7 +413,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x845" id="iddiv3x1x845"/>5.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x978" id="iddiv3x1x978"/>5.2.3 Conformance</h4><p>
Because this test involves the use of the optional wrapped delivery
format, there are a number of failure cases that fall within the
boundaries of conforming behavior.
@@ -311,7 +424,7 @@
A conforming Event Source MAY respond to the initial Subscribe
request with a wse:DeliveryFormatRequestUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x854" id="iddiv2x1x854"/>5.3 Duration Expiration Test</h3><p>
+<h3><a name="iddiv2x1x987" id="iddiv2x1x987"/>5.3 Duration Expiration Test</h3><p>
This test verifies the correct implementation of the expiration feature
on the Event Source/Subscription Manager. The initial Subscribe message
has the following features:
@@ -324,12 +437,12 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x873" id="iddiv3x1x873"/>5.3.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1006" id="iddiv3x1x1006"/>5.3.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for the
Duration Expiration Test. Note that the Subscriber waits until the
expiration time has passed before sending the GetStatus request.
</p><img src="images/duration_expiration_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x883" id="iddiv3x1x883"/>5.3.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1016" id="iddiv3x1x1016"/>5.3.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.
@@ -344,7 +457,7 @@
HTTP error (i.e. '404') that indicates the Subscription Manager no
longer exists
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x902" id="iddiv3x1x902"/>5.3.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1035" id="iddiv3x1x1035"/>5.3.3 Conformance</h4><p>
Because this test involves the use of the optional wse:Expires
element, a conforming Subscriber MAY NOT be capable of implementing
this test due to its inability to support wse:Expires.
@@ -355,7 +468,7 @@
be unable to implement this test or to fail to meet one of the
defined success criteria.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x909" id="iddiv2x1x909"/>5.4 Specific Time Expiration Test</h3><p>
+<h3><a name="iddiv2x1x1042" id="iddiv2x1x1042"/>5.4 Specific Time Expiration Test</h3><p>
This test verifies the correct implementation of the expiration feature
on the Event Source/Subscription Manager. The initial Subscribe
request has the following features:
@@ -368,11 +481,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x928" id="iddiv3x1x928"/>5.4.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1061" id="iddiv3x1x1061"/>5.4.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="iddiv3x1x933" id="iddiv3x1x933"/>5.4.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1066" id="iddiv3x1x1066"/>5.4.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.
@@ -387,7 +500,7 @@
an HTTP error (i.e. '404') that indicates the Subscription
Manager no longer exists.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x952" id="iddiv3x1x952"/>5.4.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1085" id="iddiv3x1x1085"/>5.4.3 Conformance</h4><p>
Because this test involves the use of both the optional wse:Expires
element and the optional xs:dateTime type, there are a number of
failure cases that fall within the boundaries of conforming behavior.
@@ -399,7 +512,7 @@
A conforming Event Source MAY respond to the initial Subscribe
request with a wse:UnsupportedExpirationType fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x961" id="iddiv2x1x961"/>5.5 Best Effort Expiration Test</h3><p>
+<h3><a name="iddiv2x1x1094" id="iddiv2x1x1094"/>5.5 Best Effort Expiration Test</h3><p>
This test verifies the correct implementation of the 'best effort'
expiration feature on the Event Source/Subscription Manager. The
initial subscription has the following features:
@@ -413,11 +526,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x980" id="iddiv3x1x980"/>5.5.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1113" id="iddiv3x1x1113"/>5.5.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="iddiv3x1x985" id="iddiv3x1x985"/>5.5.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1118" id="iddiv3x1x1118"/>5.5.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.
@@ -432,7 +545,7 @@
HTTP error (i.e. '404') that indicates the Subscription Manager
no longer exists.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1004" id="iddiv3x1x1004"/>5.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1137" id="iddiv3x1x1137"/>5.5.3 Conformance</h4><p>
Because this test involves the use of both the optional wse:Expires
element and the optional BestEffort attribute, there are a
number of failure cases that fall within the boundaries of
@@ -448,7 +561,7 @@
implement this test or to fail to meet one of the defined
success criteria.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1013" id="iddiv2x1x1013"/>5.6 Renew Test</h3><p>
+<h3><a name="iddiv2x1x1146" id="iddiv2x1x1146"/>5.6 Renew Test</h3><p>
This test verifies the ability of a Subscriber to update the
expiration time of a Subscription via a Renew request. The initial
Subscribe request has the following features:
@@ -465,11 +578,11 @@
</p><ul><li><p>
(short) expiration time chosen by Subscriber as xs:duration
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1038" id="iddiv3x1x1038"/>5.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1171" id="iddiv3x1x1171"/>5.6.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for
the Renew Test.
</p><img src="images/renew_test.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x1048" id="iddiv3x1x1048"/>5.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1181" id="iddiv3x1x1181"/>5.6.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.
@@ -488,7 +601,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1076" id="iddiv3x1x1076"/>5.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1209" id="iddiv3x1x1209"/>5.6.3 Conformance</h4><p>
Because this test involves the use of the optional wse:Expires element,
a conforming Subscriber MAY NOT be capable of implementing this test
due to its inability to support wse:Expires.
@@ -499,7 +612,7 @@
to implement this test or to fail to meet one of the defined
success criteria.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1083" id="iddiv2x1x1083"/>5.7 SubscriptionEnd Test</h3><p>
+<h3><a name="iddiv2x1x1216" id="iddiv2x1x1216"/>5.7 SubscriptionEnd Test</h3><p>
This test verifies the correct implementation of the SubscriptionEnd
feature for both the Subscription Manager and the target of the
SubscriptionEnd message. The initial Subscribe request has the
@@ -513,11 +626,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1102" id="iddiv3x1x1102"/>5.7.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1235" id="iddiv3x1x1235"/>5.7.1 Sequence</h4><p>
The following diagram illustrates the sequence of messages for the
SubscriptionEnd Test.
</p><img src="images/subscriptionend.jpg"/></div><div class="div3">
-<h4><a name="iddiv3x1x1112" id="iddiv3x1x1112"/>5.7.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1245" id="iddiv3x1x1245"/>5.7.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 the Subscriber.
@@ -527,7 +640,7 @@
Receipt of a valid SubscriptionEnd message by the Subscriber
(or whomever is indicated by the EndTo EPR).
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1128" id="iddiv3x1x1128"/>5.7.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1261" id="iddiv3x1x1261"/>5.7.3 Conformance</h4><p>
Because this test involves the use of the optional wse:EndTo
element there are a number of failure cases that fall within the
boundaries of conforming behavior.
@@ -539,7 +652,7 @@
A conforming Event Source MAY respond to the initial Subscribe
request with a wse:EndToNotSupported fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1137" id="iddiv2x1x1137"/>5.8 Filter Test - XPath 1.0</h3><p>
+<h3><a name="iddiv2x1x1270" id="iddiv2x1x1270"/>5.8 Filter Test - XPath 1.0</h3><p>
This test verifies the ability of the Event Source/Subscription Manager
to correctly implement XPath 1.0 filters. The initial Subscribe
request has the following features:
@@ -555,13 +668,13 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1156" id="iddiv3x1x1156"/>5.8.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1289" id="iddiv3x1x1289"/>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.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1161" id="iddiv3x1x1161"/>5.8.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1294" id="iddiv3x1x1294"/>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.
@@ -573,7 +686,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1180" id="iddiv3x1x1180"/>5.8.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1313" id="iddiv3x1x1313"/>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.
@@ -586,7 +699,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1189" id="iddiv2x1x1189"/>5.9 Filter Test - XPath 2.0</h3><p>
+<h3><a name="iddiv2x1x1322" id="iddiv2x1x1322"/>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:
@@ -602,13 +715,13 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1208" id="iddiv3x1x1208"/>5.9.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1341" id="iddiv3x1x1341"/>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.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1213" id="iddiv3x1x1213"/>5.9.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1346" id="iddiv3x1x1346"/>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.
@@ -620,7 +733,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1232" id="iddiv3x1x1232"/>5.9.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1365" id="iddiv3x1x1365"/>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.
@@ -633,7 +746,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1241" id="iddiv2x1x1241"/>5.10 Non-Addressable Event Sink Test</h3><p>
+<h3><a name="iddiv2x1x1374" id="iddiv2x1x1374"/>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
@@ -654,7 +767,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="iddiv3x1x1265" id="iddiv3x1x1265"/>5.11 Sequence</h4><p>
+<h4><a name="iddiv3x1x1398" id="iddiv3x1x1398"/>5.11 Sequence</h4><p>
The following diagram illustrates the sequence of messages for the
Non-Addressable Event Sink Test.
</p><img src="images/non_addressable_event_sink.jpg"/><p>
@@ -663,7 +776,7 @@
SubscribeResponse and UnsubscribeResponse are both transmitted on
the back-channel of their corresponding requests.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1277" id="iddiv3x1x1277"/>5.12 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1410" id="iddiv3x1x1410"/>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.
@@ -695,41 +808,41 @@
elicit a wsa:ActionNotSupported fault response or some other,
unspecified behavior.
</p></div></div><div class="div1">
-<h2><a name="iddiv1x1x1305" id="iddiv1x1x1305"/>6 WS-Transfer/WS-Fragment Tests</h2><p>
+<h2><a name="iddiv1x1x1438" id="iddiv1x1x1438"/>6 WS-Transfer/WS-Fragment Tests</h2><p>
...
</p><div class="div2">
-<h3><a name="iddiv2x1x1310" id="iddiv2x1x1310"/>6.1 xxx Tests</h3><p>
+<h3><a name="iddiv2x1x1443" id="iddiv2x1x1443"/>6.1 xxx Test</h3><p>
This test ....
</p><div class="div3">
-<h4><a name="iddiv3x1x1316" id="iddiv3x1x1316"/>6.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1449" id="iddiv3x1x1449"/>6.1.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1321" id="iddiv3x1x1321"/>6.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1454" id="iddiv3x1x1454"/>6.1.2 Success Criteria</h4><ul><li><p>
...
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1328" id="iddiv3x1x1328"/>6.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1461" id="iddiv3x1x1461"/>6.1.3 Conformance</h4><p>
...
</p></div></div></div><div class="div1">
-<h2><a name="iddiv1x1x1333" id="iddiv1x1x1333"/>7 WS-Enumeration Tests</h2><p>
+<h2><a name="iddiv1x1x1466" id="iddiv1x1x1466"/>7 WS-Enumeration Tests</h2><p>
...
</p><div class="div2">
-<h3><a name="iddiv2x1x1338" id="iddiv2x1x1338"/>7.1 xxx Tests</h3><p>
+<h3><a name="iddiv2x1x1471" id="iddiv2x1x1471"/>7.1 xxx Test</h3><p>
This test ....
</p><div class="div3">
-<h4><a name="iddiv3x1x1344" id="iddiv3x1x1344"/>7.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1477" id="iddiv3x1x1477"/>7.1.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1349" id="iddiv3x1x1349"/>7.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1482" id="iddiv3x1x1482"/>7.1.2 Success Criteria</h4><ul><li><p>
...
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1356" id="iddiv3x1x1356"/>7.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1489" id="iddiv3x1x1489"/>7.1.3 Conformance</h4><p>
...
</p></div></div></div><div class="div1">
<h2><a name="wsdl" id="wsdl"/>8 WSDL</h2><div class="div2">
-<h3><a name="iddiv2x1x1365" id="iddiv2x1x1365"/>8.1 Event Source WSDL</h3><p>
+<h3><a name="iddiv2x1x1498" id="iddiv2x1x1498"/>8.1 Event Source WSDL</h3><p>
TBD
</p></div><div class="div2">
-<h3><a name="iddiv2x1x1370" id="iddiv2x1x1370"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x1503" id="iddiv2x1x1503"/>8.2 Notification WSDL</h3><p>
TBD
</p></div></div><div class="div1">
<h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
@@ -769,7 +882,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="iddiv2x1x1397" id="iddiv2x1x1397"/>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="iddiv2x1x1530" id="iddiv2x1x1530"/>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 Friday, 31 December 2010 13:57:36 UTC