W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > May 2010

WWW/2002/ws/ra/edcopies wseventing.html,1.195,1.196 wseventing.xml,1.188,1.189

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 12 May 2010 19:55:28 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1OCI1g-000093-C9@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv32690

Modified Files:
	wseventing.html wseventing.xml 
Log Message:
9675


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.188
retrieving revision 1.189
diff -u -d -r1.188 -r1.189
--- wseventing.xml	12 May 2010 18:37:07 -0000	1.188
+++ wseventing.xml	12 May 2010 19:55:26 -0000	1.189
@@ -2837,6 +2837,38 @@
      </gitem>
     </glist>
 
+    <p>
+     The following is an example of a wse:EventSource policy assertion:
+    </p>
+
+    <example>
+     <eg>(01) &lt;wse:EventSource ...>
+(02)   &lt;wse:DateTimeSupported />
+(03)   &lt;wse:FilterDialect URI="http://www.w3.org/&wsevt.nsprefix;/ws-evt/Dialects/XPath10"/>
+(04)   &lt;wse:FormatName URI="http://www.w3.org/&wsevt.nsprefix;/ws-evt/DeliveryFormats/Wrap">
+(05)     &lt;wsdl:definitions>
+(06)       &lt;!-- WSDL for Wrapped Notifications -->
+(07)     &lt;/wsdl:definitions>
+(08)   &lt;/wse:FormatName>
+(09)   &lt;wse:EndToSupported/>
+(10)   &lt;wsevd:EventDescriptions>
+(11)     &lt;!-- EventDescription data -->
+(12)   &lt;/wsevd:EventDescriptions>
+(13) &lt;/wse:EventSource></eg>
+    </example>
+
+    <p>
+     In the above example line (02) indicates that this event source 
+     supports expiration times as specific times. Line (03) indicates that 
+     Filtering is supported and that it supports the XPath 1.0 filter 
+     dialect.  Lines (04) - (08) indicates that this event source supports 
+     sending notifications in the Wrapped format and the Notification WSDL 
+     defining the messages is included on lines (05) - (07).  Line (09) 
+     indicates that the EndTo features is supported.  And finally, lines 
+     (10) - (12) contains the EventDescription data that describes the 
+     syntax of the events that this event source might send.
+    </p>
+
    </div2>
 
    <div2>
@@ -5000,6 +5032,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9713">9713</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=9675">9675</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.195
retrieving revision 1.196
diff -u -d -r1.195 -r1.196
--- wseventing.html	12 May 2010 18:37:07 -0000	1.195
+++ wseventing.html	12 May 2010 19:55:26 -0000	1.196
@@ -78,20 +78,20 @@
 8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
 9 <a href="#metadata">WS-Eventing Metadata</a><br/>
 &nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2139">EventSource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2248">SubscriptionManager Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2260">SubscriptionManager Assertion</a><br/>
 10 <a href="#acks">Acknowledgements</a><br/>
 11 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2308">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2455">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2320">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2467">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/>
 &nbsp;&nbsp;&nbsp;A.1 <a href="#ETypes">Event Types &amp; Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2644">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2681">Bindings for Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2686">Binding for Unwrapped Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2707">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2656">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2693">Bindings for Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2698">Binding for Unwrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2719">Binding for Wrapped Notifications</a><br/>
 &nbsp;&nbsp;&nbsp;A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2734">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2746">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/>
@@ -1595,8 +1595,32 @@
          specification.
          If the Event Source advertises EventDescription data then it 
          MUST appear as a child of the EventSource element.
-        </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2248" id="iddiv2_1_2248"/>9.2 SubscriptionManager Assertion</h3><p>
+        </p></dd></dl><p>
+     The following is an example of a wse:EventSource policy assertion:
+    </p><div class="exampleOuter"><div class="exampleInner"><pre>(01) &lt;wse:EventSource ...&gt;
+(02)   &lt;wse:DateTimeSupported /&gt;
+(03)   &lt;wse:FilterDialect URI="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/Dialects/XPath10"/&gt;
+(04)   &lt;wse:FormatName URI="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/DeliveryFormats/Wrap"&gt;
+(05)     &lt;wsdl:definitions&gt;
+(06)       &lt;!-- WSDL for Wrapped Notifications --&gt;
+(07)     &lt;/wsdl:definitions&gt;
+(08)   &lt;/wse:FormatName&gt;
+(09)   &lt;wse:EndToSupported/&gt;
+(10)   &lt;wsevd:EventDescriptions&gt;
+(11)     &lt;!-- EventDescription data --&gt;
+(12)   &lt;/wsevd:EventDescriptions&gt;
+(13) &lt;/wse:EventSource&gt;</pre></div></div><p>
+     In the above example line (02) indicates that this event source 
+     supports expiration times as specific times. Line (03) indicates that 
+     Filtering is supported and that it supports the XPath 1.0 filter 
+     dialect.  Lines (04) - (08) indicates that this event source supports 
+     sending notifications in the Wrapped format and the Notification WSDL 
+     defining the messages is included on lines (05) - (07).  Line (09) 
+     indicates that the EndTo features is supported.  And finally, lines 
+     (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_2260" id="iddiv2_1_2260"/>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
@@ -1665,7 +1689,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_2308" id="iddiv2_1_2308"/>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_2320" id="iddiv2_1_2320"/>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.
@@ -1722,7 +1746,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_2455" id="iddiv2_1_2455"/>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_2467" id="iddiv2_1_2467"/>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>
@@ -1821,7 +1845,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_2634" id="idexample_1_2634"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wsevd:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2646" id="idexample_1_2646"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;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"&gt;
@@ -1841,7 +1865,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_2644" id="iddiv3_1_2644"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2656" id="iddiv3_1_2656"/>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>.
@@ -1879,7 +1903,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_2681" id="iddiv3_1_2681"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2693" id="iddiv3_1_2693"/>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 
@@ -1891,7 +1915,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_2686" id="iddiv4_1_2686"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2698" id="iddiv4_1_2698"/>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>
@@ -1906,7 +1930,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_2707" id="iddiv4_1_2707"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2719" id="iddiv4_1_2719"/>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>
@@ -1932,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_2728" id="idexample_1_2728"/>Example A-4: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2740" id="idexample_1_2740"/>Example A-4: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;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/"
@@ -1967,7 +1991,7 @@
 (33)     &lt;/wsdl:operation&gt;
 (34)   &lt;/wsdl:binding&gt;
 (35) &lt;/wsdl:definitions&gt;</pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2734" id="iddiv3_1_2734"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2746" id="iddiv3_1_2746"/>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>.
@@ -2662,4 +2686,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9699">9699</a></td></tr><tr><td> 2010/05/11 </td><td> DD </td><td> Added resolution of issue
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9676">9676</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=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></tbody></table></div></div></body></html>
\ No newline at end of file
+       <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></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 12 May 2010 19:55:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 May 2010 19:55:31 GMT