- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 07 Nov 2009 00:28:58 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv988
Modified Files:
wseventing.html wseventing.xml wsmex.html wsmex.xml
Log Message:
8168
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -d -r1.119 -r1.120
--- wseventing.html 7 Nov 2009 00:23:36 -0000 1.119
+++ wseventing.html 7 Nov 2009 00:28:55 -0000 1.120
@@ -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_2161">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2228">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2151">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2218">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2299">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2420">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2289">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2410">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_2726">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2747">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2752">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2770">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2716">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2737">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2742">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2760">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2797">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2818">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2787">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2808">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/>
@@ -640,11 +640,6 @@
property <a href="#XMLInfoset">[XML Infoset]</a> of
/s:Envelope/s:Body/*/wse:Filter.
</p></li></ul></dd></dl><p>
- Other message information headers defined by WS-Addressing
- <a href="#AddrCore">[WS-Addressing]</a> MAY be included in
- the request and response messages, according to the usage and
- semantics defined in WS-Addressing.
- </p><p>
Other components of the outline above are not further
constrained by this specification.
</p><p>
@@ -1190,11 +1185,6 @@
specified by the @xml:lang attribute, describing the reason
for the unexpected subscription termination.
</p></dd></dl><p>
- Other message information headers defined by WS-Addressing
- <a href="#AddrCore">[WS-Addressing]</a> MAY be included in
- the message, according to the usage and semantics defined in
- WS-Addressing.
- </p><p>
Other components of the outline above are not further
constrained by this specification.
</p><p><a href="#Table12">Example 4-9</a> lists a hypothetical SubscriptionEnd message
@@ -1520,7 +1510,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_2161" id="iddiv2_1_2161"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2151" id="iddiv2_1_2151"/>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 +1569,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_2228" id="iddiv2_1_2228"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2218" id="iddiv2_1_2218"/>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
@@ -1664,7 +1654,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_2299" id="iddiv2_1_2299"/>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_2289" id="iddiv2_1_2289"/>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.
@@ -1711,7 +1701,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_2420" id="iddiv2_1_2420"/>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_2410" id="iddiv2_1_2410"/>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>
@@ -1902,7 +1892,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_2716" id="idexample_1_2716"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2706" id="idexample_1_2706"/>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">
@@ -1922,7 +1912,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_2726" id="iddiv3_1_2726"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2716" id="iddiv3_1_2716"/>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>.
@@ -1933,7 +1923,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_2747" id="iddiv3_1_2747"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2737" id="iddiv3_1_2737"/>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
@@ -1945,7 +1935,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_2752" id="iddiv4_1_2752"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2742" id="iddiv4_1_2742"/>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>
@@ -1959,7 +1949,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_2770" id="iddiv4_1_2770"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2760" id="iddiv4_1_2760"/>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>
@@ -1983,7 +1973,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_2791" id="idexample_1_2791"/>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_2781" id="idexample_1_2781"/>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/"
@@ -2018,7 +2008,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2797" id="iddiv3_1_2797"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2787" id="iddiv3_1_2787"/>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>.
@@ -2034,7 +2024,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_2818" id="iddiv2_1_2818"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2808" id="iddiv2_1_2808"/>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
@@ -2638,4 +2628,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7828">7828</a></td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8076">8076</a></td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8172">8172</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=8172">8172</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8168">8168</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -d -r1.111 -r1.112
--- wseventing.xml 7 Nov 2009 00:23:36 -0000 1.111
+++ wseventing.xml 7 Nov 2009 00:28:55 -0000 1.112
@@ -1129,13 +1129,6 @@
</glist>
<p>
- Other message information headers defined by WS-Addressing
- <bibref ref="AddrCore"/> MAY be included in
- the request and response messages, according to the usage and
- semantics defined in WS-Addressing.
- </p>
-
- <p>
Other components of the outline above are not further
constrained by this specification.
</p>
@@ -1910,13 +1903,6 @@
</glist>
<p>
- Other message information headers defined by WS-Addressing
- <bibref ref="AddrCore"/> MAY be included in
- the message, according to the usage and semantics defined in
- WS-Addressing.
- </p>
-
- <p>
Other components of the outline above are not further
constrained by this specification.
</p>
@@ -4647,6 +4633,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8172">8172</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/11/06 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8168">8168</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -d -r1.70 -r1.71
--- wsmex.xml 7 Nov 2009 00:16:02 -0000 1.70
+++ wsmex.xml 7 Nov 2009 00:28:56 -0000 1.71
@@ -1225,13 +1225,6 @@
</glist>
<p>
- Other message information headers defined by WS-Addressing
- <bibref ref='AddrCore'/> MAY be included
- in the request and response messages, according to the usage and
- semantics defined in WS-Addressing.
- </p>
-
- <p>
An endpoint MAY respond with a fault message using the standard
fault codes defined in WS-Addressing
<bibref ref='AddrCore'/> (e.g., wsa:ActionNotSupported).
@@ -2502,6 +2495,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8204">8204</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/11/06 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8168">8168</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -d -r1.80 -r1.81
--- wsmex.html 7 Nov 2009 00:16:02 -0000 1.80
+++ wsmex.html 7 Nov 2009 00:28:56 -0000 1.81
@@ -61,11 +61,11 @@
9 <a href="#ImplicitWSDL">Exposing WSDL for Operations Implicitly Defined by a Policy Assertion</a><br/>
10 <a href="#Security">Security Considerations</a><br/>
11 <a href="#metadata">WS-Metadata Exchange Metadata</a><br/>
- 11.1 <a href="#iddiv2_1_1482">MetadataExchange Assertion</a><br/>
+ 11.1 <a href="#iddiv2_1_1477">MetadataExchange Assertion</a><br/>
12 <a href="#Acknowledgements">Acknowledgements</a><br/>
13 <a href="#References">References</a><br/>
- 13.1 <a href="#iddiv2_1_1546">Normative References</a><br/>
- 13.2 <a href="#iddiv2_1_1719">Informative References</a><br/>
+ 13.1 <a href="#iddiv2_1_1541">Normative References</a><br/>
+ 13.2 <a href="#iddiv2_1_1714">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
B <a href="#Appendix-B">WSDL</a><br/>
@@ -683,11 +683,6 @@
When not present the default value is
"http://www.w3.org/2009/09/ws-mex/Content/Any".
</p></dd></dl><p>
- Other message information headers defined by WS-Addressing
- <a href="#AddrCore">[WS-Addressing]</a> MAY be included
- in the request and response messages, according to the usage and
- semantics defined in WS-Addressing.
- </p><p>
An endpoint MAY respond with a fault message using the standard
fault codes defined in WS-Addressing
<a href="#AddrCore">[WS-Addressing]</a> (e.g., wsa:ActionNotSupported).
@@ -997,7 +992,7 @@
indicate a particular security mechanism used to protect the
WS-MetadataExchange operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1482" id="iddiv2_1_1482"/>11.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1477" id="iddiv2_1_1477"/>11.1 MetadataExchange Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-MetadataExchange specification is through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1075,7 +1070,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="References" id="References"/>13 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1546" id="iddiv2_1_1546"/>13.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_1541" id="iddiv2_1_1541"/>13.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.
@@ -1142,7 +1137,7 @@
, P. Biron, A. Malhotra, Editors.
World Wide Web Consortium (W3C), 28 October 2004.
Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1719" id="iddiv2_1_1719"/>13.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_1714" id="iddiv2_1_1714"/>13.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
OASIS Standard, "Web Services Secure Conversation
(WS-SecureConversation) 1.4"
</cite></a>
@@ -1369,4 +1364,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a></td></tr><tr><td> 2009/11/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8204">8204</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=8204">8204</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8168">8168</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Saturday, 7 November 2009 00:29:07 UTC