- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 18 Aug 2010 10:09:55 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv21964
Modified Files:
wsevd.html wsevd.xml wseventing.html wseventing.xml
Log Message:
10376
Index: wsevd.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsevd.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -d -r1.19 -r1.20
--- wsevd.html 17 Aug 2010 19:59:02 -0000 1.19
+++ wsevd.html 18 Aug 2010 10:09:53 -0000 1.20
@@ -51,11 +51,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="#iddiv3x1x557">Retrieving Event Descriptions</a><br/>
- 4.1.2 <a href="#iddiv3x1x597">Bindings for Event Descriptions</a><br/>
+ 4.1.2 <a href="#iddiv3x1x610">Bindings for Event Descriptions</a><br/>
5 <a href="#acks">Acknowledgements</a><br/>
6 <a href="#refs">References</a><br/>
- 6.1 <a href="#iddiv2x1x612">Normative References</a><br/>
- 6.2 <a href="#iddiv2x1x642">Informative References</a><br/>
+ 6.1 <a href="#iddiv2x1x625">Normative References</a><br/>
+ 6.2 <a href="#iddiv2x1x655">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/>
@@ -337,41 +337,55 @@
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in section 9 of WS-MetadataExchange
<a href="#MEX">[WS-MetadataExchange]</a>.
- In particular, this specification RECOMMENDS that the Event Description
+ In particular, this specification RECOMMENDS that the Event Descriptions
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
+ by either embedding the Event Descriptions 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.
+ An event source MUST NOT have more than one EventDescriptions document.
</p><p>
- The following examples show how Event Description metadata might
+ The following examples show how Event Descriptions 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 ...>
+<div class="exampleHeader"><a name="embedEVD" id="embedEVD"/>Example 4-3: Sample Embedded Event Descriptions Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
(02) <wse:FormatName URI="..."/>
(03) <wsevd:EventDescriptions ...>
(04) ...
(05) </wsevd:EventDescriptions>
-(06) </wse:EventSource></pre></div></div><p><a href="#embedEVD">Example 4-3</a> shows how the Event Description metadata
+(06) </wse:EventSource></pre></div></div><p><a href="#embedEVD">Example 4-3</a> shows how the Event Descriptions 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 ...>
+<div class="exampleHeader"><a name="refEVD" id="refEVD"/>Example 4-4: Sample Reference to Event Descriptions Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
(02) <wse:FormatName URI="..."/>
(03) <mex:Location
-(04) Type="evd:EventDescriptions"
+(04) Type="wsevd: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
+ <a href="#embedEVD">Example 4-3</a> except the embedded Event Descriptions
metadata is replaced with a reference to an HTTP resource whose
- representation is the Event Description metadata. The data can be
+ representation is the Event Descriptions metadata. The data can be
retrieved via an HTTP GET to the specified URL.
+ </p><div class="exampleOuter">
+<div class="exampleHeader"><a name="mexEVD" id="mexEVD"/>Example 4-5: Sample GetMetadataResponse with Event Descriptions Metadata</div><div class="exampleInner"><pre>(01) <mex:GetMetadataResponse>
+(02) <mex:Metadata>
+(03) <mex:MetadataSection Dialect='wsevd:EventDescriptions'
+(04) Identifier='...'>
+(05) <wsevd:EventDescriptions ...>
+(06) ...
+(07) </wsevd:EventDescriptions>
+(08) </mex:MetadataSection>
+(09) </mex:Metadata>
+(10) </mex:GetMetadataResponse> </pre></div></div><p><a href="#mexEVD">Example 4-5</a> shows how the Event Descriptions metadata
+ might appear within a GetMetadataResponse message.
+ </p><p>
+ If an EventDescriptions document appears within a WS-MetadataExchange
+ MetadataSection, then the value of the @Identifier attribute, if present,
+ MUST be equal to the value of its
+ wsevd:EventDescription/@targetNamespace.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x597" id="iddiv3x1x597"/>4.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x610" id="iddiv3x1x610"/>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
@@ -408,7 +422,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="iddiv2x1x612" id="iddiv2x1x612"/>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="iddiv2x1x625" id="iddiv2x1x625"/>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.
@@ -419,7 +433,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="iddiv2x1x642" id="iddiv2x1x642"/>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="iddiv2x1x655" id="iddiv2x1x655"/>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.
@@ -513,4 +527,5 @@
<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><tr><td> 2010/04/20 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9321">9321</a></td></tr><tr><td> 2010/05/04 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</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=9087">9087</a></td></tr><tr><td> 2010/08/18 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10376">10376</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.200
retrieving revision 1.201
diff -u -d -r1.200 -r1.201
--- wseventing.xml 17 Aug 2010 19:59:02 -0000 1.200
+++ wseventing.xml 18 Aug 2010 10:09:53 -0000 1.201
@@ -3298,25 +3298,22 @@
the mechanisms described in WS-MetadataExchange <bibref ref="MEX"/>.
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
+ This MAY be done by either embedding the Event Descriptions 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.
+ An event source MUST NOT have more than one EventDescriptions document.
</p>
<p>
- The following examples show how Event Description metadata might
+ The following examples show how Event Descriptions metadata might
appear within a WS-Eventing EventSource Policy assertion.
</p>
<example id="embedEVD">
- <head>Sample Embedded EventDescription Metadata</head>
+ <head>Sample Embedded Event Descriptions Metadata</head>
<eg>(01) <wse:EventSource ...>
(02) <wse:FormatName URI="..."/>
(03) <wsevd:EventDescriptions ...>
@@ -3326,13 +3323,13 @@
</example>
<p>
- <specref ref="embedEVD"/> shows how the Event Description metadata
+ <specref ref="embedEVD"/> shows how the Event Descriptiona metadata
might be embedded directly within a WS-Eventing EventSource Policy
assertion.
</p>
<example id="refEVD">
- <head>Sample Reference to EventDescription Metadata</head>
+ <head>Sample Reference to Event Descriptions Metadata</head>
<eg>(01) <wse:EventSource ...>
(02) <wse:FormatName URI="..."/>
(03) <mex:Location
@@ -3345,10 +3342,29 @@
<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
+ representation is the Event Descriptions metadata. The data can be
retrieved via an HTTP GET to the specified URL.
</p>
+ <example id="mexEVD">
+ <head>Sample GetMetadataResponse with Event Descriptions Metadata</head>
+ <eg>(01) <mex:GetMetadataResponse>
+(02) <mex:Metadata>
+(03) <mex:MetadataSection Dialect='wsevd:EventDescriptions'
+(04) Identifier='...'>
+(05) <wsevd:EventDescriptions ...>
+(06) ...
+(07) </wsevd:EventDescriptions>
+(08) </mex:MetadataSection>
+(09) </mex:Metadata>
+(10) </mex:GetMetadataResponse> </eg>
+ </example>
+
+ <p>
+ <specref ref="mexEVD"/> shows how the Event Descriptions metadata
+ might appear within a GetMetadataResponse message.
+ </p>
+
</div3>
<div3>
@@ -3488,6 +3504,67 @@
In particular, if an event source has Notification WSDL then it
SHOULD be referenced from the wse:EventSource policy assertion.
</p>
+
+ <example id="embedNW">
+ <head>Sample Embedded Notification WSDL Metadata</head>
+ <eg>(01) <wse:EventSource ...>
+(02) <wse:FormatName URI="...">
+(03) <wsdl:definitions ...> ... </wsdl:definitions>
+(04) </wse:FormatName>
+(05) </wse:EventSource></eg>
+ </example>
+
+ <p>
+ <specref ref="embedNW"/> shows how the Notification WSDL metadata
+ might be embedded directly within a WS-Eventing EventSource Policy
+ assertion. Notice that since Notification WSDL is related to
+ a particular FormatName, the Notification WSDL appears as a child
+ of the FormatName element.
+ </p>
+
+ <example id="refNW">
+ <head>Sample Reference to WSDL Definitions Metadata</head>
+ <eg>(01) <wse:EventSource ...>
+(02) <wse:FormatName URI="...">
+(03) <mex:Location
+(04) Type="wsdl:definitions"
+(05) URI="http://example.com/Notif_WSDL_Metadata" />
+(06) </wse:FormatName>
+(07) </wse:EventSource> </eg>
+ </example>
+
+ <p>
+ <specref ref="refNW"/> shows the same policy assertion from
+ <specref ref="embedNW"/> except the embedded Notification WSDL
+ metadata is replaced with a reference to an HTTP resource whose
+ representation is the WSDL definitions metadata. The data can be
+ retrieved via an HTTP GET to the specified URL.
+ </p>
+
+ <example id="mexNW">
+ <head>Sample GetMetadataResponse with WSDL Definitions Metadata</head>
+ <eg>(01) <mex:GetMetadataResponse>
+(02) <mex:Metadata>
+(03) <mex:MetadataSection Dialect='wsdl:definitions'
+(04) Identifier='...'>
+(05) <wsdl:definitions ...>
+(06) ...
+(07) </wsdl:definitions>
+(08) </mex:MetadataSection>
+(09) </mex:Metadata>
+(10) </mex:GetMetadataResponse> </eg>
+ </example>
+
+ <p>
+ <specref ref="mexNW"/> shows how the WSDL definitions metadata
+ might appear within a GetMetadataResponse message. Notice that
+ because the metadata returned only contains the WSDL and not
+ the associated FormatName URI, retrieving the Notificaton WSDL
+ in this fashion requires some other means to disambiguate multiple
+ Notification WSDL documents from each other as well as from any other
+ WSDL documents associated with the Event Source.
+ </p>
+
</div3>
</div2>
@@ -5071,6 +5148,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10339">10339</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/08/18 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10376">10376</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.208
retrieving revision 1.209
diff -u -d -r1.208 -r1.209
--- wseventing.html 17 Aug 2010 19:59:02 -0000 1.208
+++ wseventing.html 18 Aug 2010 10:09:53 -0000 1.209
@@ -89,11 +89,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="#iddiv3x1x2643">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3x1x2680">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4x1x2685">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4x1x2706">Binding for Wrapped Notifications</a><br/>
+ A.1.2 <a href="#iddiv3x1x2691">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4x1x2696">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4x1x2717">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3x1x2733">Retrieving Notification WSDLs</a><br/>
+ A.2.1 <a href="#iddiv3x1x2744">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/>
@@ -1849,28 +1849,25 @@
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
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
+ This MAY be done by either embedding the Event Descriptions 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.
+ An event source MUST NOT have more than one EventDescriptions document.
</p><p>
- The following examples show how Event Description metadata might
+ The following examples show how Event Descriptions 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 ...>
+<div class="exampleHeader"><a name="embedEVD" id="embedEVD"/>Example A-2: Sample Embedded Event Descriptions Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
(02) <wse:FormatName URI="..."/>
(03) <wsevd:EventDescriptions ...>
(04) ...
(05) </wsevd:EventDescriptions>
-(06) </wse:EventSource></pre></div></div><p><a href="#embedEVD">Example A-2</a> shows how the Event Description metadata
+(06) </wse:EventSource></pre></div></div><p><a href="#embedEVD">Example A-2</a> shows how the Event Descriptiona 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 ...>
+<div class="exampleHeader"><a name="refEVD" id="refEVD"/>Example A-3: Sample Reference to Event Descriptions Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
(02) <wse:FormatName URI="..."/>
(03) <mex:Location
(04) Type="evd:EventDescriptions"
@@ -1878,10 +1875,22 @@
(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
+ representation is the Event Descriptions metadata. The data can be
retrieved via an HTTP GET to the specified URL.
+ </p><div class="exampleOuter">
+<div class="exampleHeader"><a name="mexEVD" id="mexEVD"/>Example A-4: Sample GetMetadataResponse with Event Descriptions Metadata</div><div class="exampleInner"><pre>(01) <mex:GetMetadataResponse>
+(02) <mex:Metadata>
+(03) <mex:MetadataSection Dialect='wsevd:EventDescriptions'
+(04) Identifier='...'>
+(05) <wsevd:EventDescriptions ...>
+(06) ...
+(07) </wsevd:EventDescriptions>
+(08) </mex:MetadataSection>
+(09) </mex:Metadata>
+(10) </mex:GetMetadataResponse> </pre></div></div><p><a href="#mexEVD">Example A-4</a> shows how the Event Descriptions metadata
+ might appear within a GetMetadataResponse message.
</p></div><div class="div3">
-<h4><a name="iddiv3x1x2680" id="iddiv3x1x2680"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3x1x2691" id="iddiv3x1x2691"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it MUST be possible to determine how a
given wsevd:eventType will appear on the wire as a notification in a
subscription created with that format. The following sections define
@@ -1893,7 +1902,7 @@
Format, implementations MAY provide a Notification WSDL (see below)
that explicitly describes the notification operations.
</p><div class="div4">
-<h5><a name="iddiv4x1x2685" id="iddiv4x1x2685"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2696" id="iddiv4x1x2696"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
The information about an Event Type contained in the wsevd:eventType
element binds to a Unwrapped Notification for that type as follows:
</p><ul><li><p>
@@ -1908,7 +1917,7 @@
event being transmitted. If the @element attribute is absent then
the <b>[Body]</b> property has no children.
</p></li></ul></div><div class="div4">
-<h5><a name="iddiv4x1x2706" id="iddiv4x1x2706"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4x1x2717" id="iddiv4x1x2717"/>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>
@@ -1934,7 +1943,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="idexamplex1x2727" id="idexamplex1x2727"/>Example A-4: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexamplex1x2738" id="idexamplex1x2738"/>Example A-5: 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/"
@@ -1969,12 +1978,51 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3x1x2733" id="iddiv3x1x2733"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3x1x2744" id="iddiv3x1x2744"/>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>.
In particular, if an event source has Notification WSDL then it
SHOULD be referenced from the wse:EventSource policy assertion.
+ </p><div class="exampleOuter">
+<div class="exampleHeader"><a name="embedNW" id="embedNW"/>Example A-6: Sample Embedded Notification WSDL Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
+(02) <wse:FormatName URI="...">
+(03) <wsdl:definitions ...> ... </wsdl:definitions>
+(04) </wse:FormatName>
+(05) </wse:EventSource></pre></div></div><p><a href="#embedNW">Example A-6</a> shows how the Notification WSDL metadata
+ might be embedded directly within a WS-Eventing EventSource Policy
+ assertion. Notice that since Notification WSDL is related to
+ a particular FormatName, the Notification WSDL appears as a child
+ of the FormatName element.
+ </p><div class="exampleOuter">
+<div class="exampleHeader"><a name="refNW" id="refNW"/>Example A-7: Sample Reference to WSDL Definitions Metadata</div><div class="exampleInner"><pre>(01) <wse:EventSource ...>
+(02) <wse:FormatName URI="...">
+(03) <mex:Location
+(04) Type="wsdl:definitions"
+(05) URI="http://example.com/Notif_WSDL_Metadata" />
+(06) </wse:FormatName>
+(07) </wse:EventSource> </pre></div></div><p><a href="#refNW">Example A-7</a> shows the same policy assertion from
+ <a href="#embedNW">Example A-6</a> except the embedded Notification WSDL
+ metadata is replaced with a reference to an HTTP resource whose
+ representation is the WSDL definitions metadata. The data can be
+ retrieved via an HTTP GET to the specified URL.
+ </p><div class="exampleOuter">
+<div class="exampleHeader"><a name="mexNW" id="mexNW"/>Example A-8: Sample GetMetadataResponse with WSDL Definitions Metadata</div><div class="exampleInner"><pre>(01) <mex:GetMetadataResponse>
+(02) <mex:Metadata>
+(03) <mex:MetadataSection Dialect='wsdl:definitions'
+(04) Identifier='...'>
+(05) <wsdl:definitions ...>
+(06) ...
+(07) </wsdl:definitions>
+(08) </mex:MetadataSection>
+(09) </mex:Metadata>
+(10) </mex:GetMetadataResponse> </pre></div></div><p><a href="#mexNW">Example A-8</a> shows how the WSDL definitions metadata
+ might appear within a GetMetadataResponse message. Notice that
+ because the metadata returned only contains the WSDL and not
+ the associated FormatName URI, retrieving the Notificaton WSDL
+ in this fashion requires some other means to disambiguate multiple
+ Notification WSDL documents from each other as well as from any other
+ WSDL documents associated with the Event Source.
</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>,
@@ -2663,4 +2711,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9702">9702</a></td></tr><tr><td> 2010/05/13 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9610">9610</a></td></tr><tr><td> 2010/06/15 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9610">9610</a></td></tr><tr><td> 2010/08/17 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10339">10339</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=10339">10339</a></td></tr><tr><td> 2010/08/18 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10376">10376</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.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- wsevd.xml 5 Aug 2010 02:42:57 -0000 1.15
+++ wsevd.xml 18 Aug 2010 10:09:53 -0000 1.16
@@ -641,27 +641,24 @@
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in section 9 of WS-MetadataExchange
<bibref ref="MEX"/>.
- In particular, this specification RECOMMENDS that the Event Description
+ In particular, this specification RECOMMENDS that the Event Descriptions
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
+ by either embedding the Event Descriptions 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.
+ An event source MUST NOT have more than one EventDescriptions document.
</p>
<p>
- The following examples show how Event Description metadata might
+ The following examples show how Event Descriptions metadata might
appear within a WS-Eventing EventSource Policy assertion.
</p>
<example id="embedEVD">
- <head>Sample Embedded EventDescription Metadata</head>
+ <head>Sample Embedded Event Descriptions Metadata</head>
<eg>(01) <wse:EventSource ...>
(02) <wse:FormatName URI="..."/>
(03) <wsevd:EventDescriptions ...>
@@ -671,28 +668,54 @@
</example>
<p>
- <specref ref="embedEVD"/> shows how the Event Description metadata
+ <specref ref="embedEVD"/> shows how the Event Descriptions metadata
might be embedded directly within a WS-Eventing EventSource Policy
assertion.
</p>
<example id="refEVD">
- <head>Sample Reference to EventDescription Metadata</head>
+ <head>Sample Reference to Event Descriptions Metadata</head>
<eg>(01) <wse:EventSource ...>
(02) <wse:FormatName URI="..."/>
(03) <mex:Location
-(04) Type="evd:EventDescriptions"
+(04) Type="wsevd: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
+ <specref ref="embedEVD"/> except the embedded Event Descriptions
metadata is replaced with a reference to an HTTP resource whose
- representation is the Event Description metadata. The data can be
+ representation is the Event Descriptions metadata. The data can be
retrieved via an HTTP GET to the specified URL.
</p>
+
+ <example id="mexEVD">
+ <head>Sample GetMetadataResponse with Event Descriptions Metadata</head>
+ <eg>(01) <mex:GetMetadataResponse>
+(02) <mex:Metadata>
+(03) <mex:MetadataSection Dialect='wsevd:EventDescriptions'
+(04) Identifier='...'>
+(05) <wsevd:EventDescriptions ...>
+(06) ...
+(07) </wsevd:EventDescriptions>
+(08) </mex:MetadataSection>
+(09) </mex:Metadata>
+(10) </mex:GetMetadataResponse> </eg>
+ </example>
+
+ <p>
+ <specref ref="mexEVD"/> shows how the Event Descriptions metadata
+ might appear within a GetMetadataResponse message.
+ </p>
+
+ <p>
+ If an EventDescriptions document appears within a WS-MetadataExchange
+ MetadataSection, then the value of the @Identifier attribute, if present,
+ MUST be equal to the value of its
+ wsevd:EventDescription/@targetNamespace.
+ </p>
</div3>
<div3>
@@ -971,6 +994,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=9087">9087</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/08/18 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=10376">10376</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Wednesday, 18 August 2010 10:09:58 UTC