- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 12 Mar 2010 00:43:05 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv17358
Modified Files:
wsenum.html wsenum.xml wseventing.html wseventing.xml wst.html
wst.xml
Log Message:
more health warngings
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -d -r1.109 -r1.110
--- wst.xml 10 Mar 2010 05:39:39 -0000 1.109
+++ wst.xml 12 Mar 2010 00:43:03 -0000 1.110
@@ -1831,6 +1831,11 @@
</glist>
+ <p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p>
+
</div2>
<div2>
@@ -1941,6 +1946,11 @@
</glist>
+ <p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p>
+
</div2>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.166
retrieving revision 1.167
diff -u -d -r1.166 -r1.167
--- wseventing.html 10 Mar 2010 05:39:39 -0000 1.166
+++ wseventing.html 12 Mar 2010 00:43:03 -0000 1.167
@@ -77,21 +77,21 @@
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
9 <a href="#metadata">WS-Eventing Metadata</a><br/>
9.1 <a href="#iddiv2_1_2170">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2279">SubscriptionManager Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2281">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2359">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2493">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2363">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2497">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_2695">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2716">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2721">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2739">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2699">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2720">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2725">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2743">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2766">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2787">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2770">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2791">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/>
@@ -1613,8 +1613,11 @@
the WS-Eventing message exchanges. Any metadata that appears
is scoped to the operations and features of the WS-Eventing
specification.
- </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2279" id="iddiv2_1_2279"/>9.2 SubscriptionManager Assertion</h3><p>
+ </p></dd></dl><p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p></div><div class="div2">
+<h3><a name="iddiv2_1_2281" id="iddiv2_1_2281"/>9.2 SubscriptionManager Assertion</h3><p>
Services indicate support for the
WS-Eventing's definition of a subscription manager
through the use of the Web Services
@@ -1677,7 +1680,10 @@
e.g. WS-Eventing WSDL, or nested policy assertions related to the
WS-Eventing message exchanges. Any metadata that appears is scoped
to the operations and features of the WS-Eventing specification.
- </p></dd></dl></div></div><div class="div1">
+ </p></dd></dl><p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p></div></div><div class="div1">
<h2><a name="acks" id="acks"/>10 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
@@ -1709,7 +1715,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2359" id="iddiv2_1_2359"/>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_2363" id="iddiv2_1_2363"/>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.
@@ -1761,7 +1767,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_2493" id="iddiv2_1_2493"/>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_2497" id="iddiv2_1_2497"/>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>
@@ -1865,7 +1871,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_2685" id="idexample_1_2685"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2689" id="idexample_1_2689"/>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/2002/ws/ra/edcopies/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1885,7 +1891,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_2695" id="iddiv3_1_2695"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2699" id="iddiv3_1_2699"/>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>.
@@ -1896,7 +1902,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_2716" id="iddiv3_1_2716"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2720" id="iddiv3_1_2720"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it MUST 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
@@ -1908,7 +1914,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_2721" id="iddiv4_1_2721"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2725" id="iddiv4_1_2725"/>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>
@@ -1922,7 +1928,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_2739" id="iddiv4_1_2739"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2743" id="iddiv4_1_2743"/>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>
@@ -1946,7 +1952,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_2760" id="idexample_1_2760"/>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_2764" id="idexample_1_2764"/>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/"
@@ -1981,7 +1987,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2766" id="iddiv3_1_2766"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2770" id="iddiv3_1_2770"/>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>.
@@ -1997,7 +2003,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_2787" id="iddiv2_1_2787"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2791" id="iddiv2_1_2791"/>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
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -d -r1.111 -r1.112
--- wst.html 10 Mar 2010 05:39:39 -0000 1.111
+++ wst.html 12 Mar 2010 00:43:03 -0000 1.112
@@ -60,11 +60,11 @@
6 <a href="#Security_Considerations">Security Considerations</a><br/>
7 <a href="#metadata">WS-Transfer Metadata</a><br/>
7.1 <a href="#iddiv2_1_1370">TransferResource Assertion</a><br/>
- 7.2 <a href="#iddiv2_1_1458">TransferResourceFactory Assertion</a><br/>
+ 7.2 <a href="#iddiv2_1_1460">TransferResourceFactory Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1529">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1702">Informative References</a><br/>
+ 9.1 <a href="#iddiv2_1_1533">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_1706">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
B <a href="#WSDL">WSDL</a><br/>
@@ -1042,8 +1042,11 @@
e.g. WS-Transfer WSDL, or nested policy assertions related to the
WS-Transfer message exchanges. Any metadata that appears is scoped
to the operations and features of the WS-Transfer specification.
- </p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1458" id="iddiv2_1_1458"/>7.2 TransferResourceFactory Assertion</h3><p>
+ </p></dd></dl><p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p></div><div class="div2">
+<h3><a name="iddiv2_1_1460" id="iddiv2_1_1460"/>7.2 TransferResourceFactory Assertion</h3><p>
Services indicate support for
WS-Transfer's definition of a Transfer Resource Factory
through the use of the Web Services
@@ -1098,7 +1101,10 @@
e.g. WS-Transfer WSDL, or nested policy assertions related to the
WS-Transfer message exchanges. Any metadata that appears is scoped
to the operations and features of the WS-Transfer specification.
- </p></dd></dl></div></div><div class="div1">
+ </p></dd></dl><p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p></div></div><div class="div1">
<h2><a name="acks" id="acks"/>8 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
@@ -1130,7 +1136,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1529" id="iddiv2_1_1529"/>9.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_1533" id="iddiv2_1_1533"/>9.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.
@@ -1198,7 +1204,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_1702" id="iddiv2_1_1702"/>9.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
+<h3><a name="iddiv2_1_1706" id="iddiv2_1_1706"/>9.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
W3C Working Group Draft, "Web Services Fragment (WS-Fragment) 1.0"
</cite></a>
, D. Davis, et al., Editors.
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -d -r1.119 -r1.120
--- wsenum.html 10 Mar 2010 05:39:39 -0000 1.119
+++ wsenum.html 12 Mar 2010 00:43:03 -0000 1.120
@@ -72,8 +72,8 @@
6.1 <a href="#iddiv2_1_2019">Enumeration Assertion</a><br/>
7 <a href="#acks">Acknowledgements</a><br/>
8 <a href="#refs">References</a><br/>
- 8.1 <a href="#iddiv2_1_2132">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2318">Informative References</a><br/>
+ 8.1 <a href="#iddiv2_1_2134">Normative References</a><br/>
+ 8.2 <a href="#iddiv2_1_2320">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/>
@@ -1394,7 +1394,10 @@
the WS-Enumeration message exchanges. Any metadata that appears
is scoped to the operations and features of the WS-Enumeration
specification.
- </p></dd></dl></div></div><div class="div1">
+ </p></dd></dl><p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p></div></div><div class="div1">
<h2><a name="acks" id="acks"/>7 Acknowledgements</h2><p>
This specification has been developed as a
result of joint work with many individuals and teams,
@@ -1427,7 +1430,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2132" id="iddiv2_1_2132"/>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_2134" id="iddiv2_1_2134"/>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.
@@ -1499,7 +1502,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_2318" id="iddiv2_1_2318"/>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_2320" id="iddiv2_1_2320"/>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>
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -d -r1.111 -r1.112
--- wsenum.xml 10 Mar 2010 05:39:39 -0000 1.111
+++ wsenum.xml 12 Mar 2010 00:43:03 -0000 1.112
@@ -2604,6 +2604,11 @@
</glist>
+ <p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p>
+
</div2>
</div1>
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.159
retrieving revision 1.160
diff -u -d -r1.159 -r1.160
--- wseventing.xml 10 Mar 2010 05:39:39 -0000 1.159
+++ wseventing.xml 12 Mar 2010 00:43:03 -0000 1.160
@@ -2880,6 +2880,11 @@
</gitem>
</glist>
+ <p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p>
+
</div2>
<div2>
@@ -3012,6 +3017,11 @@
</glist>
+ <p>
+ Note: The use of nested policy assertions as shown here is subject to
+ change as it is being currently discussed in the WG.
+ </p>
+
</div2>
</div1>
Received on Friday, 12 March 2010 00:43:07 UTC