- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 12 Jan 2010 21:15:03 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv28921
Modified Files:
wseventing.html wseventing.xml
Log Message:
8281
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.139
retrieving revision 1.140
diff -u -d -r1.139 -r1.140
--- wseventing.xml 12 Jan 2010 21:00:50 -0000 1.139
+++ wseventing.xml 12 Jan 2010 21:15:01 -0000 1.140
@@ -2094,20 +2094,13 @@
<def>
<p>
This element (whose content is of type xs:unsignedLong) is a suggested
- minimum duration in milliseconds to wait before retransmitting the message.
- Omission of this element indicates that a retry is never likely to succeed.
- </p>
- </def>
- </gitem>
- <gitem>
- <label> /wse:RetryAfter/@any</label>
- <def>
- <p>
- OPTIONAL extensibility attributes that do not affect processing.
+ minimum duration in milliseconds to wait before retransmitting the
+ message. Omission of this element indicates that a retry is never
+ likely to succeed.
</p>
</def>
</gitem>
- </glist>
+ </glist>
</div2>
@@ -4688,6 +4681,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8164">8164</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/01/12 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8281">8281</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.145
retrieving revision 1.146
diff -u -d -r1.145 -r1.146
--- wseventing.html 12 Jan 2010 21:00:50 -0000 1.145
+++ wseventing.html 12 Jan 2010 21:15:01 -0000 1.146
@@ -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_2118">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2185">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2112">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2179">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2256">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2377">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2250">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2371">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_2683">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2704">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2709">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2727">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2677">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2698">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2703">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2721">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2754">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2775">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2748">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2769">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/>
@@ -1309,10 +1309,9 @@
the detail element of a fault.
</p><dl><dt class="label"> /wse:RetryAfter</dt><dd><p>
This element (whose content is of type xs:unsignedLong) is a suggested
- minimum duration in milliseconds to wait before retransmitting the message.
- Omission of this element indicates that a retry is never likely to succeed.
- </p></dd><dt class="label"> /wse:RetryAfter/@any</dt><dd><p>
- OPTIONAL extensibility attributes that do not affect processing.
+ minimum duration in milliseconds to wait before retransmitting the
+ message. Omission of this element indicates that a retry is never
+ likely to succeed.
</p></dd></dl></div><div class="div2">
<h3><a name="InvalidExpirationTime" id="InvalidExpirationTime"/>6.2 InvalidExpirationTime</h3><p>
This fault is generated when a request specifies an
@@ -1486,7 +1485,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_2118" id="iddiv2_1_2118"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2112" id="iddiv2_1_2112"/>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
@@ -1545,7 +1544,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_2185" id="iddiv2_1_2185"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2179" id="iddiv2_1_2179"/>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
@@ -1630,7 +1629,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_2256" id="iddiv2_1_2256"/>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_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>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1677,7 +1676,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_2377" id="iddiv2_1_2377"/>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_2371" id="iddiv2_1_2371"/>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>
@@ -1868,7 +1867,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_2673" id="idexample_1_2673"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2667" id="idexample_1_2667"/>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">
@@ -1888,7 +1887,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_2683" id="iddiv3_1_2683"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2677" id="iddiv3_1_2677"/>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>.
@@ -1899,7 +1898,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_2704" id="iddiv3_1_2704"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2698" id="iddiv3_1_2698"/>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
@@ -1911,7 +1910,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_2709" id="iddiv4_1_2709"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2703" id="iddiv4_1_2703"/>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>
@@ -1925,7 +1924,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_2727" id="iddiv4_1_2727"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2721" id="iddiv4_1_2721"/>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>
@@ -1949,7 +1948,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_2748" id="idexample_1_2748"/>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_2742" id="idexample_1_2742"/>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/"
@@ -1984,7 +1983,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2754" id="iddiv3_1_2754"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2748" id="iddiv3_1_2748"/>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>.
@@ -2000,7 +1999,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_2775" id="iddiv2_1_2775"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2769" id="iddiv2_1_2769"/>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
@@ -2605,4 +2604,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=8287">8287</a></td></tr><tr><td> 2010/01/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8165">8165</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=8164">8164</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=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></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 12 January 2010 21:15:06 UTC