- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 16 Dec 2010 15:11:50 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv13536
Modified Files:
scenario.html scenario.xml
Log Message:
Adding some thoughts from Nathan (msft)
Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- scenario.xml 15 Dec 2010 13:37:59 -0000 1.3
+++ scenario.xml 16 Dec 2010 15:11:48 -0000 1.4
@@ -148,10 +148,25 @@
</tr>
<tr>
<td> wse </td>
- <td> http://www.w3.org/2010/08/ws-evt </td>
+ <td> http://www.w3.org/&wssas.nsprefix;/ws-evt </td>
<td> <bibref ref="Eventing"/> </td>
</tr>
<tr>
+ <td> wsen </td>
+ <td> http://www.w3.org/&wssas.nsprefix;/ws-enu </td>
+ <td> <bibref ref="Enumeration"/> </td>
+ </tr>
+ <tr>
+ <td> mex </td>
+ <td> http://www.w3.org/&wssas.nsprefix;/ws-mex </td>
+ <td> <bibref ref="MetadataExchange"/> </td>
+ </tr>
+ <tr>
+ <td> sce </td>
+ <td> http://www.w3.org/2010/08/scenario </td>
+ <td> This document </td>
+ </tr>
+ <tr>
<td> gpx </td>
<td> http://www.topografix.com/GPX/1/1 </td>
<td> GPS eXchange Format </td>
@@ -258,9 +273,137 @@
These tags periodically communicate via satellite to a central system.
External systems can consume this information by using WS-Eventing to
subscribe to periodic notifications about the locations of the tags
- and, presumably, the animals they are attached to.
+ and, presumably, the animals they are attached to. Systems may also
+ query for the current data associated with an animal via WS-Enumeation,
+ to enumerate the list of animals, or WS-Transfer/Fragment to
+ retrieve the information about one particular animal. By using
+ WS-MetadataExchange a client can determine which of the various
+ WS-RA specifications are supported.
+ </p>
+
+ <p>
+ A set of properties is maintained for each animal that is tagged.
+ The following properties are stored:
</p>
+ <table id="animal_props" border="1">
+ <caption> Properties for each animal </caption>
+
+ <tbody>
+ <tr>
+ <th align="left"> Property </th>
+ <th align="left"> Description </th>
+ <th align="left"> Example </th>
+ </tr>
+ <tr>
+ <td> ID </td>
+ <td> A GUID that uniquely identifies the animal </td>
+ <td> 13c76450-de3d-11df-85ca-0800200c9a66 </td>
+ </tr>
+ <tr>
+ <td> Name </td>
+ <td> The name given to the animal </td>
+ <td> Howard </td>
+ </tr>
+ <tr>
+ <td> Birthdate </td>
+ <td> The day on which the animal was born </td>
+ <td> 12/08/2006 </td>
+ </tr>
+ <tr>
+ <td> Gender </td>
+ <td> The gender of the animal </td>
+ <td> Male </td>
+ </tr>
+ <tr>
+ <td> Family </td>
+ <td> The Family of which the animal is a member </td>
+ <td> Eschrichtiidae </td>
+ </tr>
+ <tr>
+ <td> Genus </td>
+ <td> The Genus of which the animal is a member </td>
+ <td> Eschrichtius </td>
+ </tr>
+ <tr>
+ <td> Species </td>
+ <td> The Species of which the animal is a member </td>
+ <td> robustus </td>
+ </tr>
+ <tr>
+ <td> Current Location </td>
+ <td> The current GPS location of the animal </td>
+ <td> </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>
+ The XML representation of each tag will match the following
+ pseudo-schema:
+ </p>
+
+ <example>
+ <eg><sce:Animal ...>
+ <sce:ID> <emph>xs:string</emph> </sce:ID>
+ <sce:Name> <emph>xs:string</emph> </sce:Name>
+ <sce:Birthdate> <emph>xs:date</emph> </sce:Birthdate>
+ <sce:Gender> <emph>xs:string</emph> </sce:Gender>
+ <sce:Family> <emph>xs:string</emph> </sce:Family>
+ <sce:Genus> <emph>xs:string</emph> </sce:Genus>
+ <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>
+ <emph>xs:any</emph>
+</sce:Animal> </eg>
+ </example>
+
+ <div2>
+ <head>Predefined Animals/Tags</head>
+
+ <p>
+ At a minimum each service side implementation of this scenario
+ MUST initiallize have at least the following animals/tags:
+ </p>
+
+ <ulist>
+ <item>
+ <p>
+ ID: 13c76450-de3d-11df-85ca-0800200c9a66 <phrase/>
+ Name: Howard <phrase/>
+ Birthdate: 12/08/2006 <phrase/>
+ Gender: Male <phrase/>
+ Family: Eschrichtiidae <phrase/>
+ Genus: Eschrichtius <phrase/>
+ Species: robustus <phrase/>
+ </p>
+ </item>
+ <item>
+ <p>
+ ID: 234b6840-de3d-11df-85ca-0800200c9a66 <phrase/>
+ Name: Kerry <phrase/>
+ Birthdate: 05/22/2008 <phrase/>
+ Gender: Female <phrase/>
+ Family: ... <phrase/>
+ Genus: ... <phrase/>
+ Species: ... <phrase/>
+ </p>
+ </item>
+ <item>
+ <p>
+ ID: 32675b90-de3d-11df-85ca-0800200c9a66 <phrase/>
+ Name: Oscar <phrase/>
+ Birthdate: 03/01/2010 <phrase/>
+ Gender: Male <phrase/>
+ Family: ... <phrase/>
+ Genus: ... <phrase/>
+ Species: ... <phrase/>
+ </p>
+ </item>
+ </ulist>
+
+ </div2>
+
<div2 id="evt_description">
<head>Event Description</head>
@@ -287,21 +430,6 @@
</p>
</div2>
- <div2>
- <head>Tags</head>
-
- <p>
- Again for the sake of feasibility, this scenario will only include
- three tags with the following IDs:
- </p>
-
- <ulist>
- <item> <p>13c76450-de3d-11df-85ca-0800200c9a66 (Howard)</p> </item>
- <item> <p>234b6840-de3d-11df-85ca-0800200c9a66 (Kerry)</p> </item>
- <item> <p>32675b90-de3d-11df-85ca-0800200c9a66 (Oscar)</p> </item>
- </ulist>
- </div2>
-
</div1>
<div1>
@@ -1494,6 +1622,16 @@
World Wide Web Consortium (W3C), 9 May 2006.
</bibl>
+ <bibl key="WS-Enumeration" id="Enumeration"
+ href="http://www.w3.org/TR/ws-enumeration">
+ <titleref>
+ W3C Working Group Draft, "Web Services Enumeration
+ (WS-Enumeration) 1.1"
+ </titleref>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ </bibl>
+
<bibl key="WS-Eventing" id="Eventing"
href="http://www.w3.org/TR/ws-eventing">
<titleref>
@@ -1504,6 +1642,16 @@
World Wide Web Consortium (W3C), 15 September 2009.
</bibl>
+ <bibl key="WS-MetadataExchange" id="MetadataExchange"
+ href="http://www.w3.org/TR/ws-metadata-exchange">
+ <titleref>
+ W3C Working Group Draft, "Web Services Metadata Exchange
+ (WS-MetadataExchange) 1.1"
+ </titleref>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ </bibl>
+
<bibl key="WSDL11" id="WSDL11"
href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">
<titleref>
Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- scenario.html 15 Dec 2010 13:37:59 -0000 1.3
+++ scenario.html 16 Dec 2010 15:11:48 -0000 1.4
@@ -49,31 +49,31 @@
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="#evt_description">Event Description</a><br/>
- 3.2 <a href="#iddiv2x1x318">Event Timing</a><br/>
- 3.3 <a href="#iddiv2x1x323">Tags</a><br/>
-4 <a href="#iddiv1x1x338">WS-MetadataExchange Tests</a><br/>
+ 3.1 <a href="#iddiv2x1x520">Predefined Animals/Tags</a><br/>
+ 3.2 <a href="#evt_description">Event Description</a><br/>
+ 3.3 <a href="#iddiv2x1x583">Event Timing</a><br/>
+4 <a href="#iddiv1x1x588">WS-MetadataExchange Tests</a><br/>
5 <a href="#wsevt-tests">WS-Eventing Tests</a><br/>
- 5.1 <a href="#iddiv2x1x364">Basic Test</a><br/>
- 5.2 <a href="#iddiv2x1x421">Wrapped Notifications</a><br/>
- 5.3 <a href="#iddiv2x1x473">Duration Expiration Test</a><br/>
- 5.4 <a href="#iddiv2x1x528">Specific Time Expiration Test</a><br/>
- 5.5 <a href="#iddiv2x1x580">Best Effort Expiration Test</a><br/>
- 5.6 <a href="#iddiv2x1x632">Renew Test</a><br/>
- 5.7 <a href="#iddiv2x1x702">SubscriptionEnd Test</a><br/>
- 5.8 <a href="#iddiv2x1x756">Filter Test - XPath 1.0</a><br/>
- 5.9 <a href="#iddiv2x1x808">Filter Test - XPath 2.0</a><br/>
- 5.10 <a href="#iddiv2x1x860">Non-Addressable Event Sink Test</a><br/>
-6 <a href="#iddiv1x1x924">WS-Transfer/WS-Fragment Tests</a><br/>
-7 <a href="#iddiv1x1x929">WS-Enumeration Tests</a><br/>
+ 5.1 <a href="#iddiv2x1x614">Basic Test</a><br/>
+ 5.2 <a href="#iddiv2x1x671">Wrapped Notifications</a><br/>
+ 5.3 <a href="#iddiv2x1x723">Duration Expiration Test</a><br/>
+ 5.4 <a href="#iddiv2x1x778">Specific Time Expiration Test</a><br/>
+ 5.5 <a href="#iddiv2x1x830">Best Effort Expiration Test</a><br/>
+ 5.6 <a href="#iddiv2x1x882">Renew Test</a><br/>
+ 5.7 <a href="#iddiv2x1x952">SubscriptionEnd Test</a><br/>
+ 5.8 <a href="#iddiv2x1x1006">Filter Test - XPath 1.0</a><br/>
+ 5.9 <a href="#iddiv2x1x1058">Filter Test - XPath 2.0</a><br/>
+ 5.10 <a href="#iddiv2x1x1110">Non-Addressable Event Sink Test</a><br/>
+6 <a href="#iddiv1x1x1174">WS-Transfer/WS-Fragment Tests</a><br/>
+7 <a href="#iddiv1x1x1179">WS-Enumeration Tests</a><br/>
8 <a href="#wsdl">WSDL</a><br/>
- 8.1 <a href="#iddiv2x1x938">Event Source WSDL</a><br/>
- 8.2 <a href="#iddiv2x1x943">Notification WSDL</a><br/>
+ 8.1 <a href="#iddiv2x1x1188">Event Source WSDL</a><br/>
+ 8.2 <a href="#iddiv2x1x1193">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="#iddiv2x1x970">Normative References</a><br/>
+ 12.1 <a href="#iddiv2x1x1220">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/>
@@ -86,7 +86,7 @@
<h3><a name="namespaces" id="namespaces"/>1.2 XML Namespaces</h3><p><a href="#XMLNS">Table 1-1</a> lists XML namespaces that are used in this
specification. The choice of any namespace prefix is arbitrary and
not semantically significant.
- </p><a name="XMLNS" id="XMLNS"/><table border="1"><caption>Table 1-1: Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td><a href="#SOAP12">[SOAP12]</a></td></tr><tr><td> xsd </td><td> http://www.w3.org/2001/XMLSchema </td><td><a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wse </td><td> http://www.w3.org/2010/08/ws-evt </td><td><a href="#Eventing">[WS-Eventig]</a></td></tr><tr><td> gpx </td><td> http://www.topografix.com/GPX/1/1 </td><td> GPS eXchange Format </td></tr></tbody></table></div><div class="div2">
+ </p><a name="XMLNS" id="XMLNS"/><table border="1"><caption>Table 1-1: Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespaces </th><th align="left"> Specification(s) </th></tr><tr><td> s </td><td> (Either SOAP 1.1 or 1.2) </td><td> (Either SOAP 1.1 or 1.2) </td></tr><tr><td> s11 </td><td> http://schemas.xmlsoap.org/soap/envelope/ </td><td><a href="#SOAP11">[SOAP11]</a></td></tr><tr><td> s12 </td><td> http://www.w3.org/2003/05/soap-envelope </td><td><a href="#SOAP12">[SOAP12]</a></td></tr><tr><td> xsd </td><td> http://www.w3.org/2001/XMLSchema </td><td><a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> wsdl </td><td> http://schemas.xmlsoap.org/wsdl/ </td><td><a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> wsa </td><td> http://www.w3.org/2005/08/addressing </td><td><a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td> wse </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-evt </td><td><a href="#Eventing>[WS-Eventing]</a></td></tr><tr><td> wsen </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-enu </td><td><a href="#Enumeration">[WS-Enumeration]</a></td></tr><tr><td> mex </td><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex </td><td><a href="#MetadataExchange">[WS-MetadataExchange]</a></td></tr><tr><td> sce </td><td> http://www.w3.org/2010/08/scenario </td><td> This document </td></tr><tr><td> gpx </td><td> http://www.topografix.com/GPX/1/1 </td><td> GPS eXchange Format </td></tr></tbody></table></div><div class="div2">
<h3><a name="preconditions" id="preconditions"/>1.3 Preconditions</h3></div></div><div class="div1">
<h2><a name="notterms" id="notterms"/>2 Notations and Terminology</h2><p>
This section specifies the notations, namespaces, and
@@ -124,9 +124,56 @@
These tags periodically communicate via satellite to a central system.
External systems can consume this information by using WS-Eventing to
subscribe to periodic notifications about the locations of the tags
- and, presumably, the animals they are attached to.
- </p><div class="div2">
-<h3><a name="evt_description" id="evt_description"/>3.1 Event Description</h3><p>
+ and, presumably, the animals they are attached to. Systems may also
+ query for the current data associated with an animal via WS-Enumeation,
+ to enumerate the list of animals, or WS-Transfer/Fragment to
+ retrieve the information about one particular animal. By using
+ WS-MetadataExchange a client can determine which of the various
+ WS-RA specifications are supported.
+ </p><p>
+ A set of properties is maintained for each animal that is tagged.
+ The following properties are stored:
+ </p><a name="animal_props" id="animal_props"/><table border="1"><caption>Table 3-1: Properties for each animal </caption><tbody><tr><th align="left"> Property </th><th align="left"> Description </th><th align="left"> Example </th></tr><tr><td> ID </td><td> A GUID that uniquely identifies the animal </td><td> 13c76450-de3d-11df-85ca-0800200c9a66 </td></tr><tr><td> Name </td><td> The name given to the animal </td><td> Howard </td></tr><tr><td> Birthdate </td><td> The day on which the animal was born </td><td> 12/08/2006 </td></tr><tr><td> Gender </td><td> The gender of the animal </td><td> Male </td></tr><tr><td> Family </td><td> The Family of which the animal is a member </td><td> Eschrichtiidae </td></tr><tr><td> Genus </td><td> The Genus of which the animal is a member </td><td> Eschrichtius </td></tr><tr><td> Species </td><td> The Species of which the animal is a member </td><td> robustus </td></tr><tr><td> Current Location </td><td> The current GPS location of the animal </td><td> </td></tr></tbody>/table><p>
+ The XML representation of each tag will match the following
+ pseudo-schema:
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><sce:Animal ...>
+ <sce:ID> <em>xs:string</em> </sce:ID>
+ <sce:Name> <em>xs:string</em> </sce:Name>
+ <sce:Birthdate> <em>xs:date</em> </sce:Birthdate>
+ <sce:Gender> <em>xs:string</em> </sce:Gender>
+ <sce:Family> <em>xs:string</em> </sce:Family>
+ <sce:Genus> <em>xs:string</em> </sce:Genus>
+ <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>
+ <em>xs:any</em>
+</sce:Animal> </pre></div></div><div class="div2">
+<h3><a name="iddiv2x1x520" id="iddiv2x1x520"/>3.1 Predefined Animals/Tags</h3><p>
+ At a minimum each service side implementation of this scenario
+ MUST initiallize have at least the following animals/tags:
+ </p><ul><li><p>
+ ID: 13c76450-de3d-11df-85ca-0800200c9a66 <br/>
+ Name: Howard <br/>
+ Birthdate: 12/08/2006 <br/>
+ Gender: Male <br/>
+ Family: Eschrichtiidae <br/>
+ Genus: Eschrichtius <br/>
+ Species: robustus <br/></p></li><li><p>
+ ID: 234b6840-de3d-11df-85ca-0800200c9a66 <br/>
+ Name: Kerry <br/>
+ Birthdate: 05/22/2008 <br/>
+ Gender: Female <br/>
+ Family: ... <br/>
+ Genus: ... <br/>
+ Species: ... <br/></p></li><li><p>
+ ID: 32675b90-de3d-11df-85ca-0800200c9a66 <br/>
+ Name: Oscar <br/>
+ Birthdate: 03/01/2010 <br/>
+ Gender: Male <br/>
+ Family: ... <br/>
+ Genus: ... <br/>
+ Species: ... <br/></p></li></ul></div><div class="div2">
+<h3><a name="evt_description" id="evt_description"/>3.2 Event Description</h3><p>
The location of the tags is expressed in GPS coordinates using the GPS
eXchange Format, an XML schema designed as a common GPS data format
for software applications. In addition to the basic GPS information
@@ -136,18 +183,14 @@
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="iddiv2x1x318" id="iddiv2x1x318"/>3.2 Event Timing</h3><p>
+<h3><a name="iddiv2x1x583" id="iddiv2x1x583"/>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
seconds in real-world time. The time data contained in the
notifications will reflect scenario time.
- </p></div><div class="div2">
-<h3><a name="iddiv2x1x323" id="iddiv2x1x323"/>3.3 Tags</h3><p>
- Again for the sake of feasibility, this scenario will only include
- three tags with the following IDs:
- </p><ul><li><p>13c76450-de3d-11df-85ca-0800200c9a66 (Howard)</p></li><li><p>234b6840-de3d-11df-85ca-0800200c9a66 (Kerry)</p></li><li><p>32675b90-de3d-11df-85ca-0800200c9a66 (Oscar)</p></li></ul></div></div><div class="div1">
-<h2><a name="iddiv1x1x338" id="iddiv1x1x338"/>4 WS-MetadataExchange Tests</h2><p>
+ </p></div></div><div class="div1">
+<h2><a name="iddiv1x1x588" id="iddiv1x1x588"/>4 WS-MetadataExchange Tests</h2><p>
...
</p></div><div class="div1">
<h2><a name="wsevt-tests" id="wsevt-tests"/>5 WS-Eventing Tests</h2><p>
@@ -170,15 +213,15 @@
conforming implementations are allowed to either not implement the
test or fail one or more of the success criteria.
</p></li></ul><div class="div2">
-<h3><a name="iddiv2x1x364" id="iddiv2x1x364"/>5.1 Basic Test</h3><p>
+<h3><a name="iddiv2x1x614" id="iddiv2x1x614"/>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="iddiv3x1x383" id="iddiv3x1x383"/>5.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x633" id="iddiv3x1x633"/>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="iddiv3x1x393" id="iddiv3x1x393"/>5.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x643" id="iddiv3x1x643"/>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.
@@ -189,7 +232,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x412" id="iddiv3x1x412"/>5.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x662" id="iddiv3x1x662"/>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>
@@ -200,16 +243,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="iddiv2x1x421" id="iddiv2x1x421"/>5.2 Wrapped Notifications</h3><p>
+<h3><a name="iddiv2x1x671" id="iddiv2x1x671"/>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="iddiv3x1x440" id="iddiv3x1x440"/>5.2.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x690" id="iddiv3x1x690"/>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="iddiv3x1x445" id="iddiv3x1x445"/>5.2.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x695" id="iddiv3x1x695"/>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.
@@ -220,7 +263,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x464" id="iddiv3x1x464"/>5.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x714" id="iddiv3x1x714"/>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.
@@ -231,7 +274,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="iddiv2x1x473" id="iddiv2x1x473"/>5.3 Duration Expiration Test</h3><p>
+<h3><a name="iddiv2x1x723" id="iddiv2x1x723"/>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:
@@ -244,12 +287,12 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x492" id="iddiv3x1x492"/>5.3.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x742" id="iddiv3x1x742"/>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="iddiv3x1x502" id="iddiv3x1x502"/>5.3.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x752" id="iddiv3x1x752"/>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.
@@ -264,7 +307,7 @@
HTTP error (i.e. '404') that indicates the Subscription Manager no
longer exists
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x521" id="iddiv3x1x521"/>5.3.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x771" id="iddiv3x1x771"/>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.
@@ -275,7 +318,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="iddiv2x1x528" id="iddiv2x1x528"/>5.4 Specific Time Expiration Test</h3><p>
+<h3><a name="iddiv2x1x778" id="iddiv2x1x778"/>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:
@@ -288,11 +331,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x547" id="iddiv3x1x547"/>5.4.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x797" id="iddiv3x1x797"/>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="iddiv3x1x552" id="iddiv3x1x552"/>5.4.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x802" id="iddiv3x1x802"/>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.
@@ -307,7 +350,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="iddiv3x1x571" id="iddiv3x1x571"/>5.4.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x821" id="iddiv3x1x821"/>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.
@@ -319,7 +362,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="iddiv2x1x580" id="iddiv2x1x580"/>5.5 Best Effort Expiration Test</h3><p>
+<h3><a name="iddiv2x1x830" id="iddiv2x1x830"/>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:
@@ -333,11 +376,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x599" id="iddiv3x1x599"/>5.5.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x849" id="iddiv3x1x849"/>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="iddiv3x1x604" id="iddiv3x1x604"/>5.5.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x854" id="iddiv3x1x854"/>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.
@@ -352,7 +395,7 @@
HTTP error (i.e. '404') that indicates the Subscription Manager
no longer exists.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x623" id="iddiv3x1x623"/>5.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x873" id="iddiv3x1x873"/>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
@@ -368,7 +411,7 @@
implement this test or to fail to meet one of the defined
success criteria.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x632" id="iddiv2x1x632"/>5.6 Renew Test</h3><p>
+<h3><a name="iddiv2x1x882" id="iddiv2x1x882"/>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:
@@ -385,11 +428,11 @@
</p><ul><li><p>
(short) expiration time chosen by Subscriber as xs:duration
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x657" id="iddiv3x1x657"/>5.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x907" id="iddiv3x1x907"/>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="iddiv3x1x667" id="iddiv3x1x667"/>5.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x917" id="iddiv3x1x917"/>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.
@@ -408,7 +451,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x695" id="iddiv3x1x695"/>5.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x945" id="iddiv3x1x945"/>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.
@@ -419,7 +462,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="iddiv2x1x702" id="iddiv2x1x702"/>5.7 SubscriptionEnd Test</h3><p>
+<h3><a name="iddiv2x1x952" id="iddiv2x1x952"/>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
@@ -433,11 +476,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x721" id="iddiv3x1x721"/>5.7.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x971" id="iddiv3x1x971"/>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="iddiv3x1x731" id="iddiv3x1x731"/>5.7.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x981" id="iddiv3x1x981"/>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.
@@ -447,7 +490,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="iddiv3x1x747" id="iddiv3x1x747"/>5.7.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x997" id="iddiv3x1x997"/>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.
@@ -459,7 +502,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="iddiv2x1x756" id="iddiv2x1x756"/>5.8 Filter Test - XPath 1.0</h3><p>
+<h3><a name="iddiv2x1x1006" id="iddiv2x1x1006"/>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:
@@ -475,13 +518,13 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x775" id="iddiv3x1x775"/>5.8.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1025" id="iddiv3x1x1025"/>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="iddiv3x1x780" id="iddiv3x1x780"/>5.8.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1030" id="iddiv3x1x1030"/>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.
@@ -493,7 +536,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x799" id="iddiv3x1x799"/>5.8.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1049" id="iddiv3x1x1049"/>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.
@@ -506,7 +549,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x808" id="iddiv2x1x808"/>5.9 Filter Test - XPath 2.0</h3><p>
+<h3><a name="iddiv2x1x1058" id="iddiv2x1x1058"/>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:
@@ -522,13 +565,13 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x827" id="iddiv3x1x827"/>5.9.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x1077" id="iddiv3x1x1077"/>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="iddiv3x1x832" id="iddiv3x1x832"/>5.9.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1082" id="iddiv3x1x1082"/>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.
@@ -540,7 +583,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x851" id="iddiv3x1x851"/>5.9.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x1101" id="iddiv3x1x1101"/>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.
@@ -553,7 +596,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x860" id="iddiv2x1x860"/>5.10 Non-Addressable Event Sink Test</h3><p>
+<h3><a name="iddiv2x1x1110" id="iddiv2x1x1110"/>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
@@ -574,7 +617,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="iddiv3x1x884" id="iddiv3x1x884"/>5.11 Sequence</h4><p>
+<h4><a name="iddiv3x1x1134" id="iddiv3x1x1134"/>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>
@@ -583,7 +626,7 @@
SubscribeResponse and UnsubscribeResponse are both transmitted on
the back-channel of their corresponding requests.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x896" id="iddiv3x1x896"/>5.12 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x1146" id="iddiv3x1x1146"/>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.
@@ -615,17 +658,17 @@
elicit a wsa:ActionNotSupported fault response or some other,
unspecified behavior.
</p></div></div><div class="div1">
-<h2><a name="iddiv1x1x924" id="iddiv1x1x924"/>6 WS-Transfer/WS-Fragment Tests</h2><p>
+<h2><a name="iddiv1x1x1174" id="iddiv1x1x1174"/>6 WS-Transfer/WS-Fragment Tests</h2><p>
...
</p></div><div class="div1">
-<h2><a name="iddiv1x1x929" id="iddiv1x1x929"/>7 WS-Enumeration Tests</h2><p>
+<h2><a name="iddiv1x1x1179" id="iddiv1x1x1179"/>7 WS-Enumeration Tests</h2><p>
...
</p></div><div class="div1">
<h2><a name="wsdl" id="wsdl"/>8 WSDL</h2><div class="div2">
-<h3><a name="iddiv2x1x938" id="iddiv2x1x938"/>8.1 Event Source WSDL</h3><p>
+<h3><a name="iddiv2x1x1188" id="iddiv2x1x1188"/>8.1 Event Source WSDL</h3><p>
TBD
</p></div><div class="div2">
-<h3><a name="iddiv2x1x943" id="iddiv2x1x943"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x1193" id="iddiv2x1x1193"/>8.2 Notification WSDL</h3><p>
TBD
</p></div></div><div class="div1">
<h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
@@ -665,7 +708,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="iddiv2x1x970" id="iddiv2x1x970"/>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="iddiv2x1x1220" id="iddiv2x1x1220"/>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.
@@ -686,13 +729,25 @@
</cite></a>
, M. Gudgin, M. Hadley, T. Rogers, Editors.
World Wide Web Consortium (W3C), 9 May 2006.
- Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</a>.</dd><dt class="label"><a name="Eventing" id="Eventing"/>WS-Eventing</dt><dd><a href="http://www.w3.org/TR/ws-eventing"><cite>
+ Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</a>.</dd><dt class="label"><a name="Enumeration" id="Enumeration"/>WS-Enumeration</dt><dd><a href="http://www.w3.org/TR/ws-enumeration"><cite>
+ W3C Working Group Draft, "Web Services Enumeration
+ (WS-Enumeration) 1.1"
+ </cite></a>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ Available at <a href="http://www.w3.org/TR/ws-enumeration">http://www.w3.org/TR/ws-enumeration</a>.</dd><dt class="label"><a name="Eventing" id="Eventing"/>WS-Eventing</dt><dd><a href="http://www.w3.org/TR/ws-eventing"><cite>
W3C Working Group Draft, "Web Services Eventing
(WS-Eventing) 1.1"
</cite></a>
, D. Davis, et al., Editors.
World Wide Web Consortium (W3C), 15 September 2009.
- Available at <a href="http://www.w3.org/TR/ws-eventing">http://www.w3.org/TR/ws-eventing</a>.</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
+ Available at <a href="http://www.w3.org/TR/ws-eventing">http://www.w3.org/TR/ws-eventing</a>.</dd><dt class="label"><a name="MetadataExchange" id="MetadataExchange"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+ W3C Working Group Draft, "Web Services Metadata Exchange
+ (WS-MetadataExchange) 1.1"
+ </cite></a>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ Available at <a href="http://www.w3.org/TR/ws-metadata-exchange">http://www.w3.org/TR/ws-metadata-exchange</a>.</dd><dt class="label"><a name="WSDL11" id="WSDL11"/>WSDL11</dt><dd><a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315"><cite>
W3C Note, "Web Services Description Language (WSDL) 1.1"
</cite></a>
, E. Christensen, et al., Editors.
Received on Thursday, 16 December 2010 15:11:54 UTC