- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 17 Nov 2009 21:44:14 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies In directory hutz:/tmp/cvs-serv11474 Modified Files: wseventing.html wseventing.xml Log Message: 8277 Index: wseventing.xml =================================================================== RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v retrieving revision 1.128 retrieving revision 1.129 diff -u -d -r1.128 -r1.129 --- wseventing.xml 17 Nov 2009 21:41:39 -0000 1.128 +++ wseventing.xml 17 Nov 2009 21:44:12 -0000 1.129 @@ -1941,15 +1941,8 @@ <head>Notifications</head> <p> - This specification does not constrain notifications because - any message MAY be a notification. - </p> - - <p> - However, if a subscriber wishes to have notifications annotated with - unique SOAP header blocks then it MAY include reference parameters within - the wse:NotifyTo element. These reference parameters will be processed - as specified by <bibref ref="WSABinding"/>. + Notifications are SOAP messages that are transmitted to the event sink + as the result of a successful Subscribe operation. </p> <p> @@ -4667,6 +4660,13 @@ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8276">8276</loc> </td> </tr> + <tr> + <td> 2009/11/17 </td> + <td> DD </td> + <td> Added resolution of issue + <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8277">8277</loc> + </td> + </tr> </tbody> </table> </div1> Index: wseventing.html =================================================================== RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v retrieving revision 1.135 retrieving revision 1.136 diff -u -d -r1.135 -r1.136 --- wseventing.html 17 Nov 2009 21:41:39 -0000 1.135 +++ wseventing.html 17 Nov 2009 21:44:12 -0000 1.136 @@ -75,22 +75,22 @@ 7.2 <a href="#AccessControl">Access Control</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_2131">EventSource Assertion</a><br/> - 9.2 <a href="#iddiv2_1_2198">SubscriptionManager Assertion</a><br/> + 9.1 <a href="#iddiv2_1_2126">EventSource Assertion</a><br/> + 9.2 <a href="#iddiv2_1_2193">SubscriptionManager Assertion</a><br/> 10 <a href="#acks">Acknowledgements</a><br/> 11 <a href="#refs">References</a><br/> - 11.1 <a href="#iddiv2_1_2269">Normative References</a><br/> - 11.2 <a href="#iddiv2_1_2390">Informative References</a><br/> + 11.1 <a href="#iddiv2_1_2264">Normative References</a><br/> + 11.2 <a href="#iddiv2_1_2385">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_2696">Retrieving Event Descriptions</a><br/> - A.1.2 <a href="#iddiv3_1_2717">Bindings for Event Descriptions</a><br/> - A.1.2.1 <a href="#iddiv4_1_2722">Binding for Unwrapped Notifications</a><br/> - A.1.2.2 <a href="#iddiv4_1_2740">Binding for Wrapped Notifications</a><br/> + A.1.1 <a href="#iddiv3_1_2691">Retrieving Event Descriptions</a><br/> + A.1.2 <a href="#iddiv3_1_2712">Bindings for Event Descriptions</a><br/> + A.1.2.1 <a href="#iddiv4_1_2717">Binding for Unwrapped Notifications</a><br/> + A.1.2.2 <a href="#iddiv4_1_2735">Binding for Wrapped Notifications</a><br/> A.2 <a href="#NWSDL">Notification WSDLs</a><br/> - A.2.1 <a href="#iddiv3_1_2767">Retrieving Notification WSDLs</a><br/> - A.3 <a href="#iddiv2_1_2788">Multiple Event Information Metadata Sections</a><br/> + A.2.1 <a href="#iddiv3_1_2762">Retrieving Notification WSDLs</a><br/> + A.3 <a href="#iddiv2_1_2783">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/> @@ -1214,13 +1214,8 @@ line. </p></div></div><div class="div1"> <h2><a name="Notifications" id="Notifications"/>5 Notifications</h2><p> - This specification does not constrain notifications because - any message MAY be a notification. - </p><p> - However, if a subscriber wishes to have notifications annotated with - unique SOAP header blocks then it MAY include reference parameters within - the wse:NotifyTo element. These reference parameters will be processed - as specified by <a href="#WSABinding">[WS-Addressing 1.0 SOAP Binding]</a>. + Notifications are SOAP messages that are transmitted to the event sink + as the result of a successful Subscribe operation. </p><p><a href="#Table13">Example 5-1</a> lists a hypothetical notification message sent as part of the subscription created by the subscribe request in <a href="#Table4">Example 4-1</a>. @@ -1498,7 +1493,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_2131" id="iddiv2_1_2131"/>9.1 EventSource Assertion</h3><p> +<h3><a name="iddiv2_1_2126" id="iddiv2_1_2126"/>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 @@ -1557,7 +1552,7 @@ When present, this OPTIONAL parameter indicates support for the specified event delivery format name URI. </p></dd></dl></div><div class="div2"> -<h3><a name="iddiv2_1_2198" id="iddiv2_1_2198"/>9.2 SubscriptionManager Assertion</h3><p> +<h3><a name="iddiv2_1_2193" id="iddiv2_1_2193"/>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 @@ -1642,7 +1637,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_2269" id="iddiv2_1_2269"/>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_2264" id="iddiv2_1_2264"/>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. @@ -1689,7 +1684,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_2390" id="iddiv2_1_2390"/>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_2385" id="iddiv2_1_2385"/>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> @@ -1880,7 +1875,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_2686" id="idexample_1_2686"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions +<div class="exampleHeader"><a name="idexample_1_2681" id="idexample_1_2681"/>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"> @@ -1900,7 +1895,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_2696" id="iddiv3_1_2696"/>A.1.1 Retrieving Event Descriptions</h4><p> +<h4><a name="iddiv3_1_2691" id="iddiv3_1_2691"/>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>. @@ -1911,7 +1906,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_2717" id="iddiv3_1_2717"/>A.1.2 Bindings for Event Descriptions</h4><p> +<h4><a name="iddiv3_1_2712" id="iddiv3_1_2712"/>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 @@ -1923,7 +1918,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_2722" id="iddiv4_1_2722"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p> +<h5><a name="iddiv4_1_2717" id="iddiv4_1_2717"/>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> @@ -1937,7 +1932,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_2740" id="iddiv4_1_2740"/>A.1.2.2 Binding for Wrapped Notifications</h5><p> +<h5><a name="iddiv4_1_2735" id="iddiv4_1_2735"/>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> @@ -1961,7 +1956,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_2761" id="idexample_1_2761"/>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_2756" id="idexample_1_2756"/>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/" @@ -1996,7 +1991,7 @@ (33) </wsdl:operation> (34) </wsdl:binding> (35) </wsdl:definitions></pre></div></div><div class="div3"> -<h4><a name="iddiv3_1_2767" id="iddiv3_1_2767"/>A.2.1 Retrieving Notification WSDLs</h4><p> +<h4><a name="iddiv3_1_2762" id="iddiv3_1_2762"/>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>. @@ -2012,7 +2007,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_2788" id="iddiv2_1_2788"/>A.3 Multiple Event Information Metadata Sections</h3><p> +<h3><a name="iddiv2_1_2783" id="iddiv2_1_2783"/>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 @@ -2611,4 +2606,5 @@ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8169">8169</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8020">8020</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue - <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8276">8276</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=8276">8276</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue + <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8277">8277</a></td></tr></tbody></table></div></div></body></html> \ No newline at end of file
Received on Tuesday, 17 November 2009 21:44:17 UTC