- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 28 Jan 2010 05:19:21 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv21387
Modified Files:
wseventing.html wseventing.xml
Log Message:
7986
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.147
retrieving revision 1.148
diff -u -d -r1.147 -r1.148
--- wseventing.xml 26 Jan 2010 22:47:39 -0000 1.147
+++ wseventing.xml 28 Jan 2010 05:19:19 -0000 1.148
@@ -2716,6 +2716,9 @@
<wse:MaxExpires ...> <emph>xs:duration</emph> </wse:MaxExpires> ?
<wse:FormatName ...> <emph>xs:anyURI</emph> </wse:FormatName> *
<wse:EndToSupported .../> ?
+ <wse:NotificationPolicy ...>
+ <emph>xs:any</emph>
+ </wse:NotificationPolicy> ?
...
</wse:EventSource></eg>
</example>
@@ -2793,6 +2796,25 @@
</p>
</def>
</gitem>
+
+ <gitem>
+ <label> /wse:EventSource/wse:NotificationPolicy </label>
+ <def>
+ <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 of the
+ Notification WSDLs that the event source advertises.
+ </p>
+ </def>
+ </gitem>
</glist>
</div2>
@@ -3544,6 +3566,22 @@
</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>
+
+ <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>
<!-- Subscribe request -->
<xs:element name='Subscribe'>
@@ -3742,6 +3780,8 @@
<xs:element name='FormatName' type='tns:URI' minOccurs='0'
maxOccurs='unbounded'/>
<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>
@@ -4595,6 +4635,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/27 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986">7986</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -d -r1.153 -r1.154
--- wseventing.html 26 Jan 2010 22:47:39 -0000 1.153
+++ wseventing.html 28 Jan 2010 05:19:19 -0000 1.154
@@ -77,21 +77,21 @@
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
9 <a href="#metadata">WS-Eventing Metadata</a><br/>
9.1 <a href="#iddiv2_1_2166">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2239">SubscriptionManager Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2248">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2310">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2444">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2319">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2453">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_2646">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2667">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2672">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2690">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2655">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2676">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2681">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2699">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2717">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2738">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2726">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2747">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/>
@@ -1530,6 +1530,9 @@
<wse:MaxExpires ...> <em>xs:duration</em> </wse:MaxExpires> ?
<wse:FormatName ...> <em>xs:anyURI</em> </wse:FormatName> *
<wse:EndToSupported .../> ?
+ <wse:NotificationPolicy ...>
+ <em>xs:any</em>
+ </wse:NotificationPolicy> ?
...
</wse:EventSource></pre></div></div><p>
The following describes additional, normative constraints on the
@@ -1559,8 +1562,20 @@
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 of the
+ Notification WSDLs that the event source advertises.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2239" id="iddiv2_1_2239"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2248" id="iddiv2_1_2248"/>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
@@ -1645,7 +1660,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_2310" id="iddiv2_1_2310"/>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_2319" id="iddiv2_1_2319"/>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.
@@ -1697,7 +1712,7 @@
, 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_2444" id="iddiv2_1_2444"/>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_2453" id="iddiv2_1_2453"/>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>
@@ -1801,7 +1816,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_2636" id="idexample_1_2636"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2645" id="idexample_1_2645"/>Example A-1: 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">
@@ -1821,7 +1836,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_2646" id="iddiv3_1_2646"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2655" id="iddiv3_1_2655"/>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>.
@@ -1832,7 +1847,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_2667" id="iddiv3_1_2667"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2676" id="iddiv3_1_2676"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it MUST 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
@@ -1844,7 +1859,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_2672" id="iddiv4_1_2672"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2681" id="iddiv4_1_2681"/>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>
@@ -1858,7 +1873,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_2690" id="iddiv4_1_2690"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2699" id="iddiv4_1_2699"/>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>
@@ -1882,7 +1897,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_2711" id="idexample_1_2711"/>Example A-2: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2720" id="idexample_1_2720"/>Example A-2: 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/"
@@ -1917,7 +1932,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2717" id="iddiv3_1_2717"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2726" id="iddiv3_1_2726"/>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>.
@@ -1933,7 +1948,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_2738" id="iddiv2_1_2738"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2747" id="iddiv2_1_2747"/>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
@@ -2036,6 +2051,22 @@
</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>
+
+ <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>
<!-- Subscribe request -->
<xs:element name='Subscribe'>
@@ -2234,6 +2265,8 @@
<xs:element name='FormatName' type='tns:URI' minOccurs='0'
maxOccurs='unbounded'/>
<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>
@@ -2504,4 +2537,5 @@
<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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <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></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Thursday, 28 January 2010 05:19:23 UTC