- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 10 Mar 2010 05:35:01 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv7367
Modified Files:
wsenum.html wsenum.xml wsevd.html wsevd.xml wseventing.html
wseventing.xml wsfrag.html wsfrag.xml wsmex.html wsmex.xml
wst.html wst.xml
Log Message:
MOAP
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -d -r1.107 -r1.108
--- wst.xml 24 Feb 2010 15:04:01 -0000 1.107
+++ wst.xml 10 Mar 2010 05:34:59 -0000 1.108
@@ -1646,19 +1646,29 @@
<p>
An endpoint MAY indicate that it supports WS-Transfer, or its features,
- by including the WS-Transfer Policy assertion within its WSDL. By
+ by including the WS-Transfer TransferResource or TransferResourceFactory
+ Policy assertions 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.
+ explicitly appear in its WSDL
+ (i.e. the WS-Transfer operations do not appear in the WSDL that MAY be
+ retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
</p>
<p>
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.
+ TransferResource or TransferResourceFactory assertions MAY be exposed
+ by including the WSDL as a child of the appropriate Policy assertion or
+ by including a reference to it using the mex:Location or mex:Reference
+ element (as described in
+ WS-MetadataExchange <bibref ref="MEX"/> Section 9).
+ </p>
+
+ <p>
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 might have policy assertions
+ this service's WS-Transfer operations.
+ For example, the WSDL might have policy assertions
that indicate a particular security mechanism used to protect
the WS-Transfer operations supported by this endpoint.
</p>
@@ -1667,9 +1677,9 @@
<head>TransferResource Assertion</head>
<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
+ Services indicate support for the
+ WS-Transfer's definition of a Transfer Resource
+ through the use of the Web Services
Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
Attachment <bibref ref="wspolicyattach"/> specifications.
</p>
@@ -1681,16 +1691,14 @@
</p>
<p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the wst:TransferResource
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
+ wsdl20:binding.
</p>
<p>
- The wst:TransferResource policy assertion is a nested policy container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Transfer is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource.
</p>
@@ -1714,9 +1722,11 @@
<wst:PutOperationSupported .../> ?
<wst:DeleteOperationSupported .../> ?
<wst:FaultOnPutDenied.../> ?
- <wst:Dialect ...> <emph>xs:anyURI</emph> </wst:Dialect> *
+ <wst:Dialect URI='<emph>xs:anyURI</emph> ...>
+ <emph>xs:any</emph>*
+ </wst:Dialect> *
<wst:Resource ...> <emph>xs:QName</emph> </wst:Resource> ?
- ...
+ <emph>xs:any</emph>*
</wst:TransferResource></eg>
</example>
@@ -1785,6 +1795,17 @@
</gitem>
<gitem>
+ <label> /wst:TransferResource/wst:Dialect/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional Dialect specific
+ metadata to be included within the policy assertion. Any metadata
+ that appears is scoped to the use of the specified Dialect URI.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
<label> /wst:TransferResource/wst:Resource </label>
<def>
<p>
@@ -1795,6 +1816,19 @@
</def>
</gitem>
+ <gitem>
+ <label> /wst:TransferResource/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional WS-Transfer
+ specific metadata to be included within the policy assertion -
+ 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>
+ </def>
+ </gitem>
+
</glist>
</div2>
@@ -1803,9 +1837,9 @@
<head>TransferResourceFactory Assertion</head>
<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
+ Services indicate support for
+ WS-Transfer's definition of a Transfer Resource Factory
+ through the use of the Web Services
Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
Attachment <bibref ref="wspolicyattach"/> specifications.
</p>
@@ -1818,18 +1852,14 @@
</p>
<p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the
- wst:TransferResourceFactory
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
+ wsdl20:binding.
</p>
<p>
- The wst:TransferResourceFactory policy assertion is a nested policy
- container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Transfer is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource Factory.
</p>
@@ -1850,8 +1880,10 @@
<example>
<eg><wst:TransferResourceFactory ...>
- <wst:Dialect ...> <emph>xs:anyURI</emph> </wst:Dialect> *
- ...
+ <wst:Dialect URI="<emph>xs:anyURI</emph>" ...>
+ <emph>xs:any</emph>*
+ </wst:Dialect> *
+ <emph>xs:any</emph>*
</wst:TransferResourceFactory></eg>
</example>
@@ -1883,6 +1915,30 @@
</def>
</gitem>
+ <gitem>
+ <label> /wst:TransferResourceFactory/wst:Dialect/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional Dialect specific
+ metadata to be included within the policy assertion. Any metadata
+ that appears is scoped to the use of the specified Dialect URI.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wst:TransferResourceFactory/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional WS-Transfer
+ specific metadata to be included within the policy assertion -
+ 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>
+ </def>
+ </gitem>
+
</glist>
</div2>
@@ -2254,8 +2310,16 @@
<xs:element name='DeleteOperationSupported' type='tns:Empty'
minOccurs='0'/>
<xs:element name='FaultOnPutDenied' type='tns:Empty' minOccurs='0'/>
- <xs:element name='Dialect' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='Dialect' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:element name='Resource' type='xs:QName' minOccurs='0'/>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
@@ -2267,8 +2331,16 @@
<xs:element name='TransferResourceFactory'>
<xs:complexType>
<xs:sequence>
- <xs:element name='Dialect' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='Dialect' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
</xs:sequence>
@@ -2801,6 +2873,15 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9032">9032</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.164
retrieving revision 1.165
diff -u -d -r1.164 -r1.165
--- wseventing.html 24 Feb 2010 15:04:00 -0000 1.164
+++ wseventing.html 10 Mar 2010 05:34:59 -0000 1.165
@@ -76,22 +76,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_2168">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2250">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2170">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2279">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2321">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2455">Informative 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/>
</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_2657">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2678">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2683">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2701">Binding for Wrapped Notifications</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.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2728">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2749">Multiple Event Information Metadata Sections</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/>
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/>
@@ -1494,38 +1494,43 @@
</p></div><div class="div1">
<h2><a name="metadata" id="metadata"/>9 WS-Eventing Metadata</h2><p>
An endpoint MAY indicate that it supports WS-Eventing, or its features,
- by including the WS-Eventing Policy assertion within its WSDL. By
+ by including the WS-Eventing EventSource or SubscriptionManager Policy
+ assertions 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.
+ explicitly appear in its WSDL (ie. the WS-Eventing operations do not
+ appear in the WSDL that MAY be retrievable by using WS-MetadataExchange
+ GetWSDL to that endpoint).
</p><p>
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.
+ EventSource or SubscriptionManager assertions MAY be exposed
+ by including the WSDL as a child of the appropriate Policy
+ assertion or by including a reference to it using the mex:Location
+ or mex:Reference element ( as described in
+ WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> Section 9).
+ </p><p>
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
+ this service's WS-Eventing operations. 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_2168" id="iddiv2_1_2168"/>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
+<h3><a name="iddiv2_1_2170" id="iddiv2_1_2170"/>9.1 EventSource Assertion</h3><p>
+ Services indicate support for the WS-Eventing's definition
+ of an event source through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
</p><p>
This specification defines a policy assertion (wse:EventSource). The
wse:EventSource policy assertion applies to the endpoint policy subject.
</p><p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the wse:EventSource
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl:portType,
+ wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:interface,
+ wsdl20:endpoint or wsdl20:binding.
</p><p>
- The wse:EventSource policy assertion is a nested policy container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Eventing is REQUIRED to communicate with the
subject and that the subject is a WS-Eventing event source.
</p><p>
@@ -1540,14 +1545,18 @@
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wse:EventSource ...>
<wse:DateTimeSupported .../> ?
- <wse:FilterDialect ...> <em>xs:anyURI</em> </wse:FilterDialect> *
+ <wse:FilterDialect URI="<em>xs:anyURI</em>" ...>
+ <em>xs:any</em>*
+ </wse:FilterDialect> *
<wse:MaxExpires ...> <em>xs:duration</em> </wse:MaxExpires> ?
- <wse:FormatName ...> <em>xs:anyURI</em> </wse:FormatName> *
+ <wse:FormatName URI="<em>xs:anyURI</em>" ...>
+ <em>xs:any</em>*
+ </wse:FormatName> *
<wse:EndToSupported .../> ?
<wse:NotificationPolicy ...>
<em>xs:any</em>
</wse:NotificationPolicy> ?
- ...
+ <em>xs:any</em>*
</wse:EventSource></pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
@@ -1561,6 +1570,11 @@
</p></dd><dt class="label"> /wse:EventSource/wse:FilterDialect </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
specified filter dialect IRI.
+ </p></dd><dt class="label"> /wse:EventSource/wse:FilterDialect/xs:any </dt><dd><p>
+ This extensibility point allows for additional FilterDialect
+ specific metadata to be included within the policy assertion. Any
+ metadata that appears is scoped to the use of the specified
+ FilterDialect URI.
</p></dd><dt class="label"> /wse:EventSource/wse:MaxExpires </dt><dd><p>
When present, this OPTIONAL parameter indicates the maximum
subscription expiration time that this endpoint will support.
@@ -1570,6 +1584,10 @@
</p></dd><dt class="label"> /wse:EventSource/wse:FormatName </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
specified event delivery format name URI.
+ </p></dd><dt class="label"> /wse:EventSource/wse:FormatName/xs:any </dt><dd><p>
+ This extensibility point allows for additional FormatName specific
+ metadata to be included within the policy assertion. Any metadata
+ that appears is scoped to the use of the specified FormatName URI.
</p></dd><dt class="label"> /wse:EventSource/wse:EndToSupported </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
/wse:Subscribe/wse:EndTo semantics. That is, when a subscription
@@ -1588,11 +1606,18 @@
Any policy alternatives included within this parameter SHOULD be
compatible with those Policy Alternatives available of the
Notification WSDLs that the event source advertises.
+ </p></dd><dt class="label"> /wse:EventSource/xs:any </dt><dd><p>
+ This extensibility point allows for additional WS-Eventing
+ specific metadata to be included within the policy assertion -
+ 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 class="div2">
-<h3><a name="iddiv2_1_2250" id="iddiv2_1_2250"/>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
+<h3><a name="iddiv2_1_2279" id="iddiv2_1_2279"/>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
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
</p><p>
@@ -1600,15 +1625,12 @@
The wse:SubscriptionManager policy assertion applies to the endpoint
policy subject.
</p><p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the
- wse:SubscriptionManager
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
+ wsdl20:binding.
</p><p>
- The wse:SubscriptionManager policy assertion is a nested policy container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Eventing is REQUIRED to communicate with the
subject and that the subject is a WS-Eventing subscription manager.
</p><p>
@@ -1626,7 +1648,7 @@
<wse:GetStatusOperationSupported .../> ?
<wse:UnsubscribeOperationSupported .../> ?
<wse:MaxExpires ...> <em>xs:duration</em> </wse:MaxExpires> ?
- ...
+ <em>xs:any</em>*
</wse:SubscriptionManager></pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
@@ -1649,6 +1671,12 @@
The implied default is indefinite (no expiry).
Note: a value of "PT0S" indicates that this endpoint supports
subscriptions with an infinite lifetime.
+ </p></dd><dt class="label"> /wse:SubscriptionManager/xs:any </dt><dd><p>
+ This extensibility point allows for additional WS-Eventing
+ specific metadata to be included within the policy assertion -
+ 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">
<h2><a name="acks" id="acks"/>10 Acknowledgements</h2><p>
This specification has been developed as a result of joint
@@ -1681,7 +1709,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_2321" id="iddiv2_1_2321"/>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_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>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1733,7 +1761,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_2455" id="iddiv2_1_2455"/>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_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>
OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
Web Services Make Connection (WS-MakeConnection)
</cite></a>
@@ -1837,7 +1865,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_2647" id="idexample_1_2647"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2685" id="idexample_1_2685"/>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">
@@ -1857,7 +1885,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_2657" id="iddiv3_1_2657"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2695" id="iddiv3_1_2695"/>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>.
@@ -1868,7 +1896,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_2678" id="iddiv3_1_2678"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2716" id="iddiv3_1_2716"/>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
@@ -1880,7 +1908,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_2683" id="iddiv4_1_2683"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2721" id="iddiv4_1_2721"/>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>
@@ -1894,7 +1922,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_2701" id="iddiv4_1_2701"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2739" id="iddiv4_1_2739"/>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>
@@ -1918,7 +1946,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_2722" id="idexample_1_2722"/>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_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/"
(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/"
@@ -1953,7 +1981,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2728" id="iddiv3_1_2728"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2766" id="iddiv3_1_2766"/>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>.
@@ -1969,7 +1997,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_2749" id="iddiv2_1_2749"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2787" id="iddiv2_1_2787"/>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
@@ -2281,11 +2309,27 @@
<xs:complexType>
<xs:sequence>
<xs:element name='DateTimeSupported' type='tns:Empty' minOccurs='0'/>
- <xs:element name='FilterDialect' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='FilterDialect' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:element name='MaxExpires' type='tns:Duration' minOccurs='0'/>
- <xs:element name='FormatName' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='FormatName' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:element name='EndToSupported' type='tns:Empty' minOccurs='0'/>
<xs:element name='NotificationPolicy' type='tns:NotificationPolicy'
minOccurs='0'/>
@@ -2367,9 +2411,9 @@
<wsdl:part name='body' element='wse:SubscriptionEnd' />
</wsdl:message>
- <message name='notifyEvent'>
- <part name='parameter' element='tns:Notify'/>
- </message>
+ <wsdl:message name='notifyEvent'>
+ <wsdl:part name='parameter' element='wse:Notify'/>
+ </wsdl:message>
<wsdl:portType name='EventSource' >
<wsdl:operation name='SubscribeOp' >
@@ -2417,12 +2461,12 @@
</wsdl:operation>
</wsdl:portType>
- <portType name='WrappedSinkPortType'>
- <operation name='NotifyEvent'>
- <input message='tns:notifyEvent' name='NotifyEvent'
+ <wsdl:portType name='WrappedSinkPortType'>
+ <wsdl:operation name='NotifyEvent'>
+ <wsdl:input message='wse:notifyEvent' name='NotifyEvent'
wsam:Action='http://www.w3.org/2002/ws/ra/edcopies/ws-evt/WrappedSinkPortType/NotifyEvent'/>
- </operation>
- </portType>
+ </wsdl:operation>
+ </wsdl:portType>
</wsdl:definitions></pre></div></div></div><div class="div1">
<h2><a name="wrappedWSDL" id="wrappedWSDL"/>D WSDL for Standard Wrapped Delivery</h2><p>
If an event subscriber specifies the wrapped event delivery format
@@ -2641,4 +2685,7 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435">6435</a></td></tr><tr><td> 2010/02/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8271">8271</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=8271">8271</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsevd.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- wsevd.xml 24 Feb 2010 15:04:00 -0000 1.4
+++ wsevd.xml 10 Mar 2010 05:34:59 -0000 1.5
@@ -619,18 +619,52 @@
<p>
Although there are many ways in which an endpoint can make its
EventDescriptions available, this specification RECOMMENDS the use of
- the mechanisms described in WS-MetadataExchange <bibref ref="MEX"/>.
- This specification defines the following IRI to serve as the Dialect
- IRI for the wsevd:EventDescriptions element.
+ the mechanisms described in section 9 of WS-MetadataExchange
+ <bibref ref="MEX"/>.
+ In particular, this specification RECOMMENDS that the Event Description
+ metadata be made available through the WS-Eventing
+ <bibref ref="Eventing"/> EventSource Policy assertion. This MAY be done
+ by either embedding the Event Description metadata directly within
+ the assertion, or by including a MetadataExchange reference to the data.
</p>
- <example>
- <eg><loc href="http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescriptions">http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescriptions</loc></eg>
+ <p>
+ The following examples show how Event Description metadata might
+ appear within a WS-Eventing EventSource Policy assertion.
+ </p>
+
+ <example id="embedEVD">
+ <head>Sample Embedded EventDescription Metadata</head>
+ <eg>(01) <wse:EventSource ...>
+(02) <wse:FormatName URI="..."/>
+(03) <wsevd:EventDescritions ...>
+(04) ...
+(05) </wsevd:EventDescriptions>
+(06) </wse:EventSource></eg>
</example>
<p>
- The value of the @Identifier attribute for this Metadata Section MUST
- be equal to the value of its wsevd:EventDescriptions/@targetNamespace.
+ <specref ref="embedEVD"/> shows how the Event Description metadata
+ might be embedded directly within a WS-Eventing EventSource Policy
+ assertion.
+ </p>
+
+ <example id="refEVD">
+ <head>Sample Reference to EventDescription Metadata</head>
+ <eg>(01) <wse:EventSource ...>
+(02) <wse:FormatName URI="..."/>
+(03) <mex:Location
+(04) Type="evd:EventDescriptions"
+(05) URI="http://example.com/EVD_Metadata" />
+(06) </wse:EventSource> </eg>
+ </example>
+
+ <p>
+ <specref ref="refEVD"/> shows the same policy assertion from
+ <specref ref="embedEVD"/> except the embedded Event Description
+ metadata is replaced with a reference to an HTTP resource whose
+ representation is the Event Description metadata. The data can be
+ retrieved via an HTTP GET to the specified URL.
</p>
</div3>
@@ -744,6 +778,16 @@
World Wide Web Consortium (W3C), 9 May 2006.
</bibl>
+ <bibl key="WS-Eventing" id="Eventing"
+ href="http://www.w3.org/TR/ws-eventing">
+ <titleref>
+ W3C Working Group Draft, "Web Services Eventing
+ (WS-Eventing) 1.1"
+ </titleref>
+ , D. Davis, et al., Editors.
+ 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>
@@ -872,6 +916,15 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- wsfrag.xml 4 Mar 2010 13:46:41 -0000 1.56
+++ wsfrag.xml 10 Mar 2010 05:34:59 -0000 1.57
@@ -1945,7 +1945,8 @@
<p>
An endpoint MAY indicate that it supports WS-Fragment, or its features,
- by including the WS-Fragment Policy assertion within its WSDL. By
+ by including the WS-Fragment FragmentAssertion Policy assertion within its
+ WSDL. By
doing so the endpoint is indicating that the corresponding WS-Fragment
features are supported by that endpoint.
</p>
@@ -1954,8 +1955,8 @@
<head>Fragment Assertion</head>
<p>
- The mechanism for indicating that a binding or endpoint conforms to the
- WS-Fragment specification is through the use of the Web Services
+ Services indicate support for the WS-Fragment specification through
+ the use of the Web Services
Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
Attachment <bibref ref="wspolicyattach"/> specifications.
</p>
@@ -1967,16 +1968,14 @@
</p>
<p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the wsf:FragmentAssertion
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
+ wsdl20:binding.
</p>
<p>
- The wsf:FragmentAssertion policy assertion is a nested policy container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Fragment is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource.
</p>
@@ -1997,8 +1996,10 @@
<example>
<eg><wsf:FragmentAssertion ...>
- <wsf:Language ...> <emph>xs:anyURI</emph> </wsf:Language> *
- ...
+ <wsf:Language URI="<emph>xs:anyURI</emph> ...>
+ <emph>xs:any</emph>*
+ </wsf:Language> *
+ <emph>xs:any</emph>*
</wsf:FragmentAssertion></eg>
</example>
@@ -2030,6 +2031,29 @@
</def>
</gitem>
+ <gitem>
+ <label> /wsf:FragmentAssertion/wsf:Language/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional Language specific
+ metadata to be included within the policy assertion. Any metadata
+ that appears is scoped to the use of the specified Language URI.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
+ <label> /wsf:FragmentAssertion/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional WS-Fragment
+ specific metadata to be included within the policy assertion.
+ Any metadata that appears is scoped to the operations and features
+ of the WS-Fragment specification.
+ </p>
+ </def>
+ </gitem>
+
</glist>
</div2>
@@ -2284,8 +2308,16 @@
<xs:element name='FragmentAssertion'>
<xs:complexType>
<xs:sequence>
- <xs:element name='Language' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='Language' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
</xs:sequence>
@@ -2505,6 +2537,15 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8193">8193</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- wsfrag.html 4 Mar 2010 13:46:41 -0000 1.56
+++ wsfrag.html 10 Mar 2010 05:34:59 -0000 1.57
@@ -68,7 +68,7 @@
9.1 <a href="#iddiv2_1_1939">Fragment Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_1992">Normative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2010">Normative 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="#changelog">Change Log</a><br/>
@@ -921,13 +921,14 @@
</td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unsupported Mode.</em></td></tr></tbody></table></div></div><div class="div1">
<h2><a name="metadata" id="metadata"/>9 WS-Fragment Metadata</h2><p>
An endpoint MAY indicate that it supports WS-Fragment, or its features,
- by including the WS-Fragment Policy assertion within its WSDL. By
+ by including the WS-Fragment FragmentAssertion Policy assertion within its
+ WSDL. By
doing so the endpoint is indicating that the corresponding WS-Fragment
features are supported by that endpoint.
</p><div class="div2">
<h3><a name="iddiv2_1_1939" id="iddiv2_1_1939"/>9.1 Fragment Assertion</h3><p>
- The mechanism for indicating that a binding or endpoint conforms to the
- WS-Fragment specification is through the use of the Web Services
+ Services indicate support for the WS-Fragment specification through
+ the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
</p><p>
@@ -935,14 +936,12 @@
The wsf:FragmentAssertion policy assertion applies to the endpoint policy
subject.
</p><p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the wsf:FragmentAssertion
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
+ wsdl20:binding.
</p><p>
- The wsf:FragmentAssertion policy assertion is a nested policy container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Fragment is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource.
</p><p>
@@ -956,8 +955,10 @@
</p><p>
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsf:FragmentAssertion ...>
- <wsf:Language ...> <em>xs:anyURI</em> </wsf:Language> *
- ...
+ <wsf:Language URI="<em>xs:anyURI</em> ...>
+ <em>xs:any</em>*
+ </wsf:Language> *
+ <em>xs:any</em>*
</wsf:FragmentAssertion></pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
@@ -968,6 +969,15 @@
</p></dd><dt class="label"> /wsf:FragmentAssertion/wsf:Language </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
specified Language IRI.
+ </p></dd><dt class="label"> /wsf:FragmentAssertion/wsf:Language/xs:any </dt><dd><p>
+ This extensibility point allows for additional Language specific
+ metadata to be included within the policy assertion. Any metadata
+ that appears is scoped to the use of the specified Language URI.
+ </p></dd><dt class="label"> /wsf:FragmentAssertion/xs:any </dt><dd><p>
+ This extensibility point allows for additional WS-Fragment
+ specific metadata to be included within the policy assertion.
+ Any metadata that appears is scoped to the operations and features
+ of the WS-Fragment specification.
</p></dd></dl></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
@@ -1000,7 +1010,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_1992" id="iddiv2_1_1992"/>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_2010" id="iddiv2_1_2010"/>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.
@@ -1130,8 +1140,16 @@
<xs:element name='FragmentAssertion'>
<xs:complexType>
<xs:sequence>
- <xs:element name='Language' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='Language' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
</xs:sequence>
@@ -1171,4 +1189,7 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a></td></tr><tr><td> 2010/02/10 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9032">9032</a></td></tr><tr><td> 2010/03/02 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8185">8185</a>,
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8193">8193</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=8193">8193</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</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.109
retrieving revision 1.110
diff -u -d -r1.109 -r1.110
--- wst.html 24 Feb 2010 15:04:01 -0000 1.109
+++ wst.html 10 Mar 2010 05:34:59 -0000 1.110
@@ -59,12 +59,12 @@
5.4 <a href="#UnknownResource">UnknownResource</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_1368">TransferResource Assertion</a><br/>
- 7.2 <a href="#iddiv2_1_1438">TransferResourceFactory Assertion</a><br/>
+ 7.1 <a href="#iddiv2_1_1370">TransferResource Assertion</a><br/>
+ 7.2 <a href="#iddiv2_1_1458">TransferResourceFactory Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1491">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1664">Informative 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/>
</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/>
@@ -943,24 +943,32 @@
minimal state is saved prior to any authenticating sequences.</p></li></ul></div><div class="div1">
<h2><a name="metadata" id="metadata"/>7 WS-Transfer Metadata</h2><p>
An endpoint MAY indicate that it supports WS-Transfer, or its features,
- by including the WS-Transfer Policy assertion within its WSDL. By
+ by including the WS-Transfer TransferResource or TransferResourceFactory
+ Policy assertions 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.
+ explicitly appear in its WSDL
+ (i.e. the WS-Transfer operations do not appear in the WSDL that MAY be
+ retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
</p><p>
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.
+ TransferResource or TransferResourceFactory assertions MAY be exposed
+ by including the WSDL as a child of the appropriate Policy assertion or
+ by including a reference to it using the mex:Location or mex:Reference
+ element (as described in
+ WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> Section 9).
+ </p><p>
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 might have policy assertions
+ this service's WS-Transfer operations.
+ For example, the WSDL might 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_1368" id="iddiv2_1_1368"/>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
+<h3><a name="iddiv2_1_1370" id="iddiv2_1_1370"/>7.1 TransferResource Assertion</h3><p>
+ Services indicate support for the
+ WS-Transfer's definition of a Transfer Resource
+ through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
</p><p>
@@ -968,14 +976,12 @@
The wst:TransferResource policy assertion applies to the endpoint
policy subject.
</p><p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the wst:TransferResource
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
+ wsdl20:binding.
</p><p>
- The wst:TransferResource policy assertion is a nested policy container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Transfer is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource.
</p><p>
@@ -992,9 +998,11 @@
<wst:PutOperationSupported .../> ?
<wst:DeleteOperationSupported .../> ?
<wst:FaultOnPutDenied.../> ?
- <wst:Dialect ...> <em>xs:anyURI</em> </wst:Dialect> *
+ <wst:Dialect URI='<em>xs:anyURI</em> ...>
+ <em>xs:any</em>*
+ </wst:Dialect> *
<wst:Resource ...> <em>xs:QName</em> </wst:Resource> ?
- ...
+ <em>xs:any</em>*
</wst:TransferResource></pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
@@ -1020,15 +1028,25 @@
</p></dd><dt class="label"> /wst:TransferResource/wst:Dialect </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
specified Dialect IRI.
+ </p></dd><dt class="label"> /wst:TransferResource/wst:Dialect/xs:any </dt><dd><p>
+ This extensibility point allows for additional Dialect specific
+ metadata to be included within the policy assertion. Any metadata
+ that appears is scoped to the use of the specified Dialect URI.
</p></dd><dt class="label"> /wst:TransferResource/wst:Resource </dt><dd><p>
When present, this OPTIONAL parameter provides the QName referencing
the Global Element Declaration (GED) or type of this resource. This
QName can be used in order to retrieve the schema of the resource.
+ </p></dd><dt class="label"> /wst:TransferResource/xs:any </dt><dd><p>
+ This extensibility point allows for additional WS-Transfer
+ specific metadata to be included within the policy assertion -
+ 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_1438" id="iddiv2_1_1438"/>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
+<h3><a name="iddiv2_1_1458" id="iddiv2_1_1458"/>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
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
</p><p>
@@ -1037,16 +1055,12 @@
The wst:TransferResourceFactory policy assertion applies to the endpoint
policy subject.
</p><p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the
- wst:TransferResourceFactory
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
+ wsdl20:binding.
</p><p>
- The wst:TransferResourceFactory policy assertion is a nested policy
- container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Transfer is REQUIRED to communicate with the
subject and that the subject is a WS-Transfer Resource Factory.
</p><p>
@@ -1060,8 +1074,10 @@
</p><p>
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wst:TransferResourceFactory ...>
- <wst:Dialect ...> <em>xs:anyURI</em> </wst:Dialect> *
- ...
+ <wst:Dialect URI="<em>xs:anyURI</em>" ...>
+ <em>xs:any</em>*
+ </wst:Dialect> *
+ <em>xs:any</em>*
</wst:TransferResourceFactory></pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
@@ -1072,6 +1088,16 @@
</p></dd><dt class="label"> /wst:TransferResourceFactory/wst:Dialect </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
specified Dialect IRI.
+ </p></dd><dt class="label"> /wst:TransferResourceFactory/wst:Dialect/xs:any </dt><dd><p>
+ This extensibility point allows for additional Dialect specific
+ metadata to be included within the policy assertion. Any metadata
+ that appears is scoped to the use of the specified Dialect URI.
+ </p></dd><dt class="label"> /wst:TransferResourceFactory/xs:any </dt><dd><p>
+ This extensibility point allows for additional WS-Transfer
+ specific metadata to be included within the policy assertion -
+ 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">
<h2><a name="acks" id="acks"/>8 Acknowledgements</h2><p>
This specification has been developed as a result of joint
@@ -1104,7 +1130,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_1491" id="iddiv2_1_1491"/>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_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>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1172,7 +1198,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_1664" id="iddiv2_1_1664"/>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_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>
W3C Working Group Draft, "Web Services Fragment (WS-Fragment) 1.0"
</cite></a>
, D. Davis, et al., Editors.
@@ -1334,8 +1360,16 @@
<xs:element name='DeleteOperationSupported' type='tns:Empty'
minOccurs='0'/>
<xs:element name='FaultOnPutDenied' type='tns:Empty' minOccurs='0'/>
- <xs:element name='Dialect' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='Dialect' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:element name='Resource' type='xs:QName' minOccurs='0'/>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
@@ -1347,8 +1381,16 @@
<xs:element name='TransferResourceFactory'>
<xs:complexType>
<xs:sequence>
- <xs:element name='Dialect' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='Dialect' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:any namespace='##other' processContents='lax' minOccurs='0'
maxOccurs='unbounded'/>
</xs:sequence>
@@ -1518,4 +1560,7 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8299">8299</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8298">8298</a></td></tr><tr><td> 2010/02/16 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9032">9032</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=9032">9032</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</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.94
retrieving revision 1.95
diff -u -d -r1.94 -r1.95
--- wsmex.xml 24 Feb 2010 15:04:00 -0000 1.94
+++ wsmex.xml 10 Mar 2010 05:34:59 -0000 1.95
@@ -72,10 +72,11 @@
<p>
This specification defines how metadata
associated with a Web service endpoint can be represented as
- <bibref ref='WS-Transfer'/> resources, how metadata can
+ <bibref ref='WS-Transfer'/> resources or HTTP resources, how metadata can
be embedded in <bibref ref='AddrCore'/>
endpoint references, and how metadata could be
- retrieved from a Web service endpoint.
+ retrieved from a metadata resource, and how metadata associated with
+ implicit features can be advertised.
</p>
[...2377 lines suppressed...]
+
</wsdl:portType>
</wsdl:definitions></eg>
@@ -2640,6 +3490,15 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -d -r1.117 -r1.118
--- wsenum.html 24 Feb 2010 15:04:00 -0000 1.117
+++ wsenum.html 10 Mar 2010 05:34:58 -0000 1.118
@@ -69,11 +69,11 @@
4.11 <a href="#EmptyFilter">EmptyFilter</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_2017">Enumeration Assertion</a><br/>
+ 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_2112">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2298">Informative 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/>
</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/>
@@ -1286,23 +1286,30 @@
</p></li></ul></div><div class="div1">
<h2><a name="metadata" id="metadata"/>6 WS-Enumeration Metadata</h2><p>
An endpoint MAY indicate that it supports WS-Enumeration, or its features,
- by including the WS-Enumeration Policy assertion within its WSDL. By
+ by including the WS-Enumeration DataSource 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.
+ explicitly appear in its WSDL
+ (i.e. the WS-Enumeration operations do not appear in the WSDL that MAY
+ be retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
</p><p>
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.
+ Enumeration Assertion MAY be exposed by including the WSDL as a child
+ of the DataSource Policy assertion or by including a reference to it
+ using the mex:Location or mex:Reference element (as described in
+ WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a> Section 9).
+ </p><p>
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
+ this service's WS-Enumeration operations. 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_2017" id="iddiv2_1_2017"/>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
+<h3><a name="iddiv2_1_2019" id="iddiv2_1_2019"/>6.1 Enumeration Assertion</h3><p>
+ Services indicate support for the WS-Enumeration's definition of a
+ data source through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
Attachment <a href="#wspolicyattach">[WS-Policy Attachment]</a> specifications.
</p><p>
@@ -1311,16 +1318,12 @@
wsenu:DataSource policy assertion applies to the
endpoint policy subject.
</p><p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the
- wsenu:DataSource
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint
+ or wsdl20:binding.
</p><p>
- The wsenu:DataSource policy assertion is a nested policy
- container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Enumeration is REQUIRED to communicate with the
subject and that the subject is a WS-Enumeration data source.
</p><p>
@@ -1334,13 +1337,15 @@
</p><p>
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsenu:DataSource ...>
- <wsenu:FilterDialect ...> <em>xs:anyURI</em> </wsenu:FilterDialect> *
+ <wsenu:FilterDialect URI="<em>xs:anyURI</em>" ...>
+ <em>xs:any</em>*
+ </wsenu:FilterDialect> *
<wsenu:MaxExpires ...> <em>xs:duration</em> </wsenu:MaxExpires> ?
<wsenu:MaxTime ...> <em>xs:duration</em> </wsenu:MaxTime> ?
<wsenu:MaxElements ...> <em>xs:long</em> </wsenu:MaxElements> ?
<wsenu:MaxCharacters ...> <em>xs:long</em> </wsenu:MaxCharacters> ?
<wsenu:EndToSupported .../> ?
- ...
+ <em>xs:any</em>*
</wsenu:DataSource></pre></div></div><p>
The following describes additional, normative constraints on the
outline listed above:
@@ -1351,6 +1356,11 @@
</p></dd><dt class="label"> /wsenu:DataSource/wsenu:FilterDialect </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
specified Filter Dialect IRI.
+ </p></dd><dt class="label"> /wsenu:DataSource/wsenu:FilterDialect/xs:any </dt><dd><p>
+ This extensibility point allows for additional FilterDialect
+ specific metadata to be included within the policy assertion. Any
+ metadata that appears is scoped to the use of the specified
+ FilterDialect URI.
</p></dd><dt class="label"> /wsenu:DataSource/wsenu:MaxExpires </dt><dd><p>
When present, this OPTIONAL parameter indicates the maximum lifetime
of enumerations that this endpoint will support.
@@ -1377,6 +1387,13 @@
request contains a wsen:EndTo element, a EnumerationEnd message
will be sent to the EPR contained in the wsen:EndTo element, if
the enumeration terminates unexpectedly.
+ </p></dd><dt class="label"> /wsenu:DataSource/xs:any </dt><dd><p>
+ This extensibility point allows for additional WS-Enumeration
+ specific metadata to be included within the policy assertion -
+ e.g. WS-Enumeration WSDL, or nested policy assertions related to
+ 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">
<h2><a name="acks" id="acks"/>7 Acknowledgements</h2><p>
This specification has been developed as a
@@ -1410,7 +1427,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_2112" id="iddiv2_1_2112"/>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_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>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1482,7 +1499,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_2298" id="iddiv2_1_2298"/>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_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>
W3C Working Group Draft, "Web Services Metadata Exchange
(WS-MetadataExchange) 1.1"
</cite></a>
@@ -1807,8 +1824,16 @@
<xs:element name='DataSource'>
<xs:complexType>
<xs:sequence>
- <xs:element name='FilterDialect' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='FilterDialect' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:element name='MaxExpires' type='tns:Duration' minOccurs='0'/>
<xs:element name='MaxTime' type='tns:Duration' minOccurs='0'/>
<xs:element name='MaxElements' type='tns:Long' minOccurs='0'/>
@@ -2087,4 +2112,7 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8304">8304</a></td></tr><tr><td> 2010/02/23 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8306">8306</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=8306">8306</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</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.109
retrieving revision 1.110
diff -u -d -r1.109 -r1.110
--- wsenum.xml 24 Feb 2010 15:04:00 -0000 1.109
+++ wsenum.xml 10 Mar 2010 05:34:59 -0000 1.110
@@ -2403,19 +2403,28 @@
<p>
An endpoint MAY indicate that it supports WS-Enumeration, or its features,
- by including the WS-Enumeration Policy assertion within its WSDL. By
+ by including the WS-Enumeration DataSource 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.
+ explicitly appear in its WSDL
+ (i.e. the WS-Enumeration operations do not appear in the WSDL that MAY
+ be retrievable by using a WS-MetadataExchange GetWSDL to that endpoint).
</p>
<p>
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.
+ Enumeration Assertion MAY be exposed by including the WSDL as a child
+ of the DataSource Policy assertion or by including a reference to it
+ using the mex:Location or mex:Reference element (as described in
+ WS-MetadataExchange <bibref ref="MEX"/> Section 9).
+ </p>
+
+ <p>
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
+ this service's WS-Enumeration operations. 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>
@@ -2424,8 +2433,8 @@
<head>Enumeration Assertion</head>
<p>
- The mechanism for indicating that a binding or endpoint conforms to the
- WS-Enumeration specification is through the use of the Web Services
+ Services indicate support for the WS-Enumeration's definition of a
+ data source through the use of the Web Services
Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
Attachment <bibref ref="wspolicyattach"/> specifications.
</p>
@@ -2438,18 +2447,14 @@
</p>
<p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the
- wsenu:DataSource
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl11:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint
+ or wsdl20:binding.
</p>
<p>
- The wsenu:DataSource policy assertion is a nested policy
- container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Enumeration is REQUIRED to communicate with the
subject and that the subject is a WS-Enumeration data source.
</p>
@@ -2470,13 +2475,15 @@
<example>
<eg><wsenu:DataSource ...>
- <wsenu:FilterDialect ...> <emph>xs:anyURI</emph> </wsenu:FilterDialect> *
+ <wsenu:FilterDialect URI="<emph>xs:anyURI</emph>" ...>
+ <emph>xs:any</emph>*
+ </wsenu:FilterDialect> *
<wsenu:MaxExpires ...> <emph>xs:duration</emph> </wsenu:MaxExpires> ?
<wsenu:MaxTime ...> <emph>xs:duration</emph> </wsenu:MaxTime> ?
<wsenu:MaxElements ...> <emph>xs:long</emph> </wsenu:MaxElements> ?
<wsenu:MaxCharacters ...> <emph>xs:long</emph> </wsenu:MaxCharacters> ?
<wsenu:EndToSupported .../> ?
- ...
+ <emph>xs:any</emph>*
</wsenu:DataSource></eg>
</example>
@@ -2509,6 +2516,18 @@
</gitem>
<gitem>
+ <label> /wsenu:DataSource/wsenu:FilterDialect/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional FilterDialect
+ specific metadata to be included within the policy assertion. Any
+ metadata that appears is scoped to the use of the specified
+ FilterDialect URI.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
<label> /wsenu:DataSource/wsenu:MaxExpires </label>
<def>
<p>
@@ -2569,6 +2588,20 @@
</def>
</gitem>
+ <gitem>
+ <label> /wsenu:DataSource/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional WS-Enumeration
+ specific metadata to be included within the policy assertion -
+ e.g. WS-Enumeration WSDL, or nested policy assertions related to
+ the WS-Enumeration message exchanges. Any metadata that appears
+ is scoped to the operations and features of the WS-Enumeration
+ specification.
+ </p>
+ </def>
+ </gitem>
+
</glist>
</div2>
@@ -3108,11 +3141,24 @@
</xs:simpleContent>
</xs:complexType>
+ <xs:complexType name='Empty'>
+ <xs:sequence/>
+ <xs:anyAttribute namespace='##other' processContents='lax'/>
+ </xs:complexType>
+
<xs:element name='DataSource'>
<xs:complexType>
<xs:sequence>
- <xs:element name='FilterDialect' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='FilterDialect' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:element name='MaxExpires' type='tns:Duration' minOccurs='0'/>
<xs:element name='MaxTime' type='tns:Duration' minOccurs='0'/>
<xs:element name='MaxElements' type='tns:Long' minOccurs='0'/>
@@ -3935,6 +3981,15 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8306">8306</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -d -r1.106 -r1.107
--- wsmex.html 24 Feb 2010 15:04:00 -0000 1.106
+++ wsmex.html 10 Mar 2010 05:34:59 -0000 1.107
@@ -35,39 +35,45 @@
<h2><a name="abstract" id="abstract"/>Abstract</h2><p>
This specification defines how metadata
associated with a Web service endpoint can be represented as
- <a href="#WS-Transfer">[WS-Transfer]</a> resources, how metadata can
+ <a href="#WS-Transfer">[WS-Transfer]</a> resources or HTTP resources, how metadata can
be embedded in <a href="#AddrCore">[WS-Addressing]</a>
endpoint references, and how metadata could be
- retrieved from a Web service endpoint.
+ retrieved from a metadata resource, and how metadata associated with
+ implicit features can be advertised.
</p></div><div>
[...1819 lines suppressed...]
message='tns:GetMetadataMsg'
@@ -1369,6 +1918,7 @@
wsam:Action=
'http://www.w3.org/2002/ws/ra/edcopies/ws-mex/GetMetadataResponse'/>
</wsdl:operation>
+
</wsdl:portType>
</wsdl:definitions></pre></div></div></div><div class="div1">
@@ -1430,4 +1980,7 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8290">8290</a></td></tr><tr><td> 2010/01/27 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8205">8205</a></td></tr><tr><td> 2010/01/28 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7728">7728</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</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=8160">8160</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Index: wsevd.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- wsevd.html 24 Feb 2010 15:04:00 -0000 1.5
+++ wsevd.html 10 Mar 2010 05:34:59 -0000 1.6
@@ -50,11 +50,11 @@
4 <a href="#Advertising">Advertising Event Information</a><br/>
4.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
4.1.1 <a href="#iddiv3_1_534">Retrieving Event Descriptions</a><br/>
- 4.1.2 <a href="#iddiv3_1_555">Bindings for Event Descriptions</a><br/>
+ 4.1.2 <a href="#iddiv3_1_572">Bindings for Event Descriptions</a><br/>
5 <a href="#acks">Acknowledgements</a><br/>
6 <a href="#refs">References</a><br/>
- 6.1 <a href="#iddiv2_1_570">Normative References</a><br/>
- 6.2 <a href="#iddiv2_1_600">Informative References</a><br/>
+ 6.1 <a href="#iddiv2_1_587">Normative References</a><br/>
+ 6.2 <a href="#iddiv2_1_617">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#EVDXSD">XML Schema for EventDescriptions</a><br/>
B <a href="#changelog">Change Log</a><br/>
@@ -325,14 +325,38 @@
<h4><a name="iddiv3_1_534" id="iddiv3_1_534"/>4.1.1 Retrieving Event Descriptions</h4><p>
Although there are many ways in which an endpoint can make its
EventDescriptions available, this specification RECOMMENDS the use of
- the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
- This specification defines the following IRI to serve as the Dialect
- IRI for the wsevd:EventDescriptions element.
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-evd/EventDescriptions">http://www.w3.org/2002/ws/ra/edcopies/ws-evd/EventDescriptions</a></pre></div></div><p>
- The value of the @Identifier attribute for this Metadata Section MUST
- be equal to the value of its wsevd:EventDescriptions/@targetNamespace.
+ the mechanisms described in section 9 of WS-MetadataExchange
+ <a href="#MEX">[WS-MetadataExchange]</a>.
+ In particular, this specification RECOMMENDS that the Event Description
+ metadata be made available through the WS-Eventing
+ <a href="#Eventing">[WS-Eventing]</a> EventSource Policy assertion. This MAY be done
+ by either embedding the Event Description metadata directly within
+ the assertion, or by including a MetadataExchange reference to the data.
+ </p><p>
+ The following examples show how Event Description metadata might
+ appear within a WS-Eventing EventSource Policy assertion.
+ </p><div class="exampleOuter">
+<div class="exampleHeader"><a name="embedEVD" id="embedEVD"/>Example 4-3: Sample Embedded EventDescription Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
+(02) <wse:FormatName URI="..."/>
+(03) <wsevd:EventDescritions ...>
+(04) ...
+(05) </wsevd:EventDescriptions>
+(06) </wse:EventSource></pre></div></div><p><a href="#embedEVD">Example 4-3</a> shows how the Event Description metadata
+ might be embedded directly within a WS-Eventing EventSource Policy
+ assertion.
+ </p><div class="exampleOuter">
+<div class="exampleHeader"><a name="refEVD" id="refEVD"/>Example 4-4: Sample Reference to EventDescription Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
+(02) <wse:FormatName URI="..."/>
+(03) <mex:Location
+(04) Type="evd:EventDescriptions"
+(05) URI="http://example.com/EVD_Metadata" />
+(06) </wse:EventSource> </pre></div></div><p><a href="#refEVD">Example 4-4</a> shows the same policy assertion from
+ <a href="#embedEVD">Example 4-3</a> except the embedded Event Description
+ metadata is replaced with a reference to an HTTP resource whose
+ representation is the Event Description metadata. The data can be
+ retrieved via an HTTP GET to the specified URL.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_555" id="iddiv3_1_555"/>4.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_572" id="iddiv3_1_572"/>4.1.2 Bindings for Event Descriptions</h4><p>
Any specification of a publish-subscribe system that uses
Event Descriptions to advertise the events that are generated
MUST clearly define how those events are serialized when they
@@ -369,7 +393,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>6 References</h2><div class="div2">
-<h3><a name="iddiv2_1_570" id="iddiv2_1_570"/>6.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_587" id="iddiv2_1_587"/>6.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.
@@ -380,7 +404,7 @@
, M. Duerst and M. Suignard, Authors.
Internet Engineering Task Force, January 2005.
Available at <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_600" id="iddiv2_1_600"/>6.2 Informative References</h3><dl><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
+<h3><a name="iddiv2_1_617" id="iddiv2_1_617"/>6.2 Informative References</h3><dl><dt class="label"><a name="SOAP11" id="SOAP11"/>SOAP11</dt><dd><a href="http://www.w3.org/TR/2000/NOTE-SOAP-20000508/"><cite>
W3C Note, "Simple Object Access Protocol (SOAP) 1.1"
</cite></a>
, D. Box, et al, Editors.
@@ -396,7 +420,13 @@
</cite></a>
, M. Gudgin, M. Hadley, T. Rogers, Editors.
World Wide Web Consortium (W3C), 9 May 2006.
- Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</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>
+ Available at <a href="http://www.w3.org/TR/ws-addr-core">http://www.w3.org/TR/ws-addr-core</a>.</dd><dt class="label"><a name="Eventing" id="Eventing"/>WS-Eventing</dt><dd><a href="http://www.w3.org/TR/ws-eventing"><cite>
+ W3C Working Group Draft, "Web Services Eventing
+ (WS-Eventing) 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-eventing">http://www.w3.org/TR/ws-eventing</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>
@@ -466,4 +496,7 @@
</xs:element>
</xs:schema></pre></div></div></div><div class="div1">
<h2><a name="changelog" id="changelog"/>B Change Log</h2><table border="1"><tbody><tr><th> Data </th><th> Author </th><th> Description </th></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</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=8068">8068</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</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.157
retrieving revision 1.158
diff -u -d -r1.157 -r1.158
--- wseventing.xml 24 Feb 2010 15:04:00 -0000 1.157
+++ wseventing.xml 10 Mar 2010 05:34:59 -0000 1.158
@@ -2662,19 +2662,29 @@
<p>
An endpoint MAY indicate that it supports WS-Eventing, or its features,
- by including the WS-Eventing Policy assertion within its WSDL. By
+ by including the WS-Eventing EventSource or SubscriptionManager Policy
+ assertions 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.
+ explicitly appear in its WSDL (ie. the WS-Eventing operations do not
+ appear in the WSDL that MAY be retrievable by using WS-MetadataExchange
+ GetWSDL to that endpoint).
</p>
<p>
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.
+ EventSource or SubscriptionManager assertions MAY be exposed
+ by including the WSDL as a child of the appropriate Policy
+ assertion or by including a reference to it using the mex:Location
+ or mex:Reference element ( as described in
+ WS-MetadataExchange <bibref ref="MEX"/> Section 9).
+ </p>
+
+ <p>
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
+ this service's WS-Eventing operations. 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>
@@ -2683,9 +2693,8 @@
<head>EventSource Assertion</head>
<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
+ Services indicate support for the WS-Eventing's definition
+ of an event source through the use of the Web Services
Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
Attachment <bibref ref="wspolicyattach"/> specifications.
</p>
@@ -2696,16 +2705,14 @@
</p>
<p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the wse:EventSource
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl:portType,
+ wsdl11:port or
+ wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:interface,
+ wsdl20:endpoint or wsdl20:binding.
</p>
<p>
- The wse:EventSource policy assertion is a nested policy container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Eventing is REQUIRED to communicate with the
subject and that the subject is a WS-Eventing event source.
</p>
@@ -2727,14 +2734,18 @@
<example>
<eg><wse:EventSource ...>
<wse:DateTimeSupported .../> ?
- <wse:FilterDialect ...> <emph>xs:anyURI</emph> </wse:FilterDialect> *
+ <wse:FilterDialect URI="<emph>xs:anyURI</emph>" ...>
+ <emph>xs:any</emph>*
+ </wse:FilterDialect> *
<wse:MaxExpires ...> <emph>xs:duration</emph> </wse:MaxExpires> ?
- <wse:FormatName ...> <emph>xs:anyURI</emph> </wse:FormatName> *
+ <wse:FormatName URI="<emph>xs:anyURI</emph>" ...>
+ <emph>xs:any</emph>*
+ </wse:FormatName> *
<wse:EndToSupported .../> ?
<wse:NotificationPolicy ...>
<emph>xs:any</emph>
</wse:NotificationPolicy> ?
- ...
+ <emph>xs:any</emph>*
</wse:EventSource></eg>
</example>
@@ -2777,6 +2788,18 @@
</gitem>
<gitem>
+ <label> /wse:EventSource/wse:FilterDialect/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional FilterDialect
+ specific metadata to be included within the policy assertion. Any
+ metadata that appears is scoped to the use of the specified
+ FilterDialect URI.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
<label> /wse:EventSource/wse:MaxExpires </label>
<def>
<p>
@@ -2800,6 +2823,17 @@
</gitem>
<gitem>
+ <label> /wse:EventSource/wse:FormatName/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional FormatName specific
+ metadata to be included within the policy assertion. Any metadata
+ that appears is scoped to the use of the specified FormatName URI.
+ </p>
+ </def>
+ </gitem>
+
+ <gitem>
<label> /wse:EventSource/wse:EndToSupported </label>
<def>
<p>
@@ -2830,6 +2864,20 @@
</p>
</def>
</gitem>
+
+ <gitem>
+ <label> /wse:EventSource/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional WS-Eventing
+ specific metadata to be included within the policy assertion -
+ 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>
+ </def>
+ </gitem>
</glist>
</div2>
@@ -2838,9 +2886,9 @@
<head>SubscriptionManager Assertion</head>
<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
+ Services indicate support for the
+ WS-Eventing's definition of a subscription manager
+ through the use of the Web Services
Policy - Framework <bibref ref="wspolicy"/> and Web Services Policy -
Attachment <bibref ref="wspolicyattach"/> specifications.
</p>
@@ -2852,17 +2900,14 @@
</p>
<p>
- For WSDL 1.1, these assertions MAY be attached to wsdl11:port or
- wsdl11:binding. For WSDL 2.0, they MAY be attached to wsdl20:endpoint or
- wsdl20:binding. A policy expression containing the
- wse:SubscriptionManager
- policy assertion MUST NOT be attached to a wsdl:portType or
- wsdl20:interface.
+ For WSDL 1.1, these assertions MAY be attached to wsdl:portType,
+ wsdl11:port or wsdl11:binding.
+ For WSDL 2.0, they MAY be attached to wsdl20:interface, wsdl20:endpoint or
+ wsdl20:binding.
</p>
<p>
- The wse:SubscriptionManager policy assertion is a nested policy container
- assertion. The meaning of this assertion, when present in a policy
+ The meaning of this assertion, when present in a policy
alternative, is that WS-Eventing is REQUIRED to communicate with the
subject and that the subject is a WS-Eventing subscription manager.
</p>
@@ -2887,7 +2932,7 @@
<wse:GetStatusOperationSupported .../> ?
<wse:UnsubscribeOperationSupported .../> ?
<wse:MaxExpires ...> <emph>xs:duration</emph> </wse:MaxExpires> ?
- ...
+ <emph>xs:any</emph>*
</wse:SubscriptionManager></eg>
</example>
@@ -2952,6 +2997,19 @@
</def>
</gitem>
+ <gitem>
+ <label> /wse:SubscriptionManager/xs:any </label>
+ <def>
+ <p>
+ This extensibility point allows for additional WS-Eventing
+ specific metadata to be included within the policy assertion -
+ 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>
+ </def>
+ </gitem>
+
</glist>
</div2>
@@ -3797,11 +3855,27 @@
<xs:complexType>
<xs:sequence>
<xs:element name='DateTimeSupported' type='tns:Empty' minOccurs='0'/>
- <xs:element name='FilterDialect' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='FilterDialect' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:element name='MaxExpires' type='tns:Duration' minOccurs='0'/>
- <xs:element name='FormatName' type='tns:URI' minOccurs='0'
- maxOccurs='unbounded'/>
+ <xs:element name='FormatName' minOccurs='0' maxOccurs='unbounded'>
+ <xs:complexType>
+ <xs:sequence>
+ <xs:any namespace='##other' processContents='lax' minOccurs='0'
+ maxOccurs='0'/>
+ </xs:sequence>
+ <xs:attribute name='URI' type='xs:anyURI' use='required' />
+ <xs:anyAttribute namespace="##other" processContents='lax'/>
+ </xs:complexType>
+ </xs:element>
<xs:element name='EndToSupported' type='tns:Empty' minOccurs='0'/>
<xs:element name='NotificationPolicy' type='tns:NotificationPolicy'
minOccurs='0'/>
@@ -3898,9 +3972,9 @@
<wsdl:part name='body' element='wse:SubscriptionEnd' />
</wsdl:message>
- <message name='notifyEvent'>
- <part name='parameter' element='tns:Notify'/>
- </message>
+ <wsdl:message name='notifyEvent'>
+ <wsdl:part name='parameter' element='wse:Notify'/>
+ </wsdl:message>
<wsdl:portType name='EventSource' >
<wsdl:operation name='SubscribeOp' >
@@ -3948,12 +4022,12 @@
</wsdl:operation>
</wsdl:portType>
- <portType name='WrappedSinkPortType'>
- <operation name='NotifyEvent'>
- <input message='tns:notifyEvent' name='NotifyEvent'
+ <wsdl:portType name='WrappedSinkPortType'>
+ <wsdl:operation name='NotifyEvent'>
+ <wsdl:input message='wse:notifyEvent' name='NotifyEvent'
wsam:Action='http://www.w3.org/&wsevt.nsprefix;/ws-evt/WrappedSinkPortType/NotifyEvent'/>
- </operation>
- </portType>
+ </wsdl:operation>
+ </wsdl:portType>
</wsdl:definitions></eg>
</example>
</div1>
@@ -4907,6 +4981,15 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8271">8271</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6364">6364</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</loc>,
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Wednesday, 10 March 2010 05:35:06 UTC