- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 06 Nov 2009 05:08:00 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv26638
Modified Files:
wsmex.xml wsmex.html wsenum.xml wsenum.html wseventing.html
wseventing.xml wst.xml wst.html
Log Message:
7912
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -d -r1.78 -r1.79
--- wst.xml 4 Nov 2009 19:09:12 -0000 1.78
+++ wst.xml 6 Nov 2009 05:07:58 -0000 1.79
@@ -1562,35 +1562,18 @@
by including the WS-Transfer Policy assertion within its WSDL. By
doing so the endpoint is indicating that the corresponding WS-Transfer
operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL (i.e. the WSDL that MAY be retrievable by
- using a WS-MetadataExchange GetMetadata with a Dialect IRI of
- http://schemas.xmlsoap.org/wsdl/).
+ explicitly appear in its WSDL.
</p>
<p>
- An endpoint MAY choose to expose the WS-Transfer WSDL by using the
- following WS-MetadataExchange Dialect:
- </p>
-
- <table border="1">
- <tbody>
- <tr>
- <th align="left"> Dialect IRI </th>
- <th> @Identifier value </th>
- </tr>
- <tr>
- <td> http://www.w3.org/2009/02/ws-tra/TransferWSDL </td>
- <td> Not defined </td>
- </tr>
- </tbody>
- </table>
-
- <p>
- The WS-Transfer WSDL can be annotated to indicate any endpoint
+ The WS-Transfer WSDL containing the operations indicated by the
+ TransferResource Assertion MAY be exposed as described in
+ WS-MetadataExchange <bibref ref="MEX"/> Section 9.
+ This WS-Transfer WSDL can be annotated to indicate any endpoint
specific metadata that might be needed by clients interacting with
- this service. For example, the WSDL MAY have policy assertions that
- indicate a particular security mechanism used to protect the
- WS-Transfer operations supported by this endpoint.
+ this service. For example, the WSDL MAY have policy assertions
+ that indicate a particular security mechanism used to protect
+ the WS-Transfer operations supported by this endpoint.
</p>
<div2>
@@ -1987,6 +1970,16 @@
World Wide Web Consortium (W3C), 15 September 2009.
</bibl>
+ <bibl key="WS-MetadataExchange" id="MEX"
+ href="http://www.w3.org/TR/ws-metadata-exchange">
+ <titleref>
+ W3C Working Group Draft, "Web Services Metadata Exchange
+ (WS-MetadataExchange) 1.1"
+ </titleref>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ </bibl>
+
<bibl key="WS-SecureConversation" id="WSSecureConversation"
href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc">
<titleref>
@@ -2593,6 +2586,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/11/05 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -d -r1.117 -r1.118
--- wseventing.html 6 Nov 2009 04:32:47 -0000 1.117
+++ wseventing.html 6 Nov 2009 05:07:58 -0000 1.118
@@ -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_2182">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2249">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2161">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2228">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2320">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2441">Informative 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/>
</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_2747">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2768">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2773">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2791">Binding for Wrapped Notifications</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.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2818">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2839">Multiple Event Information Metadata Sections</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/>
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/>
@@ -1509,20 +1509,18 @@
by including the WS-Eventing Policy assertion within its WSDL. By
doing so the endpoint is indicating that the corresponding WS-Eventing
operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL (i.e. the WSDL that MAY be retrievable by
- using a WS-MetadataExchange GetMetadata with a Dialect IRI of
- http://schemas.xmlsoap.org/wsdl/).
+ explicitly appear in its WSDL.
</p><p>
- An endpoint MAY choose to expose the WS-Eventing WSDL by using the
- following WS-MetadataExchange Dialect:
- </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th> @Identifier value </th></tr><tr><td> http://www.w3.org/2009/02/ws-evt/EventingWSDL </td><td> Not defined </td></tr></tbody></table><p>
- The WS-Eventing WSDL can be annotated to indicate any endpoint
+ The WS-Eventing WSDL containing the operations indicated by the
+ EventSource Assertion MAY be exposed as described in
+ WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> Section 9.
+ This WS-Eventing WSDL can be annotated to indicate any endpoint
specific metadata that might be needed by clients interacting with
- this service. For example, the WSDL MAY have policy assertions that
- indicate a particular security mechanism used to protect the
- WS-Eventing operations supported by this endpoint.
+ this service. For example, the WSDL MAY have policy assertions
+ 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_2182" id="iddiv2_1_2182"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2161" id="iddiv2_1_2161"/>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
@@ -1581,7 +1579,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_2249" id="iddiv2_1_2249"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2228" id="iddiv2_1_2228"/>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
@@ -1666,7 +1664,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_2320" id="iddiv2_1_2320"/>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_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>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1713,7 +1711,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_2441" id="iddiv2_1_2441"/>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_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>
OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
Web Services Make Connection (WS-MakeConnection)
</cite></a>
@@ -1903,7 +1901,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_2737" id="idexample_1_2737"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2716" id="idexample_1_2716"/>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">
@@ -1923,7 +1921,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_2747" id="iddiv3_1_2747"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2726" id="iddiv3_1_2726"/>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>.
@@ -1934,7 +1932,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_2768" id="iddiv3_1_2768"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2747" id="iddiv3_1_2747"/>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
@@ -1946,7 +1944,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_2773" id="iddiv4_1_2773"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2752" id="iddiv4_1_2752"/>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>
@@ -1960,7 +1958,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_2791" id="iddiv4_1_2791"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2770" id="iddiv4_1_2770"/>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>
@@ -1984,7 +1982,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_2812" id="idexample_1_2812"/>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_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/"
(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/"
@@ -2019,7 +2017,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2818" id="iddiv3_1_2818"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2797" id="iddiv3_1_2797"/>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>.
@@ -2035,7 +2033,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_2839" id="iddiv2_1_2839"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2818" id="iddiv2_1_2818"/>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
@@ -2637,4 +2635,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7586">7586</a>,
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7588">7588</a>,
<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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <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></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -d -r1.80 -r1.81
--- wst.html 4 Nov 2009 19:09:12 -0000 1.80
+++ wst.html 6 Nov 2009 05:07:58 -0000 1.81
@@ -58,12 +58,12 @@
5.3 <a href="#PutDenied">PutDenied</a><br/>
6 <a href="#Security_Considerations">Security Considerations</a><br/>
7 <a href="#metadata">WS-Transfer Metadata</a><br/>
- 7.1 <a href="#iddiv2_1_1384">TransferResource Assertion</a><br/>
- 7.2 <a href="#iddiv2_1_1454">TransferResourceFactory Assertion</a><br/>
+ 7.1 <a href="#iddiv2_1_1363">TransferResource Assertion</a><br/>
+ 7.2 <a href="#iddiv2_1_1433">TransferResourceFactory Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1507">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1680">Informative References</a><br/>
+ 9.1 <a href="#iddiv2_1_1486">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_1659">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="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
@@ -887,20 +887,18 @@
by including the WS-Transfer Policy assertion within its WSDL. By
doing so the endpoint is indicating that the corresponding WS-Transfer
operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL (i.e. the WSDL that MAY be retrievable by
- using a WS-MetadataExchange GetMetadata with a Dialect IRI of
- http://schemas.xmlsoap.org/wsdl/).
+ explicitly appear in its WSDL.
</p><p>
- An endpoint MAY choose to expose the WS-Transfer WSDL by using the
- following WS-MetadataExchange Dialect:
- </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th> @Identifier value </th></tr><tr><td> http://www.w3.org/2009/02/ws-tra/TransferWSDL </td><td> Not defined </td></tr></tbody></table><p>
- The WS-Transfer WSDL can be annotated to indicate any endpoint
+ The WS-Transfer WSDL containing the operations indicated by the
+ TransferResource Assertion MAY be exposed as described in
+ WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> Section 9.
+ This WS-Transfer WSDL can be annotated to indicate any endpoint
specific metadata that might be needed by clients interacting with
- this service. For example, the WSDL MAY have policy assertions that
- indicate a particular security mechanism used to protect the
- WS-Transfer operations supported by this endpoint.
+ this service. For example, the WSDL MAY have policy assertions
+ that indicate a particular security mechanism used to protect
+ the WS-Transfer operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1384" id="iddiv2_1_1384"/>7.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1363" id="iddiv2_1_1363"/>7.1 TransferResource Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Transfer specification's definition of a Transfer Resource
is through the use of the Web Services
@@ -968,7 +966,7 @@
the Global Element Declaration (GED) or type of this resource. This
QName may be used in order to retrieve the schema of the resource.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1454" id="iddiv2_1_1454"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1433" id="iddiv2_1_1433"/>7.2 TransferResourceFactory Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Transfer specification's definition of a Transfer Resource Factory
is through the use of the Web Services
@@ -1040,7 +1038,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1507" id="iddiv2_1_1507"/>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_1486" id="iddiv2_1_1486"/>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.
@@ -1108,12 +1106,18 @@
, 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_1680" id="iddiv2_1_1680"/>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_1659" id="iddiv2_1_1659"/>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.
World Wide Web Consortium (W3C), 15 September 2009.
- Available at <a href="http://www.w3.org/TR/ws-fragment">http://www.w3.org/TR/ws-fragment</a>.</dd><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>
+ Available at <a href="http://www.w3.org/TR/ws-fragment">http://www.w3.org/TR/ws-fragment</a>.</dd><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>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ Available at <a href="http://www.w3.org/TR/ws-metadata-exchange">http://www.w3.org/TR/ws-metadata-exchange</a>.</dd><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>
@@ -1429,4 +1433,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</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=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=7968">7968</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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <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></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.68
retrieving revision 1.69
diff -u -d -r1.68 -r1.69
--- wsmex.xml 5 Nov 2009 17:03:01 -0000 1.68
+++ wsmex.xml 6 Nov 2009 05:07:57 -0000 1.69
@@ -1499,6 +1499,57 @@
</p>
</div1>
+ <div1 id="ImplicitWSDL">
+ <head>Exposing WSDL for Operations Implicitly Defined by a Policy Assertion</head>
+
+ <p>
+ An endpoint MAY indicate that it supports a specific feature by
+ including the feature's policy assertion within its WSDL. By doing so,
+ the endpoint is indicating that corresponding operations (if any) are
+ supported by that endpoint even though they do not explicitly appear in
+ its WSDL. An example of this is an endpoint that indicates the use
+ of WS-Transfer <bibref ref="WS-Transfer"/> by the use of the
+ wstrp:TransferResource WS-Policy <bibref ref="wspolicy"/> assertion.
+ </p>
+
+ <p>
+ An endpoint MAY choose to expose the WSDL of the policy defined
+ feature by using the http://schemas.xmlsoap.org/wsdl/ dialect and
+ the dialect identifier of the target namespace of the feature.
+ </p>
+
+ <table border="1">
+ <tbody>
+ <tr>
+ <th align="left"> Dialect IRI </th>
+ <th> @Identifier Value </th>
+ <th> Metadata Returned </th>
+ </tr>
+ <tr>
+ <td> http://schemas.xmlsoap.org/wsdl/ </td>
+ <td> target namespace of endpoint </td>
+ <td> Endpoint WSDL </td>
+ </tr>
+ <tr>
+ <td> http://schemas.xmlsoap.org/wsdl/ </td>
+ <td> target namespace of feature supported by the endpoint </td>
+ <td> Feature WSDL </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>
+ The Feature WSDL, the WSDL associated with these implicit operations,
+ can be annotated to indicate any endpoint specific metadata that might be
+ needed by clients interacting with this service. For example, the WSDL
+ can have policy assertions that indicate a particular security
+ mechanism used to protect the feature's operations supported by this
+ endpoint. When a Feature WSDL does not provide a concrete endpoint,
+ the consumer MUST use the concrete aspects of the endpoint's WSDL.
+ </p>
+
+ </div1>
+
<div1 id="Security">
<head>Security Considerations</head>
@@ -2437,6 +2488,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/11/05 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -d -r1.87 -r1.88
--- wsenum.html 6 Nov 2009 04:32:47 -0000 1.87
+++ wsenum.html 6 Nov 2009 05:07:57 -0000 1.88
@@ -67,11 +67,11 @@
4.9 <a href="#UnusableEPR">UnusableEPR</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_1946">Enumeration Assertion</a><br/>
+ 6.1 <a href="#iddiv2_1_1925">Enumeration Assertion</a><br/>
7 <a href="#acks">Acknowledgements</a><br/>
8 <a href="#refs">References</a><br/>
- 8.1 <a href="#iddiv2_1_2035">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2221">Informative References</a><br/>
+ 8.1 <a href="#iddiv2_1_2014">Normative References</a><br/>
+ 8.2 <a href="#iddiv2_1_2200">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/>
@@ -1285,20 +1285,18 @@
by including the WS-Enumeration Policy assertion within its WSDL. By
doing so the endpoint is indicating that the corresponding WS-Enumeration
operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL (i.e. the WSDL that MAY be retrievable by
- using a WS-MetadataExchange GetMetadata with a Dialect IRI of
- http://schemas.xmlsoap.org/wsdl/).
+ explicitly appear in its WSDL.
</p><p>
- An endpoint MAY choose to expose the WS-Enumeration WSDL by using the
- following WS-MetadataExchange Dialect:
- </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th> @Identifier value </th></tr><tr><td> http://www.w3.org/2009/02/ws-enu/EnumerationWSDL </td><td> Not defined </td></tr></tbody></table><p>
- The WS-Enumeration WSDL can be annotated to indicate any endpoint
+ The WS-Enumeration WSDL containing the operations indicated by the
+ Enumeration Assertion MAY be exposed as described in
+ WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> Section 9.
+ This WS-Enumeration WSDL can be annotated to indicate any endpoint
specific metadata that might be needed by clients interacting with
- this service. For example, the WSDL MAY have policy assertions that
- indicate a particular security mechanism used to protect the
- WS-Enumeration operations supported by this endpoint.
+ this service. For example, the WSDL MAY have policy assertions
+ 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_1946" id="iddiv2_1_1946"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_1925" id="iddiv2_1_1925"/>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 -
@@ -1390,7 +1388,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_2035" id="iddiv2_1_2035"/>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_2014" id="iddiv2_1_2014"/>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.
@@ -1462,7 +1460,13 @@
, 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_2221" id="iddiv2_1_2221"/>8.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_2200" id="iddiv2_1_2200"/>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>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ Available at <a href="http://www.w3.org/TR/ws-metadata-exchange">http://www.w3.org/TR/ws-metadata-exchange</a>.</dd><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>
@@ -1963,4 +1967,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=8075">8075</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=8069">8069</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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <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></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.79
retrieving revision 1.80
diff -u -d -r1.79 -r1.80
--- wsenum.xml 6 Nov 2009 04:32:47 -0000 1.79
+++ wsenum.xml 6 Nov 2009 05:07:57 -0000 1.80
@@ -2336,35 +2336,18 @@
by including the WS-Enumeration Policy assertion within its WSDL. By
doing so the endpoint is indicating that the corresponding WS-Enumeration
operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL (i.e. the WSDL that MAY be retrievable by
- using a WS-MetadataExchange GetMetadata with a Dialect IRI of
- http://schemas.xmlsoap.org/wsdl/).
+ explicitly appear in its WSDL.
</p>
<p>
- An endpoint MAY choose to expose the WS-Enumeration WSDL by using the
- following WS-MetadataExchange Dialect:
- </p>
-
- <table border="1">
- <tbody>
- <tr>
- <th align="left"> Dialect IRI </th>
- <th> @Identifier value </th>
- </tr>
- <tr>
- <td> http://www.w3.org/2009/02/ws-enu/EnumerationWSDL </td>
- <td> Not defined </td>
- </tr>
- </tbody>
- </table>
-
- <p>
- The WS-Enumeration WSDL can be annotated to indicate any endpoint
+ The WS-Enumeration WSDL containing the operations indicated by the
+ Enumeration Assertion MAY be exposed as described in
+ WS-MetadataExchange <bibref ref="MEX"/> Section 9.
+ This WS-Enumeration WSDL can be annotated to indicate any endpoint
specific metadata that might be needed by clients interacting with
- this service. For example, the WSDL MAY have policy assertions that
- indicate a particular security mechanism used to protect the
- WS-Enumeration operations supported by this endpoint.
+ this service. For example, the WSDL MAY have policy assertions
+ that indicate a particular security mechanism used to protect
+ the WS-Enumeration operations supported by this endpoint.
</p>
<div2>
@@ -2673,6 +2656,16 @@
<head>Informative References</head>
<blist>
+ <bibl key="WS-MetadataExchange" id="MEX"
+ href="http://www.w3.org/TR/ws-metadata-exchange">
+ <titleref>
+ W3C Working Group Draft, "Web Services Metadata Exchange
+ (WS-MetadataExchange) 1.1"
+ </titleref>
+ , D. Davis, et al., Editors.
+ World Wide Web Consortium (W3C), 15 September 2009.
+ </bibl>
+
<bibl key="WS-SecureConversation" id="WSSecureConversation"
href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc">
<titleref>
@@ -3517,6 +3510,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8076">8076</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/11/05 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -d -r1.78 -r1.79
--- wsmex.html 5 Nov 2009 17:03:01 -0000 1.78
+++ wsmex.html 6 Nov 2009 05:07:57 -0000 1.79
@@ -58,13 +58,14 @@
6.2 <a href="#Get-Metadata">Get Metadata</a><br/>
7 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br/>
-9 <a href="#Security">Security Considerations</a><br/>
-10 <a href="#metadata">WS-Metadata Exchange Metadata</a><br/>
- 10.1 <a href="#iddiv2_1_1426">MetadataExchange Assertion</a><br/>
-11 <a href="#Acknowledgements">Acknowledgements</a><br/>
-12 <a href="#References">References</a><br/>
- 12.1 <a href="#iddiv2_1_1490">Normative References</a><br/>
- 12.2 <a href="#iddiv2_1_1663">Informative References</a><br/>
+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_1485">MetadataExchange Assertion</a><br/>
+12 <a href="#Acknowledgements">Acknowledgements</a><br/>
+13 <a href="#References">References</a><br/>
+ 13.1 <a href="#iddiv2_1_1549">Normative References</a><br/>
+ 13.2 <a href="#iddiv2_1_1722">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/>
@@ -885,7 +886,28 @@
metadata retrieval MAY be defined by communities within the
context of particular application domains.
</p></div><div class="div1">
-<h2><a name="Security" id="Security"/>9 Security Considerations</h2><p>
+<h2><a name="ImplicitWSDL" id="ImplicitWSDL"/>9 Exposing WSDL for Operations Implicitly Defined by a Policy Assertion</h2><p>
+ An endpoint MAY indicate that it supports a specific feature by
+ including the feature's policy assertion within its WSDL. By doing so,
+ the endpoint is indicating that corresponding operations (if any) are
+ supported by that endpoint even though they do not explicitly appear in
+ its WSDL. An example of this is an endpoint that indicates the use
+ of WS-Transfer <a href="#WS-Transfer">[WS-Transfer]</a> by the use of the
+ wstrp:TransferResource WS-Policy <a href="#wspolicy">[WS-Policy]</a> assertion.
+ </p><p>
+ An endpoint MAY choose to expose the WSDL of the policy defined
+ feature by using the http://schemas.xmlsoap.org/wsdl/ dialect and
+ the dialect identifier of the target namespace of the feature.
+ </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th> @Identifier Value </th><th> Metadata Returned </th></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> target namespace of endpoint </td><td> Endpoint WSDL </td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> target namespace of feature supported by the endpoint </td><td> Feature WSDL </td></tr></tbody></table><p>
+ The Feature WSDL, the WSDL associated with these implicit operations,
+ can be annotated to indicate any endpoint specific metadata that might be
+ needed by clients interacting with this service. For example, the WSDL
+ can have policy assertions that indicate a particular security
+ mechanism used to protect the feature's operations supported by this
+ endpoint. When a Feature WSDL does not provide a concrete endpoint,
+ the consumer MUST use the concrete aspects of the endpoint's WSDL.
+ </p></div><div class="div1">
+<h2><a name="Security" id="Security"/>10 Security Considerations</h2><p>
It is strongly RECOMMENDED that the communication between Web services
be secured using the mechanisms described in WS-Security
<a href="#WSSecurity">[WS-Security]</a>. In order to properly secure messages,
@@ -955,7 +977,7 @@
technologies, such as sequencing, can also be used to prevent
replay of application messages.
</p></li></ul></div><div class="div1">
-<h2><a name="metadata" id="metadata"/>10 WS-Metadata Exchange Metadata</h2><p>
+<h2><a name="metadata" id="metadata"/>11 WS-Metadata Exchange Metadata</h2><p>
An endpoint MAY indicate that it supports WS-MetadataExchange, or its
features,
by including the WS-MetadataExchange Policy assertion within its WSDL. By
@@ -975,7 +997,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_1426" id="iddiv2_1_1426"/>10.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1485" id="iddiv2_1_1485"/>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 -
@@ -1029,7 +1051,7 @@
Note: Metadata resources use the corresponding policy assertions for the
WS-Transfer operation that they support.
</p></div></div><div class="div1">
-<h2><a name="Acknowledgements" id="Acknowledgements"/>11 Acknowledgements</h2><p>
+<h2><a name="Acknowledgements" id="Acknowledgements"/>12 Acknowledgements</h2><p>
This specification has been developed as a result of joint
work with many individuals and teams, including:
Ashok Malhotra (Oracle Corp.),
@@ -1052,8 +1074,8 @@
Wu Chou (Avaya Communications),
Yves Lafon (W3C).
</p></div><div class="div1">
-<h2><a name="References" id="References"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1490" id="iddiv2_1_1490"/>12.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>
+<h2><a name="References" id="References"/>13 References</h2><div class="div2">
+<h3><a name="iddiv2_1_1549" id="iddiv2_1_1549"/>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.
@@ -1120,7 +1142,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_1663" id="iddiv2_1_1663"/>12.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_1722" id="iddiv2_1_1722"/>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>
@@ -1345,4 +1367,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</a></td></tr><tr><td> 2009/10/13 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</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=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></tbody></table></div></div></body></html>
\ No newline at end of file
+ <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></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.109
retrieving revision 1.110
diff -u -d -r1.109 -r1.110
--- wseventing.xml 6 Nov 2009 04:32:47 -0000 1.109
+++ wseventing.xml 6 Nov 2009 05:07:58 -0000 1.110
@@ -2668,35 +2668,18 @@
by including the WS-Eventing Policy assertion within its WSDL. By
doing so the endpoint is indicating that the corresponding WS-Eventing
operations are supported by that endpoint even though they do not
- explicitly appear in its WSDL (i.e. the WSDL that MAY be retrievable by
- using a WS-MetadataExchange GetMetadata with a Dialect IRI of
- http://schemas.xmlsoap.org/wsdl/).
- </p>
-
- <p>
- An endpoint MAY choose to expose the WS-Eventing WSDL by using the
- following WS-MetadataExchange Dialect:
+ explicitly appear in its WSDL.
</p>
- <table border="1">
- <tbody>
- <tr>
- <th align="left"> Dialect IRI </th>
- <th> @Identifier value </th>
- </tr>
- <tr>
- <td> http://www.w3.org/2009/02/ws-evt/EventingWSDL </td>
- <td> Not defined </td>
- </tr>
- </tbody>
- </table>
-
<p>
- The WS-Eventing WSDL can be annotated to indicate any endpoint
+ The WS-Eventing WSDL containing the operations indicated by the
+ EventSource Assertion MAY be exposed as described in
+ WS-MetadataExchange <bibref ref="MEX"/> Section 9.
+ This WS-Eventing WSDL can be annotated to indicate any endpoint
specific metadata that might be needed by clients interacting with
- this service. For example, the WSDL MAY have policy assertions that
- indicate a particular security mechanism used to protect the
- WS-Eventing operations supported by this endpoint.
+ this service. For example, the WSDL MAY have policy assertions
+ that indicate a particular security mechanism used to protect
+ the WS-Eventing operations supported by this endpoint.
</p>
<div2>
@@ -4649,6 +4632,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8076">8076</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/11/05 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7912">7912</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Friday, 6 November 2009 05:08:03 UTC