- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 17 Mar 2009 23:36:14 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv8231
Modified Files:
wseventing.html wseventing.xml
Log Message:
issue 6428
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -d -r1.18 -r1.19
--- wseventing.xml 17 Mar 2009 22:56:35 -0000 1.18
+++ wseventing.xml 17 Mar 2009 23:36:12 -0000 1.19
@@ -231,14 +231,15 @@
<p>
In order to support this broad variety of event delivery
requirements, this specification introduces an abstraction called
- a Delivery Mode. This concept is used as an extension point, so
+ a Delivery Mode and an abstraction called Delivery Format.
+ These concepts are used as an extension points, so
that event sources and event consumers may freely create new
delivery mechanisms that are tailored to their specific
requirements. This specification provides a minimal amount of
- support for delivery mode negotiation by allowing an event source
- to provide a list of supported delivery modes in response to a
- subscription request specifying a delivery mode it does not
- support.
+ support for delivery mode and format negotiation by allowing an event
+ source to provide a list of supported delivery modes and formats
+ in response to a subscription request specifying a delivery mode
+ or format it does not support.
</p>
<p>
@@ -247,17 +248,11 @@
</p>
<p>
- As an example of a possible extension, a feature may allow a
- subscriber to request that event messages be "wrapped" in a
- standard message. This feature is requested by specifying a new
- delivery mode, e.g. <loc href=
- "http://www.w3.org/2009/02/ws-evt/DeliveryModes/Wrap">
- http://www.w3.org/2009/02/ws-evt/DeliveryModes/Wrap</loc>,
- in the Subscribe request. Use of this delivery mode would
- indicate that notification messages should be "wrapped".
- Similarly, this approach could be generalized to allow the
- subscriber to provide other information regarding their
- preferences for notification message delivery.
+ This specification specifies two delivery formats: wrapped
+ and unwrapped. Use of wrapped format indicates
+ that notification messages should be contained in a wrapper
+ element. Use of unwrapped format indicates that notification messages
+ are not wrapped.
</p>
</div2>
@@ -657,8 +652,7 @@
<def>
<p>
A delivery mechanism where the source sends event messages
- to the sink as individual, unsolicited, asynchronous SOAP
- messages.
+ to the sink as unsolicited, asynchronous SOAP messages.
</p>
</def>
</gitem>
@@ -772,6 +766,7 @@
<wse:Subscribe ...>
<wse:EndTo><emph>endpoint-reference</emph></wse:EndTo> ?
<wse:Delivery Mode="<emph>xs:anyURI</emph>"? ><emph>xs:any</emph></wse:Delivery>
+ <wse:Format Name="<emph>xs:anyURI</emph>"? ><emph>xs:any*</emph></wse:Format>
<wse:Expires>(<emph>xs:dateTime</emph> | <emph>xs:duration</emph>)</wse:Expires> ?
<wse:Filter Dialect="<emph>xs:anyURI</emph>"? > <emph>xs:any</emph> </wse:Filter> ?
...
@@ -867,6 +862,44 @@
</gitem>
<gitem>
+ <label> /s:Envelope/s:Body/*/wse:Format </label>
+ <def>
+ <p>
+ The delivery format to be used for notification messages sent in
+ relation to this subscription. Implied value is
+ "http://www.w3.org/2009/02/ws-evt/DeliveryFormats/Unwrap", which
+ indicates that unwraped delivery should be used. See
+ Section <specref ref="DeliveryModes"/> for details.
+ </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>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /s:Envelope/s:Body/*/wse:Format@Name="http://www.w3.org/2009/02/ws-evt/DeliveryFormats/Unwrap" </label>
+ <def>
+ <p>
+ Indicate the unwrapped event delivery format.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /s:Envelope/s:Body/*/wse:Format@Name="http://www.w3.org/2009/02/ws-evt/DeliveryFormats/Wrap" </label>
+ <def>
+ <p>
+ Indicate the wrapped event delivery format.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
<label> /s:Envelope/s:Body/*/wse:Expires </label>
<def>
<p>
@@ -2306,6 +2339,45 @@
</tbody>
</table>
</div2>
+
+ <div2 id="DeliveryFormatRequestedUnavailable">
+ <head>DeliveryFormatRequestUnavailable</head>
+
+ <p>
+ This fault is sent when a Subscribe request specifies a delivery
+ mode that is not supported by the event source. Optionally, this
+ fault may contain a list of supported delivery mode URIs in the
+ Detail property.
+ </p>
+
+ <table border="1">
+ <tbody>
+ <tr>
+ <td><kw>[Code]</kw></td>
+ <td>s12:Sender</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Subcode]</kw></td>
+ <td>wse:DeliveryFormatRequestedUnavailable</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Reason]</kw></td>
+ <td>The requested delivery format is not supported.</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Detail]</kw></td>
+ <td>
+ <wse:SupportedDeliveryFormat> +
+ <phrase/>
+ <emph> Optional, one per delivery format supported by the receiver.</emph>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div2>
</div1>
<div1 id="Security">
@@ -2835,7 +2907,17 @@
minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="Mode" type="xs:anyURI" use="optional"
- default="http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryModes/Push" />
+ default="http://http://www.w3.org/2009/02/ws-evt/DeliveryModes/Push" />
+ <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://http://www.w3.org/2009/02/ws-evt/DeliveryFormats/Unwrap" />
<xs:anyAttribute namespace="##other" processContents="lax" />
</xs:complexType>
@@ -2878,6 +2960,7 @@
<xs:element name="EndTo" type="wsa:EndpointReferenceType"
minOccurs="0" />
<xs:element name="Delivery" type="tns:DeliveryType" />
+ <xs:element name="Format" type="tns:FormatType" />
<xs:element name="Expires" type="tns:ExpirationType"
minOccurs="0" />
<xs:element name="Filter" type="tns:FilterType"
@@ -2911,6 +2994,9 @@
<!-- Used in a fault if there's an unsupported delivery mode -->
<xs:element name="SupportedDeliveryMode" 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>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -d -r1.27 -r1.28
--- wseventing.html 17 Mar 2009 22:56:35 -0000 1.27
+++ wseventing.html 17 Mar 2009 23:36:12 -0000 1.28
@@ -66,6 +66,7 @@
6.6 <a href="#EventSourceUnableToProcess">EventSourceUnableToProcess</a><br/>
6.7 <a href="#UnableToRenew">UnableToRenew</a><br/>
6.8 <a href="#InvalidMessage">InvalidMessage</a><br/>
+ 6.9 <a href="#DeliveryFormatRequestedUnavailable">DeliveryFormatRequestUnavailable</a><br/>
7 <a href="#Security">Security Considerations</a><br/>
7.1 <a href="#MessageSecurity">Message Security</a><br/>
7.2 <a href="#AccessControl">Access Control</a><br/>
@@ -159,28 +160,24 @@
</p><p>
In order to support this broad variety of event delivery
requirements, this specification introduces an abstraction called
- a Delivery Mode. This concept is used as an extension point, so
+ a Delivery Mode and an abstraction called Delivery Format.
+ These concepts are used as an extension points, so
that event sources and event consumers may freely create new
delivery mechanisms that are tailored to their specific
requirements. This specification provides a minimal amount of
- support for delivery mode negotiation by allowing an event source
- to provide a list of supported delivery modes in response to a
- subscription request specifying a delivery mode it does not
- support.
+ support for delivery mode and format negotiation by allowing an event
+ source to provide a list of supported delivery modes and formats
+ in response to a subscription request specifying a delivery mode
+ or format it does not support.
</p><p>
This specification defines a single delivery mode, Push Mode,
which is simple asynchronous messaging.
</p><p>
- As an example of a possible extension, a feature may allow a
- subscriber to request that event messages be "wrapped" in a
- standard message. This feature is requested by specifying a new
- delivery mode, e.g. <a href="http://www.w3.org/2009/02/ws-evt/DeliveryModes/Wrap">
- http://www.w3.org/2009/02/ws-evt/DeliveryModes/Wrap</a>,
- in the Subscribe request. Use of this delivery mode would
- indicate that notification messages should be "wrapped".
- Similarly, this approach could be generalized to allow the
- subscriber to provide other information regarding their
- preferences for notification message delivery.
+ This specification specifies two delivery formats: wrapped
+ and unwrapped. Use of wrapped format indicates
+ that notification messages should be contained in a wrapper
+ element. Use of unwrapped format indicates that notification messages
+ are not wrapped.
</p></div><div class="div2">
<h3><a name="SubMgr" id="SubMgr"/>2.3 Subscription Managers</h3><p>
In some scenarios the event source itself manages the
@@ -382,8 +379,7 @@
A one-way message sent to indicate that an event has occurred.
</p></dd><dt class="label"> Push Mode </dt><dd><p>
A delivery mechanism where the source sends event messages
- to the sink as individual, unsolicited, asynchronous SOAP
- messages.
+ to the sink as unsolicited, asynchronous SOAP messages.
</p></dd><dt class="label"> Subscriber </dt><dd><p>
A Web service that sends requests to create, renew, and/or
delete subscriptions.
@@ -452,6 +448,7 @@
<wse:Subscribe ...>
<wse:EndTo><em>endpoint-reference</em></wse:EndTo> ?
<wse:Delivery Mode="<em>xs:anyURI</em>"? ><em>xs:any</em></wse:Delivery>
+ <wse:Format Name="<em>xs:anyURI</em>"? ><em>xs:any*</em></wse:Format>
<wse:Expires>(<em>xs:dateTime</em> | <em>xs:duration</em>)</wse:Expires> ?
<wse:Filter Dialect="<em>xs:anyURI</em>"? > <em>xs:any</em> </wse:Filter> ?
...
@@ -502,6 +499,21 @@
the single element, wse:NotifyTo, that contains the endpoint reference
to which notification messages should be sent. The value of this
element is not constrained for other delivery modes.
+ </p></dd><dt class="label"> /s:Envelope/s:Body/*/wse:Format </dt><dd><p>
+ The delivery format to be used for notification messages sent in
+ relation to this subscription. Implied value is
+ "http://www.w3.org/2009/02/ws-evt/DeliveryFormats/Unwrap", which
+ indicates that unwraped delivery should be used. See
+ Section <a href="#DeliveryModes"><b>2.2 Delivery Modes</b></a> for details.
+ </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"> /s:Envelope/s:Body/*/wse:Format@Name="http://www.w3.org/2009/02/ws-evt/DeliveryFormats/Unwrap" </dt><dd><p>
+ Indicate the unwrapped event delivery format.
+ </p></dd><dt class="label"> /s:Envelope/s:Body/*/wse:Format@Name="http://www.w3.org/2009/02/ws-evt/DeliveryFormats/Wrap" </dt><dd><p>
+ Indicate the wrapped event delivery format.
</p></dd><dt class="label"> /s:Envelope/s:Body/*/wse:Expires </dt><dd><p>
Requested expiration time for the subscription. (No
implied value.) The event source defines the actual
@@ -1329,7 +1341,15 @@
outline listed above, the request MUST fail and the event source
or subscription manager MAY generate the following fault
indicating that the request is invalid:
- </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:InvalidMessage</td></tr><tr><td><b>[Reason]</b></td><td>The message is not valid and cannot be processed.</td></tr><tr><td><b>[Detail]</b></td><td><em>The invalid message</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:InvalidMessage</td></tr><tr><td><b>[Reason]</b></td><td>The message is not valid and cannot be processed.</td></tr><tr><td><b>[Detail]</b></td><td><em>The invalid message</em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"/>6.9 DeliveryFormatRequestUnavailable</h3><p>
+ This fault is sent when a Subscribe request specifies a delivery
+ mode that is not supported by the event source. Optionally, this
+ fault may contain a list of supported delivery mode URIs 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><div class="div1">
<h2><a name="Security" id="Security"/>7 Security Considerations</h2><div class="div2">
<h3><a name="MessageSecurity" id="MessageSecurity"/>7.1 Message Security</h3><p>
It is strongly RECOMMENDED that the communication between
@@ -1657,7 +1677,17 @@
minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:attribute name="Mode" type="xs:anyURI" use="optional"
- default="http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryModes/Push" />
+ default="http://http://www.w3.org/2009/02/ws-evt/DeliveryModes/Push" />
+ <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://http://www.w3.org/2009/02/ws-evt/DeliveryFormats/Unwrap" />
<xs:anyAttribute namespace="##other" processContents="lax" />
</xs:complexType>
@@ -1700,6 +1730,7 @@
<xs:element name="EndTo" type="wsa:EndpointReferenceType"
minOccurs="0" />
<xs:element name="Delivery" type="tns:DeliveryType" />
+ <xs:element name="Format" type="tns:FormatType" />
<xs:element name="Expires" type="tns:ExpirationType"
minOccurs="0" />
<xs:element name="Filter" type="tns:FilterType"
@@ -1733,6 +1764,9 @@
<!-- Used in a fault if there's an unsupported delivery mode -->
<xs:element name="SupportedDeliveryMode" 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>
Received on Tuesday, 17 March 2009 23:36:23 UTC