- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 03 Nov 2009 21:14:08 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv15180
Modified Files:
wseventing.html wseventing.xml
Log Message:
SubscriptionEnd/Status also takes an xs:anyURI.
Make the outline match the xsd.
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -d -r1.102 -r1.103
--- wseventing.xml 3 Nov 2009 18:26:44 -0000 1.102
+++ wseventing.xml 3 Nov 2009 21:14:06 -0000 1.103
@@ -1840,7 +1840,8 @@
<wse:Status>
( http://www.w3.org/&wsevt.nsprefix;/ws-evt/DeliveryFailure |
http://www.w3.org/&wsevt.nsprefix;/ws-evt/SourceShuttingDown |
- http://www.w3.org/&wsevt.nsprefix;/ws-evt/SourceCancelling )
+ http://www.w3.org/&wsevt.nsprefix;/ws-evt/SourceCancelling |
+ <emph>xs:anyURI</emph> )
</wse:Status>
<wse:Reason xml:lang="<emph>language identifier</emph>" ><emph>xs:string</emph></wse:Reason> ?
<emph>xs:any</emph>*
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.110
retrieving revision 1.111
diff -u -d -r1.110 -r1.111
--- wseventing.html 3 Nov 2009 18:26:44 -0000 1.110
+++ wseventing.html 3 Nov 2009 21:14:06 -0000 1.111
@@ -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_2174">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2241">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2177">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2244">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2312">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2433">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2315">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2436">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_2739">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2755">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2760">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2778">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2742">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2758">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2763">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2781">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2805">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2821">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2808">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2824">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/>
@@ -1158,7 +1158,8 @@
<wse:Status>
( http://www.w3.org/2009/09/ws-evt/DeliveryFailure |
http://www.w3.org/2009/09/ws-evt/SourceShuttingDown |
- http://www.w3.org/2009/09/ws-evt/SourceCancelling )
+ http://www.w3.org/2009/09/ws-evt/SourceCancelling |
+ <em>xs:anyURI</em> )
</wse:Status>
<wse:Reason xml:lang="<em>language identifier</em>" ><em>xs:string</em></wse:Reason> ?
<em>xs:any</em>*
@@ -1521,7 +1522,7 @@
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_2174" id="iddiv2_1_2174"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2177" id="iddiv2_1_2177"/>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
@@ -1579,7 +1580,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_2241" id="iddiv2_1_2241"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2244" id="iddiv2_1_2244"/>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
@@ -1663,7 +1664,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_2312" id="iddiv2_1_2312"/>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_2315" id="iddiv2_1_2315"/>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.
@@ -1710,7 +1711,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_2433" id="iddiv2_1_2433"/>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_2436" id="iddiv2_1_2436"/>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>
@@ -1900,7 +1901,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_2729" id="idexample_1_2729"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2732" id="idexample_1_2732"/>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">
@@ -1920,7 +1921,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_2739" id="iddiv3_1_2739"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2742" id="iddiv3_1_2742"/>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>.
@@ -1931,7 +1932,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_2755" id="iddiv3_1_2755"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2758" id="iddiv3_1_2758"/>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
@@ -1943,7 +1944,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_2760" id="iddiv4_1_2760"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2763" id="iddiv4_1_2763"/>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>
@@ -1957,7 +1958,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_2778" id="iddiv4_1_2778"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2781" id="iddiv4_1_2781"/>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>
@@ -1981,7 +1982,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_2799" id="idexample_1_2799"/>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_2802" id="idexample_1_2802"/>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/"
@@ -2016,7 +2017,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2805" id="iddiv3_1_2805"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2808" id="iddiv3_1_2808"/>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>.
@@ -2032,7 +2033,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_2821" id="iddiv2_1_2821"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2824" id="iddiv2_1_2824"/>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
Received on Tuesday, 3 November 2009 21:14:13 UTC