- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 03 Jan 2011 15:10:27 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv6704
Modified Files:
scenario.html scenario.xml
Log Message:
some transfer/frag stuff
Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- scenario.xml 31 Dec 2010 13:57:31 -0000 1.8
+++ scenario.xml 3 Jan 2011 15:10:25 -0000 1.9
@@ -498,7 +498,9 @@
<head>WS-MetadataExchange Tests</head>
<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>
<div2 tocStop='true'>
@@ -1855,14 +1857,16 @@
<head>WS-Transfer/WS-Fragment Tests</head>
<p>
- ...
+ This section describes the tests for WS-Transfer and WS-Fragment.
</p>
<div2 tocStop='true'>
- <head>xxx Test</head>
+ <head>Create Test</head>
<p>
- This test ....
+ 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>
<div3>
@@ -1879,7 +1883,60 @@
<ulist>
<item>
<p>
- ...
+ Receipt of a valid Create message by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid CreateResponse message by the client.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <p>
+ A conforming service MUST respond to the Create request with a
+ CreateResponse message.
+ </p>
+ </div3>
+ </div2>
+
+ <div2 tocStop='true'>
+ <head>Get Test</head>
+
+ <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
+ during the Create test or returned from any other test described
+ in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <p>
+ ...
+ </p>
+ </div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid Get message by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid GetResponse message by the service.
</p>
</item>
</ulist>
@@ -1889,9 +1946,221 @@
<head>Conformance</head>
<p>
+ A conforming service MUST respond to the Get request with a
+ GetResponse message containing the current representation of
+ the Animal/Tag.
+ </p>
+ </div3>
+ </div2>
+
+
+ <div2 tocStop='true'>
+ <head>Fragment Get Test</head>
+
+ <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
+ during the Create test or returned from any other test described
+ in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <p>
...
</p>
</div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid Get message containing the WS-Fragment Dialect IRI
+ by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid GetResponse message by the service.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <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>
+ </div3>
+ </div2>
+
+ <div2 tocStop='true'>
+ <head>Put Test</head>
+
+ <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
+ Create test or returned from any other test described in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <p>
+ ...
+ </p>
+ </div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid Put message by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid PutResponse message by the client.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <p>
+ A conforming service MUST respond to the Put request with a
+ PutResponse message.
+ </p>
+ </div3>
+ </div2>
+
+ <div2 tocStop='true'>
+ <head>Fragment Put Test</head>
+
+ <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
+ Create test or returned from any other test described in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <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>
+ </div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid Put message using the WS-Fragment Dialect IRI
+ by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid PutResponse message by the client.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid Get message by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid GetResponse message by the client.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <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>
+ </div3>
+ </div2>
+
+
+ <div2 tocStop='true'>
+ <head>Delete Test</head>
+
+ <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
+ Create test or returned from any other test described in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p>
+
+ <div3>
+ <head>Sequence</head>
+
+ <p>
+ ...
+ </p>
+ </div3>
+
+ <div3>
+ <head>Success Criteria</head>
+
+ <ulist>
+ <item>
+ <p>
+ Receipt of a valid Delete message by the service.
+ </p>
+ </item>
+ <item>
+ <p>
+ Receipt of a valid DeleteResponse message by the client.
+ </p>
+ </item>
+ </ulist>
+ </div3>
+
+ <div3>
+ <head>Conformance</head>
+
+ <p>
+ A conforming service MUST respond to the Delete request with a
+ DeleteResponse message.
+ </p>
+ </div3>
</div2>
</div1>
Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -d -r1.8 -r1.9
--- scenario.html 31 Dec 2010 13:57:31 -0000 1.8
+++ scenario.html 3 Jan 2011 15:10:25 -0000 1.9
@@ -73,17 +73,22 @@
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/>
+ 6.1 <a href="#iddiv2x1x1443">Create Test</a><br/>
+ 6.2 <a href="#iddiv2x1x1469">Get Test</a><br/>
+ 6.3 <a href="#iddiv2x1x1495">Fragment Get Test</a><br/>
+ 6.4 <a href="#iddiv2x1x1521">Put Test</a><br/>
+ 6.5 <a href="#iddiv2x1x1547">Fragment Put Test</a><br/>
+ 6.6 <a href="#iddiv2x1x1579">Delete Test</a><br/>
+7 <a href="#iddiv1x1x1605">WS-Enumeration Tests</a><br/>
+ 7.1 <a href="#iddiv2x1x1610">xxx Test</a><br/>
8 <a href="#wsdl">WSDL</a><br/>
- 8.1 <a href="#iddiv2x1x1498">Event Source WSDL</a><br/>
- 8.2 <a href="#iddiv2x1x1503">Notification WSDL</a><br/>
+ 8.1 <a href="#iddiv2x1x1637">Event Source WSDL</a><br/>
+ 8.2 <a href="#iddiv2x1x1642">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="#iddiv2x1x1530">Normative References</a><br/>
+ 12.1 <a href="#iddiv2x1x1669">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/>
@@ -218,7 +223,9 @@
test or fail one or more of the success criteria.
</p></li></ul></div></div><div class="div1">
<h2><a name="iddiv1x1x685" id="iddiv1x1x685"/>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="iddiv2x1x690" id="iddiv2x1x690"/>4.1 GetWSDL Test</h3><p>
This test verifies the ability to retrieve the WSDL associated with
@@ -809,40 +816,161 @@
unspecified behavior.
</p></div></div><div class="div1">
<h2><a name="iddiv1x1x1438" id="iddiv1x1x1438"/>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="iddiv2x1x1443" id="iddiv2x1x1443"/>6.1 xxx Test</h3><p>
- This test ....
+<h3><a name="iddiv2x1x1443" id="iddiv2x1x1443"/>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="iddiv3x1x1449" id="iddiv3x1x1449"/>6.1.1 Sequence</h4><p>
...
</p></div><div class="div3">
<h4><a name="iddiv3x1x1454" id="iddiv3x1x1454"/>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="iddiv3x1x1461" id="iddiv3x1x1461"/>6.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1464" id="iddiv3x1x1464"/>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="iddiv2x1x1469" id="iddiv2x1x1469"/>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
+ during the Create test or returned from any other test described
+ in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x1475" id="iddiv3x1x1475"/>6.2.1 Sequence</h4><p>
+ ...
+ </p></div><div class="div3">
+<h4><a name="iddiv3x1x1480" id="iddiv3x1x1480"/>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="iddiv3x1x1490" id="iddiv3x1x1490"/>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="iddiv2x1x1495" id="iddiv2x1x1495"/>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
+ during the Create test or returned from any other test described
+ in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x1501" id="iddiv3x1x1501"/>6.3.1 Sequence</h4><p>
+ ...
+ </p></div><div class="div3">
+<h4><a name="iddiv3x1x1506" id="iddiv3x1x1506"/>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="iddiv3x1x1516" id="iddiv3x1x1516"/>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="iddiv2x1x1521" id="iddiv2x1x1521"/>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
+ Create test or returned from any other test described in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x1527" id="iddiv3x1x1527"/>6.4.1 Sequence</h4><p>
+ ...
+ </p></div><div class="div3">
+<h4><a name="iddiv3x1x1532" id="iddiv3x1x1532"/>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="iddiv3x1x1542" id="iddiv3x1x1542"/>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="iddiv2x1x1547" id="iddiv2x1x1547"/>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
+ Create test or returned from any other test described in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x1553" id="iddiv3x1x1553"/>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="iddiv3x1x1558" id="iddiv3x1x1558"/>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>
+ Receipt of a valid PutResponse message by the client.
+ </p></li><li><p>
+ Receipt of a valid Get message by the service.
+ </p></li><li><p>
+ Receipt of a valid GetResponse message by the client.
+ </p></li></ul></div><div class="div3">
+<h4><a name="iddiv3x1x1574" id="iddiv3x1x1574"/>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="iddiv2x1x1579" id="iddiv2x1x1579"/>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
+ Create test or returned from any other test described in this document.
+ The use of WS-MetadataExchange is recommeneded to ensure that
+ the endpoint supports WS-Transfer.
+ </p><div class="div3">
+<h4><a name="iddiv3x1x1585" id="iddiv3x1x1585"/>6.6.1 Sequence</h4><p>
...
+ </p></div><div class="div3">
+<h4><a name="iddiv3x1x1590" id="iddiv3x1x1590"/>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="iddiv3x1x1600" id="iddiv3x1x1600"/>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="iddiv1x1x1466" id="iddiv1x1x1466"/>7 WS-Enumeration Tests</h2><p>
+<h2><a name="iddiv1x1x1605" id="iddiv1x1x1605"/>7 WS-Enumeration Tests</h2><p>
...
</p><div class="div2">
-<h3><a name="iddiv2x1x1471" id="iddiv2x1x1471"/>7.1 xxx Test</h3><p>
+<h3><a name="iddiv2x1x1610" id="iddiv2x1x1610"/>7.1 xxx Test</h3><p>
This test ....
</p><div class="div3">
-<h4><a name="iddiv3x1x1477" id="iddiv3x1x1477"/>7.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1616" id="iddiv3x1x1616"/>7.1.1 Sequence</h4><p>
...
</p></div><div class="div3">
-<h4><a name="iddiv3x1x1482" id="iddiv3x1x1482"/>7.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1621" id="iddiv3x1x1621"/>7.1.2 Success Criteria</h4><ul><li><p>
...
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x1489" id="iddiv3x1x1489"/>7.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1628" id="iddiv3x1x1628"/>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="iddiv2x1x1498" id="iddiv2x1x1498"/>8.1 Event Source WSDL</h3><p>
+<h3><a name="iddiv2x1x1637" id="iddiv2x1x1637"/>8.1 Event Source WSDL</h3><p>
TBD
</p></div><div class="div2">
-<h3><a name="iddiv2x1x1503" id="iddiv2x1x1503"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x1642" id="iddiv2x1x1642"/>8.2 Notification WSDL</h3><p>
TBD
</p></div></div><div class="div1">
<h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
@@ -882,7 +1010,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="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>
+<h3><a name="iddiv2x1x1669" id="iddiv2x1x1669"/>12.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
Received on Monday, 3 January 2011 15:10:30 UTC