- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 09 Dec 2010 16:57:48 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv29394
Modified Files:
entitieswd.dtd
Added Files:
scenario.html scenario.xml
Log Message:
add scenario
Index: entitieswd.dtd
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/entitieswd.dtd,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- entitieswd.dtd 21 Apr 2010 01:49:56 -0000 1.17
+++ entitieswd.dtd 9 Dec 2010 16:57:45 -0000 1.18
@@ -12,6 +12,7 @@
<!ENTITY wsfra.nsprefix "&all.nsprefix;">
<!ENTITY wsevd.nsprefix "&all.nsprefix;">
<!ENTITY wssas.nsprefix "&all.nsprefix;">
+<!ENTITY scenario.nsprefix "&all.nsprefix;">
<!ENTITY all.year "2010">
<!ENTITY all.month "@@@@@">
@@ -131,6 +132,18 @@
<!ENTITY prev.wssas.day "&prev.all.day;">
<!ENTITY prev.wssas.dd "&prev.all.dd;">
+<!ENTITY scenario.year "&all.year;">
+<!ENTITY scenario.month "&all.month;">
+<!ENTITY scenario.mm "&all.mm;">
+<!ENTITY scenario.day "&all.day;">
+<!ENTITY scenario.dd "&all.dd;">
+
+<!ENTITY prev.scenario.year "&prev.all.year;">
+<!ENTITY prev.scenario.month "&prev.all.month;">
+<!ENTITY prev.scenario.mm "&prev.all.mm;">
+<!ENTITY prev.scenario.day "&prev.all.day;">
+<!ENTITY prev.scenario.dd "&prev.all.dd;">
+
<!ENTITY wsenu.short-status "&all.short-status;">
<!ENTITY wsevt.short-status "&all.short-status;">
<!ENTITY wsmex.short-status "&all.short-status;">
@@ -139,6 +152,7 @@
<!ENTITY wsfra.short-status "&all.short-status;">
<!ENTITY wsevd.short-status "&all.short-status;">
<!ENTITY wssas.short-status "&all.short-status;">
+<!ENTITY scenario.short-status "&all.short-status;">
<!ENTITY prev.wsenu.short-status "&prev.all.short-status;">
<!ENTITY prev.wsevt.short-status "&prev.all.short-status;">
@@ -148,6 +162,7 @@
<!ENTITY prev.wsfra.short-status "&prev.all.short-status;">
<!ENTITY prev.wsevd.short-status "&prev.all.short-status;">
<!ENTITY prev.wssas.short-status "&prev.all.short-status;">
+<!ENTITY prev.scenario.short-status "&prev.all.short-status;">
<!ENTITY wsenu.status "&all.status;">
<!ENTITY wsevt.status "&all.status;">
@@ -157,6 +172,7 @@
<!ENTITY wsfra.status "&all.status;">
<!ENTITY wsevd.status "&all.status;">
<!ENTITY wssas.status "&all.status;">
+<!ENTITY scenario.status "&all.status;">
<!ENTITY prev.wsenu.status "&prev.all.status;">
<!ENTITY prev.wsevt.status "&prev.all.status;">
@@ -166,6 +182,7 @@
<!ENTITY prev.wsfra.status "&prev.all.status;">
<!ENTITY prev.wsevd.status "&prev.all.status;">
<!ENTITY prev.wssas.status "&prev.all.status;">
+<!ENTITY prev.scenario.status "&prev.all.status;">
<!ENTITY wsenu.w3c-doctype "&all.w3c-doctype;">
<!ENTITY wsevt.w3c-doctype "&all.w3c-doctype;">
@@ -175,6 +192,7 @@
<!ENTITY wsfra.w3c-doctype "&all.w3c-doctype;">
<!ENTITY wsevd.w3c-doctype "&all.w3c-doctype;">
<!ENTITY wssas.w3c-doctype "&all.w3c-doctype;">
+<!ENTITY scenario.w3c-doctype "&all.w3c-doctype;">
<!ENTITY wsenu.role "&all.role;">
<!ENTITY wsevt.role "&all.role;">
@@ -184,6 +202,7 @@
<!ENTITY wsfra.role "&all.role;">
<!ENTITY wsevd.role "&all.role;">
<!ENTITY wssas.role "&all.role;">
+<!ENTITY scenario.role "&all.role;">
<!ENTITY wsenu.shortname "ws-enumeration">
<!ENTITY wsevt.shortname "ws-eventing">
@@ -193,6 +212,7 @@
<!ENTITY wsfra.shortname "ws-fragment">
<!ENTITY wsevd.shortname "ws-event-descriptions">
<!ENTITY wssas.shortname "ws-soap-assertions">
+<!ENTITY scenario.shortname "wsra-scenarios">
<!ENTITY wsenu.name "Web Services Enumeration (WS-Enumeration)">
<!ENTITY wsevt.name "Web Services Eventing (WS-Eventing)">
@@ -202,6 +222,7 @@
<!ENTITY wsfra.name "Web Services Fragment (WS-Fragment)">
<!ENTITY wsevd.name "Web Services Event Descriptions (WS-EventDescriptions)">
<!ENTITY wssas.name "Web Services SOAP Assertions (WS-SOAPAssertions)">
+<!ENTITY scenario.name "WSRA Scenario">
<!ENTITY wsenu.w3c-designation
"&wsenu.short-status;-&wsenu.shortname;-&wsenu.year;&wsenu.mm;&wsenu.dd;">
@@ -219,6 +240,8 @@
"&wsevd.short-status;-&wsevd.shortname;-&wsevd.year;&wsevd.mm;&wsevd.dd;">
<!ENTITY wssas.w3c-designation
"&wssas.short-status;-&wssas.shortname;-&wssas.year;&wssas.mm;&wssas.dd;">
+<!ENTITY scenario.w3c-designation
+ "&scenario.short-status;-&scenario.shortname;-&scenario.year;&scenario.mm;&scenario.dd;">
<!ENTITY prev.wsenu.w3c-designation
"&prev.wsenu.short-status;-&wsenu.shortname;-&prev.wsenu.year;&prev.wsenu.mm;&prev.wsenu.dd;">
@@ -236,6 +259,8 @@
"&prev.wsevd.short-status;-&wsevd.shortname;-&prev.wsevd.year;&prev.wsevd.mm;&prev.wsevd.dd;">
<!ENTITY prev.wssas.w3c-designation
"&prev.wssas.short-status;-&wssas.shortname;-&prev.wssas.year;&prev.wssas.mm;&prev.wssas.dd;">
+<!ENTITY prev.scenario.w3c-designation
+ "&prev.scenario.short-status;-&scenario.shortname;-&prev.scenario.year;&prev.scenario.mm;&prev.scenario.dd;">
<!ENTITY wsenu.dated "http://www.w3.org/TR/&wsenu.year;/&wsenu.w3c-designation;">
@@ -246,6 +271,7 @@
<!ENTITY wsfra.dated "http://www.w3.org/TR/&wsfra.year;/&wsfra.w3c-designation;">
<!ENTITY wsevd.dated "http://www.w3.org/TR/&wsevd.year;/&wsevd.w3c-designation;">
<!ENTITY wssas.dated "http://www.w3.org/TR/&wssas.year;/&wssas.w3c-designation;">
+<!ENTITY scenario.dated "http://www.w3.org/TR/&scenario.year;/&scenario.w3c-designation;">
<!ENTITY prev.wsenu.dated "http://www.w3.org/TR/&prev.wsenu.year;/&prev.wsenu.w3c-designation;">
<!ENTITY prev.wsevt.dated "http://www.w3.org/TR/&prev.wsevt.year;/&prev.wsevt.w3c-designation;">
@@ -255,5 +281,6 @@
<!ENTITY prev.wsfra.dated "http://www.w3.org/TR/&prev.wsfra.year;/&prev.wsfra.w3c-designation;">
<!ENTITY prev.wsevd.dated "http://www.w3.org/TR/&prev.wsevd.year;/&prev.wsevd.w3c-designation;">
<!ENTITY prev.wssas.dated "http://www.w3.org/TR/&prev.wssas.year;/&prev.wssas.w3c-designation;">
+<!ENTITY prev.scenario.dated "http://www.w3.org/TR/&prev.scenario.year;/&prev.scenario.w3c-designation;">
--- NEW FILE: scenario.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='xmlspec.xsl'?>
<!DOCTYPE spec PUBLIC "-//W3C//DTD Specification V2.1//EN" "xmlspec.dtd" [
<!ENTITY % entities SYSTEM "entitieswd.dtd" >
%entities;
<!ENTITY status "&scenario.status;" >
<!ENTITY short-status "&scenario.short-status;" >
]>
<spec w3c-doctype="&scenario.w3c-doctype;" role="&scenario.role;">
<header>
<title>&scenario.name;</title>
<w3c-designation>&scenario.w3c-designation;</w3c-designation>
<w3c-doctype>"&scenario.w3c-doctype;</w3c-doctype>
<pubdate>
<day>&scenario.day;</day>
<month>&scenario.month;</month>
<year>&scenario.year;</year>
</pubdate>
[...1565 lines suppressed...]
<td>
Editorial fixes. Changed animal names in honor of the Irish
light-bellied Brent Geese tracked by the WWT (http://www.wwt.org.uk/).
</td>
</tr>
<tr>
<td> 2010/10/30 </td>
<td> GP </td>
<td>
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>
</tbody>
</table>
</div1>
</back>
</spec>
--- NEW FILE: scenario.html ---
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml" lang="en"><head><title>WSRA Scenario</title><style type="text/css">
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
<h1><a name="title" id="title"/>WSRA Scenario</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date: 2010/12/09 16:57:45 $</h2><dl><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/wsra-scenarios">http://www.w3.org/TR/wsra-scenarios
</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-wsra-scenarios-20090317">http://www.w3.org/TR/2009/WD-wsra-scenarios-20090317
</a></dd><dt>Editor:</dt><dd>Gilert Pilz, Oracle</dd></dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
The following scenario is designed to provide a framework in which to
test the interoperability of various WS-Eventing implementations. Because
this scenario and the tests defined within it will be used to judge
which features of WS-Eventing are implemented and which are not, the
feature coverage is intended to be complete.
</p></div><div>
<h2><a name="status" id="status"/>Status of this Document</h2><p><strong>This document is an editors' copy that has
no official standing.</strong></p></div><div class="toc">
<h2><a name="contents" id="contents"/>Table of Contents</h2><p class="toc">1 <a href="#dependencies">Dependencies</a><br/>
1.1 <a href="#scope">Scope</a><br/>
1.2 <a href="#namespaces">XML Namespaces</a><br/>
1.3 <a href="#preconditions">Preconditions</a><br/>
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="#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/>
</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/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="dependencies" id="dependencies"/>1 Dependencies</h2><div class="div2">
<h3><a name="scope" id="scope"/>1.1 Scope</h3><p>
The following specifications and technologies are in scope for this
scenario:
</p><ul><li><p>SOAP 1.1</p></li><li><p>WS-Eventing</p></li><li><p>WS-EventDescription</p></li><li><p>WS-MakeConnection</p></li><li><p>WS-Policy</p></li><li><p>WSDL 1.1</p></li></ul></div><div class="div2">
<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-Eventin]</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">
<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
terminology used in this specification.
</p><div class="div2">
<h3><a name="conventions" id="conventions"/>2.1 Notational Conventions</h3><p>
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
RFC 2119 <a href="#RFC2119">[RFC 2119]</a>.
</p><p>
This specification uses the following syntax to define
normative outlines for messages:
</p><ul><li><p>
The syntax appears as an XML instance, but values in
italics indicate data types instead of values.
</p></li><li><p>
Characters are appended to elements and attributes to
indicate cardinality:
</p><ul><li><p>"?" (0 or 1)</p></li><li><p>"*" (0 or more)</p></li><li><p>"+" (1 or more)</p></li></ul></li><li><p>
The character "|" is used to indicate a choice between
alternatives.
</p></li><li><p>
The characters "(" and ")" are used to indicate that contained items
are to be treated as a group with respect to cardinality or choice.
</p></li><li><p>
The characters "[" and "]" are used to call out references and
property names.
</p></li><li><p>
Ellipsis (i.e. "...") indicate a point of extensibility.
</p></li></ul></div></div><div class="div1">
<h2><a name="description" id="description"/>3 Scenario Description</h2><p>
This scenario presupposes a cetacean tracking system in which a number
of animals have been 'tagged' with devices that track their location.
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>
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
(latitude, longitude, elevation, and time), the notifications include
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>.
</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
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="tests" id="tests"/>4 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
affect only the process of developing one or more of the components
of a WS-Eventing-based system.
</p><p>
Each of these sub-sections is organized into four parts:
</p><ul><li><p>
An overview that describes the purpose of the test and the
salient features of the messages that are exchanged.
</p></li><li><p>
A sequence diagram that illustrates the sequence of events in the test.
</p></li><li><p>
A list of criteria used to judge the success of the test.
</p></li><li><p>
A conformance section that enumerates the conditions under which
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>
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>
The following diagram illustrates the sequence of messages for the
Basic Test.
</p><img src="images/basic_test_sequence.jpg"/></div><div class="div3">
<h4><a name="iddiv3x1x388" id="iddiv3x1x388"/>4.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.
</p></li><li><p>
Receipt of one or more unwrapped Notifications by the Event Sink.
</p></li><li><p>
Receipt of a valid Unsubscribe message by the Subscription Manager.
</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>
Because this test involves only operations and elements that are
required, there are no allowable failure cases.
</p><p>
Any failure to meet the above success criteria indicates that either,
or both, of the implementations participating in the test do not
conform to WS-Eventing.
</p><p>
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>
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>
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>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
Receipt of one or more wrapped Notifications by the Event Sink.
</p></li><li><p>
Receipt of a valid Unsubscribe message by the Subscription Manager.
</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>
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.
</p><p>
A conforming Subscriber/Event Sink MAY NOT be capable of implementing
this test due to its inability to support wrapped notifications.
</p><p>
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>
This test verifies the correct implementation of the expiration feature
on the Event Source/Subscription Manager. The initial Subscribe message
has the following features:
</p><ul><li><p>
(short) expiration time chosen by Subscriber as xs:duration
</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="iddiv3x1x487" id="iddiv3x1x487"/>4.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>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
Receipt of one or more unwrapped Notifications by the Event Sink.
</p></li><li><p>
Receipt of a valid GetStatus message by the Subscription Manager.
</p></li><li><p>
Receipt, by the Subscriber, of either the 'UnknownSubscription'
fault (defined by Section 6.10 of WS-Eventing), a SOAP fault that
indicates that the Subscription Manager no longer exists, or an
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>
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.
</p><p>
Note that, because wse:Expires is sender-optional and support for
xs:duration is required, there are no valid reasons for a
conforming Event Source/Subscription Manager implementation to either
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>
This test verifies the correct implementation of the expiration feature
on the Event Source/Subscription Manager. The initial Subscribe
request has the following features:
</p><ul><li><p>
(short) expiration time chosen by Subscriber as xs:dateTime
</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="iddiv3x1x542" id="iddiv3x1x542"/>4.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>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
Receipt of one or more unwrapped Notifications by the Event Sink.
</p></li><li><p>
Receipt of a valid GetStatus message by the Subscription Manager.
</p></li><li><p>
Receipt, by the Subscriber, of either the 'UnknownSubscription'
fault (defined by Section 6.10 of WS-Eventing), a SOAP fault that
indicates that the Subscription Manager no longer exists, or
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>
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.
</p><p>
A conforming Subscriber MAY NOT be capable of implementing this test
either due to its inability to support the wse:Expires element or
the xs:dateTime type.
</p><p>
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>
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:
</p><ul><li><p>
expiration time chosen by Subscriber as xs:duration with
@BestEffort ='true'
</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="iddiv3x1x594" id="iddiv3x1x594"/>4.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>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
Receipt of one or more unwrapped Notifications by the Event Sink.
</p></li><li><p>
Receipt of a valid GetStatus message by the Subscription Manager.
</p></li><li><p>
Receipt, by the Subscriber, of either the 'UnknownSubscription'
fault (defined by Section 6.10 of WS-Eventing), a SOAP fault that
indicates that the Subscription Manager no longer exists, or an
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>
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
conforming behavior.
</p><p>
A conforming Subscriber MAY NOT be capable of implementing this test
either due to its inability to support the wse:Expires element or
the BestEffort attribute.
</p><p>
Note that, because both wse:Expires and BestEffort are
sender-optional, there are no valid reasons for a conforming Event
Source/Subscription Manager implementation to either 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="iddiv2x1x627" id="iddiv2x1x627"/>4.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:
</p><ul><li><p>
(short) expiration time chosen by Subscriber as xs:duration
</p></li><li><p>
no EndTo EPR
</p></li><li><p>
no Filter
</p></li><li><p>
unwrapped notifications
</p></li></ul><p>
The Renew request has the following features:
</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>
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>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
Receipt of one or more wrapped Notifications by the Event Sink.
</p></li><li><p>
Prior to the expiration time elapsing, receipt of a valid Renew
message by the Subscription Manager.
</p></li><li><p>
Receipt of a valid RenewResponse message by the Subscriber.
</p></li><li><p>
Subsequent to the Renew/RenewResponse exchange, receipt of one or
more wrapped Notifications by the Event Sink.
</p></li><li><p>
Receipt of a valid Unsubscribe message by the Subscription Manager.
</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>
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.
</p><p>
Note that, because wse:Expires is sender-optional and support for
xs:duration is required, there are no valid reasons for a conforming
Event Source/Subscription Manager implementation to either 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="iddiv2x1x697" id="iddiv2x1x697"/>4.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
following features:
</p><ul><li><p>
expiration time chosen by Event Source/Subscription Manager
</p></li><li><p>
EndTo EPR
</p></li><li><p>
no Filters
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
<h4><a name="iddiv3x1x716" id="iddiv3x1x716"/>4.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>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by the Subscriber.
</p></li><li><p>
Receipt of one or more wrapped Notifications by the Event Sink.
</p></li><li><p>
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>
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.
</p><p>
A conforming Subscriber/Event Sink MAY NOT be capable of implementing
this test due to its inability to support the wse:EndTo element or
the SubscriptionEnd message.
</p><p>
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>
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:
</p><ul><li><p>
expiration time chosen by Event Source/Subscription Manager
</p></li><li><p>
no EndTo EPR
</p></li><li><p>
Filter in dialect 'http://www.w3.org/2010/08/ws-evt/Dialects/XPath10'
that selects those events that apply to tag
234b6840-de3d-11df-85ca-0800200c9a66 (Kerry).
(TBD - add exact filter expression)
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
<h4><a name="iddiv3x1x770" id="iddiv3x1x770"/>4.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>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
Receipt of one or more unwrapped Notifications for the tag
234b6840-de3d-11df-85ca-0800200c9a66 by the Event Sink.
</p></li><li><p>
Receipt of a valid Unsubscribe message by the Subscription Manager.
</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>
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.
</p><p>
A conforming Subscriber/Event Sink MAY NOT be capable of implementing
this test due to its inability to support the wse:Filter element
or the XPath 1.0 dialect.
</p><p>
A conforming Event Source MAY respond to the initial Subscribe
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>
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:
</p><ul><li><p>
expiration time chosen by Event Source/Subscription Manager
</p></li><li><p>
no EndTo EPR
</p></li><li><p>
Filter in dialect 'http://www.w3.org/2010/08/ws-evt/Dialects/XPath20'
that selects those events that apply to tag
32675b90-de3d-11df-85ca-0800200c9a66 (Oscar).
(TBD - add exact filter expression)
</p></li><li><p>
unwrapped notifications
</p></li></ul><div class="div3">
<h4><a name="iddiv3x1x822" id="iddiv3x1x822"/>4.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>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
Receipt of one or more unwrapped Notifications for the tag
32675b90-de3d-11df-85ca-0800200c9a66 by the Event Sink.
</p></li><li><p>
Receipt of a valid Unsubscribe message by the Subscription Manager.
</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>
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.
</p><p>
A conforming Subscriber/Event Sink MAY NOT be capable of
implementing this test due to its inability to support the
wse:Filter element or the XPath 2.0 dialect.
</p><p>
A conforming Event Source MAY respond to the initial Subscribe
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>
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
non-addressable). The facilities described by WS-MakeConnection are
used by the Event Sink to poll for Notifications from the Event Source.
</p><p>
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><li><p>
the value of wse:Delivery/wse:NotifyTo/wsa:Address is an instance of
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>
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>
Note that the MakeConnection requests that follow both the Subscribe
and the Unsubscribe requests are optional. It may happen that the
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>
Receipt of a valid Subscribe message by the Event Source.
</p></li><li><p>
Receipt of a valid SubscribeResponse message by Subscriber.
</p></li><li><p>
Receipt of one or more unwrapped Notifications by the Event Sink.
</p></li><li><p>
Receipt of a valid Unsubscribe message by the Subscription Manager.
</p></li><li><p>
Receipt of a valid UnsubscribeResponse message by the Subscriber.
</p></li></ul></div><div class="div3"><p>
Because this test involves the use of WS-MakeConnection there are
a number of failure cases that fall within the boundaries of
conforming behavior.
</p><p>
A conforming Subscriber/Event Sink MAY NOT be capable of
implementing this test due to its inability to support
WS-MakeConnection.
</p><p>
A conforming Event Source MAY respond to the initial Subscribe
request with a wse:UnusableEPR fault. However, because WS-Eventing
does not require Event Sources to validate the NotifyTo EPR at
subscribe-time, it MAY be that the Subscribe request succeeds
(although the SubscribeResponse is never delivered to the
Subscriber) but Notifications are simply not delivered to the
Event Sink.
</p><p>
Because Event Sinks and Subscription Managers are not required
to implment WS-MakeConnection, the MakeConnection requests MAY
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>
TBD
</p></div><div class="div2">
<h3><a name="iddiv2x1x928" id="iddiv2x1x928"/>5.2 Notification WSDL</h3><p>
TBD
</p></div></div><div class="div1">
<h2><a name="evd" id="evd"/>6 EventDescriptions</h2><p>
TBD
</p></div><div class="div1">
<h2><a name="xsd" id="xsd"/>7 Schemas</h2><p>
TBD
</p></div><div class="div1">
<h2><a name="acks" id="acks"/>8 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Alessio Soldano (Red Hat),
Ashok Malhotra (Oracle Corp.),
Asir Vedamuthu (Microsoft Corp.),
Bob Freund (Hitachi, Ltd.),
Bob Natale (MITRE Corp.),
David Snelling (Fujitsu, Ltd.),
Doug Davis (IBM),
Fred Maciel (Hitachi, Ltd.),
Geoff Bullen (Microsoft Corp.),
Gilbert Pilz (Oracle Corp.),
Greg Carpenter (Microsoft Corp.),
Jeff Mischkinsky (Oracle Corp.),
Katy Warr (IBM),
Li Li (Avaya Communications),
Mark Little (Red Hat),
Martin Chapman (Oracle Corp.),
Paul Fremantle (WSO2),
Paul Nolan (IBM),
Prasad Yendluri (Software AG),
Ram Jeyaraman (Microsoft Corp.),
Sreedhara Narayanaswamy (CA),
Sumeet Vij (Software AG),
Tom Rutt (Fujitsu, Ltd.),
Vikas Varma (Software AG),
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>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
Internet Engineering Task Force, March 1997.
Available at <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</cite></a>
, D. Box, et al, Editors.
World Wide Web Consortium (W3C), 8 May 2000.
Available at <a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/">http://www.w3.org/TR/2000/NOTE-SOAP-20000508/</a>.</dd><dt class="label"><a name="SOAP12" id="SOAP12"/>SOAP12</dt><dd><a href="http://www.w3.org/TR/soap12-part1/"><cite>
W3C Recommendation, "SOAP Version 1.2 Part 1: Messaging Framework"
</cite></a>
, M. Gudgin, M. Hadley, N. Mendelsohn, J-J. Moreau, H. Frystyk Nielson,
Editors.
World Wide Web Consortium (W3C), 27 April 2007.
Available at <a href="http://www.w3.org/TR/soap12-part1/">http://www.w3.org/TR/soap12-part1/</a>.</dd><dt class="label"><a name="AddrCore" id="AddrCore"/>WS-Addressing</dt><dd><a href="http://www.w3.org/TR/ws-addr-core"><cite>
W3C Recommendation, "Web Services Addressing 1.0 (WS-Addressing)"
</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>
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>
W3C Note, "Web Services Description Language (WSDL) 1.1"
</cite></a>
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"/>XMLSchema - Part 1</dt><dd><a href="http://www.w3.org/TR/xmlschema-1/"><cite>
W3C Recommendation, "XML Schema Part 1: Structures (Second Edition)"
</cite></a>
, H. Thompson, et al., Editors.
World Wide Web Consortium (W3C), 28 October 2004.
Available at <a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>.</dd><dt class="label"><a name="XMLSchema2" id="XMLSchema2"/>XMLSchema - Part 2</dt><dd><a href="http://www.w3.org/TR/xmlschema-2/"><cite>
W3C Recommendation, "XML Schema Part 2: Datatypes (Second Edition)"
</cite></a>
, P. Biron, A. Malhotra, Editors.
World Wide Web Consortium (W3C), 28 October 2004.
Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div></div></div><div class="back"><div class="div1">
<h2><a name="Appendix-A" id="Appendix-A"/>A XML Schema</h2><p>
A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
retrieved from the following address:
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-sas/soapassertions.xsd">http://www.w3.org/2002/ws/ra/edcopies/ws-sas/soapassertions.xsd</a></pre></div></div><p>
A non-normative copy of the XML schema is listed below for convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
targetNamespace='http://www.w3.org/2002/ws/ra/edcopies/ws-sas'
xmlns:tns='http://www.w3.org/2002/ws/ra/edcopies/ws-sas'
xmlns:xs='http://www.w3.org/2001/XMLSchema'
elementFormDefault='qualified'
blockDefault='#all' >
<xs:complexType name='emptyElementType'>
<xs:sequence>
<xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded'/>
</xs:sequence>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
<xs:element name='SOAP11' type='tns:emptyElementType'/>
<xs:element name='SOAP12' type='tns:emptyElementType'/>
</xs:schema></pre></div></div></div><div class="div1">
<h2><a name="changelog" id="changelog"/>B Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2010/10/26 </td><td> GP </td><td>
Initial revision
</td></tr><tr><td> 2010/10/27 </td><td> GP </td><td>
Fleshed out Basic, Wrapped, and Expiration tests; added sequence
diagrams. Added stubs for Renew and Non-Addressable Event Sink tests.
</td></tr><tr><td> 2010/10/28 </td><td> GP </td><td>
Editorial fixes. Changed animal names in honor of the Irish
light-bellied Brent Geese tracked by the WWT (http://www.wwt.org.uk/).
</td></tr><tr><td> 2010/10/30 </td><td> GP </td><td>
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></tbody></table></div></div></body></html>
Received on Thursday, 9 December 2010 16:57:51 UTC