- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Sun, 09 Jan 2011 16:41:10 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv21871
Modified Files:
scenario.html scenario.xml
Log Message:
add a history section to the animal so we can test attribute and arrays
Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- scenario.xml 7 Jan 2011 16:57:39 -0000 1.12
+++ scenario.xml 9 Jan 2011 16:41:08 -0000 1.13
@@ -379,6 +379,9 @@
<sce:Species> <emph>xs:string</emph> </sce:Species>
<sce:CurrentLocation> <emph>xs:any</emph> </sce:CurrentLocation>
<sce:EPR> <emph>wsa:endpoint-reference to this Animal</emph> </sce:EPR> ?
+ <sce:History>
+ <sce:Entry Date="<emph>xs:date</emph>"? ...> <emph>xs:string</emph> <sce:/Entry> *
+ <sce:/History> ?
<emph>xs:any</emph>
</sce:Animal> </eg>
</example>
@@ -2517,6 +2520,15 @@
SubscriptionEnd Test, and Non-Addressable Event Sink Test.
</td>
</tr>
+ <tr>
+ <td> 2011/01/09 </td>
+ <td> DD </td>
+ <td>
+ Add a history section to each animal so we can track medical
+ history or just make notes about the animal. Really, we need
+ an array and something with an attribute to test frag stuf
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- scenario.html 7 Jan 2011 16:57:39 -0000 1.12
+++ scenario.html 9 Jan 2011 16:41:08 -0000 1.13
@@ -49,46 +49,46 @@
2 <a href="#notterms">Notations and Terminology</a><br/>
2.1 <a href="#conventions">Notational Conventions</a><br/>
3 <a href="#description">Scenario Description</a><br/>
- 3.1 <a href="#iddiv2x1x599">Predefined Animals/Tags</a><br/>
+ 3.1 <a href="#iddiv2x1x605">Predefined Animals/Tags</a><br/>
3.2 <a href="#evt_description">Event Description</a><br/>
- 3.3 <a href="#iddiv2x1x662">Event Timing</a><br/>
- 3.4 <a href="#iddiv2x1x669">Structure of Test Sections</a><br/>
-4 <a href="#iddiv1x1x687">WS-MetadataExchange Tests</a><br/>
- 4.1 <a href="#iddiv2x1x692">GetWSDL Test</a><br/>
- 4.2 <a href="#iddiv2x1x718">Empty GetMetadata Test</a><br/>
- 4.3 <a href="#iddiv2x1x744">WSDL GetMetadata Test</a><br/>
- 4.4 <a href="#iddiv2x1x770">Unknown GetMetadata Test</a><br/>
- 4.5 <a href="#iddiv2x1x796">MultiMetadata GetMetadata Test</a><br/>
- 4.6 <a href="#iddiv2x1x822">PutMetadata Test</a><br/>
- 4.7 <a href="#iddiv2x1x848">DeleteMetadata Test</a><br/>
+ 3.3 <a href="#iddiv2x1x668">Event Timing</a><br/>
+ 3.4 <a href="#iddiv2x1x675">Structure of Test Sections</a><br/>
+4 <a href="#iddiv1x1x693">WS-MetadataExchange Tests</a><br/>
+ 4.1 <a href="#iddiv2x1x698">GetWSDL Test</a><br/>
+ 4.2 <a href="#iddiv2x1x724">Empty GetMetadata Test</a><br/>
+ 4.3 <a href="#iddiv2x1x750">WSDL GetMetadata Test</a><br/>
+ 4.4 <a href="#iddiv2x1x776">Unknown GetMetadata Test</a><br/>
+ 4.5 <a href="#iddiv2x1x802">MultiMetadata GetMetadata Test</a><br/>
+ 4.6 <a href="#iddiv2x1x828">PutMetadata Test</a><br/>
+ 4.7 <a href="#iddiv2x1x854">DeleteMetadata Test</a><br/>
5 <a href="#wsevt-tests">WS-Eventing Tests</a><br/>
- 5.1 <a href="#iddiv2x1x880">Basic Test</a><br/>
- 5.2 <a href="#iddiv2x1x937">Wrapped Notifications</a><br/>
- 5.3 <a href="#iddiv2x1x989">Duration Expiration Test</a><br/>
- 5.4 <a href="#iddiv2x1x1044">Specific Time Expiration Test</a><br/>
- 5.5 <a href="#iddiv2x1x1096">Best Effort Expiration Test</a><br/>
- 5.6 <a href="#iddiv2x1x1148">Renew Test</a><br/>
- 5.7 <a href="#iddiv2x1x1218">SubscriptionEnd Test</a><br/>
- 5.8 <a href="#iddiv2x1x1272">Filter Test - XPath 1.0</a><br/>
- 5.9 <a href="#iddiv2x1x1324">Filter Test - XPath 2.0</a><br/>
- 5.10 <a href="#iddiv2x1x1376">Non-Addressable Event Sink Test</a><br/>
-6 <a href="#iddiv1x1x1440">WS-Transfer/WS-Fragment Tests</a><br/>
- 6.1 <a href="#iddiv2x1x1445">Create Test</a><br/>
- 6.2 <a href="#iddiv2x1x1471">Get Test</a><br/>
- 6.3 <a href="#iddiv2x1x1497">Fragment Get Test</a><br/>
- 6.4 <a href="#iddiv2x1x1523">Put Test</a><br/>
- 6.5 <a href="#iddiv2x1x1549">Fragment Put Test</a><br/>
- 6.6 <a href="#iddiv2x1x1581">Delete Test</a><br/>
-7 <a href="#iddiv1x1x1607">WS-Enumeration Tests</a><br/>
- 7.1 <a href="#iddiv2x1x1612">xxx Test</a><br/>
+ 5.1 <a href="#iddiv2x1x886">Basic Test</a><br/>
+ 5.2 <a href="#iddiv2x1x943">Wrapped Notifications</a><br/>
+ 5.3 <a href="#iddiv2x1x995">Duration Expiration Test</a><br/>
+ 5.4 <a href="#iddiv2x1x1050">Specific Time Expiration Test</a><br/>
+ 5.5 <a href="#iddiv2x1x1102">Best Effort Expiration Test</a><br/>
+ 5.6 <a href="#iddiv2x1x1154">Renew Test</a><br/>
+ 5.7 <a href="#iddiv2x1x1224">SubscriptionEnd Test</a><br/>
+ 5.8 <a href="#iddiv2x1x1278">Filter Test - XPath 1.0</a><br/>
+ 5.9 <a href="#iddiv2x1x1330">Filter Test - XPath 2.0</a><br/>
+ 5.10 <a href="#iddiv2x1x1382">Non-Addressable Event Sink Test</a><br/>
+6 <a href="#iddiv1x1x1446">WS-Transfer/WS-Fragment Tests</a><br/>
+ 6.1 <a href="#iddiv2x1x1451">Create Test</a><br/>
+ 6.2 <a href="#iddiv2x1x1477">Get Test</a><br/>
+ 6.3 <a href="#iddiv2x1x1503">Fragment Get Test</a><br/>
+ 6.4 <a href="#iddiv2x1x1529">Put Test</a><br/>
+ 6.5 <a href="#iddiv2x1x1555">Fragment Put Test</a><br/>
+ 6.6 <a href="#iddiv2x1x1587">Delete Test</a><br/>
+7 <a href="#iddiv1x1x1613">WS-Enumeration Tests</a><br/>
+ 7.1 <a href="#iddiv2x1x1618">xxx Test</a><br/>
8 <a href="#wsdl">WSDL</a><br/>
- 8.1 <a href="#iddiv2x1x1639">Event Source WSDL</a><br/>
- 8.2 <a href="#iddiv2x1x1644">Notification WSDL</a><br/>
+ 8.1 <a href="#iddiv2x1x1645">Event Source WSDL</a><br/>
+ 8.2 <a href="#iddiv2x1x1650">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="#iddiv2x1x1671">Normative References</a><br/>
+ 12.1 <a href="#iddiv2x1x1677">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/>
@@ -161,9 +161,12 @@
<sce:Species> <em>xs:string</em> </sce:Species>
<sce:CurrentLocation> <em>xs:any</em> </sce:CurrentLocation>
<sce:EPR> <em>wsa:endpoint-reference to this Animal</em> </sce:EPR> ?
+ <sce:History>
+ <sce:Entry Date="<em>xs:date</em>"? ...> <em>xs:string</em> <sce:/Entry> *
+ <sce:/History> ?
<em>xs:any</em>
</sce:Animal> </pre></div></div><div class="div2">
-<h3><a name="iddiv2x1x599" id="iddiv2x1x599"/>3.1 Predefined Animals/Tags</h3><p>
+<h3><a name="iddiv2x1x605" id="iddiv2x1x605"/>3.1 Predefined Animals/Tags</h3><p>
At a minimum each service side implementation of this scenario
MUST initially have at least the following animals/tags:
</p><ul><li><p>
@@ -198,7 +201,7 @@
describes the structure of the event information within the
notifications can be found in <a href="#wsdl"><b>8 WSDL</b></a>.
</p></div><div class="div2">
-<h3><a name="iddiv2x1x662" id="iddiv2x1x662"/>3.3 Event Timing</h3><p>
+<h3><a name="iddiv2x1x668" id="iddiv2x1x668"/>3.3 Event Timing</h3><p>
While in the real world the frequency of notifications might be
hourly or even daily, for the sake of feasibility we compress time
by a scale of 1/120 so that one hour in 'scenario time' is thirty
@@ -211,7 +214,7 @@
any field other than the "Current Location" field). This will allow
for interested parties to be notified when the data is updated.
</p></div><div class="div2">
-<h3><a name="iddiv2x1x669" id="iddiv2x1x669"/>3.4 Structure of Test Sections</h3><p>
+<h3><a name="iddiv2x1x675" id="iddiv2x1x675"/>3.4 Structure of Test Sections</h3><p>
The following sections describe tests designed to exercise all the
mandatory and optional features of indicated specifications.
Each of these tests is organized into four parts:
@@ -228,144 +231,144 @@
conforming implementations are allowed to either not implement the
test or fail one or more of the success criteria.
</p></li></ul></div></div><div class="div1">
-<h2><a name="iddiv1x1x687" id="iddiv1x1x687"/>4 WS-MetadataExchange Tests</h2><p>
+<h2><a name="iddiv1x1x693" id="iddiv1x1x693"/>4 WS-MetadataExchange Tests</h2><p>
This sections describes the tests for WS-MetadataExchange. These tests
are focused on testing the protocol itself and not necessarily on the
metadata transported via the protocol.
</p><div class="div2">
-<h3><a name="iddiv2x1x692" id="iddiv2x1x692"/>4.1 GetWSDL Test</h3><p>
+<h3><a name="iddiv2x1x698" id="iddiv2x1x698"/>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">
-<h4><a name="iddiv3x1x698" id="iddiv3x1x698"/>4.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x704" id="iddiv3x1x704"/>4.1.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x703" id="iddiv3x1x703"/>4.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x709" id="iddiv3x1x709"/>4.1.2 Success Criteria</h4><ul><li><p>
Receipt of a valid GetWSDL message by the service.
</p></li><li><p>
Receipt of a valid GetWSDLResponse message by the client.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x713" id="iddiv3x1x713"/>4.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x719" id="iddiv3x1x719"/>4.1.3 Conformance</h4><p>
A conforming service MUST respond to the GetWSDL request with
a GetWSDLResponse message. However, it MAY either include the
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="iddiv2x1x718" id="iddiv2x1x718"/>4.2 Empty GetMetadata Test</h3><p>
+<h3><a name="iddiv2x1x724" id="iddiv2x1x724"/>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="iddiv3x1x724" id="iddiv3x1x724"/>4.2.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x730" id="iddiv3x1x730"/>4.2.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x729" id="iddiv3x1x729"/>4.2.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x735" id="iddiv3x1x735"/>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="iddiv3x1x739" id="iddiv3x1x739"/>4.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x745" id="iddiv3x1x745"/>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="iddiv2x1x744" id="iddiv2x1x744"/>4.3 WSDL GetMetadata Test</h3><p>
+<h3><a name="iddiv2x1x750" id="iddiv2x1x750"/>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="iddiv3x1x750" id="iddiv3x1x750"/>4.3.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x756" id="iddiv3x1x756"/>4.3.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x755" id="iddiv3x1x755"/>4.3.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x761" id="iddiv3x1x761"/>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="iddiv3x1x765" id="iddiv3x1x765"/>4.3.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x771" id="iddiv3x1x771"/>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="iddiv2x1x770" id="iddiv2x1x770"/>4.4 Unknown GetMetadata Test</h3><p>
+<h3><a name="iddiv2x1x776" id="iddiv2x1x776"/>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="iddiv3x1x776" id="iddiv3x1x776"/>4.4.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x782" id="iddiv3x1x782"/>4.4.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x781" id="iddiv3x1x781"/>4.4.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x787" id="iddiv3x1x787"/>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="iddiv3x1x791" id="iddiv3x1x791"/>4.4.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x797" id="iddiv3x1x797"/>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="iddiv2x1x796" id="iddiv2x1x796"/>4.5 MultiMetadata GetMetadata Test</h3><p>
+<h3><a name="iddiv2x1x802" id="iddiv2x1x802"/>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="iddiv3x1x802" id="iddiv3x1x802"/>4.5.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x808" id="iddiv3x1x808"/>4.5.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x807" id="iddiv3x1x807"/>4.5.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x813" id="iddiv3x1x813"/>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="iddiv3x1x817" id="iddiv3x1x817"/>4.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x823" id="iddiv3x1x823"/>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="iddiv2x1x822" id="iddiv2x1x822"/>4.6 PutMetadata Test</h3><p>
+<h3><a name="iddiv2x1x828" id="iddiv2x1x828"/>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="iddiv3x1x828" id="iddiv3x1x828"/>4.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x834" id="iddiv3x1x834"/>4.6.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x833" id="iddiv3x1x833"/>4.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x839" id="iddiv3x1x839"/>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="iddiv3x1x843" id="iddiv3x1x843"/>4.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x849" id="iddiv3x1x849"/>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="iddiv2x1x848" id="iddiv2x1x848"/>4.7 DeleteMetadata Test</h3><p>
+<h3><a name="iddiv2x1x854" id="iddiv2x1x854"/>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="iddiv3x1x854" id="iddiv3x1x854"/>4.7.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x860" id="iddiv3x1x860"/>4.7.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x859" id="iddiv3x1x859"/>4.7.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x865" id="iddiv3x1x865"/>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="iddiv3x1x869" id="iddiv3x1x869"/>4.7.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x875" id="iddiv3x1x875"/>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.
@@ -376,15 +379,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="iddiv2x1x880" id="iddiv2x1x880"/>5.1 Basic Test</h3><p>
+<h3><a name="iddiv2x1x886" id="iddiv2x1x886"/>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="iddiv3x1x899" id="iddiv3x1x899"/>5.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x905" id="iddiv3x1x905"/>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="iddiv3x1x909" id="iddiv3x1x909"/>5.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x915" id="iddiv3x1x915"/>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.
@@ -395,7 +398,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x928" id="iddiv3x1x928"/>5.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x934" id="iddiv3x1x934"/>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>
@@ -406,16 +409,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="iddiv2x1x937" id="iddiv2x1x937"/>5.2 Wrapped Notifications</h3><p>
+<h3><a name="iddiv2x1x943" id="iddiv2x1x943"/>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="iddiv3x1x956" id="iddiv3x1x956"/>5.2.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x962" id="iddiv3x1x962"/>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="iddiv3x1x961" id="iddiv3x1x961"/>5.2.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x967" id="iddiv3x1x967"/>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.
@@ -426,7 +429,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x980" id="iddiv3x1x980"/>5.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x986" id="iddiv3x1x986"/>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.
@@ -437,7 +440,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="iddiv2x1x989" id="iddiv2x1x989"/>5.3 Duration Expiration Test</h3><p>
+<h3><a name="iddiv2x1x995" id="iddiv2x1x995"/>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:
@@ -450,12 +453,12 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1008" id="iddiv3x1x1008"/>5.3.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1014" id="iddiv3x1x1014"/>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="iddiv3x1x1018" id="iddiv3x1x1018"/>5.3.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1024" id="iddiv3x1x1024"/>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.
@@ -470,7 +473,7 @@
HTTP error (i.e. '404') that indicates the Subscription Manager no
longer exists
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1037" id="iddiv3x1x1037"/>5.3.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1043" id="iddiv3x1x1043"/>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.
@@ -481,7 +484,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="iddiv2x1x1044" id="iddiv2x1x1044"/>5.4 Specific Time Expiration Test</h3><p>
+<h3><a name="iddiv2x1x1050" id="iddiv2x1x1050"/>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:
@@ -494,11 +497,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1063" id="iddiv3x1x1063"/>5.4.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1069" id="iddiv3x1x1069"/>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="iddiv3x1x1068" id="iddiv3x1x1068"/>5.4.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1074" id="iddiv3x1x1074"/>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.
@@ -513,7 +516,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="iddiv3x1x1087" id="iddiv3x1x1087"/>5.4.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1093" id="iddiv3x1x1093"/>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.
@@ -525,7 +528,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="iddiv2x1x1096" id="iddiv2x1x1096"/>5.5 Best Effort Expiration Test</h3><p>
+<h3><a name="iddiv2x1x1102" id="iddiv2x1x1102"/>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:
@@ -539,11 +542,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1115" id="iddiv3x1x1115"/>5.5.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1121" id="iddiv3x1x1121"/>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="iddiv3x1x1120" id="iddiv3x1x1120"/>5.5.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1126" id="iddiv3x1x1126"/>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.
@@ -558,7 +561,7 @@
HTTP error (i.e. '404') that indicates the Subscription Manager
no longer exists.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1139" id="iddiv3x1x1139"/>5.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1145" id="iddiv3x1x1145"/>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
@@ -574,7 +577,7 @@
implement this test or to fail to meet one of the defined
success criteria.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1148" id="iddiv2x1x1148"/>5.6 Renew Test</h3><p>
+<h3><a name="iddiv2x1x1154" id="iddiv2x1x1154"/>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:
@@ -591,11 +594,11 @@
</p><ul><li><p>
(short) expiration time chosen by Subscriber as xs:duration
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1173" id="iddiv3x1x1173"/>5.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1179" id="iddiv3x1x1179"/>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="iddiv3x1x1183" id="iddiv3x1x1183"/>5.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1189" id="iddiv3x1x1189"/>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.
@@ -614,7 +617,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1211" id="iddiv3x1x1211"/>5.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1217" id="iddiv3x1x1217"/>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.
@@ -625,7 +628,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="iddiv2x1x1218" id="iddiv2x1x1218"/>5.7 SubscriptionEnd Test</h3><p>
+<h3><a name="iddiv2x1x1224" id="iddiv2x1x1224"/>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
@@ -639,11 +642,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1237" id="iddiv3x1x1237"/>5.7.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1243" id="iddiv3x1x1243"/>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="iddiv3x1x1247" id="iddiv3x1x1247"/>5.7.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1253" id="iddiv3x1x1253"/>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.
@@ -653,7 +656,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="iddiv3x1x1263" id="iddiv3x1x1263"/>5.7.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1269" id="iddiv3x1x1269"/>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.
@@ -665,7 +668,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="iddiv2x1x1272" id="iddiv2x1x1272"/>5.8 Filter Test - XPath 1.0</h3><p>
+<h3><a name="iddiv2x1x1278" id="iddiv2x1x1278"/>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:
@@ -681,13 +684,13 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1291" id="iddiv3x1x1291"/>5.8.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1297" id="iddiv3x1x1297"/>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="iddiv3x1x1296" id="iddiv3x1x1296"/>5.8.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1302" id="iddiv3x1x1302"/>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.
@@ -699,7 +702,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1315" id="iddiv3x1x1315"/>5.8.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1321" id="iddiv3x1x1321"/>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.
@@ -712,7 +715,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1324" id="iddiv2x1x1324"/>5.9 Filter Test - XPath 2.0</h3><p>
+<h3><a name="iddiv2x1x1330" id="iddiv2x1x1330"/>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:
@@ -728,13 +731,13 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x1343" id="iddiv3x1x1343"/>5.9.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1349" id="iddiv3x1x1349"/>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="iddiv3x1x1348" id="iddiv3x1x1348"/>5.9.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1354" id="iddiv3x1x1354"/>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.
@@ -746,7 +749,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1367" id="iddiv3x1x1367"/>5.9.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1373" id="iddiv3x1x1373"/>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.
@@ -759,7 +762,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x1376" id="iddiv2x1x1376"/>5.10 Non-Addressable Event Sink Test</h3><p>
+<h3><a name="iddiv2x1x1382" id="iddiv2x1x1382"/>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
@@ -780,7 +783,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="iddiv3x1x1400" id="iddiv3x1x1400"/>5.11 Sequence</h4><p>
+<h4><a name="iddiv3x1x1406" id="iddiv3x1x1406"/>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>
@@ -789,7 +792,7 @@
SubscribeResponse and UnsubscribeResponse are both transmitted on
the back-channel of their corresponding requests.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1412" id="iddiv3x1x1412"/>5.12 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1418" id="iddiv3x1x1418"/>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.
@@ -821,27 +824,27 @@
elicit a wsa:ActionNotSupported fault response or some other,
unspecified behavior.
</p></div></div><div class="div1">
-<h2><a name="iddiv1x1x1440" id="iddiv1x1x1440"/>6 WS-Transfer/WS-Fragment Tests</h2><p>
+<h2><a name="iddiv1x1x1446" id="iddiv1x1x1446"/>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="iddiv2x1x1445" id="iddiv2x1x1445"/>6.1 Create Test</h3><p>
+<h3><a name="iddiv2x1x1451" id="iddiv2x1x1451"/>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="iddiv3x1x1451" id="iddiv3x1x1451"/>6.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1457" id="iddiv3x1x1457"/>6.1.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1456" id="iddiv3x1x1456"/>6.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1462" id="iddiv3x1x1462"/>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="iddiv3x1x1466" id="iddiv3x1x1466"/>6.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1472" id="iddiv3x1x1472"/>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="iddiv2x1x1471" id="iddiv2x1x1471"/>6.2 Get Test</h3><p>
+<h3><a name="iddiv2x1x1477" id="iddiv2x1x1477"/>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
@@ -850,20 +853,20 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1477" id="iddiv3x1x1477"/>6.2.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1483" id="iddiv3x1x1483"/>6.2.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1482" id="iddiv3x1x1482"/>6.2.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1488" id="iddiv3x1x1488"/>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="iddiv3x1x1492" id="iddiv3x1x1492"/>6.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1498" id="iddiv3x1x1498"/>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="iddiv2x1x1497" id="iddiv2x1x1497"/>6.3 Fragment Get Test</h3><p>
+<h3><a name="iddiv2x1x1503" id="iddiv2x1x1503"/>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
@@ -872,22 +875,22 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1503" id="iddiv3x1x1503"/>6.3.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1509" id="iddiv3x1x1509"/>6.3.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1508" id="iddiv3x1x1508"/>6.3.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1514" id="iddiv3x1x1514"/>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="iddiv3x1x1518" id="iddiv3x1x1518"/>6.3.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1524" id="iddiv3x1x1524"/>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="iddiv2x1x1523" id="iddiv2x1x1523"/>6.4 Put Test</h3><p>
+<h3><a name="iddiv2x1x1529" id="iddiv2x1x1529"/>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
@@ -895,19 +898,19 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1529" id="iddiv3x1x1529"/>6.4.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1535" id="iddiv3x1x1535"/>6.4.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1534" id="iddiv3x1x1534"/>6.4.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1540" id="iddiv3x1x1540"/>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="iddiv3x1x1544" id="iddiv3x1x1544"/>6.4.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1550" id="iddiv3x1x1550"/>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="iddiv2x1x1549" id="iddiv2x1x1549"/>6.5 Fragment Put Test</h3><p>
+<h3><a name="iddiv2x1x1555" id="iddiv2x1x1555"/>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
@@ -915,12 +918,12 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1555" id="iddiv3x1x1555"/>6.5.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1561" id="iddiv3x1x1561"/>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="iddiv3x1x1560" id="iddiv3x1x1560"/>6.5.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1566" id="iddiv3x1x1566"/>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>
@@ -930,14 +933,14 @@
</p></li><li><p>
Receipt of a valid GetResponse message by the client.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1576" id="iddiv3x1x1576"/>6.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1582" id="iddiv3x1x1582"/>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><div class="div2">
-<h3><a name="iddiv2x1x1581" id="iddiv2x1x1581"/>6.6 Delete Test</h3><p>
+<h3><a name="iddiv2x1x1587" id="iddiv2x1x1587"/>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
@@ -945,38 +948,38 @@
The use of WS-MetadataExchange is recommeneded to ensure that
the endpoint supports WS-Transfer.
</p><div class="div3">
-<h4><a name="iddiv3x1x1587" id="iddiv3x1x1587"/>6.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1593" id="iddiv3x1x1593"/>6.6.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1592" id="iddiv3x1x1592"/>6.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1598" id="iddiv3x1x1598"/>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="iddiv3x1x1602" id="iddiv3x1x1602"/>6.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1608" id="iddiv3x1x1608"/>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="iddiv1x1x1607" id="iddiv1x1x1607"/>7 WS-Enumeration Tests</h2><p>
+<h2><a name="iddiv1x1x1613" id="iddiv1x1x1613"/>7 WS-Enumeration Tests</h2><p>
...
</p><div class="div2">
-<h3><a name="iddiv2x1x1612" id="iddiv2x1x1612"/>7.1 xxx Test</h3><p>
+<h3><a name="iddiv2x1x1618" id="iddiv2x1x1618"/>7.1 xxx Test</h3><p>
This test ....
</p><div class="div3">
-<h4><a name="iddiv3x1x1618" id="iddiv3x1x1618"/>7.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1624" id="iddiv3x1x1624"/>7.1.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1623" id="iddiv3x1x1623"/>7.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1629" id="iddiv3x1x1629"/>7.1.2 Success Criteria</h4><ul><li><p>
...
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1630" id="iddiv3x1x1630"/>7.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1636" id="iddiv3x1x1636"/>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="iddiv2x1x1639" id="iddiv2x1x1639"/>8.1 Event Source WSDL</h3><p>
+<h3><a name="iddiv2x1x1645" id="iddiv2x1x1645"/>8.1 Event Source WSDL</h3><p>
TBD
</p></div><div class="div2">
-<h3><a name="iddiv2x1x1644" id="iddiv2x1x1644"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x1650" id="iddiv2x1x1650"/>8.2 Notification WSDL</h3><p>
TBD
</p></div></div><div class="div1">
<h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
@@ -1016,7 +1019,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="iddiv2x1x1671" id="iddiv2x1x1671"/>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="iddiv2x1x1677" id="iddiv2x1x1677"/>12.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1131,4 +1134,8 @@
Added 34Conformance34 sections to each test that describe any
allowable failures. Added sequence diagrams to Renew Test,
SubscriptionEnd Test, and Non-Addressable Event Sink Test.
+ </td></tr><tr><td> 2011/01/09 </td><td> DD </td><td>
+ Add a history section to each animal so we can track medical
+ history or just make notes about the animal. Really, we need
+ an array and something with an attribute to test frag stuf
</td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Sunday, 9 January 2011 16:41:13 UTC