- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 08 Dec 2009 23:58:59 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv3860
Modified Files:
wseventing.html wseventing.xml
Log Message:
8287
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.133
retrieving revision 1.134
diff -u -d -r1.133 -r1.134
--- wseventing.xml 2 Dec 2009 00:04:36 -0000 1.133
+++ wseventing.xml 8 Dec 2009 23:58:57 -0000 1.134
@@ -2613,12 +2613,6 @@
<head>Implementation Considerations</head>
<p>
- Implementations SHOULD generate expirations in subscribe and
- renew request and response messages that are significantly larger
- than expected network latency.
- </p>
-
- <p>
Event sinks SHOULD be prepared to receive notifications after
sending a subscribe request but before receiving a subscribe
response message. Event sinks SHOULD also be prepared to receive
@@ -4687,6 +4681,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/12/08 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8287">8287</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.140
retrieving revision 1.141
diff -u -d -r1.140 -r1.141
--- wseventing.html 2 Dec 2009 00:04:36 -0000 1.140
+++ wseventing.html 8 Dec 2009 23:58:57 -0000 1.141
@@ -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_2124">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2191">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2122">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2189">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2262">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2383">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2260">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2381">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_2689">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2710">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2715">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2733">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2687">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2708">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2713">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2731">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2760">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2781">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2758">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2779">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/>
@@ -1475,10 +1475,6 @@
control Subscribe requests.
</p></div></div><div class="div1">
<h2><a name="ImplConsideration" id="ImplConsideration"/>8 Implementation Considerations</h2><p>
- Implementations SHOULD generate expirations in subscribe and
- renew request and response messages that are significantly larger
- than expected network latency.
- </p><p>
Event sinks SHOULD be prepared to receive notifications after
sending a subscribe request but before receiving a subscribe
response message. Event sinks SHOULD also be prepared to receive
@@ -1501,7 +1497,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_2124" id="iddiv2_1_2124"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2122" id="iddiv2_1_2122"/>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
@@ -1560,7 +1556,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_2191" id="iddiv2_1_2191"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2189" id="iddiv2_1_2189"/>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 +1641,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_2262" id="iddiv2_1_2262"/>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_2260" id="iddiv2_1_2260"/>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.
@@ -1692,7 +1688,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_2383" id="iddiv2_1_2383"/>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_2381" id="iddiv2_1_2381"/>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>
@@ -1883,7 +1879,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_2679" id="idexample_1_2679"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2677" id="idexample_1_2677"/>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">
@@ -1903,7 +1899,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_2689" id="iddiv3_1_2689"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2687" id="iddiv3_1_2687"/>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>.
@@ -1914,7 +1910,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_2710" id="iddiv3_1_2710"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2708" id="iddiv3_1_2708"/>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
@@ -1926,7 +1922,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_2715" id="iddiv4_1_2715"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2713" id="iddiv4_1_2713"/>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>
@@ -1940,7 +1936,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_2733" id="iddiv4_1_2733"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2731" id="iddiv4_1_2731"/>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>
@@ -1964,7 +1960,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_2754" id="idexample_1_2754"/>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_2752" id="idexample_1_2752"/>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/"
@@ -1999,7 +1995,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2760" id="iddiv3_1_2760"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2758" id="iddiv3_1_2758"/>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>.
@@ -2015,7 +2011,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_2781" id="iddiv2_1_2781"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2779" id="iddiv2_1_2779"/>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
@@ -2617,4 +2613,5 @@
<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><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=8285">8285</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8201">8201</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=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=8287">8287</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 8 December 2009 23:59:01 UTC