- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 30 Mar 2010 22:20:59 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv13256
Modified Files:
wsevd.html wsevd.xml wseventing.html wseventing.xml wsmex.html
wsmex.xml
Log Message:
9031
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.172
retrieving revision 1.173
diff -u -d -r1.172 -r1.173
--- wseventing.html 30 Mar 2010 20:46:36 -0000 1.172
+++ wseventing.html 30 Mar 2010 22:20:57 -0000 1.173
@@ -86,12 +86,11 @@
<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_2705">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2726">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2731">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2749">Binding for Wrapped Notifications</a><br/>
+ A.1.2 <a href="#iddiv3_1_2742">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2747">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2765">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2776">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2797">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2792">Retrieving Notification WSDLs</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/>
@@ -1881,7 +1880,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_2695" id="idexample_1_2695"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2695" id="idexample_1_2695"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd: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">
@@ -1895,7 +1894,7 @@
(12) <wse:eventType name="WindReportEvent"
(13) element="ow:WindReport"
(14) actionURI="http://www.example.org/oceanwatch/2003/WindReport"/>
-(15) </wse:EventDescriptions></pre></div></div><p>
+(15) </wsevd:EventDescriptions></pre></div></div><p>
Lines (12-14) describe an Event Type with a QName of
"{http://www.example.org/oceanwatch/notifications}:WindReportEvent". The
GED for this Event Type is defined on line (08) as being of type
@@ -1905,14 +1904,41 @@
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>.
- This specification defines the following IRI to serve as the Dialect
- IRI for the wse: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 wse:EventDescriptions/@targetNamespace. An
+ In particular, this specification RECOMMENDS that the Event Description
+ metadata be made available through the 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 value of the @Identifier attribute, if present, for this
+ MetadataSection MUST
+ be equal to the value of its wsevd:EventDescriptions/@targetNamespace. An
event source MUST NOT have more than one EventDescriptions document.
+ </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 A-2: 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 A-2</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 A-3: 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 A-3</a> shows the same policy assertion from
+ <a href="#embedEVD">Example A-2</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_2726" id="iddiv3_1_2726"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2742" id="iddiv3_1_2742"/>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
@@ -1924,7 +1950,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_2731" id="iddiv4_1_2731"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2747" id="iddiv4_1_2747"/>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>
@@ -1938,7 +1964,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_2749" id="iddiv4_1_2749"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2765" id="iddiv4_1_2765"/>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>
@@ -1962,7 +1988,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_2770" id="idexample_1_2770"/>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_2786" id="idexample_1_2786"/>Example A-4: 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/"
@@ -1997,35 +2023,13 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2776" id="iddiv3_1_2776"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2792" id="iddiv3_1_2792"/>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>.
- This specification defines the following IRI to serve as the Dialect
- IRI for the Notification WSDL.
- </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-evt/NotificationWSDL">http://www.w3.org/2002/ws/ra/edcopies/ws-evt/NotificationWSDL</a></pre></div></div><p>
- Because the Notification Format specified in a Subscribe request can
- affect various aspects of the Notification WSDL, it is necessary to
- correlate Notification WSDLs with their corresponding Notification
- Formats. When using WS-MetadataExchange to transfer Notification WSDLs,
- the corresponding Format IRI for that Notification WSDL MUST be
- represented via the @Identifier attribute. For any particular
- Format IRI/@Identifier, there MUST NOT exist more than one
- Notification WSDL document.
- </p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2797" id="iddiv2_1_2797"/>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
- "http://www.w3.org/2002/ws/ra/edcopies/ws-evd/EventDescriptions" and
- "http://www.w3.org/2002/ws/ra/edcopies/ws-evt/NotificationWSDL" dialects MUST
- regard these Metadata Sections as relating to the same set of events.
- In cases where the mex:Metadata element contains multiple
- Notification WSDLs (i.e. multiple Metadata Sections with a @Dialect
- of "http://www.w3.org/2002/ws/ra/edcopies/ws-evt/NotificationWSDL"), recipients MUST
- similarly regard these Notification WSDLs as relating to the same set
- of events although their Notification Formats differ.
- </p></div></div><div class="div1">
+ In particular, if an event source has Notification WSDL then it
+ SHOULD be referenced from the wse:EventSource policy assertion.
+ </p></div></div></div><div class="div1">
<h2><a name="Schema" id="Schema"/>B XML Schema</h2><p>
A normative copy of the XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> description for this specification can be
@@ -2707,4 +2711,5 @@
<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><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9320">9320</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=9320">9320</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</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.7
retrieving revision 1.8
diff -u -d -r1.7 -r1.8
--- wsevd.xml 17 Mar 2010 03:25:47 -0000 1.7
+++ wsevd.xml 30 Mar 2010 22:20:57 -0000 1.8
@@ -325,6 +325,15 @@
XML Schema <bibref ref="XMLSchema1"/>, <bibref ref="XMLSchema2"/>
</td>
</tr>
+ <tr>
+ <td>wse</td>
+ <td>
+ <loc href="http://www.w3.org/&wsevt.nsprefix;/ws-evt">
+ http://www.w3.org/&wsevt.nsprefix;/ws-evt
+ </loc>
+ </td>
+ <td>WS-Eventing <bibref ref="Eventing"/></td>
+ </tr>
</tbody>
</table>
@@ -629,6 +638,13 @@
</p>
<p>
+ The value of the @Identifier attribute, if present, for this
+ MetadataSection MUST be equal to the value of its
+ wsevd:EventDescriptions/@targetNamespace. An event source MUST NOT have
+ more than one EventDescriptions document.
+ </p>
+
+ <p>
The following examples show how Event Description metadata might
appear within a WS-Eventing EventSource Policy assertion.
</p>
@@ -923,6 +939,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8900">8900</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/30 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -d -r1.99 -r1.100
--- wsmex.xml 19 Mar 2010 18:51:19 -0000 1.99
+++ wsmex.xml 30 Mar 2010 22:20:57 -0000 1.100
@@ -309,48 +309,49 @@
<eg>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
-(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
-(04) xmlns:mex='http://www.w3.org/&wsmex.nsprefix;/ws-mex'
-(05) xmlns:wsp='http://www.w3.org/ns/ws-policy'
-(06) xmlns:wst='http://www.w3.org/&wsmex.nsprefix;/ws-tra'
-(07) xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'>
-(08) <s11:Header>
-(09) <wsa:Action>
-(10) http://www.w3.org/&wsmex.nsprefix;/ws-tra/GetResponse
-(11) </wsa:Action>
-(12) <wsa:To>http://client.example.org</wsa:To>
-(13) <wsa:RelatesTo>
-(14) urn:uuid:1cec121a-82fe-41da-87e1-3b23f254f128
-(15) </wsa:RelatesTo>
-(16) </s11:Header>
-(17) <s11:Body>
-(18) <wst:GetResponse>
-(19) <mex:Metadata>
-(20) <mex:MetadataSection Dialect='http://schemas.xmlsoap.org/wsdl/'>
-(21) <wsdl:definitions>
-(22) <!-- WSDL data removed for brevity -->
-(23) </wsdl:definitions>
-(24) </mex:MetadataSection>
-(25) <mex:MetadataSection
-(26) Dialect='http://www.w3.org/2001/XMLSchema'
-(27) Identifier='http://services.example.org/stockquote/schemas'>
-(28) <mex:MetadataLocation>
-(29) http://services.example.org/stockquote/schemas
-(30) </mex:MetadataLocation>
-(31) </mex:MetadataSection>
-(32) <mex:MetadataSection
-(33) Dialect='http://www.w3.org/ns/ws-policy'
-(34) Identifier='http://services.example.org/stockquote/policy'>
-(35) <mex:MetadataReference>
-(36) <wsa:Address>
-(37) http://services.example.org/stockquote/policy
-(38) </wsa:Address>
-(39) </mex:MetadataReference>
-(40) </mex:MetadataSection>
-(41) </mex:Metadata>
-(42) </wst:GetResponse>
-(43) </s11:Body>
-(44) </s11:Envelope></eg>
+(03) xmlns:xs='http://www.w3.org/2001/XMLSchema'
+(04) xmlns:wsa='http://www.w3.org/2005/08/addressing'
+(05) xmlns:mex='http://www.w3.org/&wsmex.nsprefix;/ws-mex'
+(06) xmlns:wsp='http://www.w3.org/ns/ws-policy'
+(07) xmlns:wst='http://www.w3.org/&wsmex.nsprefix;/ws-tra'
+(08) xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'>
+(09) <s11:Header>
+(10) <wsa:Action>
+(11) http://www.w3.org/&wsmex.nsprefix;/ws-tra/GetResponse
+(12) </wsa:Action>
+(13) <wsa:To>http://client.example.org</wsa:To>
+(14) <wsa:RelatesTo>
+(15) urn:uuid:1cec121a-82fe-41da-87e1-3b23f254f128
+(16) </wsa:RelatesTo>
+(17) </s11:Header>
+(18) <s11:Body>
+(19) <wst:GetResponse>
+(20) <mex:Metadata>
+(21) <mex:MetadataSection Dialect='wsdl:definitions'>
+(22) <wsdl:definitions>
+(23) <!-- WSDL data removed for brevity -->
+(24) </wsdl:definitions>
+(25) </mex:MetadataSection>
+(26) <mex:MetadataSection
+(27) Dialect='xs:schema'
+(28) Identifier='http://services.example.org/stockquote/schemas'>
+(29) <mex:MetadataLocation>
+(30) http://services.example.org/stockquote/schemas
+(31) </mex:MetadataLocation>
+(32) </mex:MetadataSection>
+(33) <mex:MetadataSection
+(34) Dialect='wsp:Policy'
+(35) Identifier='http://services.example.org/stockquote/policy'>
+(36) <mex:MetadataReference>
+(37) <wsa:Address>
+(38) http://services.example.org/stockquote/policy
+(39) </wsa:Address>
+(40) </mex:MetadataReference>
+(41) </mex:MetadataSection>
+(42) </mex:Metadata>
+(43) </wst:GetResponse>
+(44) </s11:Body>
+(45) </s11:Envelope></eg>
</example>
<p>
@@ -358,26 +359,26 @@
<bibref ref='WS-Transfer'/>
response message to the request of <specref ref="GetRequest"/>. The
content
- of the <kw>[Body]</kw> (lines 17-43) is a mex:Metadata element with
+ of the <kw>[Body]</kw> (lines 18-44) is a mex:Metadata element with
metadata
- about the Web service endpoint (lines 19-41). The mex:Metadata
+ about the Web service endpoint (lines 20-42). The mex:Metadata
contains three MetadataSections. The first MetadataSection
- (lines 20-24) contains the <bibref ref='WSDL11'/> of the Web
- service endpoint. The second MetadataSection (lines 25-31) contains
+ (lines 21-25) contains the <bibref ref='WSDL11'/> of the Web
+ service endpoint. The second MetadataSection (lines 26-32) contains
the location of the XML Schemas <bibref ref='XMLSchema1'/>,
<bibref ref='XMLSchema2'/> used by the WSDL document. The schemas can
be retrieved through an HTTP GET request at the identified URL
- (lines 28-30). The third MetadataSection (lines 32-40) contains
- the <bibref ref='AddrCore'/> endpoint reference (lines 35-39) of
+ (lines 29-31). The third MetadataSection (lines 33-41) contains
+ the <bibref ref='AddrCore'/> endpoint reference (lines 36-40) of
a <bibref ref='WS-Transfer'/> resource the representation of
which is a <bibref ref='wspolicy'/> document as indicated by
- the Dialect attribute (line 33).
+ the Dialect attribute (line 34).
</p>
<p>
While the WS-Policy of the Web service endpoint could be retrieved using
a WS-Transfer Get request directed to the endpoint identified by the
- mex:MetadataReference element in lines 35-39 of
+ mex:MetadataReference element in lines 36-40 of
<specref ref="GetResponse"/>,
some endpoints MAY support explicit requests for metadata via the
GetMetadata operation.
@@ -391,32 +392,33 @@
<eg>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
-(04) xmlns:mex='http://www.w3.org/&wsmex.nsprefix;/ws-mex' >
-(05) <s11:Header>
-(06) <wsa:To>http://services.example.org/stockquote</wsa:To>
-(07) <wsa:Action>
-(08) http://www.w3.org/&wsmex.nsprefix;/ws-mex/GetMetadata
-(09) </wsa:Action>
-(10) <wsa:MessageID>
-(11) urn:uuid:73d7edfc-5c3c-49b9-ba46-2480caee43e9
-(12) </wsa:MessageID>
-(13) <wsa:ReplyTo>
-(14) <wsa:Address>http://client.example.org</wsa:Address>
-(15) </wsa:ReplyTo>
-(16) </s11:Header>
-(17) <s11:Body>
-(18) <mex:GetMetadata>
-(19) <mex:Dialect URI='http://www.w3.org/ns/ws-policy'
-(20) Identifier='http://services.example.org/stockquote/policy'/>
-(21) </mex:GetMetadata>
-(22) </s11:Body>
-(23) </s11:Envelope></eg>
+(04) xmlns:wsp='http://www.w3.org/ns/ws-policy'
+(05) xmlns:mex='http://www.w3.org/&wsmex.nsprefix;/ws-mex' >
+(06) <s11:Header>
+(07) <wsa:To>http://services.example.org/stockquote</wsa:To>
+(08) <wsa:Action>
+(09) http://www.w3.org/&wsmex.nsprefix;/ws-mex/GetMetadata
+(10) </wsa:Action>
+(11) <wsa:MessageID>
+(12) urn:uuid:73d7edfc-5c3c-49b9-ba46-2480caee43e9
+(13) </wsa:MessageID>
+(14) <wsa:ReplyTo>
+(15) <wsa:Address>http://client.example.org</wsa:Address>
+(16) </wsa:ReplyTo>
+(17) </s11:Header>
+(18) <s11:Body>
+(19) <mex:GetMetadata>
+(20) <mex:Dialect Type='wsp:Policy'
+(21) Identifier='http://services.example.org/stockquote/policy'/>
+(22) </mex:GetMetadata>
+(23) </s11:Body>
+(24) </s11:Envelope></eg>
</example>
<p>
- Lines 7-9 in <specref ref="GetMexReq"/> indicate this is a GetMetadata
- request. As lines 18-21 indicate, this request is for the policy of
- the Web service endpoint (line 6).
+ Lines 8-10 in <specref ref="GetMexReq"/> indicate this is a GetMetadata
+ request. As lines 19-22 indicate, this request is for the policy of
+ the Web service endpoint (line 7).
</p>
<p>
@@ -445,7 +447,7 @@
(16) <mex:GetMetadataResponse>
(17) <mex:Metadata>
(18) <mex:MetadataSection
-(19) Dialect='http://www.w3.org/ns/ws-policy'
+(19) Dialect='wsp:Policy'
(20) Identifier='http://services.example.org/stockquote/policy'>
(21) <wsp:Policy>
(22) <wsp:ExactlyOne>
@@ -834,7 +836,7 @@
<example>
<eg><mex:Metadata ...>
- <mex:MetadataSection Dialect='<emph>xs:anyURI</emph>'
+ <mex:MetadataSection Dialect='<emph>xs:QName</emph>'
Identifier='<emph>xs:anyURI</emph>'? ...>
(
<mex:MetadataReference ...>
@@ -886,59 +888,23 @@
<label>/mex:Metadata/mex:MetadataSection/@Dialect</label>
<def>
<p>
- This indicates the format and version of the metadata unit
- contained in this MetadataSection (e.g., WSDL version 1.1). Dialect
- is an absolute IRI.
+ This indicates the type and version of the metadata unit
+ contained in this MetadataSection (e.g., WSDL version 1.1).
+ This MUST be the QName of the root element of the metadata.
+ </p>
+
+ <p>
+ If there is more than one metadata unit with the same Dialect, e.g.,
+ more than one XML Schema document, including them all, one per
+ MetadataSection, is explicitly encouraged.
</p>
+
</def>
</gitem>
- </glist>
-
- <p>
- This specification defines the following values for Dialect;
- other specifications SHOULD define values for Dialect for their
- metadata format(s).
- </p>
-
- <table border='1'>
- <tbody>
- <tr>
- <th align="left"> Dialect IRI </th>
- <th align="left"> Metadata Format </th>
- </tr>
- <tr>
- <td> http://www.w3.org/2001/XMLSchema </td>
- <td> xs:schema <bibref ref="XMLSchema1"/> </td>
- </tr>
- <tr>
- <td> http://schemas.xmlsoap.org/wsdl/ </td>
- <td> wsdl:definitions <bibref ref="WSDL11"/> </td>
- </tr>
- <tr>
- <td> http://www.w3.org/ns/ws-policy </td>
- <td> wsp:Policy <bibref ref="wspolicy"/> </td>
- </tr>
- <tr>
- <td> http://www.w3.org/TR/ws-policy-attach </td>
- <td> wsp:PolicyAttachment <bibref ref="WS-PolicyAttachment"/> </td>
- </tr>
- <tr>
- <td> http://www.w3.org/&wsmex.nsprefix;/ws-mex/Dialects/ws-mex </td>
- <td> mex:Metadata [Defined in this specification] </td>
- </tr>
- </tbody>
- </table>
- <p>
- If there is more than one metadata unit with the same Dialect, e.g.,
- more than one XML Schema document, including them all, one per
- MetadataSection, is explicitly encouraged.
- </p>
-
- <glist>
<gitem>
<label>
- /mex:Metadata/mex:MetadataSection/@Dialect='http://www.w3.org/&wsmex.nsprefix;/ws-mex/Dialects/ws-mex'
+ /mex:Metadata/mex:MetadataSection/@Dialect='mex:Metadata'
</label>
<def>
<p>
@@ -970,39 +936,38 @@
corresponding value. In other cases the value of the Identifier
attribute is not constrained.
</p>
+
+ <table border='1'>
+ <tbody>
+ <tr>
+ <th align="left"> Dialect QName </th>
+ <th align="left"> @Identifier value </th>
+ </tr>
+ <tr>
+ <td> xs:schema </td>
+ <td> xs:schema/@targetNamespace </td>
+ </tr>
+ <tr>
+ <td> wsdl:definitions </td>
+ <td> wsdl:definitions/@targetNamespace </td>
+ </tr>
+ <tr>
+ <td> wsp:Policy </td>
+ <td> wsp:Policy/@Name </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>
+ If there is more than one MetadataSection with the same
+ identifier, e.g., more than one XML Schema in the same target
+ namespace, including them all, one per MetadataSection, is
+ explicitly encouraged.
+ </p>
+
</def>
</gitem>
- </glist>
- <table border='1'>
- <tbody>
- <tr>
- <th align="left"> Dialect IRI </th>
- <th align="left"> @Identifier value </th>
- </tr>
- <tr>
- <td> http://www.w3.org/2001/XMLSchema </td>
- <td> xs:schema/@targetNamespace </td>
- </tr>
- <tr>
- <td> http://schemas.xmlsoap.org/wsdl/ </td>
- <td> wsdl:definitions/@targetNamespace </td>
- </tr>
- <tr>
- <td> http://www.w3.org/ns/ws-policy </td>
- <td> wsp:Policy/@Name </td>
- </tr>
- </tbody>
- </table>
-
- <p>
- If there is more than one MetadataSection with the same
- identifier, e.g., more than one XML Schema in the same target
- namespace, including them all, one per MetadataSection, is
- explicitly encouraged.
- </p>
-
- <glist>
<gitem>
<label>/mex:Metadata/mex:MetadataSection/mex:MetadataReference</label>
<def>
@@ -1221,7 +1186,7 @@
<kw>[Body]</kw>
<mex:GetMetadata ...>
- <mex:Dialect URI='<emph>xs:anyURI</emph>'
+ <mex:Dialect Type='<emph>xs:QName</emph>'
Identifier='<emph>xs:anyURI</emph>' ?
Content='<emph>xs:anyURI</emph>' ? .../> *
<emph>xs:any</emph>*
@@ -1240,7 +1205,7 @@
<p>
When this repeating OPTIONAL element is present, the response MUST
include only MetadataSections corresponding to metadata specified by
- the combination of the URI, Identifier and Content attributes of
+ the combination of the QName, Identifier and Content attributes of
each of the Dialect elements. For each Dialect element if there is no
metadata for that combination of attributes then the response
MUST NOT include any MetadataSections for that Dialect element.
@@ -1253,14 +1218,14 @@
</gitem>
<gitem>
- <label> <kw>[Body]</kw>/mex:GetMetadata/mex:Dialect@URI </label>
+ <label> <kw>[Body]</kw>/mex:GetMetadata/mex:Dialect@Type </label>
<def>
<p>
This REQUIRED attribute specifies the Metadata Dialect. The response
MUST only include MetadataSections corresponding to the Dialect
- specified by this IRI. If the receiver does not have any
+ specified by this QName. If the receiver does not have any
MetadataSections of this indicated Dialect, the response MUST
- include zero MetadataSections for this IRI.
+ include zero MetadataSections for this QName.
</p>
</def>
</gitem>
@@ -1273,7 +1238,7 @@
MetadataSections with the indicated identifier; if the receiver
does not have any MetadataSections of the indicated identifier,
the response MUST include zero MetadataSections for this
- IRI/Identifier pair.
+ QName/Identifier pair.
When this attribute is not present, the implied value is any
identifier.
If multiple MetadataSections have the indicated Dialect
@@ -1290,7 +1255,7 @@
MetadataSections of this specified content form. If the specified
content form is not available, or not known,
then the response MUST include zero
- MetadataSections of the specified form for this IRI/Identifier pair.
+ MetadataSections of the specified form for this QName/Identifier pair.
This specification defines the following content form IRIs:
</p>
<table border='1'>
@@ -1850,7 +1815,7 @@
<eg>(01) <wsa:EndpointReference ...>
(02) <wsa:Address>http://services.example.org/stockquote</wsa:Address>
(03) <wsa:Metadata>
-(04) <mex:Reference Type='http://www.w3.org/&wsmex.nsprefix;/ws-mex'>
+(04) <mex:Reference Type='mex:Metadata'>
(05) <wsa:Address>
(06) http://services.example.org/stockquote/metadata
(07) </wsa:Address>
@@ -1983,9 +1948,9 @@
<eg><wsa:EndpointReference>
<wsa:Address> xs:anyURI </wsa:Address>
<wsa:ReferenceParameters> xs:any* </wsa:ReferenceParameters>
- <wsa:Metadata>
- ( <wsp:Policy ...> ... </wsp:Policy> |
- <wsp:PolicyReference ...> ... </wsp:PolicyReference> ) ?
+ <wsa:Metadata>
+ ( <wsp:Policy ...> ... </wsp:Policy> |
+ <wsp:PolicyReference ...> ... </wsp:PolicyReference> ) ?
</wsa:Metadata>
</wsa:EndpointReference></eg>
</example>
@@ -2397,7 +2362,7 @@
<example>
<eg><mex:MetadataExchange ...>
<mex:GetMetadataSupported ...>
- <mex:MetadataExchangeDialect URI="<emph>xs:anyURI</emph>" ...>
+ <mex:MetadataExchangeDialect Type="<emph>xs:QName</emph>" ...>
<mex:MetadataContent URI="<emph>xs:anyURI</emph>" ...>
<emph>xs:any</emph>*
</mex:MetadataContent> *
@@ -2437,11 +2402,11 @@
</gitem>
<gitem>
- <label> /mex:MetadataExchange/mex:GetMetadataSupported/mex:MetadataExchangeDialect@URI </label>
+ <label> /mex:MetadataExchange/mex:GetMetadataSupported/mex:MetadataExchangeDialect@Type </label>
<def>
<p>
When present, this OPTIONAL parameter indicates support for the
- specified MetadataExchange Dialect IRI.
+ specified MetadataExchange Dialect QName.
</p>
</def>
</gitem>
@@ -2475,7 +2440,7 @@
This extensibility point allows for additional Metadata Dialect
specific metadata to be included within the policy assertion. Any
metadata that appears is scoped to the use of the specified
- Metadata Dialect URI.
+ Metadata Dialect QName.
</p>
</def>
</gitem>
@@ -2892,7 +2857,7 @@
<xs:element name='Dialect'>
<xs:complexType>
- <xs:attribute name='URI' type='xs:anyURI' use='required'/>
+ <xs:attribute name='Type' type='xs:QName' use='required'/>
<xs:attribute name='Identifier' type='xs:anyURI'/>
<xs:attribute name='Content' type='xs:anyURI'/>
<xs:anyAttribute namespace='##other' processContents='lax'/>
@@ -2921,7 +2886,7 @@
<xs:element name='MetadataReference' type='wsa:EndpointReferenceType' />
<xs:element name='MetadataLocation' type='tns:URI'/>
</xs:choice>
- <xs:attribute name='Dialect' type='xs:anyURI' use='required'/>
+ <xs:attribute name='Dialect' type='xs:QName' use='required'/>
<xs:attribute name='Identifier' type='xs:anyURI'/>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
@@ -3506,6 +3471,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8289">8289</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/30 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -d -r1.112 -r1.113
--- wsmex.html 20 Mar 2010 01:25:55 -0000 1.112
+++ wsmex.html 30 Mar 2010 22:20:57 -0000 1.113
@@ -61,19 +61,19 @@
7 <a href="#MetadataReferences">Metadata References</a><br/>
7.1 <a href="#mexLocation">mex:Location</a><br/>
7.2 <a href="#mexReference">mex:Reference</a><br/>
- 7.3 <a href="#iddiv2_1_1294">Examples</a><br/>
+ 7.3 <a href="#iddiv2_1_1219">Examples</a><br/>
8 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
8.1 <a href="#EPRwithMEX">Endpoint References Containing Metadata</a><br/>
8.2 <a href="#WSPAEPR">Associating Policies with Endpoint References</a><br/>
9 <a href="#ImplicitWSDL">Exposing Metadata for Implicitly Defined Features</a><br/>
10 <a href="#Security">Security Considerations</a><br/>
11 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
- 11.1 <a href="#iddiv2_1_1689">MetadataExchange Assertion</a><br/>
+ 11.1 <a href="#iddiv2_1_1612">MetadataExchange Assertion</a><br/>
12 <a href="#bootstrapping">Boostrapping Metadata Retrieval</a><br/>
13 <a href="#acks">Acknowledgements</a><br/>
14 <a href="#References">References</a><br/>
- 14.1 <a href="#iddiv2_1_1850">Normative References</a><br/>
- 14.2 <a href="#iddiv2_1_2023">Informative References</a><br/>
+ 14.1 <a href="#iddiv2_1_1773">Normative References</a><br/>
+ 14.2 <a href="#iddiv2_1_1946">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
B <a href="#Appendix-B">WSDL</a><br/>
@@ -217,70 +217,71 @@
</p><div class="exampleOuter">
<div class="exampleHeader"><a name="GetResponse" id="GetResponse"/>Example 2-4: Sample response message with metadata</div><div class="exampleInner"><pre>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
-(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
-(04) xmlns:mex='http://www.w3.org/2002/ws/ra/edcopies/ws-mex'
-(05) xmlns:wsp='http://www.w3.org/ns/ws-policy'
-(06) xmlns:wst='http://www.w3.org/2002/ws/ra/edcopies/ws-tra'
-(07) xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'>
-(08) <s11:Header>
-(09) <wsa:Action>
-(10) http://www.w3.org/2002/ws/ra/edcopies/ws-tra/GetResponse
-(11) </wsa:Action>
-(12) <wsa:To>http://client.example.org</wsa:To>
-(13) <wsa:RelatesTo>
-(14) urn:uuid:1cec121a-82fe-41da-87e1-3b23f254f128
-(15) </wsa:RelatesTo>
-(16) </s11:Header>
-(17) <s11:Body>
-(18) <wst:GetResponse>
-(19) <mex:Metadata>
-(20) <mex:MetadataSection Dialect='http://schemas.xmlsoap.org/wsdl/'>
-(21) <wsdl:definitions>
-(22) <!-- WSDL data removed for brevity -->
-(23) </wsdl:definitions>
-(24) </mex:MetadataSection>
-(25) <mex:MetadataSection
-(26) Dialect='http://www.w3.org/2001/XMLSchema'
-(27) Identifier='http://services.example.org/stockquote/schemas'>
-(28) <mex:MetadataLocation>
-(29) http://services.example.org/stockquote/schemas
-(30) </mex:MetadataLocation>
-(31) </mex:MetadataSection>
-(32) <mex:MetadataSection
-(33) Dialect='http://www.w3.org/ns/ws-policy'
-(34) Identifier='http://services.example.org/stockquote/policy'>
-(35) <mex:MetadataReference>
-(36) <wsa:Address>
-(37) http://services.example.org/stockquote/policy
-(38) </wsa:Address>
-(39) </mex:MetadataReference>
-(40) </mex:MetadataSection>
-(41) </mex:Metadata>
-(42) </wst:GetResponse>
-(43) </s11:Body>
-(44) </s11:Envelope></pre></div></div><p>
+(03) xmlns:xs='http://www.w3.org/2001/XMLSchema'
+(04) xmlns:wsa='http://www.w3.org/2005/08/addressing'
+(05) xmlns:mex='http://www.w3.org/2002/ws/ra/edcopies/ws-mex'
+(06) xmlns:wsp='http://www.w3.org/ns/ws-policy'
+(07) xmlns:wst='http://www.w3.org/2002/ws/ra/edcopies/ws-tra'
+(08) xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'>
+(09) <s11:Header>
+(10) <wsa:Action>
+(11) http://www.w3.org/2002/ws/ra/edcopies/ws-tra/GetResponse
+(12) </wsa:Action>
+(13) <wsa:To>http://client.example.org</wsa:To>
+(14) <wsa:RelatesTo>
+(15) urn:uuid:1cec121a-82fe-41da-87e1-3b23f254f128
+(16) </wsa:RelatesTo>
+(17) </s11:Header>
+(18) <s11:Body>
+(19) <wst:GetResponse>
+(20) <mex:Metadata>
+(21) <mex:MetadataSection Dialect='wsdl:definitions'>
+(22) <wsdl:definitions>
+(23) <!-- WSDL data removed for brevity -->
+(24) </wsdl:definitions>
+(25) </mex:MetadataSection>
+(26) <mex:MetadataSection
+(27) Dialect='xs:schema'
+(28) Identifier='http://services.example.org/stockquote/schemas'>
+(29) <mex:MetadataLocation>
+(30) http://services.example.org/stockquote/schemas
+(31) </mex:MetadataLocation>
+(32) </mex:MetadataSection>
+(33) <mex:MetadataSection
+(34) Dialect='wsp:Policy'
+(35) Identifier='http://services.example.org/stockquote/policy'>
+(36) <mex:MetadataReference>
+(37) <wsa:Address>
+(38) http://services.example.org/stockquote/policy
+(39) </wsa:Address>
+(40) </mex:MetadataReference>
+(41) </mex:MetadataSection>
+(42) </mex:Metadata>
+(43) </wst:GetResponse>
+(44) </s11:Body>
+(45) </s11:Envelope></pre></div></div><p>
The message of <a href="#GetResponse">Example 2-4</a> is a
<a href="#WS-Transfer">[WS-Transfer]</a>
response message to the request of <a href="#GetRequest">Example 2-3</a>. The
content
- of the <b>[Body]</b> (lines 17-43) is a mex:Metadata element with
+ of the <b>[Body]</b> (lines 18-44) is a mex:Metadata element with
metadata
- about the Web service endpoint (lines 19-41). The mex:Metadata
+ about the Web service endpoint (lines 20-42). The mex:Metadata
contains three MetadataSections. The first MetadataSection
- (lines 20-24) contains the <a href="#WSDL11">[WSDL11]</a> of the Web
- service endpoint. The second MetadataSection (lines 25-31) contains
+ (lines 21-25) contains the <a href="#WSDL11">[WSDL11]</a> of the Web
+ service endpoint. The second MetadataSection (lines 26-32) contains
the location of the XML Schemas <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,
<a href="#XMLSchema2">[XMLSchema - Part 2]</a> used by the WSDL document. The schemas can
be retrieved through an HTTP GET request at the identified URL
- (lines 28-30). The third MetadataSection (lines 32-40) contains
- the <a href="#AddrCore">[WS-Addressing]</a> endpoint reference (lines 35-39) of
+ (lines 29-31). The third MetadataSection (lines 33-41) contains
+ the <a href="#AddrCore">[WS-Addressing]</a> endpoint reference (lines 36-40) of
a <a href="#WS-Transfer">[WS-Transfer]</a> resource the representation of
which is a <a href="#wspolicy">[WS-Policy]</a> document as indicated by
- the Dialect attribute (line 33).
+ the Dialect attribute (line 34).
</p><p>
While the WS-Policy of the Web service endpoint could be retrieved using
a WS-Transfer Get request directed to the endpoint identified by the
- mex:MetadataReference element in lines 35-39 of
+ mex:MetadataReference element in lines 36-40 of
<a href="#GetResponse">Example 2-4</a>,
some endpoints MAY support explicit requests for metadata via the
GetMetadata operation.
@@ -290,29 +291,30 @@
<div class="exampleHeader"><a name="GetMexReq" id="GetMexReq"/>Example 2-5: Sample GetMetadata request message</div><div class="exampleInner"><pre>(01) <s11:Envelope
(02) xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
(03) xmlns:wsa='http://www.w3.org/2005/08/addressing'
-(04) xmlns:mex='http://www.w3.org/2002/ws/ra/edcopies/ws-mex' >
-(05) <s11:Header>
-(06) <wsa:To>http://services.example.org/stockquote</wsa:To>
-(07) <wsa:Action>
-(08) http://www.w3.org/2002/ws/ra/edcopies/ws-mex/GetMetadata
-(09) </wsa:Action>
-(10) <wsa:MessageID>
-(11) urn:uuid:73d7edfc-5c3c-49b9-ba46-2480caee43e9
-(12) </wsa:MessageID>
-(13) <wsa:ReplyTo>
-(14) <wsa:Address>http://client.example.org</wsa:Address>
-(15) </wsa:ReplyTo>
-(16) </s11:Header>
-(17) <s11:Body>
-(18) <mex:GetMetadata>
-(19) <mex:Dialect URI='http://www.w3.org/ns/ws-policy'
-(20) Identifier='http://services.example.org/stockquote/policy'/>
-(21) </mex:GetMetadata>
-(22) </s11:Body>
-(23) </s11:Envelope></pre></div></div><p>
- Lines 7-9 in <a href="#GetMexReq">Example 2-5</a> indicate this is a GetMetadata
- request. As lines 18-21 indicate, this request is for the policy of
- the Web service endpoint (line 6).
+(04) xmlns:wsp='http://www.w3.org/ns/ws-policy'
+(05) xmlns:mex='http://www.w3.org/2002/ws/ra/edcopies/ws-mex' >
+(06) <s11:Header>
+(07) <wsa:To>http://services.example.org/stockquote</wsa:To>
+(08) <wsa:Action>
+(09) http://www.w3.org/2002/ws/ra/edcopies/ws-mex/GetMetadata
+(10) </wsa:Action>
+(11) <wsa:MessageID>
+(12) urn:uuid:73d7edfc-5c3c-49b9-ba46-2480caee43e9
+(13) </wsa:MessageID>
+(14) <wsa:ReplyTo>
+(15) <wsa:Address>http://client.example.org</wsa:Address>
+(16) </wsa:ReplyTo>
+(17) </s11:Header>
+(18) <s11:Body>
+(19) <mex:GetMetadata>
+(20) <mex:Dialect Type='wsp:Policy'
+(21) Identifier='http://services.example.org/stockquote/policy'/>
+(22) </mex:GetMetadata>
+(23) </s11:Body>
+(24) </s11:Envelope></pre></div></div><p>
+ Lines 8-10 in <a href="#GetMexReq">Example 2-5</a> indicate this is a GetMetadata
+ request. As lines 19-22 indicate, this request is for the policy of
+ the Web service endpoint (line 7).
</p><p><a href="#GetMexRes">Example 2-6</a> lists a sample response to the request in
<a href="#GetMexReq">Example 2-5</a>.
</p><div class="exampleOuter">
@@ -334,7 +336,7 @@
(16) <mex:GetMetadataResponse>
(17) <mex:Metadata>
(18) <mex:MetadataSection
-(19) Dialect='http://www.w3.org/ns/ws-policy'
+(19) Dialect='wsp:Policy'
(20) Identifier='http://services.example.org/stockquote/policy'>
(21) <wsp:Policy>
(22) <wsp:ExactlyOne>
@@ -514,7 +516,7 @@
</p><p>
The outline for the Metadata element is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><mex:Metadata ...>
- <mex:MetadataSection Dialect='<em>xs:anyURI</em>'
+ <mex:MetadataSection Dialect='<em>xs:QName</em>'
Identifier='<em>xs:anyURI</em>'? ...>
(
<mex:MetadataReference ...>
@@ -543,19 +545,15 @@
endpoint reference to a Metadata Resource for the metadata
unit, or a URL to metadata unit.
</p></dd><dt class="label">/mex:Metadata/mex:MetadataSection/@Dialect</dt><dd><p>
- This indicates the format and version of the metadata unit
- contained in this MetadataSection (e.g., WSDL version 1.1). Dialect
- is an absolute IRI.
- </p></dd></dl><p>
- This specification defines the following values for Dialect;
- other specifications SHOULD define values for Dialect for their
- metadata format(s).
- </p><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th align="left"> Metadata Format </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a></td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions <a href="#WSDL11">[WSDL11]</a></td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy <a href="#wspolicy">[WS-Policy]</a></td></tr><tr><td> http://www.w3.org/TR/ws-policy-attach </td><td> wsp:PolicyAttachment <a href="#WS-PolicyAttachment">[WS-PolicyAttachment]</a></td></tr><tr><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex/Dialects/ws-mex </td><td> mex:Metadata [Defined in this specification] </td></tr></tbody></table><p>
- If there is more than one metadata unit with the same Dialect, e.g.,
- more than one XML Schema document, including them all, one per
- MetadataSection, is explicitly encouraged.
- </p><dl><dt class="label">
- /mex:Metadata/mex:MetadataSection/@Dialect='http://www.w3.org/2002/ws/ra/edcopies/ws-mex/Dialects/ws-mex'
+ This indicates the type and version of the metadata unit
+ contained in this MetadataSection (e.g., WSDL version 1.1).
+ This MUST be the QName of the root element of the metadata.
+ </p><p>
+ If there is more than one metadata unit with the same Dialect, e.g.,
+ more than one XML Schema document, including them all, one per
+ MetadataSection, is explicitly encouraged.
+ </p></dd><dt class="label">
+ /mex:Metadata/mex:MetadataSection/@Dialect='mex:Metadata'
</dt><dd><p>
This Dialect value indicates that the type of the metadata contained
within the MetadataSection is itself a mex:Metadata element.
@@ -575,12 +573,12 @@
the table below, the Identifier attribute MUST have the indicated,
corresponding value. In other cases the value of the Identifier
attribute is not constrained.
- </p></dd></dl><table border="1"><tbody><tr><th align="left"> Dialect IRI </th><th align="left"> @Identifier value </th></tr><tr><td> http://www.w3.org/2001/XMLSchema </td><td> xs:schema/@targetNamespace </td></tr><tr><td> http://schemas.xmlsoap.org/wsdl/ </td><td> wsdl:definitions/@targetNamespace </td></tr><tr><td> http://www.w3.org/ns/ws-policy </td><td> wsp:Policy/@Name </td></tr></tbody></table><p>
- If there is more than one MetadataSection with the same
- identifier, e.g., more than one XML Schema in the same target
- namespace, including them all, one per MetadataSection, is
- explicitly encouraged.
- </p><dl><dt class="label">/mex:Metadata/mex:MetadataSection/mex:MetadataReference</dt><dd><p>
+ </p><table border="1"><tbody><tr><th align="left"> Dialect QName </th><th align="left"> @Identifier value </th></tr><tr><td> xs:schema </td><td> xs:schema/@targetNamespace </td></tr><tr><td> wsdl:definitions </td><td> wsdl:definitions/@targetNamespace </td></tr><tr><td> wsp:Policy </td><td> wsp:Policy/@Name </td></tr></tbody></table><p>
+ If there is more than one MetadataSection with the same
+ identifier, e.g., more than one XML Schema in the same target
+ namespace, including them all, one per MetadataSection, is
+ explicitly encouraged.
+ </p></dd><dt class="label">/mex:Metadata/mex:MetadataSection/mex:MetadataReference</dt><dd><p>
This is an endpoint reference to a metadata resource and is
of type EndpointReferenceType as defined by <a href="#AddrCore">[WS-Addressing]</a>.
The metadata resource MUST support the Get operation
@@ -716,7 +714,7 @@
<b>[Body]</b>
<mex:GetMetadata ...>
- <mex:Dialect URI='<em>xs:anyURI</em>'
+ <mex:Dialect Type='<em>xs:QName</em>'
Identifier='<em>xs:anyURI</em>' ?
Content='<em>xs:anyURI</em>' ? .../> *
<em>xs:any</em>*
@@ -726,25 +724,25 @@
</p><dl><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect </dt><dd><p>
When this repeating OPTIONAL element is present, the response MUST
include only MetadataSections corresponding to metadata specified by
- the combination of the URI, Identifier and Content attributes of
+ the combination of the QName, Identifier and Content attributes of
each of the Dialect elements. For each Dialect element if there is no
metadata for that combination of attributes then the response
MUST NOT include any MetadataSections for that Dialect element.
</p><p>
When this element is not present, the endpoint MUST return all
available metadata.
- </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@URI </dt><dd><p>
+ </p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@Type </dt><dd><p>
This REQUIRED attribute specifies the Metadata Dialect. The response
MUST only include MetadataSections corresponding to the Dialect
- specified by this IRI. If the receiver does not have any
+ specified by this QName. If the receiver does not have any
MetadataSections of this indicated Dialect, the response MUST
- include zero MetadataSections for this IRI.
+ include zero MetadataSections for this QName.
</p></dd><dt class="label"><b>[Body]</b>/mex:GetMetadata/mex:Dialect@Identifier </dt><dd><p>
When this OPTIONAL attribute is present, the response MUST include only
MetadataSections with the indicated identifier; if the receiver
does not have any MetadataSections of the indicated identifier,
the response MUST include zero MetadataSections for this
- IRI/Identifier pair.
+ QName/Identifier pair.
When this attribute is not present, the implied value is any
identifier.
If multiple MetadataSections have the indicated Dialect
@@ -754,7 +752,7 @@
MetadataSections of this specified content form. If the specified
content form is not available, or not known,
then the response MUST include zero
- MetadataSections of the specified form for this IRI/Identifier pair.
+ MetadataSections of the specified form for this QName/Identifier pair.
This specification defines the following content form IRIs:
</p><table border="1"><tbody><tr><th align="left"> Content Form IRI </th><th align="left"> Form </th></tr><tr><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex/Content/EPR </td><td> A MetadataReference element is returned </td></tr><tr><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex/Content/URI </td><td> A MetadataLocation element is returned </td></tr><tr><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex/Content/Metadata </td><td> The metadata is embedded </td></tr><tr><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex/Content/Any </td><td> The service is free to choose any content form </td></tr><tr><td> http://www.w3.org/2002/ws/ra/edcopies/ws-mex/Content/All </td><td> The service MUST return all available content forms </td></tr></tbody></table><p>
When not present the default value is
@@ -848,7 +846,7 @@
being referenced. Identifier is an absolute IRI. If omitted, there
is no implied value.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1294" id="iddiv2_1_1294"/>7.3 Examples</h3><p>
+<h3><a name="iddiv2_1_1219" id="iddiv2_1_1219"/>7.3 Examples</h3><p>
The following examples show how metadata might appear in various
locations:
</p><div class="exampleOuter">
@@ -879,7 +877,7 @@
The following example WSDL shows how support for a particular feature
might be indicated:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_1326" id="idexample_1_1326"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
+<div class="exampleHeader"><a name="idexample_1_1251" id="idexample_1_1251"/>Example 7-3: Feature Metadata in a Policy Assertion</div><div class="exampleInner"><pre>(01) <wsdl:definitions>
(02) ...
(03) <wsdl:service name="stockQuote">
(04) <wsdl:port binding="..." name="...">
@@ -1069,7 +1067,7 @@
<div class="exampleHeader"><a name="EPRrefMDref" id="EPRrefMDref"/>Example 8-3: Endpoint reference with a reference to metadata about the Metadata Reference</div><div class="exampleInner"><pre>(01) <wsa:EndpointReference ...>
(02) <wsa:Address>http://services.example.org/stockquote</wsa:Address>
(03) <wsa:Metadata>
-(04) <mex:Reference Type='http://www.w3.org/2002/ws/ra/edcopies/ws-mex'>
+(04) <mex:Reference Type='mex:Metadata'>
(05) <wsa:Address>
(06) http://services.example.org/stockquote/metadata
(07) </wsa:Address>
@@ -1166,9 +1164,9 @@
</p><div class="exampleOuter"><div class="exampleInner"><pre><wsa:EndpointReference>
<wsa:Address> xs:anyURI </wsa:Address>
<wsa:ReferenceParameters> xs:any* </wsa:ReferenceParameters>
- <wsa:Metadata>
- ( <wsp:Policy ...> ... </wsp:Policy> |
- <wsp:PolicyReference ...> ... </wsp:PolicyReference> ) ?
+ <wsa:Metadata>
+ ( <wsp:Policy ...> ... </wsp:Policy> |
+ <wsp:PolicyReference ...> ... </wsp:PolicyReference> ) ?
</wsa:Metadata>
</wsa:EndpointReference></pre></div></div><p>
If multiple alternatives are desired, the operators defined in
@@ -1422,7 +1420,7 @@
indicate a particular security mechanism used to protect the
WS-MetadataExchange operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1689" id="iddiv2_1_1689"/>11.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1612" id="iddiv2_1_1612"/>11.1 MetadataExchange Assertion</h3><p>
Services indicate support for the WS-MetadataExchange specification
through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1452,7 +1450,7 @@
The normative outline of this assertion is:
</p><div class="exampleOuter"><div class="exampleInner"><pre><mex:MetadataExchange ...>
<mex:GetMetadataSupported ...>
- <mex:MetadataExchangeDialect URI="<em>xs:anyURI</em>" ...>
+ <mex:MetadataExchangeDialect Type="<em>xs:QName</em>" ...>
<mex:MetadataContent URI="<em>xs:anyURI</em>" ...>
<em>xs:any</em>*
</mex:MetadataContent> *
@@ -1470,9 +1468,9 @@
</p></dd><dt class="label"> /mex:MetadataExchange/mex:GetMetadataSupported </dt><dd><p>
When present, this OPTIONAL parameter indicates that the
GetMetadata operation is supported by this endpoint.
- </p></dd><dt class="label"> /mex:MetadataExchange/mex:GetMetadataSupported/mex:MetadataExchangeDialect@URI </dt><dd><p>
+ </p></dd><dt class="label"> /mex:MetadataExchange/mex:GetMetadataSupported/mex:MetadataExchangeDialect@Type </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
- specified MetadataExchange Dialect IRI.
+ specified MetadataExchange Dialect QName.
</p></dd><dt class="label"> /mex:MetadataExchange/mex:GetMetadataSupported/mex:MetadataExchangeDialect/mex:MetadataContent </dt><dd><p>
When present, this OPTIONAL parameter indicates support for the
specified MetadataExchange content IRI.
@@ -1485,7 +1483,7 @@
This extensibility point allows for additional Metadata Dialect
specific metadata to be included within the policy assertion. Any
metadata that appears is scoped to the use of the specified
- Metadata Dialect URI.
+ Metadata Dialect QName.
</p></dd><dt class="label"> /mex:MetadataExchange/mex:GetMetadataSupported/xs:any </dt><dd><p>
This extensibility point allows for additional metadata specific
to the GetMetadata operation to be included within the policy
@@ -1590,7 +1588,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="References" id="References"/>14 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1850" id="iddiv2_1_1850"/>14.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_1773" id="iddiv2_1_1773"/>14.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.
@@ -1657,7 +1655,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_2023" id="iddiv2_1_2023"/>14.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_1946" id="iddiv2_1_1946"/>14.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
OASIS Standard, "Web Services Secure Conversation
(WS-SecureConversation) 1.4"
</cite></a>
@@ -1751,7 +1749,7 @@
<xs:element name='Dialect'>
<xs:complexType>
- <xs:attribute name='URI' type='xs:anyURI' use='required'/>
+ <xs:attribute name='Type' type='xs:QName' use='required'/>
<xs:attribute name='Identifier' type='xs:anyURI'/>
<xs:attribute name='Content' type='xs:anyURI'/>
<xs:anyAttribute namespace='##other' processContents='lax'/>
@@ -1780,7 +1778,7 @@
<xs:element name='MetadataReference' type='wsa:EndpointReferenceType' />
<xs:element name='MetadataLocation' type='tns:URI'/>
</xs:choice>
- <xs:attribute name='Dialect' type='xs:anyURI' use='required'/>
+ <xs:attribute name='Dialect' type='xs:QName' use='required'/>
<xs:attribute name='Identifier' type='xs:anyURI'/>
<xs:anyAttribute namespace='##other' processContents='lax'/>
</xs:complexType>
@@ -1984,4 +1982,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</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><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8289">8289</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=8289">8289</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</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.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- wsevd.html 17 Mar 2010 03:25:47 -0000 1.10
+++ wsevd.html 30 Mar 2010 22:20:57 -0000 1.11
@@ -49,12 +49,12 @@
3.5 <a href="#compliance">Compliance</a><br/>
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_531">Retrieving Event Descriptions</a><br/>
- 4.1.2 <a href="#iddiv3_1_569">Bindings for Event Descriptions</a><br/>
+ 4.1.1 <a href="#iddiv3_1_553">Retrieving Event Descriptions</a><br/>
+ 4.1.2 <a href="#iddiv3_1_593">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_584">Normative References</a><br/>
- 6.2 <a href="#iddiv2_1_614">Informative References</a><br/>
+ 6.1 <a href="#iddiv2_1_608">Normative References</a><br/>
+ 6.2 <a href="#iddiv2_1_638">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/>
@@ -146,7 +146,9 @@
</a></td><td>This specification</td></tr><tr><td>xs</td><td><a href="http://www.w3.org/2001/XMLSchema">
http://www.w3.org/2001/XMLSchema
</a></td><td>
- XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a></td></tr></tbody></table><p>
+ XML Schema <a href="#XMLSchema1">[XMLSchema - Part 1]</a>, <a href="#XMLSchema2">[XMLSchema - Part 2]</a></td></tr><tr><td>wse</td><td><a href="http://www.w3.org/2002/ws/ra/edcopies/ws-evt">
+ http://www.w3.org/2002/ws/ra/edcopies/ws-evt
+ </a></td><td>WS-Eventing <a href="#Eventing">[WS-Eventing]</a></td></tr></tbody></table><p>
The working group intends to update the value of the Web Services
Event Descriptions namespace URI each time a new version of this document
is published until such time that the document reaches Candidate
@@ -322,7 +324,7 @@
(24) </ow:WindReport>
(25) </s12:Body>
(26) </s12:Envelope></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_531" id="iddiv3_1_531"/>4.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_553" id="iddiv3_1_553"/>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 section 9 of WS-MetadataExchange
@@ -333,6 +335,11 @@
by either embedding the Event Description metadata directly within
the assertion, or by including a MetadataExchange reference to the data.
</p><p>
+ The value of the @Identifier attribute, if present, for this
+ MetadataSection MUST be equal to the value of its
+ wsevd:EventDescriptions/@targetNamespace. An event source MUST NOT have
+ more than one EventDescriptions document.
+ </p><p>
The following examples show how Event Description metadata might
appear within a WS-Eventing EventSource Policy assertion.
</p><div class="exampleOuter">
@@ -356,7 +363,7 @@
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_569" id="iddiv3_1_569"/>4.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_593" id="iddiv3_1_593"/>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
@@ -393,7 +400,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_584" id="iddiv2_1_584"/>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_608" id="iddiv2_1_608"/>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.
@@ -404,7 +411,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_614" id="iddiv2_1_614"/>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_638" id="iddiv2_1_638"/>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.
@@ -495,4 +502,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</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><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8900">8900</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=8900">8900</a></td></tr><tr><td> 2010/03/30 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</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.165
retrieving revision 1.166
diff -u -d -r1.165 -r1.166
--- wseventing.xml 30 Mar 2010 20:46:46 -0000 1.165
+++ wseventing.xml 30 Mar 2010 22:20:57 -0000 1.166
@@ -3353,7 +3353,7 @@
<example>
<head>EventDescriptions</head>
- <eg>(01) <wse:EventDescriptions
+ <eg>(01) <wsevd:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wse="http://www.w3.org/&wsevt.nsprefix;/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -3367,7 +3367,7 @@
(12) <wse:eventType name="WindReportEvent"
(13) element="ow:WindReport"
(14) actionURI="http://www.example.org/oceanwatch/2003/WindReport"/>
-(15) </wse:EventDescriptions></eg>
+(15) </wsevd:EventDescriptions></eg>
</example>
<p>
@@ -3383,19 +3383,59 @@
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 <bibref ref="MEX"/>.
- This specification defines the following IRI to serve as the Dialect
- IRI for the wse:EventDescriptions element.
+ In particular, this specification RECOMMENDS that the Event Description
+ metadata be made available through the 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 value of the @Identifier attribute, if present, for this
+ MetadataSection MUST
+ be equal to the value of its wsevd:EventDescriptions/@targetNamespace. An
+ event source MUST NOT have more than one EventDescriptions document.
+ </p>
+
+ <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 wse:EventDescriptions/@targetNamespace. An
- event source MUST NOT have more than one EventDescriptions document.
+ <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>
<div3>
@@ -3529,45 +3569,13 @@
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 <bibref ref="MEX"/>.
- This specification defines the following IRI to serve as the Dialect
- IRI for the Notification WSDL.
- </p>
-
- <example>
- <eg><loc href="http://www.w3.org/&wsevt.nsprefix;/ws-evt/NotificationWSDL">http://www.w3.org/&wsevt.nsprefix;/ws-evt/NotificationWSDL</loc></eg>
- </example>
-
- <p>
- Because the Notification Format specified in a Subscribe request can
- affect various aspects of the Notification WSDL, it is necessary to
- correlate Notification WSDLs with their corresponding Notification
- Formats. When using WS-MetadataExchange to transfer Notification WSDLs,
- the corresponding Format IRI for that Notification WSDL MUST be
- represented via the @Identifier attribute. For any particular
- Format IRI/@Identifier, there MUST NOT exist more than one
- Notification WSDL document.
+ In particular, if an event source has Notification WSDL then it
+ SHOULD be referenced from the wse:EventSource policy assertion.
</p>
</div3>
</div2>
- <div2>
- <head>Multiple Event Information Metadata Sections</head>
- <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
- "http://www.w3.org/&wsevd.nsprefix;/ws-evd/EventDescriptions" and
- "http://www.w3.org/&wsevt.nsprefix;/ws-evt/NotificationWSDL" dialects MUST
- regard these Metadata Sections as relating to the same set of events.
- In cases where the mex:Metadata element contains multiple
- Notification WSDLs (i.e. multiple Metadata Sections with a @Dialect
- of "http://www.w3.org/&wsevt.nsprefix;/ws-evt/NotificationWSDL"), recipients MUST
- similarly regard these Notification WSDLs as relating to the same set
- of events although their Notification Formats differ.
- </p>
- </div2>
-
</div1>
<div1 id="Schema">
@@ -5031,6 +5039,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9320">9320</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/03/30 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031">9031</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Tuesday, 30 March 2010 22:21:03 UTC