- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 15 Dec 2010 13:38:01 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv4201
Modified Files:
scenario.html scenario.xml
Log Message:
add placeholders for the other tests
Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- scenario.xml 10 Dec 2010 03:23:21 -0000 1.2
+++ scenario.xml 15 Dec 2010 13:37:59 -0000 1.3
@@ -304,8 +304,16 @@
</div1>
- <div1 id="tests">
- <head>Tests</head>
+ <div1>
+ <head>WS-MetadataExchange Tests</head>
+
+ <p>
+ ...
+ </p>
+ </div1>
+
+ <div1 id="wsevt-tests">
+ <head>WS-Eventing Tests</head>
<p>
The following sub-sections describe tests designed to exercise all the
@@ -1356,6 +1364,22 @@
</div1>
+ <div1>
+ <head>WS-Transfer/WS-Fragment Tests</head>
+
+ <p>
+ ...
+ </p>
+ </div1>
+
+ <div1>
+ <head>WS-Enumeration Tests</head>
+
+ <p>
+ ...
+ </p>
+ </div1>
+
<div1 id="wsdl">
<head>WSDL</head>
Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/scenario.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- scenario.html 10 Dec 2010 03:23:21 -0000 1.2
+++ scenario.html 15 Dec 2010 13:37:59 -0000 1.3
@@ -52,25 +52,28 @@
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="#tests">Tests</a><br/>
- 4.1 <a href="#iddiv2x1x359">Basic Test</a><br/>
- 4.2 <a href="#iddiv2x1x416">Wrapped Notifications</a><br/>
- 4.3 <a href="#iddiv2x1x468">Duration Expiration Test</a><br/>
- 4.4 <a href="#iddiv2x1x523">Specific Time Expiration Test</a><br/>
- 4.5 <a href="#iddiv2x1x575">Best Effort Expiration Test</a><br/>
- 4.6 <a href="#iddiv2x1x627">Renew Test</a><br/>
- 4.7 <a href="#iddiv2x1x697">SubscriptionEnd Test</a><br/>
- 4.8 <a href="#iddiv2x1x751">Filter Test - XPath 1.0</a><br/>
- 4.9 <a href="#iddiv2x1x803">Filter Test - XPath 2.0</a><br/>
- 4.10 <a href="#iddiv2x1x855">Non-Addressable Event Sink Test</a><br/>
-5 <a href="#wsdl">WSDL</a><br/>
- 5.1 <a href="#iddiv2x1x923">Event Source WSDL</a><br/>
- 5.2 <a href="#iddiv2x1x928">Notification WSDL</a><br/>
-6 <a href="#evd">EventDescriptions</a><br/>
-7 <a href="#xsd">Schemas</a><br/>
-8 <a href="#acks">Acknowledgements</a><br/>
-9 <a href="#References">References</a><br/>
- 9.1 <a href="#iddiv2x1x955">Normative References</a><br/>
+4 <a href="#iddiv1x1x338">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/>
+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/>
+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/>
</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/>
@@ -131,7 +134,7 @@
an ID that uniquely identifies the tag and, by inference, the animal
that the tag is attached to. An EventDescriptions document that
describes the structure of the event information within the
- notifications can be found in <a href="#wsdl"><b>5 WSDL</b></a>.
+ 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>
While in the real world the frequency of notifications might be
@@ -144,7 +147,10 @@
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="tests" id="tests"/>4 Tests</h2><p>
+<h2><a name="iddiv1x1x338" id="iddiv1x1x338"/>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>
The following sub-sections describe tests designed to exercise all the
mandatory and optional features of WS-Eventing except for those
(such as the use of EventDescriptions or Notification WSDLs) that
@@ -164,15 +170,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="iddiv2x1x359" id="iddiv2x1x359"/>4.1 Basic Test</h3><p>
+<h3><a name="iddiv2x1x364" id="iddiv2x1x364"/>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="iddiv3x1x378" id="iddiv3x1x378"/>4.1.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x383" id="iddiv3x1x383"/>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="iddiv3x1x388" id="iddiv3x1x388"/>4.1.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x393" id="iddiv3x1x393"/>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.
@@ -183,7 +189,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x407" id="iddiv3x1x407"/>4.1.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x412" id="iddiv3x1x412"/>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>
@@ -194,16 +200,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="iddiv2x1x416" id="iddiv2x1x416"/>4.2 Wrapped Notifications</h3><p>
+<h3><a name="iddiv2x1x421" id="iddiv2x1x421"/>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="iddiv3x1x435" id="iddiv3x1x435"/>4.2.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x440" id="iddiv3x1x440"/>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="iddiv3x1x440" id="iddiv3x1x440"/>4.2.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x445" id="iddiv3x1x445"/>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.
@@ -214,7 +220,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x459" id="iddiv3x1x459"/>4.2.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x464" id="iddiv3x1x464"/>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.
@@ -225,7 +231,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="iddiv2x1x468" id="iddiv2x1x468"/>4.3 Duration Expiration Test</h3><p>
+<h3><a name="iddiv2x1x473" id="iddiv2x1x473"/>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:
@@ -238,12 +244,12 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x487" id="iddiv3x1x487"/>4.3.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x492" id="iddiv3x1x492"/>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="iddiv3x1x497" id="iddiv3x1x497"/>4.3.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x502" id="iddiv3x1x502"/>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.
@@ -258,7 +264,7 @@
HTTP error (i.e. '404') that indicates the Subscription Manager no
longer exists
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x516" id="iddiv3x1x516"/>4.3.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x521" id="iddiv3x1x521"/>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.
@@ -269,7 +275,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="iddiv2x1x523" id="iddiv2x1x523"/>4.4 Specific Time Expiration Test</h3><p>
+<h3><a name="iddiv2x1x528" id="iddiv2x1x528"/>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:
@@ -282,11 +288,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x542" id="iddiv3x1x542"/>4.4.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x547" id="iddiv3x1x547"/>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="iddiv3x1x547" id="iddiv3x1x547"/>4.4.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x552" id="iddiv3x1x552"/>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.
@@ -301,7 +307,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="iddiv3x1x566" id="iddiv3x1x566"/>4.4.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x571" id="iddiv3x1x571"/>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.
@@ -313,7 +319,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="iddiv2x1x575" id="iddiv2x1x575"/>4.5 Best Effort Expiration Test</h3><p>
+<h3><a name="iddiv2x1x580" id="iddiv2x1x580"/>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:
@@ -327,11 +333,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x594" id="iddiv3x1x594"/>4.5.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x599" id="iddiv3x1x599"/>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="iddiv3x1x599" id="iddiv3x1x599"/>4.5.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x604" id="iddiv3x1x604"/>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.
@@ -346,7 +352,7 @@
HTTP error (i.e. '404') that indicates the Subscription Manager
no longer exists.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x618" id="iddiv3x1x618"/>4.5.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x623" id="iddiv3x1x623"/>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
@@ -362,7 +368,7 @@
implement this test or to fail to meet one of the defined
success criteria.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x627" id="iddiv2x1x627"/>4.6 Renew Test</h3><p>
+<h3><a name="iddiv2x1x632" id="iddiv2x1x632"/>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:
@@ -379,11 +385,11 @@
</p><ul><li><p>
(short) expiration time chosen by Subscriber as xs:duration
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x652" id="iddiv3x1x652"/>4.6.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x657" id="iddiv3x1x657"/>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="iddiv3x1x662" id="iddiv3x1x662"/>4.6.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x667" id="iddiv3x1x667"/>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.
@@ -402,7 +408,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x690" id="iddiv3x1x690"/>4.6.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x695" id="iddiv3x1x695"/>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.
@@ -413,7 +419,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="iddiv2x1x697" id="iddiv2x1x697"/>4.7 SubscriptionEnd Test</h3><p>
+<h3><a name="iddiv2x1x702" id="iddiv2x1x702"/>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
@@ -427,11 +433,11 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x716" id="iddiv3x1x716"/>4.7.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x721" id="iddiv3x1x721"/>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="iddiv3x1x726" id="iddiv3x1x726"/>4.7.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x731" id="iddiv3x1x731"/>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.
@@ -441,7 +447,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="iddiv3x1x742" id="iddiv3x1x742"/>4.7.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x747" id="iddiv3x1x747"/>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.
@@ -453,7 +459,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="iddiv2x1x751" id="iddiv2x1x751"/>4.8 Filter Test - XPath 1.0</h3><p>
+<h3><a name="iddiv2x1x756" id="iddiv2x1x756"/>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:
@@ -469,13 +475,13 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x770" id="iddiv3x1x770"/>4.8.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x775" id="iddiv3x1x775"/>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="iddiv3x1x775" id="iddiv3x1x775"/>4.8.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x780" id="iddiv3x1x780"/>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.
@@ -487,7 +493,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x794" id="iddiv3x1x794"/>4.8.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x799" id="iddiv3x1x799"/>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.
@@ -500,7 +506,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x803" id="iddiv2x1x803"/>4.9 Filter Test - XPath 2.0</h3><p>
+<h3><a name="iddiv2x1x808" id="iddiv2x1x808"/>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:
@@ -516,13 +522,13 @@
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
-<h4><a name="iddiv3x1x822" id="iddiv3x1x822"/>4.9.1 Sequence</h4><p>
+<h4><a name="iddiv3x1x827" id="iddiv3x1x827"/>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="iddiv3x1x827" id="iddiv3x1x827"/>4.9.2 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x832" id="iddiv3x1x832"/>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.
@@ -534,7 +540,7 @@
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3">
-<h4><a name="iddiv3x1x846" id="iddiv3x1x846"/>4.9.3 Conformance</h4><p>
+<h4><a name="iddiv3x1x851" id="iddiv3x1x851"/>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.
@@ -547,7 +553,7 @@
request with either a wse:FilteringNotSupported fault or a
wse:FilteringRequestedUnavailable fault.
</p></div></div><div class="div2">
-<h3><a name="iddiv2x1x855" id="iddiv2x1x855"/>4.10 Non-Addressable Event Sink Test</h3><p>
+<h3><a name="iddiv2x1x860" id="iddiv2x1x860"/>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
@@ -568,7 +574,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="iddiv3x1x879" id="iddiv3x1x879"/>4.11 Sequence</h4><p>
+<h4><a name="iddiv3x1x884" id="iddiv3x1x884"/>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>
@@ -577,7 +583,7 @@
SubscribeResponse and UnsubscribeResponse are both transmitted on
the back-channel of their corresponding requests.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x891" id="iddiv3x1x891"/>4.12 Success Criteria</h4><ul><li><p>
+<h4><a name="iddiv3x1x896" id="iddiv3x1x896"/>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.
@@ -609,20 +615,26 @@
elicit a wsa:ActionNotSupported fault response or some other,
unspecified behavior.
</p></div></div><div class="div1">
-<h2><a name="wsdl" id="wsdl"/>5 WSDL</h2><div class="div2">
-<h3><a name="iddiv2x1x923" id="iddiv2x1x923"/>5.1 Event Source WSDL</h3><p>
+<h2><a name="iddiv1x1x924" id="iddiv1x1x924"/>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>
+ ...
+ </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>
TBD
</p></div><div class="div2">
-<h3><a name="iddiv2x1x928" id="iddiv2x1x928"/>5.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x943" id="iddiv2x1x943"/>8.2 Notification WSDL</h3><p>
TBD
</p></div></div><div class="div1">
-<h2><a name="evd" id="evd"/>6 EventDescriptions</h2><p>
+<h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
TBD
</p></div><div class="div1">
-<h2><a name="xsd" id="xsd"/>7 Schemas</h2><p>
+<h2><a name="xsd" id="xsd"/>10 Schemas</h2><p>
TBD
</p></div><div class="div1">
-<h2><a name="acks" id="acks"/>8 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>11 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Alessio Soldano (Red Hat),
@@ -652,8 +664,8 @@
Wu Chou (Avaya Communications),
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
-<h2><a name="References" id="References"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2x1x955" id="iddiv2x1x955"/>9.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>
+<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>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
Received on Wednesday, 15 December 2010 13:38:04 UTC