You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3055 lines
174 KiB
3055 lines
174 KiB
<?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" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Web Services Eventing (WS-Eventing)</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/W3C-REC.css" /></head><body><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72" /></a></p>
|
|
<h1><a name="title" id="title"></a>Web Services Eventing (WS-Eventing)</h1>
|
|
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Recommendation 13 December 2011</h2><dl><dt>This version:</dt><dd>
|
|
<a href="http://www.w3.org/TR/2011/REC-ws-eventing-20111213">http://www.w3.org/TR/2011/REC-ws-eventing-20111213
|
|
</a>
|
|
</dd><dt>Latest version:</dt><dd>
|
|
<a href="http://www.w3.org/TR/ws-eventing">http://www.w3.org/TR/ws-eventing
|
|
</a>
|
|
</dd><dt>Previous version:</dt><dd>
|
|
<a href="http://www.w3.org/TR/2011/PR-ws-eventing-20110927">http://www.w3.org/TR/2011/PR-ws-eventing-20110927
|
|
</a>
|
|
</dd><dt>Editors:</dt><dd>Doug Davis, IBM</dd><dd>Ashok Malhotra, Oracle</dd><dd>Katy Warr, IBM</dd><dd>Wu Chou, Avaya</dd></dl><p>Please refer to the <a href="http://www.w3.org/2002/ws/ra/errata/ws-eventing-20111213-errata"><strong>errata</strong></a> for this document, which may
|
|
include normative corrections.</p><p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=ws-eventing"><strong>translations</strong></a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <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"></a>Abstract</h2><p>
|
|
This specification describes a protocol that allows Web
|
|
services to subscribe to or accept subscriptions for
|
|
notification messages.
|
|
</p></div><div>
|
|
<h2><a name="status" id="status"></a>Status of this Document</h2><p><em>
|
|
This section describes the status of this document at the time
|
|
of its publication. Other documents may supersede this document.
|
|
A list of current W3C publications and the latest revision of
|
|
this technical report can be found in the
|
|
<a href="http://www.w3.org/TR/">W3C technical reports index</a>
|
|
at http://www.w3.org/TR/.
|
|
</em></p><p>
|
|
This is the 13 December 2011 Recommendation of the <em>Web Services Eventing (WS-Eventing)</em> specification.
|
|
It has been produced by the
|
|
<a href="http://www.w3.org/2002/ws/ra/">Web
|
|
Services Resource Access Working Group</a> (WG), which is part of the
|
|
<a href="http://www.w3.org/2002/ws/Activity">W3C Web Services
|
|
Activity</a>.
|
|
</p><p>
|
|
The public is encouraged to send comments to the Working Group's public mailing list
|
|
<a href="mailto:public-ws-resource-access-comments@w3.org">
|
|
public-ws-resource-access-comments@w3.org</a>
|
|
mailing list (<a href="http://lists.w3.org/Archives/Public/public-ws-resource-access-comments/">public
|
|
archive</a>). See <a href="http://www.w3.org/Mail/">W3C mailing list and archive usage guidelines</a>.
|
|
</p><p>No substantive changes were made as a result of the Proposed Recommendation phase (see also <a href="diff-ws-evt.html">diff</a>, <a href="http://www.w3.org/2002/ws/ra/test/scenario.html">test scenario</a> and <a href="http://www.w3.org/2002/ws/ra/test/testResults.html">implementation report</a>).</p><p>This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.</p><p>
|
|
This document was produced by a group operating under the
|
|
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
|
|
February 2004 W3C Patent Policy</a>. W3C maintains a
|
|
<a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/43088/status">public
|
|
list of any patent disclosures</a> made in connection with the
|
|
deliverables of the group; that page also includes instructions for
|
|
disclosing a patent. An individual who has actual knowledge of a
|
|
patent which the individual believes contains
|
|
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
|
|
Claim(s)</a> must disclose the information in accordance with
|
|
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
|
|
6 of the W3C Patent Policy</a>.
|
|
</p></div><div class="toc">
|
|
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#composable">Composable Architecture</a><br />
|
|
2 <a href="#intro">Introduction</a><br />
|
|
2.1 <a href="#reqs">Requirements</a><br />
|
|
2.2 <a href="#Delivery">Delivery</a><br />
|
|
2.3 <a href="#NotificationFormats">Notification Formats</a><br />
|
|
2.4 <a href="#SubMgr">Subscription Managers</a><br />
|
|
2.5 <a href="#example">Example</a><br />
|
|
3 <a href="#notterms">Notations and Terminology</a><br />
|
|
3.1 <a href="#conventions">Notational Conventions</a><br />
|
|
3.2 <a href="#extensions">Considerations on the Use of Extensibility Points</a><br />
|
|
3.3 <a href="#terms">Terminology</a><br />
|
|
3.4 <a href="#compliance">Compliance</a><br />
|
|
3.5 <a href="#namespaces">XML Namespaces</a><br />
|
|
4 <a href="#SubMsgs">Subscription Messages</a><br />
|
|
4.1 <a href="#Subscribe">Subscribe</a><br />
|
|
4.2 <a href="#Renew">Renew</a><br />
|
|
4.3 <a href="#GetStatus">GetStatus</a><br />
|
|
4.4 <a href="#Unsubscribe">Unsubscribe</a><br />
|
|
4.5 <a href="#SubscriptionEnd">SubscriptionEnd</a><br />
|
|
5 <a href="#Notifications">Notifications</a><br />
|
|
6 <a href="#Faults">Faults</a><br />
|
|
6.1 <a href="#FaultDetailRetryElement">Fault Detail RetryAfter Element</a><br />
|
|
6.2 <a href="#UnsupportedExpirationValue">UnsupportedExpirationValue</a><br />
|
|
6.3 <a href="#UnsupportedExpirationType">UnsupportedExpirationType</a><br />
|
|
6.4 <a href="#FilteringNotSupported">FilteringNotSupported</a><br />
|
|
6.5 <a href="#FilteringRequestedUnavailable">FilteringRequestedUnavailable</a><br />
|
|
6.6 <a href="#DeliveryFormatRequestedUnavailable">DeliveryFormatRequestedUnavailable</a><br />
|
|
6.7 <a href="#EmptyFilter">EmptyFilter</a><br />
|
|
6.8 <a href="#UnusableEPR">UnusableEPR</a><br />
|
|
6.9 <a href="#UnknownSubscription">UnknownSubscription</a><br />
|
|
6.10 <a href="#EndToNotSupported">EndToNotSupported</a><br />
|
|
6.11 <a href="#NoDeliveryMechanismEstablished">NoDeliveryMechanismEstablished</a><br />
|
|
6.12 <a href="#CannotProcessFilter">CannotProcessFilter</a><br />
|
|
7 <a href="#Security">Security Considerations</a><br />
|
|
7.1 <a href="#idp1706496">Notifications</a><br />
|
|
7.2 <a href="#idp1709584">Subscriptions</a><br />
|
|
7.3 <a href="#idp1711632">Endpoint Verification</a><br />
|
|
8 <a href="#ImplConsideration">Implementation Considerations</a><br />
|
|
9 <a href="#metadata">WS-Eventing Metadata</a><br />
|
|
9.1 <a href="#idp1720480">EventSource Assertion</a><br />
|
|
9.2 <a href="#idp1753440">SubscriptionManager Assertion</a><br />
|
|
10 <a href="#acks">Acknowledgements</a><br />
|
|
11 <a href="#refs">References</a><br />
|
|
11.1 <a href="#idp1771456">Normative References</a><br />
|
|
11.2 <a href="#idp1812592">Informative References</a><br />
|
|
</p>
|
|
<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br />
|
|
A.1 <a href="#ETypes">Event Types & Event Descriptions</a><br />
|
|
A.1.1 <a href="#idp1852112">Retrieving Event Descriptions</a><br />
|
|
A.1.2 <a href="#idp1866096">Bindings for Event Descriptions</a><br />
|
|
A.1.2.1 <a href="#idp1867904">Binding for Unwrapped Notifications</a><br />
|
|
A.1.2.2 <a href="#idp1872992">Binding for Wrapped Notifications</a><br />
|
|
A.2 <a href="#NWSDL">Notification WSDLs</a><br />
|
|
A.2.1 <a href="#idp1881200">Retrieving Notification WSDLs</a><br />
|
|
B <a href="#Schema">XML Schema</a><br />
|
|
C <a href="#WSDL">WSDL</a><br />
|
|
D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br />
|
|
E <a href="#actiontables">Action Tables</a><br />
|
|
F <a href="#changelog">Change Log</a><br />
|
|
</p></div><hr /><div class="body"><div class="div1">
|
|
<h2><a name="composable" id="composable"></a>1 Composable Architecture</h2><p>
|
|
By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
|
|
<a href="#SOAP12">[SOAP12]</a>, and WSDL <a href="#WSDL11">[WSDL11]</a>
|
|
extensibility models, the Web service
|
|
specifications (WS-*) are designed to be composed with each other
|
|
to provide a rich set of tools for the Web
|
|
services environment. This specification specifically relies on
|
|
other Web service specifications to provide secure, reliable,
|
|
and/or transacted message delivery and to express Web service and
|
|
client policy.
|
|
</p></div><div class="div1">
|
|
<h2><a name="intro" id="intro"></a>2 Introduction</h2><p>
|
|
Web services often want to receive messages when events occur
|
|
in other services and applications. A mechanism for registering
|
|
interest is needed because the set of Web services interested in
|
|
receiving such messages is often unknown in advance or will
|
|
change over time. This specification defines a protocol for one
|
|
Web service (called a "subscriber") to register interest (called
|
|
a "subscription") with another Web service (called an "event
|
|
source") in receiving messages about events (called
|
|
"notifications"). The subscriber can manage
|
|
the subscription by interacting with a Web service (called the
|
|
"subscription manager") designated by the event source.
|
|
</p><p>
|
|
To improve robustness, a subscription can be leased by an
|
|
event source to a subscriber, and the subscription expires over
|
|
time. The subscription manager provides the ability for the
|
|
subscriber to renew or cancel the subscription before it
|
|
expires.
|
|
</p><p>
|
|
There are many mechanisms by which notifications can be delivered
|
|
to event sinks. This specification provides an extensible
|
|
way for subscribers to identify the delivery mechanism they
|
|
prefer.
|
|
</p><div class="div2">
|
|
<h3><a name="reqs" id="reqs"></a>2.1 Requirements</h3><p>
|
|
This specification intends to meet the following requirements:
|
|
</p><ul><li><p>
|
|
Define means to create and cancel event subscriptions.
|
|
</p></li><li><p>
|
|
Define expiration for subscriptions and allow them to be renewed.
|
|
</p></li><li><p>
|
|
Define how one Web service can subscribe on behalf of another.
|
|
</p></li><li><p>
|
|
Define how an event source delegates subscription
|
|
management to another Web service.
|
|
</p></li><li><p>
|
|
Allow subscribers to specify how notifications are to be delivered.
|
|
</p></li><li><p>
|
|
Leverage other Web service specifications for secure,
|
|
reliable, transacted message delivery.
|
|
</p></li><li><p>
|
|
Support complex eventing topologies that allow the
|
|
originating event source and the final event sink to be
|
|
decoupled.
|
|
</p></li><li><p>
|
|
Provide extensibility for more sophisticated and/or
|
|
currently unanticipated subscription scenarios.
|
|
</p></li><li><p>
|
|
Support a variety of encoding formats, including (but not
|
|
limited to) both SOAP 1.1 <a href="#SOAP11">[SOAP11]</a>
|
|
and SOAP 1.2 <a href="#SOAP12">[SOAP12]</a> Envelopes.
|
|
</p></li></ul></div><div class="div2">
|
|
<h3><a name="Delivery" id="Delivery"></a>2.2 Delivery</h3><p>
|
|
This specification defines a method for transmitting notifications
|
|
to the event sink through the use of the wse:NotifyTo element. Other
|
|
methods or combination of methods MAY be defined through the use
|
|
of delivery extensions.
|
|
</p><p>
|
|
When the wse:NotifyTo element is used within the Delivery element it
|
|
specifies the endpoint to which notifications are sent. For delivery
|
|
to addressable endpoints this is sufficient. However, for
|
|
non-addressable endpoints some additional mechanisms are needed. A
|
|
subscription manager MAY choose to support mechanisms, such as the
|
|
<a href="#WSMC">[WS-MakeConnection]</a> specification, to enable delivery of
|
|
notifications and the SubscriptionEnd message to non-addressable
|
|
endpoints. See the
|
|
<a href="#WSMC">[WS-MakeConnection]</a> specification for more information, and an
|
|
example, of how this would work.
|
|
</p></div><div class="div2">
|
|
<h3><a name="NotificationFormats" id="NotificationFormats"></a>2.3 Notification Formats</h3><p>
|
|
This specification does not mandate how events are serialized into
|
|
notification messages. Rather, within the Subscribe request message
|
|
a subscriber can specify a "Format" that indicates the set of rules
|
|
that MUST be followed when constructing notification messages.
|
|
</p><p>
|
|
This specification specifies two delivery formats: wrapped and
|
|
unwrapped. Use of wrapped format indicates that notification messages
|
|
MUST be contained in a wrapper element defined by this
|
|
specification. Use of unwrapped format indicates that notification
|
|
messages are not contained in a wrapper element.
|
|
Conformant Event Source implementations MUST support both wrapped
|
|
and unwrapped notifications.
|
|
</p><p>
|
|
Filtering occurs prior to any formatting of notification messages.
|
|
This ensures that regardless of what type of formatting might occur,
|
|
the same Filter dialect/expression can be used to subset the event stream.
|
|
</p></div><div class="div2">
|
|
<h3><a name="SubMgr" id="SubMgr"></a>2.4 Subscription Managers</h3><p>
|
|
In some scenarios the event source itself manages the
|
|
subscriptions it has created. In other scenarios, for example a
|
|
geographically distributed publish-and-subscribe system, it might
|
|
be useful to delegate the management of a subscription to another
|
|
Web service. To support this flexibility, the response to a
|
|
subscription request to an event source will include the EPR of a
|
|
service that the subscriber can interact with to manage this
|
|
subscription. This EPR MUST be the target for future requests
|
|
to renew or cancel the subscription. It can address the same Web
|
|
service (Address and ReferenceParameters) as the event source
|
|
itself, or it can address some other Web service to which the
|
|
event source has delegated management of this subscription.
|
|
</p><p>
|
|
The term "subscription manager" is used in this specification
|
|
to refer to the Web service that manages the subscription,
|
|
whether it is the event source itself or some separate Web
|
|
service.
|
|
</p></div><div class="div2">
|
|
<h3><a name="example" id="example"></a>2.5 Example</h3><p>
|
|
<a href="#Table1">Example 2-1</a> lists a hypothetical request to create a
|
|
subscription for storm warnings.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table1" id="Table1"></a>Example 2-1: Hypothetical request to create a subscription</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ew="http://www.example.com/warnings" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.w3.org/2011/03/ws-evt/Subscribe
|
|
(09) </wsa:Action>
|
|
(10) <wsa:MessageID>
|
|
(11) urn:uuid:d7c5726b-de29-4313-b4d4-b3425b200839
|
|
(12) </wsa:MessageID>
|
|
(13) <wsa:ReplyTo>
|
|
(14) <wsa:Address>http://www.example.com/MyEventSink</wsa:Address>
|
|
(15) </wsa:ReplyTo>
|
|
(16) <wsa:To>http://www.example.org/oceanwatch/EventSource</wsa:To>
|
|
(17) </s12:Header>
|
|
(18) <s12:Body>
|
|
(19) <wse:Subscribe>
|
|
(20) <wse:Delivery>
|
|
(21) <wse:NotifyTo>
|
|
(22) <wsa:Address>
|
|
(23) http://www.example.com/MyEventSink/OnStormWarning
|
|
(24) </wsa:Address>
|
|
(25) <wsa:ReferenceParameters>
|
|
(26) <ew:MySubscription>2597</ew:MySubscription>
|
|
(27) </wsa:ReferenceParameters>
|
|
(28) </wse:NotifyTo>
|
|
(29) </wse:Delivery>
|
|
(30) </wse:Subscribe>
|
|
(31) </s12:Body>
|
|
(32) </s12:Envelope></pre></div></div><p>
|
|
Lines (07-09) in <a href="#Table1">Example 2-1</a> indicate the
|
|
message is a request to create a subscription, and line (16)
|
|
indicates that it is sent to a hypothetical event source of ocean
|
|
events.
|
|
</p><p>
|
|
While lines (13-15) indicate where a reply is sent,
|
|
lines (20-29) indicate where and how notifications are to be
|
|
delivered; there is no requirement that these match. The absence
|
|
of any extensions to the wse:Delivery or wse:NotifyTo elements
|
|
indicates that notifications
|
|
are sent as SOAP messages to the endpoint described in
|
|
lines (21-28). Note that lines (25-27) illustrate a typical
|
|
pattern where the event sink lists a reference parameter (line 26)
|
|
that identifies the subscription and will be included in each
|
|
notification.
|
|
</p><p>
|
|
<a href="#Table2">Example 2-2</a> lists a hypothetical response to the request in
|
|
<a href="#Table1">Example 2-1</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table2" id="Table2"></a>Example 2-2: Hypothetical response to a subscribe request</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ow="http://www.example.org/oceanwatch" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.w3.org/2011/03/ws-evt/SubscribeResponse
|
|
(09) </wsa:Action>
|
|
(10) <wsa:RelatesTo>
|
|
(11) urn:uuid:d7c5726b-de29-4313-b4d4-b3425b200839
|
|
(12) </wsa:RelatesTo>
|
|
(13) <wsa:To>http://www.example.com/MyEventSink</wsa:To>
|
|
(14) </s12:Header>
|
|
(15) <s12:Body>
|
|
(16) <wse:SubscribeResponse>
|
|
(17) <wse:SubscriptionManager>
|
|
(18) <wsa:Address>
|
|
(19) http://www.example.org/oceanwatch/SubscriptionManager
|
|
(20) </wsa:Address>
|
|
(21) <wsa:ReferenceParameters>
|
|
(22) <ow:MyId>
|
|
(23) 28
|
|
(24) </ow:MyId>
|
|
(25) </wsa:ReferenceParameters>
|
|
(26) </wse:SubscriptionManager>
|
|
(27) <wse:GrantedExpires>PT0S</wse:GrantedExpires>
|
|
(28) </wse:SubscribeResponse>
|
|
(29) </s12:Body>
|
|
(30) </s12:Envelope></pre></div></div><p>
|
|
Lines (07-09) in <a href="#Table2">Example 2-2</a> indicate this
|
|
message is a response to a request to create a subscription, and
|
|
lines (10-12) indicate that it is a response to the request in
|
|
<a href="#Table1">Example 2-1</a>. Lines (17-26) provide the
|
|
subscription manager EPR for this subscription, and line (27)
|
|
indicates the subscription will not expire.
|
|
</p></div></div><div class="div1">
|
|
<h2><a name="notterms" id="notterms"></a>3 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"></a>3.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><li><p>
|
|
XML namespace prefixes (see <a href="#Table3">Table 3-1</a>)
|
|
are used to indicate the namespace of the element being
|
|
defined.
|
|
</p></li></ul><p>
|
|
In addition to Message Information Header properties
|
|
<a href="#AddrCore">[WS-Addressing]</a>,
|
|
this specification uses the following properties to define messages:
|
|
</p><dl><dt class="label"> <b>[Headers]</b> </dt><dd><p> Unordered message headers. </p></dd><dt class="label"> <b>[Action]</b> </dt><dd><p> The value to be used for the wsa:Action IRI. </p></dd><dt class="label"> <b>[Body]</b> </dt><dd><p> A message body. </p></dd></dl><p>
|
|
These properties bind to a SOAP Envelope as follows:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><s:Envelope>
|
|
<s:Header>
|
|
<b>[Headers]</b>
|
|
<wsa:Action><b>[Action]</b></wsa:Action>
|
|
...
|
|
</s:Header>
|
|
<s:Body><b>[Body]</b></s:Body>
|
|
</s:Envelope></pre></div></div><p>
|
|
This specification can be used in terms of XML Information Set (Infoset)
|
|
<a href="#XMLInfoset">[XML Infoset]</a>, even though the specification uses XML 1.0
|
|
terminology. Valid Infoset for this specification is the one
|
|
serializable in XML 1.0, hence the use of XML 1.0.
|
|
</p><p>
|
|
The term "generate" is used in relation to the various faults defined
|
|
by this specification to imply that a fault is produced and no
|
|
further processing SHOULD be performed. In these cases the fault
|
|
SHOULD be transmitted. However, there might be reasons when a compliant
|
|
implementation can choose not to transmit the fault - for example,
|
|
security concerns - in these situations the service MAY choose
|
|
not to transmit the fault.
|
|
</p></div><div class="div2">
|
|
<h3><a name="extensions" id="extensions"></a>3.2 Considerations on the Use of Extensibility Points</h3><p>
|
|
The elements defined in this specification MAY be extended at the
|
|
points indicated by their outlines and schema. Implementations MAY
|
|
add child elements and/or attributes at the indicated extension
|
|
points but MUST NOT contradict the semantics of the parent and/or
|
|
owner, respectively. If a receiver does not recognize an extension,
|
|
the receiver SHOULD ignore that extension. Senders MAY indicate
|
|
the presence of an extension that has to be understood through the use
|
|
of a corresponding SOAP Header with a soap:mustUnderstand attribute
|
|
with the value "1".
|
|
</p><p>
|
|
In cases where it is either desirable or necessary for the receiver
|
|
of a request that has been extended to indicate that it has
|
|
recognized and accepted the semantics associated with that extension,
|
|
it is RECOMMENDED that the receiver add a corresponding extension
|
|
to the response message. The definition of an extension SHOULD clearly
|
|
specify how the extension that appears in the response correlates
|
|
with that in the corresponding request.
|
|
</p><p>
|
|
Extension elements and attributes MUST NOT use the Web Services
|
|
Eventing namespace URI.
|
|
</p></div><div class="div2">
|
|
<h3><a name="terms" id="terms"></a>3.3 Terminology</h3><dl><dt class="label"> Event Source </dt><dd><p>
|
|
A Web service that accepts requests to create subscriptions.
|
|
Notifications MAY be sent by any endpoint including the event source.
|
|
</p></dd><dt class="label"> Event Sink </dt><dd><p>
|
|
A Web service that receives notifications.
|
|
</p></dd><dt class="label"> Notification </dt><dd><p>
|
|
A message sent to indicate that an event, or events, have occurred.
|
|
</p></dd><dt class="label"> Subscription </dt><dd><p>
|
|
A registration of interest in receiving notification messages from
|
|
an event source. Subscriptions MAY be created, renewed, expired
|
|
or cancelled. A subscription is "active" when it has been created
|
|
but has not been expired or cancelled.
|
|
</p></dd><dt class="label"> Subscriber </dt><dd><p>
|
|
A Web service that sends requests to create, renew, and/or
|
|
cancel subscriptions.
|
|
</p></dd><dt class="label"> Subscription Manager </dt><dd><p>
|
|
A Web service that accepts requests to manage, get the status of,
|
|
renew, and/or cancel subscriptions on behalf of an event source.
|
|
</p></dd></dl></div><div class="div2">
|
|
<h3><a name="compliance" id="compliance"></a>3.4 Compliance</h3><p>
|
|
An implementation is not compliant with this specification if it fails to
|
|
satisfy one or more of the MUST or REQUIRED level requirements defined
|
|
herein. A SOAP Node MUST NOT use the XML namespace identifier for this
|
|
specification (listed in <a href="#namespaces"><b>3.5 XML Namespaces</b></a>) within SOAP
|
|
Envelopes unless it is compliant with this specification.
|
|
</p><p>
|
|
Normative text within this specification takes precedence over the XML
|
|
Schema and WSDL descriptions, which in turn take precedence over
|
|
outlines, which in turn take precedence over examples.
|
|
</p><p>
|
|
All messages defined by this specification MUST conform to the
|
|
WS-Addressing specifications and be sent to a Web service that
|
|
is addressable by an EPR (see <a href="#AddrCore">[WS-Addressing]</a>).
|
|
</p><p>
|
|
Unless otherwise noted, all IRIs are absolute IRIs and IRI comparison
|
|
MUST be performed according to <a href="#RFC3987">[RFC 3987]</a> section 5.3.1.
|
|
</p><p>
|
|
For any message defined by this specification, any OPTIONAL elements
|
|
or attributes in the message MAY be used by senders of the message;
|
|
however receivers of those messages MUST support those OPTIONAL
|
|
elements and attributes, unless other behavior is explicitly defined
|
|
by this specification.
|
|
</p><p>
|
|
Implementations are expected to support both UTF-8 and UTF-16 as
|
|
described in XML 1.0.
|
|
</p><p>
|
|
Implementations of this specification MUST conform to the corrected
|
|
version of WSDL as defined by the 'WSDL Correction' sections of WS-I
|
|
Basic Profile 1.2 <a href="#BP12">[BP12]</a> and WS-I Basic Profile 2.0
|
|
<a href="#BP20">[BP20]</a>.
|
|
</p></div><div class="div2">
|
|
<h3><a name="namespaces" id="namespaces"></a>3.5 XML Namespaces</h3><p>
|
|
The XML namespace URI that MUST be used by implementations of
|
|
this specification is:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-evt">http://www.w3.org/2011/03/ws-evt</a></pre></div></div><p>
|
|
<a href="#Table3">Table 3-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="Table3" id="Table3"></a><table border="1"><caption>Table 3-1: Prefixes and XML namespaces used in this specification </caption><tbody><tr><th align="left"> Prefix </th><th align="left"> XML Namespace </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>
|
|
<a href="http://schemas.xmlsoap.org/soap/envelope/">
|
|
http://schemas.xmlsoap.org/soap/envelope/
|
|
</a>
|
|
</td><td>SOAP 1.1 <a href="#SOAP11">[SOAP11]</a></td></tr><tr><td>s12</td><td>
|
|
<a href="http://www.w3.org/2003/05/soap-envelope">
|
|
http://www.w3.org/2003/05/soap-envelope
|
|
</a>
|
|
</td><td>SOAP 1.2 <a href="#SOAP12">[SOAP12]</a></td></tr><tr><td>wsdl</td><td>
|
|
<a href="http://schemas.xmlsoap.org/wsdl/">
|
|
http://schemas.xmlsoap.org/wsdl/
|
|
</a>
|
|
</td><td>WSDL <a href="#WSDL11">[WSDL11]</a></td></tr><tr><td>wsa</td><td>
|
|
<a href="http://www.w3.org/2005/08/addressing">
|
|
http://www.w3.org/2005/08/addressing
|
|
</a>
|
|
</td><td>WS-Addressing <a href="#AddrCore">[WS-Addressing]</a></td></tr><tr><td>wse</td><td>
|
|
<a href="http://www.w3.org/2011/03/ws-evt">
|
|
http://www.w3.org/2011/03/ws-evt
|
|
</a>
|
|
</td><td>This specification</td></tr><tr><td>wsp</td><td>
|
|
<a href="http://www.w3.org/ns/ws-policy">
|
|
http://www.w3.org/ns/ws-policy</a>
|
|
</td><td>WS-Policy <a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td>xs</td><td>
|
|
<a href="http://www.w3.org/2001/XMLSchema">
|
|
http://www.w3.org/2001/XMLSchema
|
|
</a>
|
|
</td><td>
|
|
XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a>
|
|
</td></tr></tbody></table><p>
|
|
The working group intends to update the value of the Web Services
|
|
Eventing namespace URI each time a new version of this document is
|
|
published until such time that the document reaches Candidate
|
|
Recommendation status. Once it has reached Candidate Recommendation
|
|
status, the working group intends to maintain the value of the
|
|
Web Services Eventing namespace URI that was assigned in the
|
|
Candidate Recommendation unless significant changes are made that
|
|
impact the implementation or break post-CR implementations of the
|
|
specification. Also see
|
|
<a href="http://www.w3.org/2001/tag/doc/namespaceState.html">
|
|
http://www.w3.org/2001/tag/doc/namespaceState.html
|
|
</a> and
|
|
<a href="http://www.w3.org/2005/07/13-nsuri">
|
|
http://www.w3.org/2005/07/13-nsuri
|
|
</a>.
|
|
</p></div></div><div class="div1">
|
|
<h2><a name="SubMsgs" id="SubMsgs"></a>4 Subscription Messages</h2><p>
|
|
To create, renew, and cancel subscriptions, subscribers send
|
|
request messages to event sources and subscription managers.
|
|
</p><p>
|
|
Subscriptions are created with a specific expiration time that is
|
|
negotiated between the Subscriber and the Event Source/Subscription
|
|
Manager via the Subscribe-SubscribeResponse message exchange. This
|
|
expiration time can be subsequently re-negotiated via the
|
|
Renew-RenewResponse message exchange. There are a number of options
|
|
to these negotiations. In addition to requesting a subscription with
|
|
a specific expiration time, Subscribers can request a subscription
|
|
with an infinite expiration (i.e. a subscription that never expires).
|
|
Subscribers can also indicate their willingness to accept a "best effort"
|
|
attempt to match their desired expiration, as well as indicate that
|
|
the expiration value will be chosen by the Event Source or
|
|
Subscription Manager.
|
|
</p><p>
|
|
An event source MAY support filtering to
|
|
limit notifications that are delivered to the event sink; if it
|
|
does, and a subscribe request contains a filter,
|
|
only events that match the requested filter are sent.
|
|
</p><p>
|
|
Notifications are sent to the event sink until one of the following
|
|
happens: the subscription manager accepts an unsubscribe request
|
|
for the subscription; the subscription expires;
|
|
or the event source/subscription manager cancels the subscription
|
|
prematurely. In this last case, the event source/subscription manager
|
|
makes a best
|
|
effort to indicate why the subscription ended,
|
|
via a SubscriptionEnd message if an EndTo was present in the
|
|
Subscribe message.
|
|
</p><p>
|
|
In the absence of reliable messaging at the application layer
|
|
(e.g. <a href="#WSReliableMessaging">[WS-ReliableMessaging]</a>),
|
|
messages defined herein are delivered using the quality of
|
|
service of the underlying transport(s) and on a best-effort basis
|
|
at the application layer.
|
|
</p><p>
|
|
A subscription can become invalid for any reason including:
|
|
</p><ol class="enumar"><li><p>
|
|
Subscription canceled at the request of the subscriber
|
|
(via Unsubscribe)
|
|
</p></li><li><p>Subscription canceled upon expiration</p></li><li><p>
|
|
Subscription canceled due to come condition or action of/by
|
|
the Event Source or Subscription Manager.
|
|
</p></li></ol><p>
|
|
As the last item indicates, the Event Source/Subscription Manager MAY
|
|
cancel a subscription at any time.
|
|
</p><p>
|
|
When processing a Renew, GetStatus or Unsubscribe operation, a
|
|
Subscription Manager MUST generate an wse:UnknownSubscription fault if
|
|
it determines that the subscription is invalid.
|
|
</p><p>
|
|
Once a Subscriber determines that a subscription is invalid, it MUST
|
|
NOT issue any more WS-Eventing request messages using that subscription.
|
|
</p><div class="div2">
|
|
<h3><a name="Subscribe" id="Subscribe"></a>4.1 Subscribe</h3><p>
|
|
To create a subscription, a subscriber sends a Subscribe request message
|
|
to an event source. This operation MUST be supported by
|
|
compliant event sources.
|
|
The message MUST be of the following form:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
|
|
http://www.w3.org/2011/03/ws-evt/Subscribe
|
|
|
|
<b>[Body]</b>
|
|
<wse:Subscribe ...>
|
|
<wse:EndTo> <em>endpoint-reference</em> </wse:EndTo> ?
|
|
<wse:Delivery ...> <em>xs:any</em>* </wse:Delivery>
|
|
<wse:Format Name="<em>xs:anyURI</em>"? > <em>xs:any</em>* </wse:Format> ?
|
|
<wse:Expires BestEffort="<em>xs:boolean</em>"? ...>
|
|
(<em>xs:dateTime</em> | <em>xs:duration</em>)
|
|
</wse:Expires> ?
|
|
<wse:Filter Dialect="<em>xs:anyURI</em>"? ...> <em>xs:any</em>* </wse:Filter> ?
|
|
<em>xs:any</em>*
|
|
</wse:Subscribe></pre></div></div><p>
|
|
The following describes additional, normative constraints on
|
|
the outline listed above:
|
|
</p><dl><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:EndTo </dt><dd><p>
|
|
Where to send a SubscriptionEnd message if the
|
|
subscription is terminated unexpectedly. (See
|
|
<a href="#SubscriptionEnd"><b>4.5 SubscriptionEnd</b></a>.) If
|
|
present, this element MUST be of type
|
|
wsa:EndpointReferenceType. Default is not to send this
|
|
message. The endpoint to which the EndTo EPR refers MUST support the
|
|
SubcriptionEndPortType portType.
|
|
Unless some mechanism is used to indicate otherwise, the messages
|
|
sent to this endpoint MUST use the same version of SOAP that was
|
|
used for the Subscribe message.
|
|
</p><p>
|
|
If the event source does not support the use of the EndTo EPR,
|
|
the event source MUST generate a wse:EndToNotSupported fault.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Delivery </dt><dd><p>
|
|
This element contains the information necessary to convey
|
|
notification messages to the event sink in
|
|
a manner REQUIRED by the subscriber. This element MUST contain
|
|
at least one child element. If no delivery mechanism is
|
|
specified then the event source MUST generate a
|
|
wse:NoDeliveryMechanismEstablished fault.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Delivery/wse:NotifyTo </dt><dd><p>
|
|
This is an OPTIONAL element. When present, this element indicates
|
|
that notifications MUST be sent to the EndpointReference identified
|
|
by this element.
|
|
Unless some mechanism is used to indicate otherwise, the messages
|
|
sent to this endpoint MUST use the same version of SOAP that was
|
|
used for the Subscribe message.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Format </dt><dd><p>
|
|
This OPTIONAL element contains
|
|
the delivery format to be used for notification messages sent in
|
|
relation to this subscription. The absence of this element
|
|
is the equivalent to its presence with a @Name value of
|
|
"http://www.w3.org/2011/03/ws-evt/DeliveryFormats/Unwrap", which
|
|
indicates that unwrapped delivery MUST be used. See
|
|
Section <a href="#NotificationFormats"><b>2.3 Notification Formats</b></a> for details.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Format@Name </dt><dd><p>
|
|
Implied value is
|
|
"http://www.w3.org/2011/03/ws-evt/DeliveryFormats/Unwrap".
|
|
</p><p>
|
|
If the event source does not support the requested delivery
|
|
format, the request MUST
|
|
generate a wse:DeliveryFormatRequestedUnavailable fault indicating
|
|
that the requested delivery format is not supported.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Format@Name="http://www.w3.org/2011/03/ws-evt/DeliveryFormats/Unwrap" </dt><dd><p>
|
|
Indicate the unwrapped event delivery format.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Format@Name="http://www.w3.org/2011/03/ws-evt/DeliveryFormats/Wrap" </dt><dd><p>
|
|
Indicate the wrapped event delivery format.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Expires </dt><dd><p>
|
|
This OPTIONAL element can be used by the subscriber to indicate the
|
|
expiration time of the requested subscription.
|
|
A value of PT0S indicates a request for an infinite expiration time
|
|
(i.e. a subscription that never expires).
|
|
</p><p>
|
|
The absence of the wse:Expires element indicates that the expiration
|
|
value will be chosen by the event source or subscription manager.
|
|
This value is communicated via the wse:GrantedExpires element
|
|
(see below).
|
|
</p><p>
|
|
If the wse:Expires element is present and the event source is not
|
|
able to grant an expiration time that matches the specified value
|
|
then it MUST generate a wse:UnsupportedExpirationValue fault.
|
|
</p><p>
|
|
The value of the wse:Expires element MAY be either a duration
|
|
(xs:duration) or a specific time (xs:dateTime). Event sources
|
|
and subscription managers MUST accept duration values and MAY
|
|
accept specific time values. Upon receiving a request that
|
|
contains specific time values, an event source or subscription
|
|
manager that does not support such value types MUST fail the
|
|
request and generate a wse:UnsupportedExpirationType fault.
|
|
</p><p>
|
|
If a subscriber chooses to use specific time values in a request,
|
|
it is RECOMMENDED that these values include a time zone component.
|
|
Specific time values that lack a time zone MUST be interpreted in
|
|
the local time zone of the receiver.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Expires@BestEffort </dt><dd><p>
|
|
This OPTIONAL attribute, when present with a value of 'true',
|
|
indicates that the event source MUST grant an expiration time that
|
|
is its best effort to match the requested
|
|
expiration time. Default value of this attribute is "false" in
|
|
which case the event source MUST grant the requested expiration time
|
|
or fault the subscription request as defined above.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Filter </dt><dd><p>
|
|
A Boolean expression in some dialect, either as a string
|
|
or as an XML fragment (see
|
|
<b>[<a href="#Dialect"> [Body]/wse:Subscribe/wse:Filter/@Dialect </a>]</b>). If
|
|
the expression evaluates to false for a notification, the
|
|
notification MUST NOT be sent to the event sink. Implied
|
|
value is an expression that always returns true. If the event
|
|
source does not support filtering, then a request that
|
|
specifies a filter MUST fail, and the event source MUST
|
|
generate a wse:FilteringNotSupported fault indicating that
|
|
filtering is not supported.
|
|
</p><p>
|
|
If the event source supports filtering but cannot honor
|
|
the requested filtering, the request MUST fail, and the event
|
|
source MUST generate a wse:FilteringRequestedUnavailable fault
|
|
indicating that the requested filter dialect is not
|
|
supported.
|
|
</p><p>
|
|
If the event source supports filtering and the
|
|
requested dialect but cannot process the requested filter content,
|
|
the request MUST fail, and the event source MUST generate a
|
|
wse:CannotProcessFilter fault.
|
|
</p><p>
|
|
It is possible for a Subscribe request to contain a filter that
|
|
will never evaluate to true for the lifetime of the subscription.
|
|
If an event source detects this condition during the processing
|
|
of the Subscribe request it MUST generate a
|
|
wse:EmptyFilter fault in response to the Subscribe request message.
|
|
If, after the SubscribeResponse message has been sent, the
|
|
event source determines that the filter will never evaluate to true
|
|
for the lifetime of the subscription, or if there is an error within
|
|
the filter expression, the subscription MUST be terminated. In
|
|
this case if an EndTo was provided, then a SubscriptionEnd message
|
|
MUST be sent with a Status value of
|
|
"http://www.w3.org/2011/03/ws-evt/SourceCancelling".
|
|
|
|
</p></dd><dt class="label"><a name="Dialect" id="Dialect"></a> <b>[Body]</b>/wse:Subscribe/wse:Filter/@Dialect </dt><dd><p>
|
|
Implied value is "http://www.w3.org/2011/03/ws-evt/Dialects/XPath10".
|
|
</p><p>
|
|
If filtering is supported, then support for the XPath 1.0 dialect
|
|
(described below) is RECOMMENDED.
|
|
Alternate filter dialects can be defined.
|
|
Such dialect definitions MUST include sufficient information for
|
|
proper application. For example, it would need to define the context
|
|
(which data) over which the filter operates.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Filter/@Dialect="<a href="http://www.w3.org/2011/03/ws-evt/Dialects/XPath10">
|
|
http://www.w3.org/2011/03/ws-evt/Dialects/XPath10
|
|
</a>"
|
|
</dt><dd><p>
|
|
Value of <b>[Body]</b>/wse:Subscribe/wse:Filter is an XPath
|
|
<a href="#XPath1">[XPath1.0]</a> predicate expression
|
|
(PredicateExpr); the context of the expression is:
|
|
</p><ul><li><p>Context Node: the root of the event XML.</p></li><li><p>Context Position: 1.</p></li><li><p>Context Size: 1.</p></li><li><p>Variable Bindings: None.</p></li><li><p>
|
|
Function Libraries: Core Function Library <a href="#XPath1">[XPath1.0]</a>.
|
|
</p></li><li><p>
|
|
Namespace Declarations: The [in-scope namespaces]
|
|
property <a href="#XMLInfoset">[XML Infoset]</a> of
|
|
/s:Envelope/s:Body/*/wse:Filter.
|
|
</p></li></ul><p>
|
|
The namespace bindings are evaluated against any namespace
|
|
declarations that are in scope where the XPath expression appears
|
|
within the SOAP message.
|
|
Note that the evaluation of expressions that rely on such context
|
|
dependent bindings is fragile in the face of transformations that alter
|
|
namespace prefixes. Such transformations might occur during the
|
|
transmission, processing, storage, or retrieval of a request. Clients
|
|
that wish to isolate expressions from the effects of any changes to the
|
|
namespace prefixes in the containing SOAP message are advised to
|
|
construct expressions in a manner that avoids the use of namespace
|
|
prefixes. For example, use an expression such as
|
|
"/*[local-name()='a' and namespace-uri()='http://www.example.com']"
|
|
not "/ns1:a".
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:Subscribe/wse:Filter/@Dialect="<a href="http://www.w3.org/2011/03/ws-evt/Dialects/XPath20">
|
|
http://www.w3.org/2011/03/ws-evt/Dialects/XPath20
|
|
</a>"
|
|
</dt><dd><p>
|
|
This filter dialect is the same as the XPath 1.0 filter dialect
|
|
except that it uses <a href="#XPath2">[XPath2.0]</a> instead of XPath 1.0
|
|
as the expression language.
|
|
</p></dd></dl><p>
|
|
Other components of the outline above are not further
|
|
constrained by this specification.
|
|
</p><p>
|
|
If included within the Subscribe request message, the wse:NotifyTo
|
|
and wse:EndTo SHOULD have some cursory validity checking performed before
|
|
the Subscribe response is returned. While not all errors can be detected
|
|
prior to sending a message to those EPRs, some obvious ones can be
|
|
detected. For example, an unsupported transport specified within the
|
|
wsa:Address IRI.
|
|
Detecting these errors during Subscribe processing will lessen the chances
|
|
of the subscriber creating an unusable subscription. If this check is
|
|
performed and a problem is detected then the event source MUST generate
|
|
a wse:UnusableEPR fault rather than returning the SubscribeResponse
|
|
message.
|
|
</p><p>
|
|
If the event source chooses not to accept a subscription due
|
|
to the content of the Subscribe message, then the
|
|
event source MUST generate a
|
|
SOAP 1.1 Client fault or a SOAP 1.2 Sender
|
|
fault. If the event source
|
|
does not accept this subscription due to an internal processing
|
|
reason and not due to the specific content of the Subscribe
|
|
message, then the event source MUST
|
|
generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault
|
|
which MAY contain the RetryAfter fault detail element.
|
|
</p><p>
|
|
If the event source accepts a request to create a
|
|
subscription, it MUST reply with a response of the following
|
|
form:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
|
|
http://www.w3.org/2011/03/ws-evt/SubscribeResponse
|
|
|
|
<b>[Body]</b>
|
|
<wse:SubscribeResponse ...>
|
|
<wse:SubscriptionManager>
|
|
<em>wsa:EndpointReferenceType</em>
|
|
</wse:SubscriptionManager>
|
|
<wse:GrantedExpires ...>
|
|
(<em>xs:dateTime</em> | <em>xs:duration</em>)
|
|
</wse:GrantedExpires>
|
|
<em>xs:any</em>*
|
|
</wse:SubscribeResponse></pre></div></div><p>
|
|
The following describes additional, normative constraints on
|
|
the outline listed above:
|
|
</p><dl><dt class="label"> <b>[Body]</b>/wse:SubscribeResponse/wse:SubscriptionManager </dt><dd><p>
|
|
The EPR of the subscription manager for this subscription.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:SubscribeResponse/wse:GrantedExpires </dt><dd><p>
|
|
The expiration time assigned by the event source. The
|
|
expiration time MAY be either a specific time or a duration
|
|
but MUST be of the same type as the wse:Expires element of
|
|
the corresponding request. If the corresponding request
|
|
did not contain a wse:Expires element, this element MUST be
|
|
a duration (xs:duration).
|
|
</p><p>
|
|
When expressed as a duration, the wse:GrantedExpires element
|
|
designates the amount of time remaining on this subscription
|
|
as measured from the moment the request message was processed.
|
|
Although this specification cannot dictate when, during the
|
|
processing of a request message a subscription's remaining time
|
|
is determined, the event source MUST measure the expiration
|
|
duration from a time that is at or before the transmission of
|
|
the response message.
|
|
</p><p>
|
|
A wse:GrantedExpires value of PT0S indicates that the
|
|
subscription will never expire.
|
|
</p></dd></dl><p>
|
|
Other components of the outline above are not further
|
|
constrained by this specification.
|
|
</p><p>
|
|
<a href="#Table4">Example 4-1</a> lists another hypothetical request to create a
|
|
subscription.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table4" id="Table4"></a>Example 4-1: Second hypothetical request to create a subscription</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ew="http://www.example.com/warnings" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.w3.org/2011/03/ws-evt/Subscribe
|
|
(09) </wsa:Action>
|
|
(10) <wsa:MessageID>
|
|
(11) urn:uuid:e1886c5c-5e86-48d1-8c77-fc1c28d47180
|
|
(12) </wsa:MessageID>
|
|
(13) <wsa:ReplyTo>
|
|
(14) <wsa:Address>http://www.example.com/MyEvEntsink</wsa:Address>
|
|
(15) <wsa:ReferenceParameters>
|
|
(16) <ew:MySubscription>2597</ew:MySubscription>
|
|
(17) </wsa:ReferenceParameters>
|
|
(18) </wsa:ReplyTo>
|
|
(19) <wsa:To>http://www.example.org/oceanwatch/EventSource</wsa:To>
|
|
(20) </s12:Header>
|
|
(21) <s12:Body>
|
|
(22) <wse:Subscribe>
|
|
(23) <wse:EndTo>
|
|
(24) <wsa:Address>
|
|
(25) http://www.example.com/MyEventSink
|
|
(26) </wsa:Address>
|
|
(27) <wsa:ReferenceParameters>
|
|
(28) <ew:MySubscription>2597</ew:MySubscription>
|
|
(29) </wsa:ReferenceParameters>
|
|
(30) </wse:EndTo>
|
|
(31) <wse:Delivery>
|
|
(32) <wse:NotifyTo>
|
|
(33) <wsa:Address>
|
|
(34) http://www.other.example.com/OnStormWarning
|
|
(35) </wsa:Address>
|
|
(36) <wsa:ReferenceParameters>
|
|
(37) <ew:MySubscription>2597</ew:MySubscription>
|
|
(38) </wsa:ReferenceParameters>
|
|
(39) </wse:NotifyTo>
|
|
(40) </wse:Delivery>
|
|
(41) <wse:Expires>2004-06-26T21:07:00.000-08:00</wse:Expires>
|
|
(42) <wse:Filter xmlns:ow="http://www.example.org/oceanwatch" >
|
|
(43) /*/ow:Speed &gt; 50
|
|
(44) </wse:Filter>
|
|
(45) </wse:Subscribe>
|
|
(46) </s12:Body>
|
|
(47) </s12:Envelope></pre></div></div><p>
|
|
Like the request in <a href="#Table1">Example 2-1</a>, lines
|
|
(07-09) of <a href="#Table4">Example 4-1</a> indicate the message is
|
|
a request to create a subscription. Line (19) indicates that it
|
|
is sent to a hypothetical event source of ocean events.
|
|
</p><p>
|
|
Lines (13-18) indicate where to send the response to this
|
|
request, lines (23-30) indicate where to send a SubscriptionEnd
|
|
message if necessary, and lines (31-34) indicate how and where to
|
|
send notifications.
|
|
</p><p>
|
|
Line (41) indicates the event sink would prefer to have the
|
|
subscription expire on 26 June 2004 at 9:07 PM Pacific time.
|
|
</p><p>
|
|
Lines (42-44) indicate the event sink only wants weather
|
|
reports where the speed of wind is greater than 50.
|
|
</p><p>
|
|
<a href="#Table5">Example 4-2</a> lists a hypothetical response to the request in
|
|
<a href="#Table4">Example 4-1</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table5" id="Table5"></a>Example 4-2: Hypothetical response to second subscribe request</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ew="http://www.example.com/warnings"
|
|
(06) xmlns:ow="http://www.example.org/oceanwatch" >
|
|
(07) <s12:Header>
|
|
(08) <wsa:Action>
|
|
(09) http://www.w3.org/2011/03/ws-evt/SubscribeResponse
|
|
(10) </wsa:Action>
|
|
(11) <wsa:RelatesTo>
|
|
(12) urn:uuid:e1886c5c-5e86-48d1-8c77-fc1c28d47180
|
|
(13) </wsa:RelatesTo>
|
|
(14) <wsa:To>http://www.example.com/MyEventSink</wsa:To>
|
|
(15) <ew:MySubscription wsa:IsReferenceParameter="true">
|
|
(16) 2597
|
|
(17) </ew:MySubscription>
|
|
(18) </s12:Header>
|
|
(19) <s12:Body>
|
|
(20) <wse:SubscribeResponse>
|
|
(21) <wse:SubscriptionManager>
|
|
(22) <wsa:Address>
|
|
(23) http://www.example.org/oceanwatch/SubscriptionManager
|
|
(24) </wsa:Address>
|
|
(25) <wsa:ReferenceParameters>
|
|
(26) <x:SubID xmlns:x="http://example.com">
|
|
(27) urn:uuid:22e8a584-0d18-4228-b2a8-3716fa2097fa
|
|
(28) </x:SubID>
|
|
(29) </wsa:ReferenceParameters>
|
|
(30) </wse:SubscriptionManager>
|
|
(31) <wse:Expires>2004-06-26T21:07:00.000-08:00</wse:Expires>
|
|
(32) </wse:SubscribeResponse>
|
|
(33) </s12:Body>
|
|
(34) </s12:Envelope></pre></div></div><p>
|
|
Like the response in <a href="#Table2">Example 2-2</a>, lines
|
|
(08-10) of <a href="#Table5">Example 4-2</a> indicate this message is
|
|
a response to a request to create a subscription, and lines
|
|
(11-13) indicate that it is a response to the request in
|
|
<a href="#Table4">Example 4-1</a> . Lines (14-17) indicate the response is
|
|
sent to the event sink indicated in lines (13-18) of
|
|
<a href="#Table4">Example 4-1</a>. Lines (21-30) provide the address of the
|
|
subscription manager for this subscription; note that this
|
|
particular response uses the x:SubID element as a reference
|
|
parameter to distinguish
|
|
this subscription EPR from other subscription EPRs.
|
|
Finally, line (31) indicates the
|
|
subscription will expire on 26 June 2004 at 9:07 PM Pacific time
|
|
unless renewed.
|
|
</p></div><div class="div2">
|
|
<h3><a name="Renew" id="Renew"></a>4.2 Renew</h3><p>
|
|
To update, or renew, the expiration for a subscription, a
|
|
subscriber sends a Renew request message to the subscription
|
|
manager.
|
|
This operation MUST be supported by compliant subscription managers.
|
|
The Renew request message MUST be of the following form:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
|
|
http://www.w3.org/2011/03/ws-evt/Renew
|
|
|
|
<b>[Body]</b>
|
|
<wse:Renew ...>
|
|
<wse:Expires BestEffort="<em>xs:boolean</em>"? ...>
|
|
(<em>xs:dateTime</em> | <em>xs:duration</em>)
|
|
</wse:Expires> ?
|
|
<em>xs:any</em>*
|
|
</wse:Renew></pre></div></div><p>
|
|
Components of the outline listed above are additionally
|
|
constrained as for a request to create a subscription (see
|
|
<a href="#Subscribe"><b>4.1 Subscribe</b></a>). Other components
|
|
of the outline above are not further constrained by this
|
|
specification.
|
|
</p><p>
|
|
If the subscription manager chooses not to renew this
|
|
subscription, the request MUST fail, and the subscription manager
|
|
MUST generate a SOAP 1.1 Server fault or a SOAP 1.2 Receiver fault
|
|
indicating that the renewal was not accepted. This fault MAY contain
|
|
the RetryAfter fault detail element.
|
|
</p><p>
|
|
If the subscription manager accepts a request to renew a
|
|
subscription, it MUST reply with a response of the following
|
|
form:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
|
|
http://www.w3.org/2011/03/ws-evt/RenewResponse
|
|
|
|
<b>[Body]</b>
|
|
<wse:RenewResponse ...>
|
|
<wse:GrantedExpires ...>
|
|
(<em>xs:dateTime</em> | <em>xs:duration</em>)
|
|
</wse:GrantedExpires> ?
|
|
<em>xs:any</em>*
|
|
</wse:RenewResponse></pre></div></div><p>
|
|
Components of the outline listed above are constrained as for
|
|
a response to a subscribe request (see <a href="#Subscribe"><b>4.1 Subscribe</b></a>).
|
|
Other components of the outline above are not further
|
|
constrained by this specification.
|
|
</p><p>
|
|
<a href="#Table6">Example 4-3</a> lists a hypothetical request to renew the
|
|
subscription created in <a href="#Table5">Example 4-2</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table6" id="Table6"></a>Example 4-3: Hypothetical request to renew second subscription</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ow="http://www.example.org/oceanwatch" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.w3.org/2011/03/ws-evt/Renew
|
|
(09) </wsa:Action>
|
|
(10) <wsa:MessageID>
|
|
(11) urn:uuid:bd88b3df-5db4-4392-9621-aee9160721f6
|
|
(12) </wsa:MessageID>
|
|
(13) <wsa:ReplyTo>
|
|
(14) <wsa:Address>http://www.example.com/MyEventSink</wsa:Address>
|
|
(15) </wsa:ReplyTo>
|
|
(16) <wsa:To>
|
|
(17) http://www.example.org/oceanwatch/SubscriptionManager
|
|
(18) </wsa:To>
|
|
(19) <x:SubID wsa:IsReferenceParameter="true" xmlns:x="http://example.com">
|
|
(20) urn:uuid:22e8a584-0d18-4228-b2a8-3716fa2097fa
|
|
(21) </x:SubID>
|
|
(22) </s12:Header>
|
|
(23) <s12:Body>
|
|
(24) <wse:Renew>
|
|
(25) <wse:Expires>2004-06-26T21:07:00.000-08:00</wse:Expires>
|
|
(26) </wse:Renew>
|
|
(27) </s12:Body>
|
|
(28) </s12:Envelope></pre></div></div><p>
|
|
Lines (07-09) indicate this is a request to renew a
|
|
subscription. Lines (19-21) contain the reference parameter that
|
|
indicates the subscription to be renewed is the one created in
|
|
<a href="#Table5">Example 4-2</a>. Line (25) in <a href="#Table6">Example 4-3</a>
|
|
indicates the request is to extend the
|
|
subscription until 26 June 2004 at 9:07 PM Pacific.
|
|
</p><p>
|
|
<a href="#Table7">Example 4-4</a> lists a hypothetical response to the request in
|
|
<a href="#Table6">Example 4-3</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table7" id="Table7"></a>Example 4-4: Hypothetical response to renew request</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ow="http://www.example.org/oceanwatch" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.w3.org/2011/03/ws-evt/RenewResponse
|
|
(09) </wsa:Action>
|
|
(10) <wsa:RelatesTo>
|
|
(11) urn:uuid:bd88b3df-5db4-4392-9621-aee9160721f6
|
|
(12) </wsa:RelatesTo>
|
|
(13) <wsa:To>http://www.example.com/MyEventSink</wsa:To>
|
|
(14) </s12:Header>
|
|
(15) <s12:Body>
|
|
(16) <wse:RenewResponse>
|
|
(17) <wse:Expires>2004-06-26T21:07:00.000-08:00</wse:Expires>
|
|
(18) </wse:RenewResponse>
|
|
(19) </s12:Body>
|
|
(20) </s12:Envelope></pre></div></div><p>
|
|
Line (17) in <a href="#Table7">Example 4-4</a> indicates the
|
|
subscription has been extended only until 26 June 2004 at
|
|
noon.
|
|
</p></div><div class="div2">
|
|
<h3><a name="GetStatus" id="GetStatus"></a>4.3 GetStatus</h3><p>
|
|
To get the status of a subscription, the subscriber sends a
|
|
GetStatus request message to the subscription manager.
|
|
This operation MUST be supported by compliant subscription managers.
|
|
The GetStatus request MUST be of the following form:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
|
|
http://www.w3.org/2011/03/ws-evt/GetStatus
|
|
|
|
<b>[Body]</b>
|
|
<wse:GetStatus ...>
|
|
<em>xs:any</em>*
|
|
</wse:GetStatus></pre></div></div><p>
|
|
Components of the outline listed above are not further constrained
|
|
by this specification.
|
|
</p><p>
|
|
If the subscription is active, the
|
|
subscription manager MUST reply with a response of the following
|
|
form:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
|
|
http://www.w3.org/2011/03/ws-evt/GetStatusResponse
|
|
|
|
<b>[Body]</b>
|
|
<wse:GetStatusResponse ...>
|
|
<wse:GrantedExpires ...>
|
|
(<em>xs:dateTime</em> | <em>xs:duration</em>)
|
|
</wse:GrantedExpires> ?
|
|
<em>xs:any</em>*
|
|
</wse:GetStatusResponse></pre></div></div><p>
|
|
Components of the outline listed above are constrained as for
|
|
a response to a renew request (see <a href="#Renew"><b>4.2 Renew</b></a>).
|
|
Other components of the outline above are not further
|
|
constrained by this specification.
|
|
</p><p>
|
|
This operation is safe; it will not result in any side effect
|
|
imputable to the requester. This means that in case of an underlying
|
|
protocol error that might get unnoticed, resending the same request
|
|
can be done automatically.
|
|
</p><p>
|
|
<a href="#Table8">Example 4-5</a> lists a hypothetical request to get the
|
|
status of the subscription created in <a href="#Table5">Example 4-2</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table8" id="Table8"></a>Example 4-5: Hypothetical request to get the status of the second subscription</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ow="http://www.example.org/oceanwatch" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.w3.org/2011/03/ws-evt/GetStatus
|
|
(09) </wsa:Action>
|
|
(10) <wsa:MessageID>
|
|
(11) urn:uuid:bd88b3df-5db4-4392-9621-aee9160721f6
|
|
(12) </wsa:MessageID>
|
|
(13) <wsa:ReplyTo>
|
|
(14) <wsa:Address>http://www.example.com/MyEventSink</wsa:Address>
|
|
(15) </wsa:ReplyTo>
|
|
(16) <wsa:To>
|
|
(17) http://www.example.org/oceanwatch/SubscriptionManager
|
|
(18) </wsa:To>
|
|
(19) <x:SubID wsa:IsReferenceParameter="true" xmlns:x="http://example.com">
|
|
(20) urn:uuid:22e8a584-0d18-4228-b2a8-3716fa2097fa
|
|
(21) </x:SubID>
|
|
(22) </s12:Header>
|
|
(23) <s12:Body>
|
|
(24) <wse:GetStatus />
|
|
(25) </s12:Body>
|
|
(26) </s12:Envelope></pre></div></div><p>
|
|
Lines (07-09) indicate this is a request to get the status of
|
|
a subscription. Lines (16-21) indicate that the request is sent
|
|
to the subscription manager for the subscription created in
|
|
<a href="#Table5">Example 4-2</a>.
|
|
</p><p>
|
|
<a href="#Table9">Example 4-6</a> lists a hypothetical response to the request in
|
|
<a href="#Table8">Example 4-5</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table9" id="Table9"></a>Example 4-6: Hypothetical response to get status request</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ow="http://www.example.org/oceanwatch" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.w3.org/2011/03/ws-evt/GetStatusResponse
|
|
(09) </wsa:Action>
|
|
(10) <wsa:RelatesTo>
|
|
(11) urn:uuid:bd88b3df-5db4-4392-9621-aee9160721f6
|
|
(12) </wsa:RelatesTo>
|
|
(13) <wsa:To>http://www.example.com/MyEventSink</wsa:To>
|
|
(14) </s12:Header>
|
|
(15) <s12:Body>
|
|
(16) <wse:GetStatusResponse>
|
|
(17) <wse:Expires>2004-06-26T12:00:00.000-00:00</wse:Expires>
|
|
(18) </wse:GetStatusResponse>
|
|
(19) </s12:Body>
|
|
(20) </s12:Envelope></pre></div></div><p>
|
|
Line (17) in <a href="#Table9">Example 4-6</a> indicates the
|
|
subscription will expire on 26 June 2004 at noon.
|
|
</p></div><div class="div2">
|
|
<h3><a name="Unsubscribe" id="Unsubscribe"></a>4.4 Unsubscribe</h3><p>
|
|
Though subscriptions with a non-infinite expiration time will
|
|
eventually be canceled, to minimize resources,
|
|
the subscriber SHOULD explicitly cancel a
|
|
subscription when it no longer wants notifications associated
|
|
with the subscription.
|
|
</p><p>
|
|
To explicitly cancel a subscription, a subscriber
|
|
sends an Unsubscribe request message to the subscription manager.
|
|
This operation MUST be supported by compliant subscription managers.
|
|
The Unsubscribe request message MUST be of the following form:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
|
|
http://www.w3.org/2011/03/ws-evt/Unsubscribe
|
|
|
|
<b>[Body]</b>
|
|
<wse:Unsubscribe ...>
|
|
<em>xs:any</em>*
|
|
</wse:Unsubscribe></pre></div></div><p>
|
|
Components of the outline above are additionally constrained
|
|
only as for a request to renew a subscription (see
|
|
<a href="#Renew"><b>4.2 Renew</b></a>). For example, the faults listed
|
|
there are also defined for a request to cancel a
|
|
subscription.
|
|
</p><p>
|
|
If the subscription manager accepts a request to cancel a
|
|
subscription, it MUST reply with a response of the following
|
|
form:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
|
|
http://www.w3.org/2011/03/ws-evt/UnsubscribeResponse
|
|
|
|
<b>[Body]</b>
|
|
<wse:UnsubscribeResponse ...>
|
|
<em>xs:any</em>*
|
|
</wse:UnsubscribeResponse></pre></div></div><p>
|
|
Components of the outline listed above are not further
|
|
constrained by this specification.
|
|
</p><p>
|
|
<a href="#Table10">Example 4-7</a> lists a hypothetical request to cancel the
|
|
subscription created in <a href="#Table5">Example 4-2</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table10" id="Table10"></a>Example 4-7: Hypothetical unsubscribe request to cancel second subscription</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ow="http://www.example.org/oceanwatch" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.w3.org/2011/03/ws-evt/Unsubscribe
|
|
(09) </wsa:Action>
|
|
(10) <wsa:MessageID>
|
|
(11) urn:uuid:2653f89f-25bc-4c2a-a7c4-620504f6b216
|
|
(12) </wsa:MessageID>
|
|
(13) <wsa:ReplyTo>
|
|
(14) <wsa:Address>http://www.example.com/MyEventSink</wsa:Address>
|
|
(15) </wsa:ReplyTo>
|
|
(16) <wsa:To>
|
|
(17) http://www.example.org/oceanwatch/SubscriptionManager
|
|
(18) </wsa:To>
|
|
(19) <x:SubID wsa:IsReferenceParameter="true" xmlns:x="http://example.com">
|
|
(20) urn:uuid:22e8a584-0d18-4228-b2a8-3716fa2097fa
|
|
(21) </x:SubID>
|
|
(22) </s12:Header>
|
|
(23) <s12:Body>
|
|
(24) <wse:Unsubscribe />
|
|
(25) </s12:Body>
|
|
(26) </s12:Envelope></pre></div></div><p>
|
|
Lines (07-09) in <a href="#Table10">Example 4-7</a> indicate the
|
|
message is a request to cancel a subscription. Lines (16-21)
|
|
indicate that the request is addressed to the manager for the
|
|
subscription created in <a href="#Table5">Example 4-2</a>.
|
|
</p><p>
|
|
<a href="#Table11">Example 4-8</a> lists a hypothetical response to the request in
|
|
<a href="#Table10">Example 4-7</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table11" id="Table11"></a>Example 4-8: Hypothetical response to unsubscribe request</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing" >
|
|
(04) <s12:Header>
|
|
(05) <wsa:Action>
|
|
(06) http://www.w3.org/2011/03/ws-evt/UnsubscribeResponse
|
|
(07) </wsa:Action>
|
|
(08) <wsa:RelatesTo>
|
|
(09) urn:uuid:2653f89f-25bc-4c2a-a7c4-620504f6b216
|
|
(10) </wsa:RelatesTo>
|
|
(11) <wsa:To>http://www.example.com/MyEventSink</wsa:To>
|
|
(12) </s12:Header>
|
|
(13) <s12:Body>
|
|
(14) <wse:UnsubscribeResponse/>
|
|
(15) </s12:Body>
|
|
(16) </s12:Envelope></pre></div></div></div><div class="div2">
|
|
<h3><a name="SubscriptionEnd" id="SubscriptionEnd"></a>4.5 SubscriptionEnd</h3><p>
|
|
If the event source terminates a subscription unexpectedly,
|
|
and it supports the use of the EndTo EPR, and the EndTo EPR
|
|
was present in the Subscribe message for that subscription
|
|
(see <a href="#Subscribe"><b>4.1 Subscribe</b></a>), the SubscriptionEnd message
|
|
MUST be sent to the endpoint reference indicated by that EPR,
|
|
if possible.
|
|
</p><p>
|
|
Note, a subscription expiring as expected is not considered to be
|
|
an unexpected termination, therefore a SubscriptionEnd message MUST NOT
|
|
be sent in this case.
|
|
</p><p>
|
|
The message MUST be of the following form:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
|
|
http://www.w3.org/2011/03/ws-evt/SubscriptionEnd
|
|
|
|
<b>[Body]</b>
|
|
<wse:SubscriptionEnd ...>
|
|
<wse:Status>
|
|
( http://www.w3.org/2011/03/ws-evt/DeliveryFailure |
|
|
http://www.w3.org/2011/03/ws-evt/SourceShuttingDown |
|
|
http://www.w3.org/2011/03/ws-evt/SourceCancelling |
|
|
<em>xs:anyURI</em> )
|
|
</wse:Status>
|
|
<wse:Reason xml:lang="<em>language identifier</em>" ><em>xs:string</em></wse:Reason> ?
|
|
<em>xs:any</em>*
|
|
</wse:SubscriptionEnd></pre></div></div><p>
|
|
The following describes additional, normative constraints on
|
|
the outline listed above:
|
|
</p><dl><dt class="label">
|
|
<b>[Body]</b>/wse:SubscriptionEnd/wse:Status =
|
|
"http://www.w3.org/2011/03/ws-evt/DeliveryFailure"
|
|
</dt><dd><p>
|
|
This value MUST be used if the event source terminated the
|
|
subscription because of problems delivering
|
|
notifications.
|
|
</p></dd><dt class="label">
|
|
<b>[Body]</b>/wse:SubscriptionEnd/wse:Status =
|
|
"http://www.w3.org/2011/03/ws-evt/SourceShuttingDown"
|
|
</dt><dd><p>
|
|
This value MUST be used if the event source terminated the
|
|
subscription because the source is being shut down in a
|
|
controlled manner; that is, if the event source is being shut
|
|
down but has the opportunity to send a SubscriptionEnd
|
|
message before it exits.
|
|
</p></dd><dt class="label">
|
|
<b>[Body]</b>/wse:SubscriptionEnd/wse:Status =
|
|
"http://www.w3.org/2011/03/ws-evt/SourceCancelling"
|
|
</dt><dd><p>
|
|
This value MUST be used if the event source terminated the
|
|
subscription for some other reason before it expired.
|
|
</p></dd><dt class="label"> <b>[Body]</b>/wse:SubscriptionEnd/wse:Reason </dt><dd><p>
|
|
This OPTIONAL element contains text, in the language
|
|
specified by the @xml:lang attribute, describing the reason
|
|
for the unexpected subscription termination.
|
|
</p></dd></dl><p>
|
|
Other components of the outline above are not further
|
|
constrained by this specification.
|
|
</p><p>
|
|
<a href="#Table12">Example 4-9</a> lists a hypothetical SubscriptionEnd message
|
|
corresponding to an early termination of the subscription created
|
|
in <a href="#Table4">Example 4-1</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table12" id="Table12"></a>Example 4-9: Hypothetical subscription end message</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:wse="http://www.w3.org/2011/03/ws-evt"
|
|
(05) xmlns:ew="http://www.example.com/warnings" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.w3.org/2011/03/ws-evt/SubscriptionEnd
|
|
(09) </wsa:Action>
|
|
(10) <wsa:To>http://www.example.com/MyEventSink</wsa:To>
|
|
(11) <ew:MySubscription wsa:IsReferenceParameter="true">
|
|
(12) 2597
|
|
(13) </ew:MySubscription>
|
|
(14) </s12:Header>
|
|
(15) <s12:Body>
|
|
(16) <wse:SubscriptionEnd>
|
|
(17) <wse:Status>wse:SourceShuttingDown</wse:Status>
|
|
(18) <wse:Reason xml:lang="en-US" >
|
|
(19) Event source going off line.
|
|
(20) </wse:Reason>
|
|
(21) </wse:SubscriptionEnd>
|
|
(22) </s12:Body>
|
|
(23) </s12:Envelope></pre></div></div><p>
|
|
Line (08) is the action IRI for SubscriptionEnd. Lines
|
|
(10-13) indicate the message is sent to the EndTo of the
|
|
subscribe request (lines (23-30) in <a href="#Table4">Example 4-1</a>).
|
|
Line (17) indicates the event source is shutting down, and
|
|
lines (18-20) indicate that the event source was going off
|
|
line.
|
|
</p></div></div><div class="div1">
|
|
<h2><a name="Notifications" id="Notifications"></a>5 Notifications</h2><p>
|
|
Notifications are SOAP messages that are transmitted to the event sink
|
|
as the result of a successful Subscribe operation.
|
|
</p><p>
|
|
<a href="#Table13">Example 5-1</a> lists a hypothetical notification message sent as
|
|
part of the subscription created by the subscribe request in
|
|
<a href="#Table4">Example 4-1</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="Table13" id="Table13"></a>Example 5-1: Hypothetical notification message</div><div class="exampleInner"><pre>(01) <s12:Envelope
|
|
(02) xmlns:s12="http://www.w3.org/2003/05/soap-envelope"
|
|
(03) xmlns:wsa="http://www.w3.org/2005/08/addressing"
|
|
(04) xmlns:ew="http://www.example.com/warnings"
|
|
(05) xmlns:ow="http://www.example.org/oceanwatch" >
|
|
(06) <s12:Header>
|
|
(07) <wsa:Action>
|
|
(08) http://www.example.org/oceanwatch/2003/WindReport
|
|
(09) </wsa:Action>
|
|
(10) <wsa:MessageID>
|
|
(11) urn:uuid:568b4ff2-5bc1-4512-957c-0fa545fd8d7f
|
|
(12) </wsa:MessageID>
|
|
(13) <wsa:To>http://www.other.example.com/OnStormWarning</wsa:To>
|
|
(14) <ew:MySubscription wsa:IsReferenceParameter="true">
|
|
(15) 2597
|
|
(16) </ew:MySubscription>
|
|
(17) </s12:Header>
|
|
(18) <s12:Body>
|
|
(19) <ow:WindReport>
|
|
(20) <ow:Date>030701</ow:Date>
|
|
(21) <ow:Time>0041</ow:Time>
|
|
(22) <ow:Speed>65</ow:Speed>
|
|
(23) <ow:Location>BRADENTON BEACH</ow:Location>
|
|
(24) <ow:County>MANATEE</ow:County>
|
|
(25) <ow:State>FL</ow:State>
|
|
(26) <ow:Lat>27.46</ow:Lat>
|
|
(27) <ow:Long>82.70</ow:Long>
|
|
(28) <ow:Comments xml:lang="en-US" >
|
|
(29) WINDS 55 WITH GUSTS TO 65. ROOF TORN OFF BOAT HOUSE. REPORTED
|
|
(30) BY STORM SPOTTER. (TBW)
|
|
(31) </ow:Comments>
|
|
(32) </ow:WindReport>
|
|
(33) </s12:Body>
|
|
(34) </s12:Envelope></pre></div></div><p>
|
|
Lines (13-16) indicate the message is sent to the endpoint
|
|
indicated by the subscribe request (lines (32-39) in
|
|
<a href="#Table4">Example 4-1</a>). Line (22) matches the filter in the
|
|
subscribe request (lines (42-44) in <a href="#Table4">Example 4-1</a>).
|
|
</p></div><div class="div1">
|
|
<h2><a name="Faults" id="Faults"></a>6 Faults</h2><p>
|
|
All fault messages defined in this specification MUST be sent
|
|
according to the rules and usage described in
|
|
<a href="#WSABinding">[WS-Addressing 1.0 SOAP Binding]</a>
|
|
Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults.
|
|
The <b>[Action]</b> property below MUST be used for faults
|
|
defined in this specification:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-evt/fault">http://www.w3.org/2011/03/ws-evt/fault</a></pre></div></div><p>
|
|
The definitions of faults in this section use the following properties:
|
|
</p><p>
|
|
<b>[Code]</b> The fault code.<br />
|
|
<b>[Subcode]</b> The fault subcode.<br />
|
|
<b>[Reason]</b> The English language reason element.<br />
|
|
<b>[Detail]</b> The detail element. If absent, no detail element
|
|
is defined for the fault.<br />
|
|
</p><p>The properties above bind to a SOAP 1.2 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre><s12:Envelope>
|
|
<s12:Header>
|
|
<wsa:Action> <b>[Action]</b> </wsa:Action>
|
|
<!-- Headers elided for brevity. -->
|
|
</s12:Header>
|
|
<s12:Body>
|
|
<s12:Fault>
|
|
<s12:Code>
|
|
<s12:Value><b>[Code]</b></s12:Value>
|
|
<s12:Subcode>
|
|
<s12:Value><b>[Subcode]</b></s12:Value>
|
|
</s12:Subcode>
|
|
</s12:Code>
|
|
<s12:Reason>
|
|
<s12:Text xml:lang="en"><b>[Reason]</b></s12:Text>
|
|
</s12:Reason>
|
|
<s12:Detail>
|
|
<b>[Detail]</b>
|
|
...
|
|
</s12:Detail>
|
|
</s12:Fault>
|
|
</s12:Body>
|
|
</s12:Envelope></pre></div></div><p>The properties bind to a SOAP 1.1 fault as follows:</p><div class="exampleOuter"><div class="exampleInner"><pre><s11:Envelope>
|
|
<s12:Header>
|
|
<wsa:Action> <b>[Action]</b> </wsa:Action>
|
|
<!-- Headers elided for brevity. -->
|
|
</s12:Header>
|
|
<s11:Body>
|
|
<s11:Fault>
|
|
<faultcode><b>[Subcode]</b></faultcode>
|
|
<faultstring xml:lang="en"><b>[Reason]</b></faultstring>
|
|
<detail>
|
|
<b>[Detail]</b>
|
|
...
|
|
</detail>
|
|
</s11:Fault>
|
|
</s11:Body>
|
|
</s11:Envelope></pre></div></div><div class="div2">
|
|
<h3><a name="FaultDetailRetryElement" id="FaultDetailRetryElement"></a>6.1 Fault Detail RetryAfter Element</h3><p>
|
|
The following element MAY be used to convey additional information in
|
|
the detail element of a fault.
|
|
</p><dl><dt class="label"> /wse:RetryAfter</dt><dd><p>
|
|
This element (whose content is of type xs:unsignedLong) is a suggested
|
|
minimum duration in milliseconds to wait before retransmitting the
|
|
message. Omission of this element indicates that a retry is never
|
|
likely to succeed.
|
|
</p></dd></dl></div><div class="div2">
|
|
<h3><a name="UnsupportedExpirationValue" id="UnsupportedExpirationValue"></a>6.2 UnsupportedExpirationValue</h3><p>
|
|
This fault MUST be generated when a request specifies an
|
|
expiration that is not within the min/max range.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnsupportedExpirationValue</td></tr><tr><td><b>[Reason]</b></td><td>The expiration time requested is not within the min/max range.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="UnsupportedExpirationType" id="UnsupportedExpirationType"></a>6.3 UnsupportedExpirationType</h3><p>
|
|
This fault MUST be generated when a request specifies an
|
|
expiration time and the event source is only capable of accepting
|
|
expiration durations; for instance, if the event source does not
|
|
have access to absolute time.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnsupportedExpirationType</td></tr><tr><td><b>[Reason]</b></td><td>Only expiration durations are supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="FilteringNotSupported" id="FilteringNotSupported"></a>6.4 FilteringNotSupported</h3><p>
|
|
This fault MUST be generated when a Subscribe request contains a filter
|
|
and the event source does not support filtering.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>Filtering is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="FilteringRequestedUnavailable" id="FilteringRequestedUnavailable"></a>6.5 FilteringRequestedUnavailable</h3><p>
|
|
This fault MUST be generated when a Subscribe request specifies a filter
|
|
dialect that the event source does not support. This
|
|
fault MAY contain a list of supported filter dialect IRIs in the
|
|
Detail property.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested filter dialect is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
|
|
<wse:SupportedDialect> +
|
|
<br />
|
|
<em>OPTIONAL; one per filter dialect supported by the
|
|
receiver</em>
|
|
</td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"></a>6.6 DeliveryFormatRequestedUnavailable</h3><p>
|
|
This fault MUST be generated when a Subscribe request specifies a delivery
|
|
format that is not supported by the event source. This
|
|
fault MAY contain a list of supported delivery format IRIs in the
|
|
Detail property.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:DeliveryFormatRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested delivery format is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
|
|
<wse:SupportedDeliveryFormat> +
|
|
<br />
|
|
<em> OPTIONAL, one per delivery format supported by the receiver.</em>
|
|
</td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="EmptyFilter" id="EmptyFilter"></a>6.7 EmptyFilter</h3><p>
|
|
This fault MUST be generated when an event source detects a
|
|
wse:Subscribe request containing a filter that, for whatever
|
|
reason, will never evaluate to true.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EmptyFilter</td></tr><tr><td><b>[Reason]</b></td><td>The wse:Filter would result in zero notifications.</td></tr><tr><td><b>[Detail]</b></td><td>
|
|
<em> The wse:Filter value. </em>
|
|
</td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="UnusableEPR" id="UnusableEPR"></a>6.8 UnusableEPR</h3><p>
|
|
This fault MUST be generated when an event source detects
|
|
that the wse:NotifyTo or wse:EndTo EPR is unusable.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnusableEPR</td></tr><tr><td><b>[Reason]</b></td><td>An EPR in the Subscribe request message is unusable.</td></tr><tr><td><b>[Detail]</b></td><td>
|
|
<em> The specific EPR that generated the error and why. </em>
|
|
</td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="UnknownSubscription" id="UnknownSubscription"></a>6.9 UnknownSubscription</h3><p>
|
|
This fault MUST be generated when a request specifies a subscription
|
|
that is not known.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnknownSubscription</td></tr><tr><td><b>[Reason]</b></td><td>The subscription is not known.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="EndToNotSupported" id="EndToNotSupported"></a>6.10 EndToNotSupported</h3><p>
|
|
This fault MUST be generated by an event source that does not support
|
|
/wse:Subscribe/wse:EndTo semantics, in response to a subscription
|
|
request that contains a wse:EndTo element.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EndToNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>wse:EndTo semantics is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="NoDeliveryMechanismEstablished" id="NoDeliveryMechanismEstablished"></a>6.11 NoDeliveryMechanismEstablished</h3><p>
|
|
This fault MUST be generated by an event source when the
|
|
Subscribe request message did not specify a delivery mechanism.
|
|
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:NoDeliveryMechanismEstablished</td></tr><tr><td><b>[Reason]</b></td><td>No delivery mechanism specified.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
|
|
<h3><a name="CannotProcessFilter" id="CannotProcessFilter"></a>6.12 CannotProcessFilter</h3><p>
|
|
This fault MUST be generated when the data source can not process the
|
|
filter content.
|
|
</p><table border="1"><tbody><tr><td> <b>[Code]</b> </td><td> s12:Sender </td></tr><tr><td> <b>[Subcode]</b> </td><td> wse:CannotProcessFilter </td></tr><tr><td> <b>[Reason]</b> </td><td>
|
|
Cannot filter as requested.
|
|
</td></tr><tr><td> <b>[Detail]</b> </td><td> </td></tr></tbody></table></div></div><div class="div1">
|
|
<h2><a name="Security" id="Security"></a>7 Security Considerations</h2><p>
|
|
This specification considers two sets of security requirements, those of
|
|
the applications that use the WS-Eventing protocol and those of the
|
|
protocol itself.
|
|
</p><p>
|
|
This specification makes no assumptions about the security requirements
|
|
of the applications that use WS-Eventing. However, once those
|
|
requirements have been satisfied within a given operational context,
|
|
the addition of WS-Eventing to this operational context cannot
|
|
undermine the fulfillment of those requirements; the use of
|
|
WS-Eventing SHOULD NOT create additional attack vectors within an
|
|
otherwise secure system.
|
|
</p><p>
|
|
The material below is not a "check list". There are many other
|
|
security concerns that need to be considered when implementing or
|
|
using this protocol. Implementers and users of this protocol are
|
|
urged to perform a security analysis to determine their particular
|
|
threat profile and the appropriate responses to those threats.
|
|
</p><div class="div2">
|
|
<h3><a name="idp1706496" id="idp1706496"></a>7.1 Notifications</h3><p>
|
|
The information contained in Notifications might be sensitive. In
|
|
such cases it is advisable to authenticate and authorize subscribers
|
|
as part of the processing of the Subscribe request. Note that an
|
|
Event Source may authorize the delivery of Notifications on a
|
|
per-message basis after the subscription has been created. This
|
|
might be necessary in cases where the sensitivity of the Notification
|
|
information is not known at Subscribe time or varies over the
|
|
lifetime of a subscription.
|
|
</p><p>
|
|
To protect the Notifications sent over a network, Notifications ought
|
|
to have the proper authenticity, integrity and confidentiality
|
|
protections applied.
|
|
</p><p>
|
|
The ability to subscribe on behalf of a third-party Event Sink
|
|
could be misused by a malicious Subscriber to create a
|
|
denial-of-service attack. While it does not remove the ability for
|
|
such misuse, authenticating Subscribers provides a way to deter
|
|
and trace the origin of such attempts. Additionally, the
|
|
authorization of Subscribers reduces the pool of potential attackers.
|
|
</p></div><div class="div2">
|
|
<h3><a name="idp1709584" id="idp1709584"></a>7.2 Subscriptions</h3><p>
|
|
Once created, subscriptions ought to be treated as protected
|
|
resources. Renew, GetStatus, and Unsubscribe requests ought to be
|
|
authenticated and authorized (for example, the identity of the
|
|
requester ought to be checked against the identity of the entity
|
|
that performed the original Subscribe request). Likewise
|
|
SubscriptionEnd messages ought to be authenticated and authorized
|
|
(for example, the identity of the sender ought to be checked
|
|
against the identity of the entity that sent the original
|
|
SubscribeResponse message). Note that authentication and
|
|
authorization policies (i.e. the rules that define which entities
|
|
are allowed to perform which requests and the mechanisms by which
|
|
the identities of these entities are discovered and verified)
|
|
are particular to individual deployments.
|
|
</p></div><div class="div2">
|
|
<h3><a name="idp1711632" id="idp1711632"></a>7.3 Endpoint Verification</h3><p>
|
|
Implementations that perform validity checks on the EPRs used in
|
|
WS-Eventing (wse:NotifyTo, wse:EndTo) are advised that such checks
|
|
can be misused to obtain information about a target network. For
|
|
example, suppose an Event Source implementation verifies the address
|
|
of NotifyTo EPRs by attempting to create a connection to the EPR's
|
|
address and faulting the Subscribe request if a connection cannot
|
|
be created. When deployed within a DMZ, such an Event Source could
|
|
be exploited by a malicious Subscriber to probe for other,
|
|
non-visible hosts by guessing target addresses and using them in
|
|
Subscribe requests. Note that, even if the returned fault does not
|
|
provide connection information, the time the Event Source spends
|
|
processing the Subscribe request might reveal if there is a host
|
|
with the target address.
|
|
</p><p>
|
|
Implementations that perform validity checks on the EPRs used in
|
|
WS-Eventing are advised to provide a means to disable such checks
|
|
in environments where these types of attacks are an issue.
|
|
</p></div></div><div class="div1">
|
|
<h2><a name="ImplConsideration" id="ImplConsideration"></a>8 Implementation Considerations</h2><p>
|
|
Event sinks SHOULD be prepared to receive notifications after
|
|
sending a subscribe request but before receiving a subscribe
|
|
response message. Event sinks SHOULD also be prepared to receive
|
|
notifications after receiving an unsubscribe response
|
|
message.
|
|
</p></div><div class="div1">
|
|
<h2><a name="metadata" id="metadata"></a>9 WS-Eventing Metadata</h2><p>
|
|
An endpoint MAY indicate its support of WS-Eventing, or its features,
|
|
by including the WS-Eventing EventSource or SubscriptionManager Policy
|
|
assertions within its WSDL. By
|
|
doing so the endpoint is indicating that the corresponding WS-Eventing
|
|
operations are supported by that endpoint even though they are implicit
|
|
and do not
|
|
explicitly appear in its WSDL (ie. the WS-Eventing operations do not
|
|
appear in the WSDL that MAY be retrievable by using WS-MetadataExchange
|
|
GetWSDL to that endpoint).
|
|
</p><p>
|
|
The WS-Eventing WSDL containing the operations indicated by the
|
|
EventSource or SubscriptionManager assertions MAY be exposed
|
|
by including the WSDL as a child of the appropriate Policy
|
|
assertion or by including a reference to it using the mex:Location
|
|
or mex:Reference element ( as described in
|
|
WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> Section 9).
|
|
</p><p>
|
|
This WS-Eventing WSDL can be annotated to indicate any endpoint
|
|
specific metadata that might be needed by clients interacting with
|
|
the WS-Eventing operations. For example, the WSDL MAY
|
|
have policy assertions
|
|
that indicate a particular security mechanism used to protect
|
|
the WS-Eventing operations supported by this endpoint.
|
|
</p><div class="div2">
|
|
<h3><a name="idp1720480" id="idp1720480"></a>9.1 EventSource Assertion</h3><p>
|
|
Services indicate support for the WS-Eventing's definition
|
|
of an event source through the use of the Web Services
|
|
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
|
|
Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
|
|
</p><p>
|
|
This specification defines a policy assertion (wse:EventSource).
|
|
The normative outline of this assertion is:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><wse:EventSource ...>
|
|
<wse:FilterDialect URI="<em>xs:anyURI</em>" ...>
|
|
<em>xs:any</em>*
|
|
</wse:FilterDialect> *
|
|
<wse:FormatName URI="<em>xs:anyURI</em>" ...>
|
|
<!-- Notification WSDL can go here - see <a href="#Advertising"><b>Advertising Event Information</b></a> -->
|
|
<em>xs:any</em>*
|
|
</wse:FormatName> *
|
|
<wse:DateTimeSupported .../> ?
|
|
<wse:Expires min="<em>xs:duration</em>"? max="<em>xs:duration</em>"? .../> ?
|
|
<wse:EndToSupported .../> ?
|
|
<wse:NotificationPolicy ...>
|
|
<em>xs:any</em>
|
|
</wse:NotificationPolicy> ?
|
|
<!-- EventDescription data can go here - see <a href="#Advertising"><b>Advertising Event Information</b></a> -->
|
|
<em>xs:any</em>*
|
|
</wse:EventSource></pre></div></div><p>
|
|
The following describes additional, normative constraints on the
|
|
outline listed above:
|
|
</p><dl><dt class="label"> /wse:EventSource </dt><dd><p>
|
|
This policy assertion has Endpoint Policy Subject. When present in a
|
|
policy alternative, it indicates that the subject is an event source
|
|
and the WS-Eventing protocol MUST
|
|
be used when communicating with this endpoint.
|
|
</p></dd><dt class="label"> /wse:EventSource/wse:FilterDialect </dt><dd><p>
|
|
When present, this OPTIONAL parameter indicates support for the
|
|
specified filter dialect IRI.
|
|
</p></dd><dt class="label"> /wse:EventSource/wse:FilterDialect/xs:any </dt><dd><p>
|
|
This extensibility point allows for additional FilterDialect
|
|
specific metadata to be included within the policy assertion. Any
|
|
metadata that appears is scoped to the use of the specified
|
|
FilterDialect URI.
|
|
</p></dd><dt class="label"> /wse:EventSource/wse:FormatName </dt><dd><p>
|
|
When present, this OPTIONAL parameter indicates support for the
|
|
specified event delivery format name URI.
|
|
</p></dd><dt class="label"> /wse:EventSource/wse:FormatName/xs:any </dt><dd><p>
|
|
This extensibility point allows for additional FormatName specific
|
|
metadata to be included within the policy assertion. Any metadata
|
|
that appears is scoped to the use of the specified FormatName URI.
|
|
If the Event Source advertises Notification WSDL then it MUST
|
|
appear as a child of the FormatName element.
|
|
</p></dd><dt class="label"> /wse:EventSource/wse:DateTimeSupported </dt><dd><p>
|
|
When present, this OPTIONAL parameter indicates support for
|
|
expiration time expressed as specific time (rather than duration).
|
|
</p></dd><dt class="label"> /wse:EventSource/wse:Expires </dt><dd><p>
|
|
When present, this OPTIONAL parameter indicates the minimum and
|
|
maximum subscription expiration times that this endpoint will support.
|
|
When the OPTIONAL 'min' attribute is absent then the Event Source
|
|
MUST not impose a lower bound on the accepted Expires values. The
|
|
implied default value for the OPTIONAL 'max' attribute is
|
|
infinite (or PT0S). In all cases, the 'min' value MUST be less
|
|
than or equal to the 'max' value.
|
|
</p></dd><dt class="label"> /wse:EventSource/wse:EndToSupported </dt><dd><p>
|
|
When present, this OPTIONAL parameter indicates support for the
|
|
/wse:Subscribe/wse:EndTo semantics. That is, when a subscription
|
|
request contains a wse:EndTo element, a SubscriptionEnd message
|
|
will be sent to the EPR contained in the wse:EndTo element, if
|
|
the subscription terminates unexpectedly.
|
|
</p></dd><dt class="label"> /wse:EventSource/wse:NotificationPolicy </dt><dd><p>
|
|
When present, this OPTIONAL parameter includes the Endpoint Subject
|
|
Policy that the event source supports for sending notifications.
|
|
This element MUST have one child element - typically a wsp:Policy
|
|
element or a wsp:PolicyReference element. A subscriber can use
|
|
this information to discover the valid set of Policy Alternatives
|
|
that MAY be used within a wse:NotifyTo EPR which will be
|
|
used for any Notification message sent from the event source to
|
|
the event sink.
|
|
Any policy alternatives included within this parameter SHOULD be
|
|
compatible with those Policy Alternatives available from the
|
|
Notification WSDLs that the event source advertises.
|
|
</p></dd><dt class="label"> /wse:EventSource/xs:any </dt><dd><p>
|
|
This extensibility point allows for additional WS-Eventing
|
|
specific metadata to be included within the policy assertion -
|
|
e.g. WS-Eventing WSDL, or nested policy assertions related to
|
|
the WS-Eventing message exchanges. Any metadata that appears
|
|
is scoped to the operations and features of the WS-Eventing
|
|
specification.
|
|
If the Event Source advertises EventDescription data then it
|
|
MUST appear as a child of the EventSource element.
|
|
</p></dd></dl><p>
|
|
The following is an example of a wse:EventSource policy assertion:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre>(01) <wse:EventSource ...>
|
|
(02) <wse:DateTimeSupported />
|
|
(03) <wse:FilterDialect URI="http://www.w3.org/2011/03/ws-evt/Dialects/XPath10"/>
|
|
(04) <wse:FormatName URI="http://www.w3.org/2011/03/ws-evt/DeliveryFormats/Wrap">
|
|
(05) <wsdl:definitions>
|
|
(06) <!-- WSDL for Wrapped Notifications -->
|
|
(07) </wsdl:definitions>
|
|
(08) </wse:FormatName>
|
|
(09) <wse:EndToSupported/>
|
|
(10) <wsevd:EventDescriptions>
|
|
(11) <!-- EventDescription data -->
|
|
(12) </wsevd:EventDescriptions>
|
|
(13) </wse:EventSource></pre></div></div><p>
|
|
In the above example line (02) indicates that this event source
|
|
supports expiration times as specific times. Line (03) indicates that
|
|
Filtering is supported and that it supports the XPath 1.0 filter
|
|
dialect. Lines (04) - (08) indicates that this event source supports
|
|
sending notifications in the Wrapped format and the Notification WSDL
|
|
defining the messages is included on lines (05) - (07). Line (09)
|
|
indicates that the EndTo features is supported. And finally, lines
|
|
(10) - (12) contains the EventDescription data that describes the
|
|
syntax of the events that this event source might send.
|
|
</p></div><div class="div2">
|
|
<h3><a name="idp1753440" id="idp1753440"></a>9.2 SubscriptionManager Assertion</h3><p>
|
|
Services indicate support for the
|
|
WS-Eventing's definition of a subscription manager
|
|
through the use of the Web Services
|
|
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
|
|
Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
|
|
</p><p>
|
|
This specification defines a policy assertion (wse:SubscriptionManager).
|
|
The normative outline of this assertion is:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><wse:SubscriptionManager ...>
|
|
<wse:DateTimeSupported .../> ?
|
|
<wse:Expires min="<em>xs:duration</em>"? max="<em>xs:duration</em>"? .../> ?
|
|
<em>xs:any</em>*
|
|
</wse:SubscriptionManager></pre></div></div><p>
|
|
The following describes additional, normative constraints on the
|
|
outline listed above:
|
|
</p><dl><dt class="label"> /wse:SubscriptionManager </dt><dd><p>
|
|
This policy assertion has Endpoint Policy Subject. When present in a
|
|
policy alternative, it indicates that the subject is an subscription
|
|
manager
|
|
and the WS-Eventing protocol MUST
|
|
be used when communicating with this endpoint.
|
|
</p></dd><dt class="label"> /wse:SubscriptionManager/wse:DateTimeSupported </dt><dd><p>
|
|
When present, this OPTIONAL parameter indicates support for
|
|
expiration time expressed as specific time (rather than duration).
|
|
</p></dd><dt class="label"> /wse:SubscriptionManager/wse:Expires </dt><dd><p>
|
|
When present, this OPTIONAL parameter indicates the minimum and
|
|
maximum subscription expiration times that this endpoint will support.
|
|
When the OPTIONAL 'min' attribute is absent then the Event Source
|
|
MUST not impose a lower bound on the accepted Expires values. The
|
|
implied default value for the OPTIONAL 'max' attribute is
|
|
infinite (or PT0S). In all cases, the 'min' value MUST be less
|
|
than or equal to the 'max' value.
|
|
</p></dd><dt class="label"> /wse:SubscriptionManager/xs:any </dt><dd><p>
|
|
This extensibility point allows for additional WS-Eventing
|
|
specific metadata to be included within the policy assertion -
|
|
e.g. WS-Eventing WSDL, or nested policy assertions related to the
|
|
WS-Eventing message exchanges. Any metadata that appears is scoped
|
|
to the operations and features of the WS-Eventing specification.
|
|
</p></dd></dl></div></div><div class="div1">
|
|
<h2><a name="acks" id="acks"></a>10 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="refs" id="refs"></a>11 References</h2><div class="div2">
|
|
<h3><a name="idp1771456" id="idp1771456"></a>11.1 Normative References</h3><dl><dt class="label"><a name="BP12" id="BP12"></a>BP12</dt><dd>
|
|
<a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html"><cite>
|
|
WS-I Profile, Basic Profile Version 1.2
|
|
</cite></a>
|
|
, R. Chumbley, et al, Editors.
|
|
Web Services Interoperability Organization (WS-I), 9 November 2010.
|
|
Available at <a href="http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-1.2-2010-11-09.html</a>.</dd><dt class="label"><a name="BP20" id="BP20"></a>BP20</dt><dd>
|
|
<a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html"><cite>
|
|
WS-I Profile, Basic Profile Version 2.0
|
|
</cite></a>
|
|
, R. Chumbley, et al, Editors.
|
|
Web Services Interoperability Organization (WS-I), 9 November 2010.
|
|
Available at <a href="http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html">http://ws-i.org/profiles/BasicProfile-2.0-2010-11-09.html</a>.</dd><dt class="label"><a name="RFC2119" id="RFC2119"></a>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="RFC3987" id="RFC3987"></a>RFC 3987</dt><dd>
|
|
<a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>
|
|
Internationalized Resource Identifiers (IRIs)
|
|
</cite></a>
|
|
, M. Duerst and M. Suignard, Authors.
|
|
Internet Engineering Task Force, January 2005.
|
|
Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd><dt class="label"><a name="SOAP11" id="SOAP11"></a>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"></a>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"></a>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="WSABinding" id="WSABinding"></a>WS-Addressing 1.0 SOAP Binding</dt><dd>
|
|
<a href="http://www.w3.org/TR/ws-addr-soap"><cite>
|
|
W3C Recommendation, "Web Services Addressing 1.0 - SOAP Binding"
|
|
</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-soap">http://www.w3.org/TR/ws-addr-soap</a>.</dd><dt class="label"><a name="WSEVD" id="WSEVD"></a>WS-EventDescriptions</dt><dd>
|
|
<a href="http://www.w3.org/TR/ws-event-descriptions"><cite>
|
|
W3C Working Group Draft, "Web Services Event Descriptions (WS-EventDescriptions) 1.0"
|
|
</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-event-descriptions">http://www.w3.org/TR/ws-event-descriptions</a>.</dd><dt class="label"><a name="wspolicy" id="wspolicy"></a>WS-Policy</dt><dd>
|
|
<a href="http://www.w3.org/TR/ws-policy/"><cite>
|
|
W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Framework"
|
|
</cite></a>
|
|
, A. Vedamuthu, et al., Editors.
|
|
World Wide Web Consortium (W3C), 4 September 2007.
|
|
Available at <a href="http://www.w3.org/TR/ws-policy/">http://www.w3.org/TR/ws-policy/</a>.</dd><dt class="label"><a name="wspolicyattach" id="wspolicyattach"></a>WS-Policy Attachment</dt><dd>
|
|
<a href="http://www.w3.org/TR/ws-policy-attach"><cite>
|
|
W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
|
|
</cite></a>
|
|
, A. Vedamuthu, et al., Editors.
|
|
World Wide Web Consortium (W3C), 4 September 2007.
|
|
Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd><dt class="label"><a name="WSDL11" id="WSDL11"></a>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></dl></div><div class="div2">
|
|
<h3><a name="idp1812592" id="idp1812592"></a>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"></a>WS-MakeConnection</dt><dd>
|
|
<a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
|
|
OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
|
|
Web Services Make Connection (WS-MakeConnection)
|
|
</cite></a>
|
|
, D. Davis, et al., Editors.
|
|
Organization for the Advancement of Structured Information Standards
|
|
(OASIS), 2 February 2009.
|
|
Available at <a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc">http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc</a>.</dd><dt class="label"><a name="MEX" id="MEX"></a>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="WSReliableMessaging" id="WSReliableMessaging"></a>WS-ReliableMessaging</dt><dd>
|
|
<a href="http://docs.oasis-open.org/ws-rx/wsrm/v1.2/wsrm.doc"><cite>
|
|
OASIS Standard, "Web Services Reliable Messaging Protocol
|
|
(WS-ReliableMessaging) 1.2"
|
|
</cite></a>
|
|
, Davis, et al., Editors.
|
|
Organization for the Advancement of Structured Information Standards
|
|
(OASIS), 2 February 2009.
|
|
Available at <a href="http://docs.oasis-open.org/ws-rx/wsrm/v1.2/wsrm.doc">http://docs.oasis-open.org/ws-rx/wsrm/v1.2/wsrm.doc</a>.</dd><dt class="label"><a name="XMLInfoset" id="XMLInfoset"></a>XML Infoset</dt><dd>
|
|
<a href="http://www.w3.org/TR/xml-infoset"><cite>
|
|
W3C Recommendation, "XML Information Set (Second Edition)"
|
|
</cite></a>
|
|
, J. Cowan, R. Tobin, Editors.
|
|
World Wide Web Consortium (W3C), 4 February 2004.
|
|
Available at <a href="http://www.w3.org/TR/xml-infoset">http://www.w3.org/TR/xml-infoset</a>.</dd><dt class="label"><a name="XMLSchema1" id="XMLSchema1"></a>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"></a>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><dt class="label"><a name="XPath1" id="XPath1"></a>XPath1.0</dt><dd>
|
|
<a href="http://www.w3.org/TR/xpath"><cite>
|
|
W3C Recommendation, "XML Path Language (XPath) Version 1.0"
|
|
</cite></a>
|
|
, J. Clark, S. DeRose, Editors.
|
|
World Wide Web Consortium (W3C), 16 November 1999.
|
|
Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd><dt class="label"><a name="XPath2" id="XPath2"></a>XPath2.0</dt><dd>
|
|
<a href="http://www.w3.org/TR/xpath20/"><cite>
|
|
W3C Recommendation, "XML Path Language (XPath) 2.0"
|
|
</cite></a>
|
|
, A. Berglund, et al., Editors.
|
|
World Wide Web Consortium (W3C), 23 January 2007.
|
|
Available at <a href="http://www.w3.org/TR/xpath20/">http://www.w3.org/TR/xpath20/</a>.</dd></dl></div></div></div><div class="back"><div class="div1">
|
|
<h2><a name="Advertising" id="Advertising"></a>A Advertising Event Information</h2><p>
|
|
There are many use cases for WS-Eventing in which it is necessary for the
|
|
subscriber and the event sink to know the structure and contents of the
|
|
notifications that can result from a successful Subscribe request. For
|
|
example, a developer might wish to use WSDL-based tools to generate
|
|
service stubs capable of unmarshalling and dispatching notifications. In
|
|
addition to this, the effective use of filters (including those in the
|
|
XPath dialect defined in <a href="#Subscribe"><b>4.1 Subscribe</b></a> as well as other
|
|
dialects not defined in this specification) requires some knowledge of
|
|
the schema of the events over which the filter will be applied.
|
|
</p><p>
|
|
There are many ways in which an event source could describe and
|
|
advertise the structure of the events for which it will issue
|
|
notifications. To provide a basic level of interoperability, this
|
|
specification uses the following two OPTIONAL mechanisms, in
|
|
<a href="#ETypes"><b>A.1 Event Types & Event Descriptions</b></a> and <a href="#NWSDL"><b>A.2 Notification WSDLs</b></a>, for describing and
|
|
advertising event information. If an implementation of a WS-Eventing
|
|
event source chooses to describe the structure of its events and
|
|
advertise this description, it is RECOMMENDED that at least one of
|
|
these mechanisms be used. Mechanisms other than these MAY be used
|
|
to describe and advertise the structure of events, but the definition
|
|
of such mechanisms is out of the scope of this specification.
|
|
</p><div class="div2">
|
|
<h3><a name="ETypes" id="ETypes"></a>A.1 Event Types & Event Descriptions</h3><p>
|
|
An event source MAY advertise the events that are generated by making
|
|
available an Event Description document as defined by
|
|
WS-EventDescriptions <a href="#WSEVD">[WS-EventDescriptions]</a>.
|
|
</p><p>
|
|
The following is an example of an EventDescriptions element that could
|
|
serve as a description of the Event Type used in
|
|
<a href="#Table1">Example 2-1</a>.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="idp1849856" id="idp1849856"></a>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
|
|
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
|
|
(03) xmlns:wsevd="http://www.w3.org/2011/03/ws-evt"
|
|
(04) xmlns:ow="http://www.example.org/oceanwatch">
|
|
(05) <wsevd:types>
|
|
(06) <xs:schema targetNamespace="http://www.example.org/oceanwatch">
|
|
(07) <xs:include schemaLocation="http://www.example.org/schemas/oceanwatch.xsd"/>
|
|
(08) <xs:element id="WindReport" type="ow:WindReportType"/>
|
|
(09) </xs:schema>
|
|
(10) </wsevd:types>
|
|
(11)
|
|
(12) <wsevd:eventType id="WindReportEvent"
|
|
(13) element="ow:WindReport"
|
|
(14) actionURI="http://www.example.org/oceanwatch/2003/WindReport"/>
|
|
(15) </wsevd:EventDescriptions></pre></div></div><p>
|
|
Lines (12-14) describe an Event Type with a QName of
|
|
"{http://www.example.org/oceanwatch/notifications}:WindReportEvent". The
|
|
XML Schema Global Element Declaration
|
|
(GED) for this Event Type is defined on line (08) as being of type
|
|
"{http://www.example.org/oceanwatch}:WindReportType".
|
|
</p><div class="div3">
|
|
<h4><a name="idp1852112" id="idp1852112"></a>A.1.1 Retrieving Event Descriptions</h4><p>
|
|
Although there are many ways in which an event source can make its
|
|
EventDescriptions available, this specification RECOMMENDS the use of
|
|
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
|
|
In particular, this specification RECOMMENDS that the Event Description
|
|
metadata be made available through the EventSource Policy assertion.
|
|
This MAY be done by either embedding the Event Descriptions metadata
|
|
directly within the assertion, or by including a MetadataExchange
|
|
reference to the data.
|
|
</p><p>
|
|
An event source MUST NOT have more than one EventDescriptions document.
|
|
</p><p>
|
|
The following examples show how Event Descriptions metadata might
|
|
appear within a WS-Eventing EventSource Policy assertion.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="embedEVD" id="embedEVD"></a>Example A-2: Sample Embedded Event Descriptions Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
|
|
(02) <wse:FormatName URI="..."/>
|
|
(03) <wsevd:EventDescriptions ...>
|
|
(04) ...
|
|
(05) </wsevd:EventDescriptions>
|
|
(06) </wse:EventSource></pre></div></div><p>
|
|
<a href="#embedEVD">Example A-2</a> shows how the Event Descriptiona metadata
|
|
might be embedded directly within a WS-Eventing EventSource Policy
|
|
assertion.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="refEVD" id="refEVD"></a>Example A-3: Sample Reference to Event Descriptions Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
|
|
(02) <wse:FormatName URI="..."/>
|
|
(03) <mex:Location
|
|
(04) Type="evd:EventDescriptions"
|
|
(05) URI="http://example.com/EVD_Metadata" />
|
|
(06) </wse:EventSource> </pre></div></div><p>
|
|
<a href="#refEVD">Example A-3</a> shows the same policy assertion from
|
|
<a href="#embedEVD">Example A-2</a> except the embedded Event Description
|
|
metadata is replaced with a reference to an HTTP resource whose
|
|
representation is the Event Descriptions metadata. The data can be
|
|
retrieved via an HTTP GET to the specified URL.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="mexEVD" id="mexEVD"></a>Example A-4: Sample GetMetadataResponse with Event Descriptions Metadata</div><div class="exampleInner"><pre>(01) <mex:GetMetadataResponse>
|
|
(02) <mex:Metadata>
|
|
(03) <mex:MetadataSection Dialect='wsevd:EventDescriptions'
|
|
(04) Identifier='...'>
|
|
(05) <wsevd:EventDescriptions ...>
|
|
(06) ...
|
|
(07) </wsevd:EventDescriptions>
|
|
(08) </mex:MetadataSection>
|
|
(09) </mex:Metadata>
|
|
(10) </mex:GetMetadataResponse> </pre></div></div><p>
|
|
<a href="#mexEVD">Example A-4</a> shows how the Event Descriptions metadata
|
|
might appear within a GetMetadataResponse message.
|
|
</p></div><div class="div3">
|
|
<h4><a name="idp1866096" id="idp1866096"></a>A.1.2 Bindings for Event Descriptions</h4><p>
|
|
For any Notification Format it MUST be possible to determine how a
|
|
given wsevd:eventType will appear on the wire as a notification in a
|
|
subscription created with that format. The following sections define
|
|
how wsevd:eventTypes bind to notifications for the two Notification
|
|
Formats defined in this specification; Unwrapped and Wrapped.
|
|
Specifications or profiles that define additional Notification Formats
|
|
MUST define how wsevd:eventTypes bind to the notifications for those
|
|
formats. In the absence of a mapping for a particular Notification
|
|
Format, implementations MAY provide a Notification WSDL (see below)
|
|
that explicitly describes the notification operations.
|
|
</p><div class="div4">
|
|
<h5><a name="idp1867904" id="idp1867904"></a>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
|
|
The information about an Event Type contained in the wsevd:eventType
|
|
element binds to a Unwrapped Notification for that type as follows:
|
|
</p><ul><li><p>
|
|
The <b>[Action]</b> property of the notification has the value of
|
|
the @actionURI attribute of the wsevd:eventType element
|
|
corresponding to the type of the event being transmitted.
|
|
</p></li><li><p>
|
|
The <b>[Body]</b> property of the notification
|
|
has a single child element. This child element is an instance of
|
|
the Global Element Declaration referenced by the @element attribute
|
|
of the wsevd:eventType element corresponding to the type of the
|
|
event being transmitted. If the @element attribute is absent then
|
|
the <b>[Body]</b> property has no children.
|
|
</p></li></ul></div><div class="div4">
|
|
<h5><a name="idp1872992" id="idp1872992"></a>A.1.2.2 Binding for Wrapped Notifications</h5><p>
|
|
The information about an Event Type contained in the eventType element
|
|
binds to a Wrapped Notification for that type as follows:
|
|
</p><ul><li><p>
|
|
The /soap:Envelope/soap:Body/wse:Notify/@actionURI attribute of the
|
|
Wrapped Notification has the value of the @actionURI attribute of
|
|
the eventType element corresponding to the type of the event
|
|
being transmitted.
|
|
</p></li><li><p>
|
|
The /soap:Envelope/soap:Body/wse:Notify element has a single child
|
|
element. This child element is an instance of the Global Element
|
|
Declaration referenced by the @element attribute of the eventType
|
|
element corresponding to the type of the event being transmitted.
|
|
If the @element attribute is absent then the wse:Notify element
|
|
has no children.
|
|
</p></li></ul></div></div></div><div class="div2">
|
|
<h3><a name="NWSDL" id="NWSDL"></a>A.2 Notification WSDLs</h3><p>
|
|
As described previously, events are transmitted to event sinks as
|
|
SOAP messages called "Notifications". These notifications MAY be
|
|
described via a Web Services Description Language <a href="#WSDL11">[WSDL11]</a>
|
|
definitions element termed a "Notification WSDL". A Notification WSDL
|
|
describes the interface that the event sink is REQUIRED to implement to
|
|
receive and process the notifications that might result from a
|
|
successful Subscribe request that used a particular Format IRI. The
|
|
following is an example of a Notification WSDL:
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="idp1879760" id="idp1879760"></a>Example A-5: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
|
|
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
|
|
(03) xmlns:xs="http://www.w3.org/2001/XMLSchema"
|
|
(04) xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
|
|
(05) xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"
|
|
(06) xmlns:ow="http://www.example.org/oceanwatch"
|
|
(07) xmlns:tns="http://www.example.org/oceanwatch/notifications">
|
|
(08) <wsdl:types>
|
|
(09) <xs:schema targetNamespace="http://www.example.org/oceanwatch">
|
|
(10) <xs:include schemaLocation="http://www.example.org/schemas/oceanwatch.xsd"/>
|
|
(11) <xs:element name="WindReport" type="ow:WindReportType"/>
|
|
(12) </xs:schema>
|
|
(13) </wsdl:types>
|
|
(14)
|
|
(15) <wsdl:message name="WindReportNotificationMsg">
|
|
(16) <wsdl:part name="event" element="ow:WindReport"/>
|
|
(17) </wsdl:message>
|
|
(18)
|
|
(19) <wsdl:portType name="WindReportPortType">
|
|
(20) <wsdl:operation name="WindReportNotificationOp">
|
|
(21) <wsdl:input message="tns:WindReportNotificationMsg"
|
|
(22) wsam:Action="http://www.example.org/oceanwatch/2003/WindReport"/>
|
|
(23) </wsdl:operation>
|
|
(24) </wsdl:portType>
|
|
(25)
|
|
(26) <wsdl:binding name="WindReportBinding" type="tns:WindReportPortType">
|
|
(27) <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
|
|
(28) <wsdl:operation name="WindReportNotificationOp">
|
|
(29) <soap:operation soapAction=""/>
|
|
(30) <wsdl:input>
|
|
(31) <soap:body use="literal"/>
|
|
(32) </wsdl:input>
|
|
(33) </wsdl:operation>
|
|
(34) </wsdl:binding>
|
|
(35) </wsdl:definitions></pre></div></div><div class="div3">
|
|
<h4><a name="idp1881200" id="idp1881200"></a>A.2.1 Retrieving Notification WSDLs</h4><p>
|
|
Although there are many ways in which an event source can make
|
|
Notification WSDLs available, this specification RECOMMENDS the use of
|
|
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
|
|
In particular, if an event source has Notification WSDL then it
|
|
SHOULD be referenced from the wse:EventSource policy assertion.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="embedNW" id="embedNW"></a>Example A-6: Sample Embedded Notification WSDL Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
|
|
(02) <wse:FormatName URI="...">
|
|
(03) <wsdl:definitions ...> ... </wsdl:definitions>
|
|
(04) </wse:FormatName>
|
|
(05) </wse:EventSource></pre></div></div><p>
|
|
<a href="#embedNW">Example A-6</a> shows how the Notification WSDL metadata
|
|
might be embedded directly within a WS-Eventing EventSource Policy
|
|
assertion. Notice that since Notification WSDL is related to
|
|
a particular FormatName, the Notification WSDL appears as a child
|
|
of the FormatName element.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="refNW" id="refNW"></a>Example A-7: Sample Reference to WSDL Definitions Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
|
|
(02) <wse:FormatName URI="...">
|
|
(03) <mex:Location
|
|
(04) Type="wsdl:definitions"
|
|
(05) URI="http://example.com/Notif_WSDL_Metadata" />
|
|
(06) </wse:FormatName>
|
|
(07) </wse:EventSource> </pre></div></div><p>
|
|
<a href="#refNW">Example A-7</a> shows the same policy assertion from
|
|
<a href="#embedNW">Example A-6</a> except the embedded Notification WSDL
|
|
metadata is replaced with a reference to an HTTP resource whose
|
|
representation is the WSDL definitions metadata. The data can be
|
|
retrieved via an HTTP GET to the specified URL.
|
|
</p><div class="exampleOuter">
|
|
<div class="exampleHeader"><a name="mexNW" id="mexNW"></a>Example A-8: Sample GetMetadataResponse with WSDL Definitions Metadata</div><div class="exampleInner"><pre>(01) <mex:GetMetadataResponse>
|
|
(02) <mex:Metadata>
|
|
(03) <mex:MetadataSection Dialect='wsdl:definitions'
|
|
(04) Identifier='...'>
|
|
(05) <wsdl:definitions ...>
|
|
(06) ...
|
|
(07) </wsdl:definitions>
|
|
(08) </mex:MetadataSection>
|
|
(09) </mex:Metadata>
|
|
(10) </mex:GetMetadataResponse> </pre></div></div><p>
|
|
<a href="#mexNW">Example A-8</a> shows how the WSDL definitions metadata
|
|
might appear within a GetMetadataResponse message. Notice that
|
|
because the metadata returned only contains the WSDL, and not
|
|
the associated FormatName URI, retrieving the Notificaton WSDL
|
|
in this fashion requires some other means to disambiguate multiple
|
|
Notification WSDL documents from each other as well as from any other
|
|
WSDL documents associated with the Event Source.
|
|
</p></div></div></div><div class="div1">
|
|
<h2><a name="Schema" id="Schema"></a>B 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/2011/03/ws-evt/eventing.xsd">http://www.w3.org/2011/03/ws-evt/eventing.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/2011/03/ws-evt'
|
|
xmlns:tns='http://www.w3.org/2011/03/ws-evt'
|
|
xmlns:wsa='http://www.w3.org/2005/08/addressing'
|
|
xmlns:xs='http://www.w3.org/2001/XMLSchema'
|
|
elementFormDefault='qualified'
|
|
blockDefault='#all'>
|
|
|
|
<xs:import
|
|
namespace='http://www.w3.org/XML/1998/namespace'
|
|
schemaLocation='http://www.w3.org/2001/xml.xsd' />
|
|
<xs:import
|
|
namespace='http://www.w3.org/2005/08/addressing'
|
|
schemaLocation='http://www.w3.org/2006/03/addressing/ws-addr.xsd' />
|
|
|
|
<!-- Types and global elements -->
|
|
<xs:complexType name='DeliveryType' mixed='true'>
|
|
<xs:sequence>
|
|
<xs:element ref='tns:NotifyTo' minOccurs='0' maxOccurs='1' />
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
|
|
<xs:complexType name='FormatType' mixed='true'>
|
|
<xs:sequence>
|
|
<xs:any namespace='##any' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:attribute name='Name' type='xs:anyURI' use='optional'
|
|
default='http://www.w3.org/2011/03/ws-evt/DeliveryFormats/Unwrap' />
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
|
|
<xs:simpleType name='NonNegativeDurationType'>
|
|
<xs:restriction base='xs:duration'>
|
|
<xs:minInclusive value='P0Y0M0DT0H0M0S' />
|
|
</xs:restriction>
|
|
</xs:simpleType>
|
|
|
|
<xs:simpleType name='DurationDateTime'>
|
|
<xs:union memberTypes='xs:dateTime tns:NonNegativeDurationType' />
|
|
</xs:simpleType>
|
|
|
|
<xs:complexType name='MiniExpirationType'>
|
|
<xs:simpleContent>
|
|
<xs:extension base='tns:DurationDateTime'>
|
|
<xs:anyAttribute namespace='##other' processContents='lax'/>
|
|
</xs:extension>
|
|
</xs:simpleContent>
|
|
</xs:complexType>
|
|
|
|
<xs:complexType name='ExpirationType'>
|
|
<xs:simpleContent>
|
|
<xs:extension base='tns:MiniExpirationType'>
|
|
<xs:attribute name='BestEffort' type='xs:boolean' use='optional'/>
|
|
<xs:anyAttribute namespace='##other' processContents='lax'/>
|
|
</xs:extension>
|
|
</xs:simpleContent>
|
|
</xs:complexType>
|
|
|
|
<xs:complexType name='FilterType' mixed='true'>
|
|
<xs:sequence>
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:attribute name='Dialect' type='xs:anyURI' use='optional'
|
|
default='http://www.w3.org/2011/03/ws-evt/Dialects/XPath10' />
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
|
|
<xs:complexType name='LanguageSpecificStringType'>
|
|
<xs:simpleContent>
|
|
<xs:extension base='xs:string'>
|
|
<xs:attribute ref='xml:lang' />
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:extension>
|
|
</xs:simpleContent>
|
|
</xs:complexType>
|
|
|
|
<xs:element name='NotifyTo' type='wsa:EndpointReferenceType' />
|
|
|
|
<xs:complexType name='NotificationPolicy'>
|
|
<xs:sequence>
|
|
<xs:any namespace='##other' processContents='lax'
|
|
maxOccurs='unbounded'/>
|
|
</xs:sequence>
|
|
</xs:complexType>
|
|
|
|
<!-- Subscribe request -->
|
|
<xs:element name='Subscribe'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:element name='EndTo' type='wsa:EndpointReferenceType'
|
|
minOccurs='0' />
|
|
<xs:element name='Delivery' type='tns:DeliveryType' />
|
|
<xs:element name='Format' type='tns:FormatType'
|
|
minOccurs='0' />
|
|
<xs:element name='Expires' type='tns:ExpirationType'
|
|
minOccurs='0' />
|
|
<xs:element name='Filter' type='tns:FilterType'
|
|
minOccurs='0' />
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<!-- Subscribe response -->
|
|
<xs:element name='SubscribeResponse'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:element name='SubscriptionManager'
|
|
type='wsa:EndpointReferenceType' />
|
|
<xs:element name='GrantedExpires' type='tns:MiniExpirationType' />
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<!-- Used in a fault if there's an unsupported dialect -->
|
|
<xs:element name='SupportedDialect' type='xs:anyURI' />
|
|
|
|
<!-- Used in a fault if there's an unsupported format name -->
|
|
<xs:element name='SupportedDeliveryFormat' type='xs:anyURI' />
|
|
|
|
<!-- Renew request -->
|
|
<xs:element name='Renew'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:element name='Expires' type='tns:ExpirationType'
|
|
minOccurs='0' />
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<!-- Renew response -->
|
|
<xs:element name='RenewResponse'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:element name='GrantedExpires' type='tns:MiniExpirationType' />
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<!-- GetStatus request -->
|
|
<xs:element name='GetStatus'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<!-- GetStatus response -->
|
|
<xs:element name='GetStatusResponse'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:element name='GrantedExpires' type='tns:MiniExpirationType' />
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<!-- Unsubscribe request -->
|
|
<xs:element name='Unsubscribe'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<!-- Unsubscribe response -->
|
|
<xs:element name='UnsubscribeResponse'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<!-- SubscriptionEnd message -->
|
|
<xs:element name='SubscriptionEnd'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:element name='Status'
|
|
type='tns:OpenSubscriptionEndCodeType' />
|
|
<xs:element name='Reason'
|
|
type='tns:LanguageSpecificStringType'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
<xs:any namespace='##other' processContents='lax'
|
|
minOccurs='0' maxOccurs='unbounded' />
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<xs:simpleType name='SubscriptionEndCodeType'>
|
|
<xs:restriction base='xs:anyURI'>
|
|
<xs:enumeration value=
|
|
'http://www.w3.org/2011/03/ws-evt/DeliveryFailure' />
|
|
<xs:enumeration value=
|
|
'http://www.w3.org/2011/03/ws-evt/SourceShuttingDown' />
|
|
<xs:enumeration value=
|
|
'http://www.w3.org/2011/03/ws-evt/SourceCancelling' />
|
|
</xs:restriction>
|
|
</xs:simpleType>
|
|
|
|
<xs:simpleType name='OpenSubscriptionEndCodeType'>
|
|
<xs:union memberTypes='tns:SubscriptionEndCodeType xs:anyURI' />
|
|
</xs:simpleType>
|
|
|
|
<!-- RetryAfter Fault Detail Element -->
|
|
<xs:element name='RetryAfter' type='tns:RetryAfterType'/>
|
|
<xs:complexType name='RetryAfterType'>
|
|
<xs:simpleContent>
|
|
<xs:extension base='xs:nonNegativeInteger'>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:extension>
|
|
</xs:simpleContent>
|
|
</xs:complexType>
|
|
|
|
<!-- Wrapped Events -->
|
|
<xs:complexType name='EventType' mixed='true'>
|
|
<xs:sequence>
|
|
<xs:any namespace='##any' processContents='lax' minOccurs='0'
|
|
maxOccurs='unbounded'/>
|
|
</xs:sequence>
|
|
<xs:attribute name='actionURI' type='xs:anyURI' use='optional' />
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
|
|
<xs:element name='Notify' type='tns:EventType' />
|
|
|
|
<!-- Policy -->
|
|
<xs:complexType name='Duration'>
|
|
<xs:simpleContent>
|
|
<xs:extension base='tns:NonNegativeDurationType'>
|
|
<xs:anyAttribute namespace='##other' processContents='lax'/>
|
|
</xs:extension>
|
|
</xs:simpleContent>
|
|
</xs:complexType>
|
|
|
|
<xs:complexType name='URI'>
|
|
<xs:simpleContent>
|
|
<xs:extension base='xs:anyURI'>
|
|
<xs:anyAttribute namespace='##other' processContents='lax'/>
|
|
</xs:extension>
|
|
</xs:simpleContent>
|
|
</xs:complexType>
|
|
|
|
<xs:complexType name='Empty'>
|
|
<xs:sequence/>
|
|
<xs:anyAttribute namespace='##other' processContents='lax'/>
|
|
</xs:complexType>
|
|
|
|
<xs:element name='EventSource'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:element name='FilterDialect' minOccurs='0' maxOccurs='unbounded'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:any namespace='##other' processContents='lax' minOccurs='0'
|
|
maxOccurs='0'/>
|
|
</xs:sequence>
|
|
<xs:attribute name='URI' type='xs:anyURI' use='required' />
|
|
<xs:anyAttribute namespace="##other" processContents='lax'/>
|
|
</xs:complexType>
|
|
</xs:element>
|
|
<xs:element name='FormatName' minOccurs='0' maxOccurs='unbounded'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:any namespace='##other' processContents='lax' minOccurs='0'
|
|
maxOccurs='0'/>
|
|
</xs:sequence>
|
|
<xs:attribute name='URI' type='xs:anyURI' use='required' />
|
|
<xs:anyAttribute namespace="##other" processContents='lax'/>
|
|
</xs:complexType>
|
|
</xs:element>
|
|
<xs:element name='DateTimeSupported' type='tns:Empty' minOccurs='0'/>
|
|
<xs:element name='Expires' minOccurs='0'>
|
|
<xs:complexType>
|
|
<xs:attribute name='min' type='xs:duration' use='optional'/>
|
|
<xs:attribute name='max' type='xs:duration' use='optional'/>
|
|
</xs:complexType>
|
|
</xs:element>
|
|
<xs:element name='EndToSupported' type='tns:Empty' minOccurs='0'/>
|
|
<xs:element name='NotificationPolicy' type='tns:NotificationPolicy'
|
|
minOccurs='0'/>
|
|
<xs:any namespace='##other' processContents='lax' minOccurs='0'
|
|
maxOccurs='unbounded'/>
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
|
|
<xs:element name='SubscriptionManager'>
|
|
<xs:complexType>
|
|
<xs:sequence>
|
|
<xs:element name='DateTimeSupported' type='tns:Empty' minOccurs='0'/>
|
|
<xs:element name='Expires' minOccurs='0'>
|
|
<xs:complexType>
|
|
<xs:attribute name='min' type='xs:duration' use='optional'/>
|
|
<xs:attribute name='max' type='xs:duration' use='optional'/>
|
|
</xs:complexType>
|
|
</xs:element>
|
|
<xs:any namespace='##other' processContents='lax' minOccurs='0'
|
|
maxOccurs='unbounded'/>
|
|
</xs:sequence>
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
</xs:element>
|
|
</xs:schema></pre></div></div></div><div class="div1">
|
|
<h2><a name="WSDL" id="WSDL"></a>C WSDL</h2><p>
|
|
A normative copy of the WSDL <a href="#WSDL11">[WSDL11]</a>
|
|
description can be retrieved from the following address:
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2011/03/ws-evt/eventing.wsdl">http://www.w3.org/2011/03/ws-evt/eventing.wsdl</a></pre></div></div><p>
|
|
A non-normative copy of the WSDL description is listed below
|
|
for convenience.
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsdl:definitions
|
|
targetNamespace='http://www.w3.org/2011/03/ws-evt'
|
|
xmlns:wsa='http://www.w3.org/2005/08/addressing'
|
|
xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'
|
|
xmlns:wse='http://www.w3.org/2011/03/ws-evt'
|
|
xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
|
|
xmlns:xs='http://www.w3.org/2001/XMLSchema' >
|
|
|
|
<wsdl:types>
|
|
<xs:schema>
|
|
<xs:import
|
|
namespace='http://www.w3.org/2011/03/ws-evt'
|
|
schemaLocation=
|
|
'http://www.w3.org/2011/03/ws-evt/eventing.xsd' />
|
|
</xs:schema>
|
|
</wsdl:types>
|
|
|
|
<wsdl:message name='SubscribeMsg' >
|
|
<wsdl:part name='body' element='wse:Subscribe' />
|
|
</wsdl:message>
|
|
<wsdl:message name='SubscribeResponseMsg' >
|
|
<wsdl:part name='body' element='wse:SubscribeResponse' />
|
|
</wsdl:message>
|
|
|
|
<wsdl:message name='RenewMsg' >
|
|
<wsdl:part name='body' element='wse:Renew' />
|
|
</wsdl:message>
|
|
<wsdl:message name='RenewResponseMsg' >
|
|
<wsdl:part name='body' element='wse:RenewResponse' />
|
|
</wsdl:message>
|
|
|
|
<wsdl:message name='GetStatusMsg' >
|
|
<wsdl:part name='body' element='wse:GetStatus' />
|
|
</wsdl:message>
|
|
<wsdl:message name='GetStatusResponseMsg' >
|
|
<wsdl:part name='body' element='wse:GetStatusResponse' />
|
|
</wsdl:message>
|
|
|
|
<wsdl:message name='UnsubscribeMsg' >
|
|
<wsdl:part name='body' element='wse:Unsubscribe' />
|
|
</wsdl:message>
|
|
<wsdl:message name='UnsubscribeResponseMsg' >
|
|
<wsdl:part name='body' element='wse:UnsubscribeResponse' />
|
|
</wsdl:message>
|
|
|
|
<wsdl:message name='SubscriptionEnd' >
|
|
<wsdl:part name='body' element='wse:SubscriptionEnd' />
|
|
</wsdl:message>
|
|
|
|
<wsdl:message name='notifyEvent'>
|
|
<wsdl:part name='parameter' element='wse:Notify'/>
|
|
</wsdl:message>
|
|
|
|
<wsdl:portType name='EventSource' >
|
|
<wsdl:operation name='SubscribeOp' >
|
|
<wsdl:input
|
|
message='wse:SubscribeMsg'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/Subscribe'/>
|
|
<wsdl:output
|
|
message='wse:SubscribeResponseMsg'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/SubscribeResponse'/>
|
|
</wsdl:operation>
|
|
</wsdl:portType>
|
|
|
|
<wsdl:portType name='SubscriptionEndPortType' >
|
|
<wsdl:operation name='SubscriptionEnd' >
|
|
<wsdl:input
|
|
message='wse:SubscriptionEnd'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/SubscriptionEnd'/>
|
|
</wsdl:operation>
|
|
</wsdl:portType>
|
|
|
|
<wsdl:portType name='SubscriptionManager' >
|
|
<wsdl:operation name='RenewOp' >
|
|
<wsdl:input
|
|
message='wse:RenewMsg'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/Renew'/>
|
|
<wsdl:output
|
|
message='wse:RenewResponseMsg'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/RenewResponse'/>
|
|
</wsdl:operation>
|
|
<wsdl:operation name='GetStatusOp' >
|
|
<wsdl:input
|
|
message='wse:GetStatusMsg'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/GetStatus'/>
|
|
<wsdl:output
|
|
message='wse:GetStatusResponseMsg'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/GetStatusResponse'/>
|
|
</wsdl:operation>
|
|
<wsdl:operation name='UnsubscribeOp' >
|
|
<wsdl:input
|
|
message='wse:UnsubscribeMsg'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/Unsubscribe'/>
|
|
<wsdl:output
|
|
message='wse:UnsubscribeResponseMsg'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/UnsubscribeResponse'/>
|
|
</wsdl:operation>
|
|
</wsdl:portType>
|
|
|
|
<wsdl:portType name='WrappedSinkPortType'>
|
|
<wsdl:operation name='NotifyEvent'>
|
|
<wsdl:input message='wse:notifyEvent'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/WrappedSinkPortType/NotifyEvent'/>
|
|
</wsdl:operation>
|
|
</wsdl:portType>
|
|
</wsdl:definitions></pre></div></div></div><div class="div1">
|
|
<h2><a name="wrappedWSDL" id="wrappedWSDL"></a>D WSDL for Standard Wrapped Delivery</h2><p>
|
|
If an event subscriber specifies the wrapped event delivery format
|
|
http://www.w3.org/2011/03/ws-evt/DeliveryFormats/Wrap
|
|
in the Subscribe request message, then the event sink MUST implement
|
|
the following abstract WSDL and notification messages MUST be
|
|
wrapped in the element defined in the WSDL.
|
|
</p><div class="exampleOuter"><div class="exampleInner"><pre><definitions
|
|
xmlns='http://schemas.xmlsoap.org/wsdl/'
|
|
xmlns:xs='http://www.w3.org/2001/XMLSchema'
|
|
xmlns:wsam='http://www.w3.org/2007/05/addressing/metadata'
|
|
xmlns:wsa='http://www.w3.org/2005/08/addressing/'
|
|
xmlns:tns='http://www.w3.org/2011/03/ws-evt'
|
|
targetNamespace='http://www.w3.org/2011/03/ws-evt'>
|
|
|
|
<types>
|
|
<xs:schema
|
|
targetNamespace='http://www.w3.org/2011/03/ws-evt'>
|
|
|
|
<xs:complexType name='EventType' mixed='true'>
|
|
<xs:sequence>
|
|
<xs:any namespace='##any' processContents='lax' minOccurs='0'
|
|
maxOccurs='unbounded'/>
|
|
</xs:sequence>
|
|
<xs:attribute name='actionURI' type='xs:anyURI' use='optional' />
|
|
<xs:anyAttribute namespace='##other' processContents='lax' />
|
|
</xs:complexType>
|
|
|
|
<xs:element name='Notify' type='tns:EventType' />
|
|
</xs:schema>
|
|
</types>
|
|
|
|
<message name='notifyEvent'>
|
|
<part name='parameter' element='tns:Notify'/>
|
|
</message>
|
|
|
|
<portType name='WrappedSinkPortType'>
|
|
<operation name='NotifyEvent'>
|
|
<input message='tns:notifyEvent'
|
|
wsam:Action='http://www.w3.org/2011/03/ws-evt/WrappedSinkPortType/NotifyEvent'/>
|
|
</operation>
|
|
</portType>
|
|
</definitions></pre></div></div></div><div class="div1">
|
|
<h2><a name="actiontables" id="actiontables"></a>E Action Tables</h2><p>
|
|
The purpose of the action tables is to illustrate, via a separate means
|
|
from the normative text, the allowable order and interactions of various
|
|
messages and activities. The action tables are not intended to constrain
|
|
implementations beyond those necessary to insure this ordering.
|
|
</p><ul><li><p>
|
|
Actions are represented as columns.
|
|
</p></li><li><p>
|
|
Triggers (messages, application actions, timer events) are represented
|
|
as rows. Triggers are annotated by their type;
|
|
"[app]" - represents an application action (e.g. a user selecting a
|
|
"Subscribe" menu item);
|
|
"[msg]" - represents an incoming, WS-Eventing defined, message;
|
|
"[timer]" - represents an internal timer event.
|
|
</p></li><li><p>
|
|
Each cell describes the appropriate action for a given state and
|
|
trigger.
|
|
Where the
|
|
action is dependent upon other factors than the state
|
|
and trigger (e.g. the value of a fault message), the activity is
|
|
described in pseudo-code. The section of the specification that
|
|
describes these activities is displayed in curly
|
|
brackets (e.g. "{4.2}").
|
|
</p></li><li><p>
|
|
Empty box indicates that the spec is silent for the specified
|
|
trigger/action pair.
|
|
</p></li></ul><table border="1"><caption>Table E-1: Event Source Action Table</caption><tbody><tr><td valign="bottom"> <b>Trigger</b> </td><td colspan="3" align="center"> <b>Action</b> </td></tr><tr><td valign="top" nowrap="nowrap"><code>
|
|
Subscribe Request <br />
|
|
[msg] </code>
|
|
</td><td valign="top"><code>
|
|
Create subscription<br />
|
|
Send SubscribeResponse +
|
|
Subscription Manager EPR<br />
|
|
{<a href="#Subscribe"><b>4.1</b></a>}</code>
|
|
</td></tr><tr><td valign="top" nowrap="nowrap"><code>
|
|
Event<br />
|
|
[app] </code>
|
|
</td><td valign="top"><code>
|
|
Send notification to all pertinent subscriptions<br />
|
|
{<a href="#Notifications"><b>5</b></a>}</code>
|
|
</td></tr></tbody></table><p></p><table border="1"><caption>Table E-2: Subscription Manager Action Table</caption><tbody><tr><td rowspan="2" valign="bottom"> <b>Trigger</b> </td><td colspan="2" align="center"> <b>Action</b> </td></tr><tr><td> <b>Trigger refers to a valid subscription</b> </td><td> <b>Trigger refers to an invalid subscription</b> </td></tr><tr><td valign="top" nowrap="nowrap"><code>
|
|
Renew Request<br />
|
|
[msg] </code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
Update expiration timer<br />
|
|
Send RenewResponse<br />
|
|
{<a href="#Renew"><b>4.2</b></a>}</code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
Generate UnknownSubscription Fault<br />
|
|
{<a href="#Renew"><b>4.2</b></a>}</code>
|
|
</td></tr><tr><td valign="top" nowrap="nowrap"><code>
|
|
GetStatus Request<br />
|
|
[msg] </code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
Send GetStatusResponse<br />
|
|
{<a href="#GetStatus"><b>4.3</b></a>}</code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
Generate UnknownSubscription Fault<br />
|
|
{<a href="#GetStatus"><b>4.3</b></a>}</code>
|
|
</td></tr><tr><td valign="top" nowrap="nowrap"><code>
|
|
Unsubscribe Request<br />
|
|
[msg] </code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
Invalidate Subscription<br />
|
|
Send UnsubscribeResponse<br />
|
|
{<a href="#Unsubscribe"><b>4.4</b></a>}</code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
Generate UnknownSubscription Fault<br />
|
|
{<a href="#Unsubscribe"><b>4.4</b></a>}</code>
|
|
</td></tr><tr><td valign="top" nowrap="nowrap"><code>
|
|
Expiration<br />
|
|
[timer] </code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
If (EndTo engaged)<br />
|
|
Send SubscriptionEnd<br />
|
|
Invalidate subscription<br />
|
|
{<a href="#Subscribe"><b>4.1</b></a>}</code>
|
|
</td><td valign="top" nowrap="nowrap"><code></code>
|
|
</td></tr><tr><td valign="top" nowrap="nowrap"><code>
|
|
Shutdown/Error<br />
|
|
[app] </code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
If (EndTo engaged)<br />
|
|
Send SubscriptionEnd<br />
|
|
Invalidate subscription<br />
|
|
{<a href="#Subscribe"><b>4.1</b></a>}</code>
|
|
</td><td valign="top" nowrap="nowrap"><code></code>
|
|
</td></tr></tbody></table><p></p><table border="1"><caption>Table E-3: Event Sink Action Table</caption><tbody><tr><td valign="bottom"> <b>Trigger</b> </td><td align="center"> <b>Action</b> </td></tr><tr><td valign="top" nowrap="nowrap"><code>
|
|
Expiration<br />
|
|
[timer] </code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
Invalidate subscription<br />
|
|
{<a href="#Subscribe"><b>4.1</b></a>}</code>
|
|
</td></tr><tr><td valign="top" nowrap="nowrap"><code>
|
|
SubscriptionEnd<br />
|
|
[msg]</code>
|
|
</td><td valign="top" nowrap="nowrap"><code>
|
|
Invalidate subscription<br />
|
|
{<a href="#SubscriptionEnd"><b>4.5</b></a>}</code>
|
|
</td></tr></tbody></table></div><div class="div1">
|
|
<h2><a name="changelog" id="changelog"></a>F Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6391">6391</a>
|
|
</td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6519">6519</a>
|
|
</td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6427">6427</a>
|
|
</td></tr><tr><td> 2009/03/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6459">6459</a>
|
|
</td></tr><tr><td> 2009/03/09 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6397">6397</a>
|
|
</td></tr><tr><td> 2009/03/09 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6426">6426</a>
|
|
</td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added change log </td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6641">6641</a>
|
|
</td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6498">6498</a>
|
|
</td></tr><tr><td> 2009/03/11 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6425">6425</a>
|
|
</td></tr><tr><td> 2009/03/16 </td><td> KW </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6587">6587</a>
|
|
</td></tr><tr><td> 2009/03/17 </td><td> KW </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6400">6400</a>
|
|
</td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6428">6428</a>
|
|
</td></tr><tr><td> 2009/03/17 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6687">6687</a>
|
|
</td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6666">6666</a>
|
|
</td></tr><tr><td> 2009/03/23 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6681">6681</a>
|
|
</td></tr><tr><td> 2009/03/24 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6595">6595</a>
|
|
</td></tr><tr><td> 2009/03/24 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6648">6648</a>
|
|
</td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6727">6727</a>
|
|
</td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6725">6725</a>
|
|
</td></tr><tr><td> 2009/04/07 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6715">6715</a>
|
|
</td></tr><tr><td> 2009/04/22 </td><td> KW </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6739">6739</a>
|
|
</td></tr><tr><td> 2009/04/28 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6787">6787</a>
|
|
</td></tr><tr><td> 2009/04/28 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6788">6788</a>
|
|
</td></tr><tr><td> 2009/05/13 </td><td> KW </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6472">6472</a>
|
|
</td></tr><tr><td> 2009/05/13 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6850">6850</a>
|
|
</td></tr><tr><td> 2009/05/13 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6696">6696</a>
|
|
</td></tr><tr><td> 2009/05/19 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6907">6907</a>
|
|
</td></tr><tr><td> 2009/05/19 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6429">6429</a>
|
|
</td></tr><tr><td> 2009/05/21 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6674">6674</a>
|
|
</td></tr><tr><td> 2009/05/27 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6906">6906</a>
|
|
</td></tr><tr><td> 2009/06/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6955">6955</a>
|
|
</td></tr><tr><td> 2009/06/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6916">6916</a>
|
|
</td></tr><tr><td> 2009/06/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6986">6986</a>
|
|
</td></tr><tr><td> 2009/07/07 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7039">7039</a>
|
|
</td></tr><tr><td> 2009/07/21 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6980">6980</a>
|
|
</td></tr><tr><td> 2009/07/28 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6692">6692</a>
|
|
</td></tr><tr><td> 2009/08/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7136">7136</a>
|
|
</td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6432">6432</a>
|
|
</td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7159">7159</a>
|
|
</td></tr><tr><td> 2009/08/05 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7205">7205</a>
|
|
</td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</a>
|
|
</td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7365">7365</a>
|
|
</td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a>
|
|
</td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7235">7235</a>
|
|
</td></tr><tr><td> 2009/08/26 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7160">7160</a>
|
|
</td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</a>
|
|
</td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a>
|
|
</td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6401">6401</a>
|
|
</td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a>
|
|
</td></tr><tr><td> 2009/09/22 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7698">7698</a>
|
|
</td></tr><tr><td> 2009/09/23 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6569">6569</a>
|
|
</td></tr><tr><td> 2009/10/01 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7589">7589</a>
|
|
</td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7426">7426</a>
|
|
</td></tr><tr><td> 2009/10/02 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7554">7554</a>
|
|
</td></tr><tr><td> 2009/10/05 </td><td> DD </td><td> Added resolution of issues
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6402">6402</a>,
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</a>
|
|
</td></tr><tr><td> 2009/10/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7478">7478</a>
|
|
</td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</a>
|
|
</td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7982">7982</a>
|
|
</td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a>
|
|
</td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7553">7553</a>
|
|
</td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a>
|
|
</td></tr><tr><td> 2009/10/27 </td><td> DD </td><td> Added resolution of issues
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7586">7586</a>,
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7588">7588</a>,
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7828">7828</a>
|
|
</td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8076">8076</a>
|
|
</td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8172">8172</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8168">8168</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7970">7970</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8213">8213</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8170">8170</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8162">8162</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8163">8163</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8166">8166</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8167">8167</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8169">8169</a>
|
|
</td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a>
|
|
</td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</a>
|
|
</td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8276">8276</a>
|
|
</td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8277">8277</a>
|
|
</td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8285">8285</a>
|
|
</td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</a>
|
|
</td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8287">8287</a>
|
|
</td></tr><tr><td> 2010/01/05 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8165">8165</a>
|
|
</td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8164">8164</a>
|
|
</td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8281">8281</a>
|
|
</td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</a>
|
|
</td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</a>
|
|
</td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</a>
|
|
</td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</a>
|
|
</td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8288">8288</a>
|
|
</td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</a>
|
|
</td></tr><tr><td> 2010/01/27 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986">7986</a>
|
|
</td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</a>
|
|
</td></tr><tr><td> 2010/02/05 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435">6435</a>
|
|
</td></tr><tr><td> 2010/02/08 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</a>
|
|
</td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a>
|
|
</td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8271">8271</a>
|
|
</td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</a>,
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a>
|
|
</td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a>
|
|
</td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9320">9320</a>
|
|
</td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</a>
|
|
</td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9266">9266</a>
|
|
</td></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</a>
|
|
</td></tr><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9543">9543</a>
|
|
</td></tr><tr><td> 2010/04/27 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8832">8832</a>
|
|
</td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9588">9588</a>
|
|
</td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9567">9567</a>
|
|
</td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9613">9613</a>
|
|
</td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9699">9699</a>
|
|
</td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9676">9676</a>
|
|
</td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9712">9712</a>
|
|
</td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9713">9713</a>
|
|
</td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9675">9675</a>
|
|
</td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9717">9717</a>
|
|
</td></tr><tr><td> 2010/05/12 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9701">9701</a>
|
|
</td></tr><tr><td> 2010/05/13 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9702">9702</a>
|
|
</td></tr><tr><td> 2010/05/13 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9610">9610</a>
|
|
</td></tr><tr><td> 2010/06/15 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9610">9610</a>
|
|
</td></tr><tr><td> 2010/08/17 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10339">10339</a>
|
|
</td></tr><tr><td> 2010/08/18 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10376">10376</a>
|
|
</td></tr><tr><td> 2010/08/18 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10960">10960</a>
|
|
</td></tr><tr><td> 2010/08/19 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8284">8284</a>
|
|
</td></tr><tr><td> 2011/01/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11667">11667</a>
|
|
</td></tr><tr><td> 2011/01/04 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11551">11551</a>
|
|
</td></tr><tr><td> 2011/01/26 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11874">11874</a>
|
|
</td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11882">11882</a>
|
|
</td></tr><tr><td> 2011/02/01 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11703">11703</a>
|
|
</td></tr><tr><td> 2011/02/07 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11899">11899</a>
|
|
</td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12051">12051</a>
|
|
</td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11698">11698</a>
|
|
</td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11894">11894</a>
|
|
</td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12063">12063</a>
|
|
</td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11949">11949</a>
|
|
</td></tr><tr><td> 2011/04/24 </td><td> DD </td><td> Added resolution of issue
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12722">12722</a>
|
|
</td></tr></tbody></table></div></div></body></html>
|