- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 12 May 2010 22:24:13 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv1979
Modified Files:
wseventing.html wseventing.xml
Log Message:
9701
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.190
retrieving revision 1.191
diff -u -d -r1.190 -r1.191
--- wseventing.xml 12 May 2010 22:16:30 -0000 1.190
+++ wseventing.xml 12 May 2010 22:24:11 -0000 1.191
@@ -928,7 +928,9 @@
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.
+ at least one child element. If no delivery mechanism is
+ specified then the event source MUST generate a
+ wse:NoDeliveryMechanismEstablished fault.
</p>
</def>
</gitem>
@@ -2530,6 +2532,39 @@
</table>
</div2>
+ <div2 id="NoDeliveryMechanismEstablished">
+ <head>NoDeliveryMechanismEstablished</head>
+
+ <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><kw>[Code]</kw></td>
+ <td>s12:Sender</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Subcode]</kw></td>
+ <td>wse:NoDeliveryMechanismEstablished</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Reason]</kw></td>
+ <td>No delivery mechanism specified.</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Detail]</kw></td>
+ <td><emph>none</emph></td>
+ </tr>
+ </tbody>
+ </table>
+ </div2>
+
</div1>
<div1 id="Security">
@@ -5071,6 +5106,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9717">9717</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/05/12 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9701">9701</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.197
retrieving revision 1.198
diff -u -d -r1.197 -r1.198
--- wseventing.html 12 May 2010 22:16:30 -0000 1.197
+++ wseventing.html 12 May 2010 22:24:11 -0000 1.198
@@ -71,27 +71,28 @@
6.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
6.10 <a href="#UnknownSubscription">UnknownSubscription</a><br/>
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_2119">Notifications</a><br/>
- 7.2 <a href="#iddiv2_1_2128">Subscriptions</a><br/>
- 7.3 <a href="#iddiv2_1_2133">Endpoint Verification</a><br/>
+ 7.1 <a href="#iddiv2_1_2169">Notifications</a><br/>
+ 7.2 <a href="#iddiv2_1_2178">Subscriptions</a><br/>
+ 7.3 <a href="#iddiv2_1_2183">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_2159">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2280">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2209">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2330">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2340">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2487">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2390">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2537">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_2689">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2726">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2731">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2752">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2739">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2776">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2781">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2802">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2779">Retrieving Notification WSDLs</a><br/>
+ A.2.1 <a href="#iddiv3_1_2829">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/>
@@ -550,7 +551,9 @@
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.
+ 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
@@ -1410,7 +1413,11 @@
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><div class="div1">
+ </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"/>6.12 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><div class="div1">
<h2><a name="Security" id="Security"/>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
@@ -1430,7 +1437,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_2119" id="iddiv2_1_2119"/>7.1 Notifications</h3><p>
+<h3><a name="iddiv2_1_2169" id="iddiv2_1_2169"/>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
@@ -1451,7 +1458,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_2128" id="iddiv2_1_2128"/>7.2 Subscriptions</h3><p>
+<h3><a name="iddiv2_1_2178" id="iddiv2_1_2178"/>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
@@ -1466,7 +1473,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_2133" id="iddiv2_1_2133"/>7.3 Endpoint Verification</h3><p>
+<h3><a name="iddiv2_1_2183" id="iddiv2_1_2183"/>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
@@ -1517,7 +1524,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_2159" id="iddiv2_1_2159"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2209" id="iddiv2_1_2209"/>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 -
@@ -1627,7 +1634,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_2280" id="iddiv2_1_2280"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2330" id="iddiv2_1_2330"/>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
@@ -1696,7 +1703,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_2340" id="iddiv2_1_2340"/>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="iddiv2_1_2390" id="iddiv2_1_2390"/>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.
@@ -1753,7 +1760,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_2487" id="iddiv2_1_2487"/>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="iddiv2_1_2537" id="iddiv2_1_2537"/>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>
@@ -1857,7 +1864,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_2679" id="idexample_1_2679"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2729" id="idexample_1_2729"/>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">
@@ -1877,7 +1884,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_2689" id="iddiv3_1_2689"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2739" id="iddiv3_1_2739"/>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>.
@@ -1915,7 +1922,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_2726" id="iddiv3_1_2726"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2776" id="iddiv3_1_2776"/>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
@@ -1927,7 +1934,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_2731" id="iddiv4_1_2731"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2781" id="iddiv4_1_2781"/>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>
@@ -1942,7 +1949,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_2752" id="iddiv4_1_2752"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2802" id="iddiv4_1_2802"/>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>
@@ -1968,7 +1975,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_2773" id="idexample_1_2773"/>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="idexample_1_2823" id="idexample_1_2823"/>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/"
@@ -2003,7 +2010,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2779" id="iddiv3_1_2779"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2829" id="iddiv3_1_2829"/>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>.
@@ -2700,4 +2707,5 @@
<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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <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></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 12 May 2010 22:24:15 UTC