- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 05 Oct 2009 12:54:53 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv22109
Modified Files:
wseventing.html wseventing.xml
Log Message:
6402, 6721
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.85
retrieving revision 1.86
diff -u -d -r1.85 -r1.86
--- wseventing.xml 2 Oct 2009 16:01:19 -0000 1.85
+++ wseventing.xml 5 Oct 2009 12:54:51 -0000 1.86
@@ -644,6 +644,15 @@
<td>This specification</td>
</tr>
<tr>
+ <td>wsevp</td>
+ <td>
+ <loc href="http://www.w3.org/&wsevt.nsprefix;/ws-evt">
+ http://www.w3.org/&wsevt.nsprefix;/ws-evp
+ </loc>
+ </td>
+ <td>This specification</td>
+ </tr>
+ <tr>
<td>xs</td>
<td>
<loc href="http://www.w3.org/2001/XMLSchema">
@@ -2562,18 +2571,289 @@
</p>
</div1>
- <div1 id="policy">
- <head>WS-Eventing Policy Assertion(s)</head>
+ <div1 id="metadata">
+ <head>WS-Eventing Metadata</head>
<p>
- An endpoint MAY indicate that it supports WS-Eventing, or its features,
- by including the WS-Eventing Policy assertion(s) within its WSDL. By
- doing so the endpoint is indicating that the corresponding WS-Eventing
- operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL.
+ An endpoint MAY indicate that it supports WS-Eventing, or its features,
+ by including the WS-Eventing Policy assertion within its WSDL. By
+ doing so the endpoint is indicating that the corresponding WS-Eventing
+ operations are supported by that endpoint even though they do not
+ explicitly appear in its WSDL (i.e. retrievable by using a
+ WS-MetadataExchange GetMetadata with a Dialect URI of
+ http://schemas.xmlsoap.org/wsdl/).
</p>
+
+ <p>
+ An endpoint MAY choose to expose the WS-Eventing WSDL by using the
+ following WS-MetadataExchange Dialect:
+ </p>
+
+ <table border="1">
+ <tbody>
+ <tr>
+ <th align="left"> Dialect URI </th>
+ <th> @Identifier value </th>
+ </tr>
+ <tr>
+ <td> http://www.w3.org/2009/02/ws-evt/EventingWSDL </td>
+ <td> Not defined </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>
+ The WS-Eventing WSDL can be annotated to indicate any endpoint
+ specific metadata that might be needed by clients interacting with
+ this service. 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>
+
+ <div2>
+ <head>EventSource Assertion</head>
+
+ <p>
+ The mechanism for indicating that a binding or endpoint conforms to the
+ WS-Eventing specification's definition of an Event Source
+ is through the use of the Web Services
+ Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
+ Attachment <bibref ref="wspolicyattach"/> specifications.
+ </p>
+
+ <p>
+ This specification defines a policy assertion (wsevp:EventSource). The
+ wsevp:EventSource policy assertion applies to the endpoint policy subject.
+ </p>
+
+ <p>
+ For WSDL 1.1, these assertions may be attached to wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they may be attached to wsdl20:endpoint or
+ wsdl20:binding. A policy expression containing the wsevp:EventSource
+ policy assertion MUST NOT be attached to a wsdl:portType or
+ wsdl20:interface.
+ </p>
+
+ <p>
+ The wsevp:EventSource policy assertion is a nested policy container
+ assertion. The meaning of this assertion, when present in a policy
+ alternative, is that WS-Eventing is required to communicate with the
+ subject. In order to indicate that the subject supports WS-Eventing
+ but does not require its use, an additional policy alternative should
+ be provided which does not contain this assertion; the compact
+ authoring style for an optional policy assertion provided by WS-Policy
+ may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+ used with the wsevp:EventSource assertion. This indicates two policy
+ alternatives, one which contains the policy assertion, and another
+ which does not.
+ </p>
+
+ <p>
+ The inclusion of this assertion implies support for the WS-Eventing
+ specification and that the subject is an Event Source.
+ </p>
+
+ <p>
+ The normative outline of this assertion is:
+ </p>
+
+ <example>
+ <eg><wsevp:EventSource [wsp:Optional="<emph>xs:boolean</emph>"]? ...>
+ <wsevp:DateTimeSupported .../> ?
+ <wsevp:FilterDialect ...> <emph>xs:anyURI</emph> </wsevp:FilterDialect> *
+ <wsevp:MaxExpires ...> <emph>xs:duration</emph> </wsevp:MaxExpires> ?
+ <wsevp:FormatName ...> <emph>xs:anyURI</emph> </wsevp:FormatName> *
+ ...
+</wsevp:EventSource></eg>
+ </example>
+
+ <p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p>
+
+ <glist>
+
+ <gitem>
+ <label> /wsevp:EventSource </label>
+ <def>
+ <p>
+ A policy assertion that specifies that WS-Eventing protocol MUST be
+ used when communicating with this endpoint and that the subject is
+ an EventSource. This assertion has Endpoint Policy Subject.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wsevp:EventSource/wsevp:DateTimeSupported </label>
+ <def>
+ <p>
+ When present, this parameter indicates support for expiration time
+ expressed as specific time (rather than duration
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wsevp:EventSource/wsevp:FilterDialect </label>
+ <def>
+ <p>
+ When present, this parameter indicates support for the specified
+ Filter Dialect URI.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wsevp:EventSource/wsevp:MaxExpires </label>
+ <def>
+ <p>
+ When present, this parameter indicates the maximum subscriptions
+ expiration time that this endpoint will support. Note: a value of
+ "PT0S" indicates that this endpoint supports subscriptions with
+ an infinite lifetime.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wsevp:EventSource/wsevp:FormatName </label>
+ <def>
+ <p>
+ When present, this parameter indicates support for the specified
+ event delivery format Name URI.
+ </p>
+ </def>
+ </gitem>
+ </glist>
+
+ </div2>
+
+ <div2>
+ <head>SubscriptionManager Assertion</head>
+
+ <p>
+ The mechanism for indicating that a binding or endpoint conforms to the
+ WS-Eventing specification's definition of a Subscription Manager
+ is through the use of the Web Services
+ Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
+ Attachment <bibref ref="wspolicyattach"/> specifications.
+ </p>
+
+ <p>
+ This specification defines a policy assertion (wsevp:SubscriptionManager).
+ The wsevp:SubscriptionManager policy assertion applies to the endpoint
+ policy subject.
+ </p>
+
+ <p>
+ For WSDL 1.1, these assertions may be attached to wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they may be attached to wsdl20:endpoint or
+ wsdl20:binding. A policy expression containing the
+ wsevp:SubscriptionManager
+ policy assertion MUST NOT be attached to a wsdl:portType or
+ wsdl20:interface.
+ </p>
+
+ <p>
+ The wsevp:SubscriptionManager policy assertion is a nested policy container
+ assertion. The meaning of this assertion, when present in a policy
+ alternative, is that WS-Eventing is required to communicate with the
+ subject. In order to indicate that the subject supports WS-Eventing
+ but does not require its use, an additional policy alternative should
+ be provided which does not contain this assertion; the compact
+ authoring style for an optional policy assertion provided by WS-Policy
+ may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+ used with the wsevp:SubscriptionManager assertion. This indicates two
+ policy alternatives, one which contains the policy assertion, and another
+ which does not.
+ </p>
+
+ <p>
+ The inclusion of this assertion implies support for the WS-Eventing
+ specification and that the subject is a Subscription Manager.
+ </p>
+
+ <p>
+ The normative outline of this assertion is:
+ </p>
+
+ <example>
+ <eg><wsevp:SubscriptionManager [wsp:Optional="<emph>xs:boolean</emph>"]? ...>
+ <wsevp:DateTimeSupported .../> ?
+ <wsevp:GetStatusOperationSupported .../> ?
+ <wsevp:UnsubscribeOperationSupported .../> ?
+ <wsevp:MaxExpires ...> <emph>xs:duration</emph> </wsevp:MaxExpires> ?
+ ...
+</wsevp:SubscriptionManager></eg>
+ </example>
+
+ <p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p>
+
+ <glist>
+
+ <gitem>
+ <label> /wsevp:SubscriptionManager </label>
+ <def>
+ <p>
+ A policy assertion that specifies that WS-Eventing protocol MUST be
+ used when communicating with this endpoint and that the subject is
+ a Subscription Manager. This assertion has Endpoint Policy Subject.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wsevp:SubscriptionManager/wsevp:DateTimeSupported </label>
+ <def>
+ <p>
+ When present, this parameter indicates support for expiration time
+ expressed as specific time (rather than duration).
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wsevp:SubscriptionManager/wsevp:GetStatusOperationSupported </label>
+ <def>
+ <p>
+ When present, this parameter indicates that the GetStatus operation
+ is supported by this endpoint.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wsevp:SubscriptionManager/wsevp:UnsubscribeOperationSupported </label>
+ <def>
+ <p>
+ When present, this parameter indicates that the Unsubscribe operation
+ is supported by this endpoint.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wsevp:SubscriptionManager/wsevp:MaxExpires </label>
+ <def>
+ <p>
+ When present, this parameter indicates the maximum subscriptions
+ expiration time that this endpoint will support. Note: a value of
+ "PT0S" indicates that this endpoint supports subscriptions with an
+ infinite lifetime.
+ </p>
+ </def>
+ </gitem>
+
+ </glist>
+
+ </div2>
</div1>
-
+
<div1 id="acks">
<head>Acknowledgements</head>
@@ -2681,6 +2961,15 @@
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
</bibl>
+
+ <bibl key="WS-Policy Attachment" id="wspolicyattach"
+ href="http://www.w3.org/TR/ws-policy-attach">
+ <titleref>
+ W3C Recommendation, "Web Services Policy (WS-Policy) 1.5 - Attachment"
+ </titleref>
+ , A. Vedamuthu, et al., Editors.
+ World Wide Web Consortium (W3C), 4 September 2007.
+ </bibl>
</blist>
</div2>
@@ -3713,6 +4002,41 @@
</example>
</div1>
+ <div1 id="policyXSD">
+ <head>Eventing Policy Schema</head>
+
+ <p>
+ A normative copy of the XML Schema description for the Eventing
+ Policy assertions can be retrieved from the following address:
+ </p>
+
+ <example>
+ <eg>http://www.w3.org/2009/09/ws-evt/EventingsPolicy.xsd</eg>
+ </example>
+
+ <p>
+ A non-normative copy of the XML schema is listed below for convenience.
+ </p>
+
+ <example>
+ <eg><wsevp:EventSource [wsp:Optional="xs:boolean"]? ...>
+ <wsevp:DateTimeSupported .../> ?
+ <wsevp:FilterDialect ...> xs:anyURI </wsevp:FilterDialect> *
+ <wsevp:MaxExpires ...> xs:duration </wsevp:MaxExpires> ?
+ <wsevp:FormatName ...> xs:anyURI </wsevp:FormatName> *
+ ...
+</wsevp:EventSource>
+
+<wsevp:SubscriptionManager [wsp:Optional="xs:boolean"]? ...>
+ <wsevp:DateTimeSupported .../> ?
+ <wsevp:GetStatusOperationSupported .../> ?
+ <wsevp:UnsubscribeOperationSupported .../> ?
+ <wsevp:MaxExpires ...> xs:duration </wsevp:MaxExpires> ?
+ ...
+</wsevp:SubscriptionManager></eg>
+ </example>
+ </div1>
+
<div1 id="changelog">
<head>Change Log</head>
@@ -4106,6 +4430,14 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7554">7554</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/10/05 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6402">6402</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -d -r1.93 -r1.94
--- wseventing.html 2 Oct 2009 16:01:19 -0000 1.93
+++ wseventing.html 5 Oct 2009 12:54:51 -0000 1.94
@@ -73,26 +73,29 @@
7.1 <a href="#MessageSecurity">Message Security</a><br/>
7.2 <a href="#AccessControl">Access Control</a><br/>
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
-9 <a href="#policy">WS-Eventing Policy Assertion(s)</a><br/>
+9 <a href="#metadata">WS-Eventing Metadata</a><br/>
+ 9.1 <a href="#iddiv2_1_2075">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2145">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2039">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2147">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2219">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2340">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_2453">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2469">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2474">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2492">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2646">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2662">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2667">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2685">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2519">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2535">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2712">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2728">Multiple Event Information Metadata Sections</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="#EDXSD">XML Schema for EventDescriptions</a><br/>
-F <a href="#changelog">Change Log</a><br/>
+F <a href="#policyXSD">Eventing Policy Schema</a><br/>
+G <a href="#changelog">Change Log</a><br/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a name="composable" id="composable"/>1 Composable Architecture</h2><p>
By using the XML, SOAP <a href="#SOAP11">[SOAP11]</a>,
@@ -388,6 +391,8 @@
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/2009/09/ws-evt">
http://www.w3.org/2009/09/ws-evt
+ </a></td><td>This specification</td></tr><tr><td>wsevp</td><td><a href="http://www.w3.org/2009/09/ws-evt">
+ http://www.w3.org/2009/09/ws-evp
</a></td><td>This specification</td></tr><tr><td>xs</td><td><a href="http://www.w3.org/2001/XMLSchema">
http://www.w3.org/2001/XMLSchema
</a></td><td>
@@ -1454,13 +1459,146 @@
notifications after receiving an unsubscribe response
message.
</p></div><div class="div1">
-<h2><a name="policy" id="policy"/>9 WS-Eventing Policy Assertion(s)</h2><p>
- An endpoint MAY indicate that it supports WS-Eventing, or its features,
- by including the WS-Eventing Policy assertion(s) within its WSDL. By
- doing so the endpoint is indicating that the corresponding WS-Eventing
- operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL.
- </p></div><div class="div1">
+<h2><a name="metadata" id="metadata"/>9 WS-Eventing Metadata</h2><p>
+ An endpoint MAY indicate that it supports WS-Eventing, or its features,
+ by including the WS-Eventing Policy assertion within its WSDL. By
+ doing so the endpoint is indicating that the corresponding WS-Eventing
+ operations are supported by that endpoint even though they do not
+ explicitly appear in its WSDL (i.e. retrievable by using a
+ WS-MetadataExchange GetMetadata with a Dialect URI of
+ http://schemas.xmlsoap.org/wsdl/).
+ </p><p>
+ An endpoint MAY choose to expose the WS-Eventing WSDL by using the
+ following WS-MetadataExchange Dialect:
+ </p><table border="1"><tbody><tr><th align="left"> Dialect URI </th><th> @Identifier value </th></tr><tr><td> http://www.w3.org/2009/02/ws-evt/EventingWSDL </td><td> Not defined </td></tr></tbody></table><p>
+ The WS-Eventing WSDL can be annotated to indicate any endpoint
+ specific metadata that might be needed by clients interacting with
+ this service. 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="iddiv2_1_2075" id="iddiv2_1_2075"/>9.1 EventSource Assertion</h3><p>
+ The mechanism for indicating that a binding or endpoint conforms to the
+ WS-Eventing specification's definition of an Event Source
+ is 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 (wsevp:EventSource). The
+ wsevp:EventSource policy assertion applies to the endpoint policy subject.
+ </p><p>
+ For WSDL 1.1, these assertions may be attached to wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they may be attached to wsdl20:endpoint or
+ wsdl20:binding. A policy expression containing the wsevp:EventSource
+ policy assertion MUST NOT be attached to a wsdl:portType or
+ wsdl20:interface.
+ </p><p>
+ The wsevp:EventSource policy assertion is a nested policy container
+ assertion. The meaning of this assertion, when present in a policy
+ alternative, is that WS-Eventing is required to communicate with the
+ subject. In order to indicate that the subject supports WS-Eventing
+ but does not require its use, an additional policy alternative should
+ be provided which does not contain this assertion; the compact
+ authoring style for an optional policy assertion provided by WS-Policy
+ may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+ used with the wsevp:EventSource assertion. This indicates two policy
+ alternatives, one which contains the policy assertion, and another
+ which does not.
+ </p><p>
+ The inclusion of this assertion implies support for the WS-Eventing
+ specification and that the subject is an Event Source.
+ </p><p>
+ The normative outline of this assertion is:
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><wsevp:EventSource [wsp:Optional="<em>xs:boolean</em>"]? ...>
+ <wsevp:DateTimeSupported .../> ?
+ <wsevp:FilterDialect ...> <em>xs:anyURI</em> </wsevp:FilterDialect> *
+ <wsevp:MaxExpires ...> <em>xs:duration</em> </wsevp:MaxExpires> ?
+ <wsevp:FormatName ...> <em>xs:anyURI</em> </wsevp:FormatName> *
+ ...
+</wsevp:EventSource></pre></div></div><p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p><dl><dt class="label"> /wsevp:EventSource </dt><dd><p>
+ A policy assertion that specifies that WS-Eventing protocol MUST be
+ used when communicating with this endpoint and that the subject is
+ an EventSource. This assertion has Endpoint Policy Subject.
+ </p></dd><dt class="label"> /wsevp:EventSource/wsevp:DateTimeSupported </dt><dd><p>
+ When present, this parameter indicates support for expiration time
+ expressed as specific time (rather than duration
+ </p></dd><dt class="label"> /wsevp:EventSource/wsevp:FilterDialect </dt><dd><p>
+ When present, this parameter indicates support for the specified
+ Filter Dialect URI.
+ </p></dd><dt class="label"> /wsevp:EventSource/wsevp:MaxExpires </dt><dd><p>
+ When present, this parameter indicates the maximum subscriptions
+ expiration time that this endpoint will support. Note: a value of
+ "PT0S" indicates that this endpoint supports subscriptions with
+ an infinite lifetime.
+ </p></dd><dt class="label"> /wsevp:EventSource/wsevp:FormatName </dt><dd><p>
+ When present, this parameter indicates support for the specified
+ event delivery format Name URI.
+ </p></dd></dl></div><div class="div2">
+<h3><a name="iddiv2_1_2145" id="iddiv2_1_2145"/>9.2 SubscriptionManager Assertion</h3><p>
+ The mechanism for indicating that a binding or endpoint conforms to the
+ WS-Eventing specification's definition of a Subscription Manager
+ is 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 (wsevp:SubscriptionManager).
+ The wsevp:SubscriptionManager policy assertion applies to the endpoint
+ policy subject.
+ </p><p>
+ For WSDL 1.1, these assertions may be attached to wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they may be attached to wsdl20:endpoint or
+ wsdl20:binding. A policy expression containing the
+ wsevp:SubscriptionManager
+ policy assertion MUST NOT be attached to a wsdl:portType or
+ wsdl20:interface.
+ </p><p>
+ The wsevp:SubscriptionManager policy assertion is a nested policy container
+ assertion. The meaning of this assertion, when present in a policy
+ alternative, is that WS-Eventing is required to communicate with the
+ subject. In order to indicate that the subject supports WS-Eventing
+ but does not require its use, an additional policy alternative should
+ be provided which does not contain this assertion; the compact
+ authoring style for an optional policy assertion provided by WS-Policy
+ may be used. The wsp:Optional attribute, as a syntactic shortcut, can be
+ used with the wsevp:SubscriptionManager assertion. This indicates two
+ policy alternatives, one which contains the policy assertion, and another
+ which does not.
+ </p><p>
+ The inclusion of this assertion implies support for the WS-Eventing
+ specification and that the subject is a Subscription Manager.
+ </p><p>
+ The normative outline of this assertion is:
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><wsevp:SubscriptionManager [wsp:Optional="<em>xs:boolean</em>"]? ...>
+ <wsevp:DateTimeSupported .../> ?
+ <wsevp:GetStatusOperationSupported .../> ?
+ <wsevp:UnsubscribeOperationSupported .../> ?
+ <wsevp:MaxExpires ...> <em>xs:duration</em> </wsevp:MaxExpires> ?
+ ...
+</wsevp:SubscriptionManager></pre></div></div><p>
+ The following describes additional, normative constraints on the
+ outline listed above:
+ </p><dl><dt class="label"> /wsevp:SubscriptionManager </dt><dd><p>
+ A policy assertion that specifies that WS-Eventing protocol MUST be
+ used when communicating with this endpoint and that the subject is
+ a Subscription Manager. This assertion has Endpoint Policy Subject.
+ </p></dd><dt class="label"> /wsevp:SubscriptionManager/wsevp:DateTimeSupported </dt><dd><p>
+ When present, this parameter indicates support for expiration time
+ expressed as specific time (rather than duration).
+ </p></dd><dt class="label"> /wsevp:SubscriptionManager/wsevp:GetStatusOperationSupported </dt><dd><p>
+ When present, this parameter indicates that the GetStatus operation
+ is supported by this endpoint.
+ </p></dd><dt class="label"> /wsevp:SubscriptionManager/wsevp:UnsubscribeOperationSupported </dt><dd><p>
+ When present, this parameter indicates that the Unsubscribe operation
+ is supported by this endpoint.
+ </p></dd><dt class="label"> /wsevp:SubscriptionManager/wsevp:MaxExpires </dt><dd><p>
+ When present, this parameter indicates the maximum subscriptions
+ expiration time that this endpoint will support. Note: a value of
+ "PT0S" indicates that this endpoint supports subscriptions with an
+ infinite lifetime.
+ </p></dd></dl></div></div><div class="div1">
<h2><a name="acks" id="acks"/>10 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
@@ -1485,7 +1623,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2039" id="iddiv2_1_2039"/>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_2219" id="iddiv2_1_2219"/>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.
@@ -1526,8 +1664,13 @@
</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></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2147" id="iddiv2_1_2147"/>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>
+ 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"/>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></dl></div><div class="div2">
+<h3><a name="iddiv2_1_2340" id="iddiv2_1_2340"/>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>
@@ -1717,7 +1860,7 @@
serve as a description of the Event Type used in
<a href="#Table1">Example 2-1</a> and <a href="#EDExample">Example A-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2443" id="idexample_1_2443"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2636" id="idexample_1_2636"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wse="http://www.w3.org/2009/09/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1737,7 +1880,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_2453" id="iddiv3_1_2453"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2646" id="iddiv3_1_2646"/>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>.
@@ -1748,7 +1891,7 @@
be equal to the value of its wse:EventDescriptions/@targetNamespace. An
Event Source MUST NOT have more than one EventDescriptions document.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_2469" id="iddiv3_1_2469"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2662" id="iddiv3_1_2662"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it SHOULD be possible to determine how a
given wse:eventType will appear on the wire as a Notification in a
Subscription created with that format. The following sections define
@@ -1760,7 +1903,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_2474" id="iddiv4_1_2474"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2667" id="iddiv4_1_2667"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
The information about an Event Type contained in the wse:eventType
element binds to a Unwrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1774,7 +1917,7 @@
of the wse:eventType element corresponding to the type of the
Event being transmitted.
</p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2492" id="iddiv4_1_2492"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2685" id="iddiv4_1_2685"/>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>
@@ -1798,7 +1941,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_2513" id="idexample_1_2513"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2706" id="idexample_1_2706"/>Example A-3: 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/"
@@ -1833,7 +1976,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2519" id="iddiv3_1_2519"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2712" id="iddiv3_1_2712"/>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>.
@@ -1849,7 +1992,7 @@
Format IRI/@Identifier, there MUST NOT exist more than one
Notification WSDL document.
</p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2535" id="iddiv2_1_2535"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2728" id="iddiv2_1_2728"/>A.3 Multiple Event Information Metadata Sections</h3><p>
When WS-MetadataExchange is used to retrieve metadata about an Event
Source, recipients of mex:Metadata elements that contain Metadata
Sections with both the
@@ -2299,7 +2442,27 @@
</xs:complexType>
</xs:element>
</xs:schema></pre></div></div></div><div class="div1">
-<h2><a name="changelog" id="changelog"/>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
+<h2><a name="policyXSD" id="policyXSD"/>F Eventing Policy Schema</h2><p>
+ A normative copy of the XML Schema description for the Eventing
+ Policy assertions can be retrieved from the following address:
+ </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/09/ws-evt/EventingsPolicy.xsd</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><wsevp:EventSource [wsp:Optional="xs:boolean"]? ...>
+ <wsevp:DateTimeSupported .../> ?
+ <wsevp:FilterDialect ...> xs:anyURI </wsevp:FilterDialect> *
+ <wsevp:MaxExpires ...> xs:duration </wsevp:MaxExpires> ?
+ <wsevp:FormatName ...> xs:anyURI </wsevp:FormatName> *
+ ...
+</wsevp:EventSource>
+
+<wsevp:SubscriptionManager [wsp:Optional="xs:boolean"]? ...>
+ <wsevp:DateTimeSupported .../> ?
+ <wsevp:GetStatusOperationSupported .../> ?
+ <wsevp:UnsubscribeOperationSupported .../> ?
+ <wsevp:MaxExpires ...> xs:duration </wsevp:MaxExpires> ?
+ ...
+</wsevp:SubscriptionManager></pre></div></div></div><div class="div1">
+<h2><a name="changelog" id="changelog"/>G 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
@@ -2353,4 +2516,6 @@
<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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <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 issue
+ <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></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Monday, 5 October 2009 12:54:59 UTC