- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 19 Jan 2010 22:38:50 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv17575
Modified Files:
wsenum.html wsenum.xml wseventing.html wseventing.xml
Log Message:
8286
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.142
retrieving revision 1.143
diff -u -d -r1.142 -r1.143
--- wseventing.xml 19 Jan 2010 22:17:20 -0000 1.142
+++ wseventing.xml 19 Jan 2010 22:38:48 -0000 1.143
@@ -859,6 +859,11 @@
message. The endpoint to which the EndTo EPR refers MUST support the
SubcriptionEndPortType portType.
</p>
+
+ <p>
+ If the event source does not support the use of the EndTo EPR,
+ the event source MUST generate a wse:EndToNotSupported fault.
+ </p>
</def>
</gitem>
@@ -1790,18 +1795,14 @@
</div2>
<div2 id="SubscriptionEnd">
- <head>Subscription End</head>
+ <head>SubscriptionEnd</head>
<p>
- If the event source terminates a subscription unexpectedly,
- a SubscriptionEnd SOAP message SHOULD be sent to
- the endpoint reference indicated when the subscription was
- created (see <specref ref="Subscribe"/>).
- This endpoint reference MUST refer to an endpoint that supports the
- SubscriptionEndPortType portType. Support for including the
- EndTo EPR in a Subscribe request message
- (and implicitly the sending of the SubscriptionEnd message)
- MUST be supported by compliant event sources.
+ If the event source terminates a subscription unexpectedly,
+ and it supports the use of the EndTo EPR, and the EndTo EPR
+ was present in the Subscribe message for that subscription
+ (see <specref ref="Subscribe"/>), the SubscriptionEnd message
+ MUST be sent to the endpoint reference indicated by that EPR.
The message MUST be of the following form:
</p>
@@ -2424,6 +2425,40 @@
</table>
</div2>
+ <div2 id="EndToNotSupported">
+ <head>EndToNotSupported</head>
+
+ <p>
+ This fault is generated by an event source that does not support
+ /wse:Subscribe/wse:EndTo semantics, in response to a subscription
+ request that contains a wse:EndTo element.
+ </p>
+
+ <table border="1">
+ <tbody>
+ <tr>
+ <td><kw>[Code]</kw></td>
+ <td>s12:Sender</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Subcode]</kw></td>
+ <td>wse:EndToNotSupported</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Reason]</kw></td>
+ <td>wse:EndTo semantics is not supported.</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Detail]</kw></td>
+ <td><emph>none</emph></td>
+ </tr>
+ </tbody>
+ </table>
+ </div2>
+
</div1>
<div1 id="Security">
@@ -2676,6 +2711,7 @@
<wse:FilterDialect ...> <emph>xs:anyURI</emph> </wse:FilterDialect> *
<wse:MaxExpires ...> <emph>xs:duration</emph> </wse:MaxExpires> ?
<wse:FormatName ...> <emph>xs:anyURI</emph> </wse:FormatName> *
+ <wse:EndToSupported .../> ?
...
</wse:EventSource></eg>
</example>
@@ -2740,6 +2776,19 @@
</p>
</def>
</gitem>
+
+ <gitem>
+ <label> /wse:EventSource/wse:EndToSupported </label>
+ <def>
+ <p>
+ When present, this OPTIONAL parameter indicates support for the
+ /wse:Subscribe/wse:EndTo semantics. That is, when a subscription
+ request contains an wse:EndTo element, a SubscriptionEnd message
+ will be sent to the EPR contained in the wse:EndTo element, if
+ the subscription terminates unexpectedly.
+ </p>
+ </def>
+ </gitem>
</glist>
</div2>
@@ -3688,6 +3737,7 @@
<xs:element name='MaxExpires' type='tns:Duration' minOccurs='0'/>
<xs:element name='FormatName' type='tns:URI' minOccurs='0'
maxOccurs='unbounded'/>
+ <xs:element name='EndToSupported' type='tns:Empty' minOccurs='0'/>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
</xs:sequence>
@@ -4513,6 +4563,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/19 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.148
retrieving revision 1.149
diff -u -d -r1.148 -r1.149
--- wseventing.html 19 Jan 2010 22:17:20 -0000 1.148
+++ wseventing.html 19 Jan 2010 22:38:48 -0000 1.149
@@ -57,7 +57,7 @@
4.2 <a href="#Renew">Renew</a><br/>
4.3 <a href="#GetStatus">GetStatus</a><br/>
4.4 <a href="#Unsubscribe">Unsubscribe</a><br/>
- 4.5 <a href="#SubscriptionEnd">Subscription End</a><br/>
+ 4.5 <a href="#SubscriptionEnd">SubscriptionEnd</a><br/>
5 <a href="#Notifications">Notifications</a><br/>
6 <a href="#Faults">Faults</a><br/>
6.1 <a href="#FaultDetailRetryElement">Fault Detail RetryAfter Element</a><br/>
@@ -70,27 +70,28 @@
6.8 <a href="#EmptyFilter">EmptyFilter</a><br/>
6.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
6.10 <a href="#UnknownSubscription">UnknownSubscription</a><br/>
+ 6.11 <a href="#EndToNotSupported">EndToNotSupported</a><br/>
7 <a href="#Security">Security Considerations</a><br/>
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="#metadata">WS-Eventing Metadata</a><br/>
- 9.1 <a href="#iddiv2_1_2112">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2179">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2164">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2237">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2250">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2384">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2308">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2442">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_2586">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2607">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2612">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2630">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2644">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2665">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2670">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2688">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2657">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2678">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2715">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2736">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/>
@@ -502,11 +503,14 @@
</p><dl><dt class="label"><b>[Body]</b>/wse:Subscribe/wse:EndTo </dt><dd><p>
Where to send a SubscriptionEnd message if the
subscription is terminated unexpectedly. (See
- <a href="#SubscriptionEnd"><b>4.5 Subscription End</b></a>.) If
+ <a href="#SubscriptionEnd"><b>4.5 SubscriptionEnd</b></a>.) If
present, this element MUST be of type
wsa:EndpointReferenceType. Default is not to send this
message. The endpoint to which the EndTo EPR refers MUST support the
SubcriptionEndPortType portType.
+ </p><p>
+ If the event source does not support the use of the EndTo EPR,
+ the event source MUST generate a wse:EndToNotSupported fault.
</p></dd><dt class="label"><b>[Body]</b>/wse:Subscribe/wse:Delivery </dt><dd><p>
This element contains the information necessary to convey
notification messages to the event sink in
@@ -1125,16 +1129,12 @@
(14) <wse:UnsubscribeResponse/>
(15) </s12:Body>
(16) </s12:Envelope></pre></div></div></div><div class="div2">
-<h3><a name="SubscriptionEnd" id="SubscriptionEnd"/>4.5 Subscription End</h3><p>
- If the event source terminates a subscription unexpectedly,
- a SubscriptionEnd SOAP message SHOULD be sent to
- the endpoint reference indicated when the subscription was
- created (see <a href="#Subscribe"><b>4.1 Subscribe</b></a>).
- This endpoint reference MUST refer to an endpoint that supports the
- SubscriptionEndPortType portType. Support for including the
- EndTo EPR in a Subscribe request message
- (and implicitly the sending of the SubscriptionEnd message)
- MUST be supported by compliant event sources.
+<h3><a name="SubscriptionEnd" id="SubscriptionEnd"/>4.5 SubscriptionEnd</h3><p>
+ If the event source terminates a subscription unexpectedly,
+ and it supports the use of the EndTo EPR, and the EndTo EPR
+ was present in the Subscribe message for that subscription
+ (see <a href="#Subscribe"><b>4.1 Subscribe</b></a>), the SubscriptionEnd message
+ MUST be sent to the endpoint reference indicated by that EPR.
The message MUST be of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
http://www.w3.org/2009/09/ws-evt/SubscriptionEnd
@@ -1362,7 +1362,12 @@
<h3><a name="UnknownSubscription" id="UnknownSubscription"/>6.10 UnknownSubscription</h3><p>
This fault is generated when a request specifies a subscription
that is not known.
- </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnknownSubscription</td></tr><tr><td><b>[Reason]</b></td><td>The subscription is not known.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
+ </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:UnknownSubscription</td></tr><tr><td><b>[Reason]</b></td><td>The subscription is not known.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="EndToNotSupported" id="EndToNotSupported"/>6.11 EndToNotSupported</h3><p>
+ This fault is generated by an event source that does not support
+ /wse:Subscribe/wse:EndTo semantics, in response to a subscription
+ request that contains a wse:EndTo element.
+ </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:EndToNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>wse:EndTo semantics is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
<h2><a name="Security" id="Security"/>7 Security Considerations</h2><div class="div2">
<h3><a name="MessageSecurity" id="MessageSecurity"/>7.1 Message Security</h3><p>
It is strongly RECOMMENDED that the communication between
@@ -1487,7 +1492,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_2112" id="iddiv2_1_2112"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2164" id="iddiv2_1_2164"/>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
@@ -1522,6 +1527,7 @@
<wse:FilterDialect ...> <em>xs:anyURI</em> </wse:FilterDialect> *
<wse:MaxExpires ...> <em>xs:duration</em> </wse:MaxExpires> ?
<wse:FormatName ...> <em>xs:anyURI</em> </wse:FormatName> *
+ <wse:EndToSupported .../> ?
...
</wse:EventSource></pre></div></div><p>
The following describes additional, normative constraints on the
@@ -1545,8 +1551,14 @@
</p></dd><dt class="label"> /wse:EventSource/wse:FormatName </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
specified event delivery format name URI.
+ </p></dd><dt class="label"> /wse:EventSource/wse:EndToSupported </dt><dd><p>
+ When present, this OPTIONAL parameter indicates support for the
+ /wse:Subscribe/wse:EndTo semantics. That is, when a subscription
+ request contains an 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></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2179" id="iddiv2_1_2179"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2237" id="iddiv2_1_2237"/>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
@@ -1631,7 +1643,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_2250" id="iddiv2_1_2250"/>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_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>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1683,7 +1695,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_2384" id="iddiv2_1_2384"/>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_2442" id="iddiv2_1_2442"/>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>
@@ -1787,7 +1799,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_2576" id="idexample_1_2576"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2634" id="idexample_1_2634"/>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">
@@ -1807,7 +1819,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_2586" id="iddiv3_1_2586"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2644" id="iddiv3_1_2644"/>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>.
@@ -1818,7 +1830,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_2607" id="iddiv3_1_2607"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2665" id="iddiv3_1_2665"/>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
@@ -1830,7 +1842,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_2612" id="iddiv4_1_2612"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2670" id="iddiv4_1_2670"/>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>
@@ -1844,7 +1856,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_2630" id="iddiv4_1_2630"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2688" id="iddiv4_1_2688"/>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>
@@ -1868,7 +1880,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_2651" id="idexample_1_2651"/>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_2709" id="idexample_1_2709"/>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/"
@@ -1903,7 +1915,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2657" id="iddiv3_1_2657"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2715" id="iddiv3_1_2715"/>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>.
@@ -1919,7 +1931,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_2678" id="iddiv2_1_2678"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2736" id="iddiv2_1_2736"/>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
@@ -2219,6 +2231,7 @@
<xs:element name='MaxExpires' type='tns:Duration' minOccurs='0'/>
<xs:element name='FormatName' type='tns:URI' minOccurs='0'
maxOccurs='unbounded'/>
+ <xs:element name='EndToSupported' type='tns:Empty' minOccurs='0'/>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
</xs:sequence>
@@ -2485,4 +2498,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8164">8164</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8281">8281</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8176">8176</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=8068">8068</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=8068">8068</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=8286">8286</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -d -r1.101 -r1.102
--- wsenum.html 16 Dec 2009 20:07:00 -0000 1.101
+++ wsenum.html 19 Jan 2010 22:38:48 -0000 1.102
@@ -65,13 +65,14 @@
4.7 <a href="#InvalidEnumerationContext">InvalidEnumerationContext</a><br/>
4.8 <a href="#TimedOut">TimedOut</a><br/>
4.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
+ 4.10 <a href="#EndToNotSupported">EndToNotSupported</a><br/>
5 <a href="#Security">Security Considerations</a><br/>
6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
- 6.1 <a href="#iddiv2_1_1903">Enumeration Assertion</a><br/>
+ 6.1 <a href="#iddiv2_1_1955">Enumeration Assertion</a><br/>
7 <a href="#acks">Acknowledgements</a><br/>
8 <a href="#refs">References</a><br/>
- 8.1 <a href="#iddiv2_1_1992">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2178">Informative References</a><br/>
+ 8.1 <a href="#iddiv2_1_2050">Normative References</a><br/>
+ 8.2 <a href="#iddiv2_1_2236">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
B <a href="#WSDL">WSDL</a><br/>
@@ -392,6 +393,9 @@
be of type wsa:EndpointReferenceType. Default is to not send this
message. The endpoint to which the EndTo EPR
refers MUST support the EnumerationEndPortType portType.
+ </p><p>
+ If the event source does not support the use of the EndTo EPR,
+ the data source MUST generate a wsen:EndToNotSupported fault.
</p></dd><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:Expires </dt><dd><p>
This OPTIONAL element can be used by the consumer to indicate the
expiration time of the requested enumeration. The value of this
@@ -1013,13 +1017,11 @@
is a Release response message.
</p></div><div class="div2">
<h3><a name="EnumerationEnd" id="EnumerationEnd"/>3.6 EnumerationEnd</h3><p>
- If the data source terminates an enumeration
- unexpectedly, the data source SHOULD send an EnumerationEnd SOAP
- message to the endpoint reference indicated when the enumeration
- was created (see <a href="#Enumerate"><b>3.1 Enumerate</b></a>).
- Support for including the EndTo EPR in a Enumerate request message
- (and implicitly the sending of the EnumerationEnd message) MUST
- be supported by compliant data sources.
+ If the data source terminates an enumeration unexpectedly, and it
+ supports the use of the EndTo EPR, and the EndTo EPR was present in the
+ Enumerate message for that enumeration (see <a href="#Enumerate"><b>3.1 Enumerate</b></a>),
+ the EnumerationEnd message MUST be sent to the endpoint reference
+ indicated by that EPR.
The message MUST be of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
http://www.w3.org/2009/09/ws-enu/EnumerationEnd
@@ -1163,7 +1165,12 @@
<h3><a name="UnusableEPR" id="UnusableEPR"/>4.9 UnusableEPR</h3><p>
This fault MAY be generated when a data source detects
that the wsen:EndTo EPR is unusable.
- </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:UnusableEPR</td></tr><tr><td><b>[Reason]</b></td><td>The wsen:EndTo EPR is unusable.</td></tr><tr><td><b>[Detail]</b></td><td><em> Details as to why the EPR is unusable. </em></td></tr></tbody></table></div></div><div class="div1">
+ </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:UnusableEPR</td></tr><tr><td><b>[Reason]</b></td><td>The wsen:EndTo EPR is unusable.</td></tr><tr><td><b>[Detail]</b></td><td><em> Details as to why the EPR is unusable. </em></td></tr></tbody></table></div><div class="div2">
+<h3><a name="EndToNotSupported" id="EndToNotSupported"/>4.10 EndToNotSupported</h3><p>
+ This fault is generated by an event source that does not support
+ /wsen:Enumerate/wsen:EndTo semantics, in response to a enumerate
+ request that contains a wsen:EndTo element.
+ </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wsen:EndToNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>wsen:EndTo semantics is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div></div><div class="div1">
<h2><a name="Security" id="Security"/>5 Security Considerations</h2><p>
It is strongly RECOMMENDED that the
communication between services be secured using the mechanisms
@@ -1272,7 +1279,7 @@
that indicate a particular security mechanism used to protect
the WS-Enumeration operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1903" id="iddiv2_1_1903"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_1955" id="iddiv2_1_1955"/>6.1 Enumeration Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Enumeration specification is through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1311,6 +1318,7 @@
<wsenu:MaxTime ...> <em>xs:duration</em> </wsenu:MaxTime> ?
<wsenu:MaxElements ...> <em>xs:long</em> </wsenu:MaxElements> ?
<wsenu:MaxCharacters ...> <em>xs:long</em> </wsenu:MaxCharacters> ?
+ <wsenu:EndToSupported .../> ?
...
</wsenu:DataSource></pre></div></div><p>
The following describes additional, normative constraints on the
@@ -1342,6 +1350,12 @@
When present, this OPTIONAL parameter indicates the maximum
MaxCharacters value supported by this endpoint. The value specified
MUST be greater than zero.
+ </p></dd><dt class="label"> /wsenu:DataSource/wsenu:EndToSupported </dt><dd><p>
+ When present, this OPTIONAL parameter indicates support for the
+ /wsen:Enumerate/wsen:EndTo semantics. That is, when a enumerate
+ request contains an wsen:EndTo element, a EnumerationEnd message
+ will be sent to the EPR contained in the wsen:EndTo element, if
+ the enumeration terminates unexpectedly.
</p></dd></dl></div></div><div class="div1">
<h2><a name="acks" id="acks"/>7 Acknowledgements</h2><p>
This specification has been developed as a
@@ -1368,7 +1382,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1992" id="iddiv2_1_1992"/>8.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_2050" id="iddiv2_1_2050"/>8.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.
@@ -1440,7 +1454,7 @@
, J. Clark, S. DeRose, Editors.
World Wide Web Consortium (W3C), 16 November 1999.
Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2178" id="iddiv2_1_2178"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+<h3><a name="iddiv2_1_2236" id="iddiv2_1_2236"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
W3C Working Group Draft, "Web Services Metadata Exchange
(WS-MetadataExchange) 1.1"
</cite></a>
@@ -1607,6 +1621,7 @@
minOccurs='0' />
<xs:element name='MaxCharacters' type='xs:positiveInteger'
minOccurs='0' />
+ <xs:element name='EndToSupported' type='tns:Empty' minOccurs='0' />
<xs:any namespace='##other' processContents='lax'
minOccurs='0' maxOccurs='unbounded' />
</xs:sequence>
@@ -1945,4 +1960,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</a></td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8305">8305</a></td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8159">8159</a></td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8161">8161</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=8161">8161</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=8286">8286</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -d -r1.94 -r1.95
--- wsenum.xml 16 Dec 2009 20:07:00 -0000 1.94
+++ wsenum.xml 19 Jan 2010 22:38:48 -0000 1.95
@@ -676,6 +676,11 @@
message. The endpoint to which the EndTo EPR
refers MUST support the EnumerationEndPortType portType.
</p>
+
+ <p>
+ If the event source does not support the use of the EndTo EPR,
+ the data source MUST generate a wsen:EndToNotSupported fault.
+ </p>
</def>
</gitem>
@@ -1673,13 +1678,11 @@
<head>EnumerationEnd</head>
<p>
- If the data source terminates an enumeration
- unexpectedly, the data source SHOULD send an EnumerationEnd SOAP
- message to the endpoint reference indicated when the enumeration
- was created (see <specref ref="Enumerate"/>).
- Support for including the EndTo EPR in a Enumerate request message
- (and implicitly the sending of the EnumerationEnd message) MUST
- be supported by compliant data sources.
+ If the data source terminates an enumeration unexpectedly, and it
+ supports the use of the EndTo EPR, and the EndTo EPR was present in the
+ Enumerate message for that enumeration (see <specref ref="Enumerate"/>),
+ the EnumerationEnd message MUST be sent to the endpoint reference
+ indicated by that EPR.
The message MUST be of the following form:
</p>
@@ -2148,6 +2151,42 @@
</table>
</div2>
+ <div2 id="EndToNotSupported">
+ <head>EndToNotSupported</head>
+
+ <p>
+ This fault is generated by an event source that does not support
+ /wsen:Enumerate/wsen:EndTo semantics, in response to a enumerate
+ request that contains a wsen:EndTo element.
+ </p>
+
+ <table border="1">
+ <tbody>
+ <tr>
+ <td><kw>[Code]</kw></td>
+ <td>s12:Sender</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Subcode]</kw></td>
+ <td>wsen:EndToNotSupported</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Reason]</kw></td>
+ <td>wsen:EndTo semantics is not supported.</td>
+ </tr>
+
+ <tr>
+ <td><kw>[Detail]</kw></td>
+ <td>
+ <emph>none</emph>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div2>
+
</div1>
<div1 id="Security">
@@ -2376,6 +2415,7 @@
<wsenu:MaxTime ...> <emph>xs:duration</emph> </wsenu:MaxTime> ?
<wsenu:MaxElements ...> <emph>xs:long</emph> </wsenu:MaxElements> ?
<wsenu:MaxCharacters ...> <emph>xs:long</emph> </wsenu:MaxCharacters> ?
+ <wsenu:EndToSupported .../> ?
...
</wsenu:DataSource></eg>
</example>
@@ -2456,6 +2496,19 @@
</def>
</gitem>
+ <gitem>
+ <label> /wsenu:DataSource/wsenu:EndToSupported </label>
+ <def>
+ <p>
+ When present, this OPTIONAL parameter indicates support for the
+ /wsen:Enumerate/wsen:EndTo semantics. That is, when a enumerate
+ request contains an wsen:EndTo element, a EnumerationEnd message
+ will be sent to the EPR contained in the wsen:EndTo element, if
+ the enumeration terminates unexpectedly.
+ </p>
+ </def>
+ </gitem>
+
</glist>
</div2>
@@ -2833,6 +2886,7 @@
minOccurs='0' />
<xs:element name='MaxCharacters' type='xs:positiveInteger'
minOccurs='0' />
+ <xs:element name='EndToSupported' type='tns:Empty' minOccurs='0' />
<xs:any namespace='##other' processContents='lax'
minOccurs='0' maxOccurs='unbounded' />
</xs:sequence>
@@ -3528,6 +3582,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8161">8161</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/19 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Tuesday, 19 January 2010 22:38:53 UTC