- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 02 Jun 2010 12:06:45 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv1264
Modified Files:
wseventing.html wseventing.xml
Log Message:
add missing VerifySupported policy parameter
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.194
retrieving revision 1.195
diff -u -d -r1.194 -r1.195
--- wseventing.xml 13 May 2010 22:39:18 -0000 1.194
+++ wseventing.xml 2 Jun 2010 12:06:43 -0000 1.195
@@ -2979,6 +2979,7 @@
<wse:ExpiresTimeSupported .../> ?
<wse:DateTimeSupported .../> ?
<wse:MaxExpires ...> <emph>xs:duration</emph> </wse:MaxExpires> ?
+ <wse:VerifySupported .../> ?
<emph>xs:any</emph>*
</wse:SubscriptionManager></eg>
</example>
@@ -3037,6 +3038,16 @@
</gitem>
<gitem>
+ <label> /wse:SubscriptionManager/wse:VerifySupported </label>
+ <def>
+ <p>
+ When present, this OPTIONAL parameter indicates support for
+ the Verify element on the GetStatus operation.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
<label> /wse:SubscriptionManager/xs:any </label>
<def>
<p>
@@ -4044,6 +4055,7 @@
<xs:element name='ExpiresSupported' type='tns:Empty' minOccurs='0'/>
<xs:element name='DateTimeSupported' type='tns:Empty' minOccurs='0'/>
<xs:element name='MaxExpires' type='tns:Duration' minOccurs='0'/>
+ <xs:element name='VerifySupported' type='tns:Empty' minOccurs='0'/>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
</xs:sequence>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.201
retrieving revision 1.202
diff -u -d -r1.201 -r1.202
--- wseventing.html 13 May 2010 22:39:18 -0000 1.201
+++ wseventing.html 2 Jun 2010 12:06:43 -0000 1.202
@@ -31,7 +31,8 @@
</style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"/></head><body><div class="head">
<h1><a name="title" id="title"/>Web Services Eventing (WS-Eventing)</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"/>Editor's Draft $Date$</h2><dl><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/2009/WD-ws-eventing-20090317">http://www.w3.org/TR/2009/WD-ws-eventing-20090317</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 class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consrtium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
+ </a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2009/WD-ws-eventing-20090317">http://www.w3.org/TR/2009/WD-ws-eventing-20090317
+ </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 class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p></div><hr/><div>
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
This specification describes a protocol that allows Web
services to subscribe to or accept subscriptions for
@@ -73,29 +74,29 @@
6.11 <a href="#EndToNotSupported">EndToNotSupported</a><br/>
6.12 <a href="#NoDeliveryMechanismEstablished">NoDeliveryMechanismEstablished</a><br/>
7 <a href="#Security">Security Considerations</a><br/>
- 7.1 <a href="#iddiv2_1_2159">Notifications</a><br/>
- 7.2 <a href="#iddiv2_1_2168">Subscriptions</a><br/>
- 7.3 <a href="#iddiv2_1_2173">Endpoint Verification</a><br/>
+ 7.1 <a href="#iddiv2x1x2159">Notifications</a><br/>
+ 7.2 <a href="#iddiv2x1x2168">Subscriptions</a><br/>
+ 7.3 <a href="#iddiv2x1x2173">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="#iddiv2_1_2199">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2326">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2x1x2199">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2x1x2326">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2392">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2539">Informative References</a><br/>
+ 11.1 <a href="#iddiv2x1x2398">Normative References</a><br/>
+ 11.2 <a href="#iddiv2x1x2545">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>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="#iddiv3_1_2741">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2778">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2783">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2804">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3x1x2747">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3x1x2784">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4x1x2789">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4x1x2810">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2831">Retrieving Notification WSDLs</a><br/>
+ A.2.1 <a href="#iddiv3x1x2837">Retrieving Notification WSDLs</a><br/>
B <a href="#VerificationEvent">Verification Event</a><br/>
- B.1 <a href="#iddiv2_1_2848">EventDescription for the Verification Event</a><br/>
- B.2 <a href="#iddiv2_1_2857">Notification WSDL for the Verification Event</a><br/>
+ B.1 <a href="#iddiv2x1x2854">EventDescription for the Verification Event</a><br/>
+ B.2 <a href="#iddiv2x1x2863">Notification WSDL for the Verification Event</a><br/>
C <a href="#Schema">XML Schema</a><br/>
D <a href="#WSDL">WSDL</a><br/>
E <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -1455,7 +1456,7 @@
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="iddiv2_1_2159" id="iddiv2_1_2159"/>7.1 Notifications</h3><p>
+<h3><a name="iddiv2x1x2159" id="iddiv2x1x2159"/>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
@@ -1476,7 +1477,7 @@
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="iddiv2_1_2168" id="iddiv2_1_2168"/>7.2 Subscriptions</h3><p>
+<h3><a name="iddiv2x1x2168" id="iddiv2x1x2168"/>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
@@ -1491,7 +1492,7 @@
the identities of these entities are discovered and verified)
are particular to individual deployments.
</p></div><div class="div2">
-<h3><a name="iddiv2_1_2173" id="iddiv2_1_2173"/>7.3 Endpoint Verification</h3><p>
+<h3><a name="iddiv2x1x2173" id="iddiv2x1x2173"/>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
@@ -1542,7 +1543,7 @@
that indicate a particular security mechanism used to protect
the WS-Eventing operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_2199" id="iddiv2_1_2199"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2x1x2199" id="iddiv2x1x2199"/>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 -
@@ -1656,7 +1657,7 @@
(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="iddiv2_1_2326" id="iddiv2_1_2326"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2x1x2326" id="iddiv2x1x2326"/>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
@@ -1669,6 +1670,7 @@
<wse:ExpiresTimeSupported .../> ?
<wse:DateTimeSupported .../> ?
<wse:MaxExpires ...> <em>xs:duration</em> </wse:MaxExpires> ?
+ <wse:VerifySupported .../> ?
<em>xs:any</em>*
</wse:SubscriptionManager></pre></div></div><p>
The following describes additional, normative constraints on the
@@ -1691,6 +1693,9 @@
The implied default is indefinite.
Note: a value of "PT0S" indicates that this endpoint supports
subscriptions with an infinite lifetime.
+ </p></dd><dt class="label"> /wse:SubscriptionManager/wse:VerifySupported </dt><dd><p>
+ When present, this OPTIONAL parameter indicates support for
+ the Verify element on the GetStatus operation.
</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 -
@@ -1729,7 +1734,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2392" id="iddiv2_1_2392"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2x1x2398" id="iddiv2x1x2398"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1786,7 +1791,7 @@
, 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="iddiv2_1_2539" id="iddiv2_1_2539"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+<h3><a name="iddiv2x1x2545" id="iddiv2x1x2545"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>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>
@@ -1890,7 +1895,7 @@
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="idexample_1_2731" id="idexample_1_2731"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
+<div class="exampleHeader"><a name="idexamplex1x2737" id="idexamplex1x2737"/>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/2002/ws/ra/edcopies/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1910,7 +1915,7 @@
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="iddiv3_1_2741" id="iddiv3_1_2741"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x2747" id="iddiv3x1x2747"/>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>.
@@ -1948,7 +1953,7 @@
representation is the Event Description metadata. The data can be
retrieved via an HTTP GET to the specified URL.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_2778" id="iddiv3_1_2778"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x2784" id="iddiv3x1x2784"/>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
@@ -1960,7 +1965,7 @@
Format, implementations MAY provide a Notification WSDL (see below)
that explicitly describes the notification operations.
</p><div class="div4">
-<h5><a name="iddiv4_1_2783" id="iddiv4_1_2783"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2789" id="iddiv4x1x2789"/>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>
@@ -1975,7 +1980,7 @@
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="iddiv4_1_2804" id="iddiv4_1_2804"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2810" id="iddiv4x1x2810"/>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>
@@ -2001,7 +2006,7 @@
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="idexample_1_2825" id="idexample_1_2825"/>Example A-4: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexamplex1x2831" id="idexamplex1x2831"/>Example A-4: 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/"
@@ -2036,7 +2041,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2831" id="iddiv3_1_2831"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3x1x2837" id="iddiv3x1x2837"/>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>.
@@ -2049,7 +2054,7 @@
notification to the event sink. A notification of the 'verification event'
is used in this test.
</p><div class="div2">
-<h3><a name="iddiv2_1_2848" id="iddiv2_1_2848"/>B.1 EventDescription for the Verification Event</h3><p>
+<h3><a name="iddiv2x1x2854" id="iddiv2x1x2854"/>B.1 EventDescription for the Verification Event</h3><p>
The verification event is described by the following EventDescription.
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsevd:EventDescriptions
xmlns:wsevd='http://www.w3.org/2002/ws/ra/edcopies/ws-evd'
@@ -2068,7 +2073,7 @@
element='wse:Verification'
actionURI='http://www.w3.org/2002/ws/ra/edcopies/ws-evt/Verfication'/>
</wsevd:EventDescriptions></pre></div></div></div><div class="div2">
-<h3><a name="iddiv2_1_2857" id="iddiv2_1_2857"/>B.2 Notification WSDL for the Verification Event</h3><p>
+<h3><a name="iddiv2x1x2863" id="iddiv2x1x2863"/>B.2 Notification WSDL for the Verification Event</h3><p>
The verification event is described by the following Notification WSDL.
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsdl:definitions
xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
@@ -2449,6 +2454,7 @@
<xs:element name='ExpiresSupported' type='tns:Empty' minOccurs='0'/>
<xs:element name='DateTimeSupported' type='tns:Empty' minOccurs='0'/>
<xs:element name='MaxExpires' type='tns:Duration' minOccurs='0'/>
+ <xs:element name='VerifySupported' type='tns:Empty' minOccurs='0'/>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
</xs:sequence>
Received on Wednesday, 2 June 2010 12:06:47 UTC