- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 03 Nov 2009 22:38:54 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv29373
Modified Files:
wseventing.html wseventing.xml
Log Message:
more minor tweaks
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -d -r1.105 -r1.106
--- wseventing.xml 3 Nov 2009 22:09:16 -0000 1.105
+++ wseventing.xml 3 Nov 2009 22:38:52 -0000 1.106
@@ -3242,7 +3242,7 @@
(06) <wsa:Action>
(07) http://www.w3.org/&wsevt.nsprefix;/ws-evt/wrap/GenericSinkPortType/NotifyEvent
(08) </wsa:Action>
-(09) . . .
+(09) ...
(10) </s12:Header>
(11) <s12:Body>
(12) <wse:Notify actionURI="http://www.example.org/oceanwatch/2003/WindReport">
@@ -3413,7 +3413,7 @@
</p>
<example>
- <eg>http://www.w3.org/&wsevt.nsprefix;/ws-evt/EventDescriptions</eg>
+ <eg><loc href="http://www.w3.org/&wsevt.nsprefix;/ws-evt/EventDescriptions">http://www.w3.org/&wsevt.nsprefix;/ws-evt/EventDescriptions</loc></eg>
</example>
<p>
@@ -3429,7 +3429,7 @@
For any Notification Format it SHOULD be possible to determine how a
given wse:eventType will appear on the wire as a notification in a
subscription created with that format. The following sections define
- how wse:eventTypes bind to notifications for the two notification
+ how wse:eventTypes bind to notifications for the two Notification
Formats defined in this specification; Unwrapped and Wrapped.
Specifications or profiles that define additional Notification Formats
SHOULD define how wse:eventTypes bind to the notifications for those
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -d -r1.113 -r1.114
--- wseventing.html 3 Nov 2009 22:09:16 -0000 1.113
+++ wseventing.html 3 Nov 2009 22:38:52 -0000 1.114
@@ -85,12 +85,12 @@
<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_2742">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2758">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2763">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2781">Binding for Wrapped Notifications</a><br/>
+ A.1.2 <a href="#iddiv3_1_2763">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2768">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2786">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2808">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2824">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2813">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2829">Multiple Event Information Metadata Sections</a><br/>
B <a href="#Schema">XML Schema</a><br/>
C <a href="#WSDL">WSDL</a><br/>
D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -1824,7 +1824,7 @@
(06) <wsa:Action>
(07) http://www.w3.org/2009/09/ws-evt/wrap/GenericSinkPortType/NotifyEvent
(08) </wsa:Action>
-(09) . . .
+(09) ...
(10) </s12:Header>
(11) <s12:Body>
(12) <wse:Notify actionURI="http://www.example.org/oceanwatch/2003/WindReport">
@@ -1927,16 +1927,16 @@
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>http://www.w3.org/2009/09/ws-evt/EventDescriptions</pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-evt/EventDescriptions">http://www.w3.org/2009/09/ws-evt/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
event source MUST NOT have more than one EventDescriptions document.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_2758" id="iddiv3_1_2758"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2763" id="iddiv3_1_2763"/>A.1.2 Bindings for Event Descriptions</h4><p>
For any Notification Format it SHOULD be possible to determine how a
given wse:eventType will appear on the wire as a notification in a
subscription created with that format. The following sections define
- how wse:eventTypes bind to notifications for the two notification
+ how wse:eventTypes bind to notifications for the two Notification
Formats defined in this specification; Unwrapped and Wrapped.
Specifications or profiles that define additional Notification Formats
SHOULD define how wse:eventTypes bind to the notifications for those
@@ -1944,7 +1944,7 @@
Format, implementations MAY provide a Notification WSDL (see below)
that explicitly describes the notification operations.
</p><div class="div4">
-<h5><a name="iddiv4_1_2763" id="iddiv4_1_2763"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2768" id="iddiv4_1_2768"/>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>
@@ -1958,7 +1958,7 @@
of the wse:eventType element corresponding to the type of the
event being transmitted.
</p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2781" id="iddiv4_1_2781"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2786" id="iddiv4_1_2786"/>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>
@@ -1982,7 +1982,7 @@
successful Subscribe request that used a particular Format IRI. The
following is an example of a Notification WSDL:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2802" id="idexample_1_2802"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2807" id="idexample_1_2807"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:xs="http://www.w3.org/2001/XMLSchema"
(04) xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -2017,7 +2017,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2808" id="iddiv3_1_2808"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2813" id="iddiv3_1_2813"/>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>.
@@ -2033,7 +2033,7 @@
Format IRI/@Identifier, there MUST NOT exist more than one
Notification WSDL document.
</p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2824" id="iddiv2_1_2824"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2829" id="iddiv2_1_2829"/>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
Received on Tuesday, 3 November 2009 22:39:04 UTC