- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 01 Oct 2009 14:05:47 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv6250
Modified Files:
wseventing.html wseventing.xml
Log Message:
put xs:stuff in italics
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -d -r1.81 -r1.82
--- wseventing.xml 1 Oct 2009 14:01:02 -0000 1.81
+++ wseventing.xml 1 Oct 2009 14:05:45 -0000 1.82
@@ -3025,16 +3025,16 @@
</p>
<example>
- <eg><wse:EventDescriptions targetNamespace="xs:anyURI" ...>
+ <eg><wse:EventDescriptions targetNamespace="<emph>xs:anyURI</emph>" ...>
<wse:types>
- [ <xs:import namespace="xs:anyURI" schemaLocation="xs:anyURI"/> ? |
- <xs:schema targetNamespace="xs:anyURI"/> ?] *
- xs:any *
+ [ <xs:import namespace="<emph>xs:anyURI</emph>" schemaLocation="<emph>xs:anyURI</emph>"/> ? |
+ <xs:schema targetNamespace="<emph>xs:anyURI</emph>"/> ?] *
+ <emph>xs:any</emph>*
</wse:types>
- <wse:eventType name="xs:NCName" element="xs:QName" actionURI="xs:anyURI"? ...>
- xs:any *
+ <wse:eventType name="<emph>xs:NCName</emph>" element="<emph>xs:QName</emph>" actionURI="<emph>xs:anyURI</emph>"? ...>
+ <emph>xs:any</emph>*
</wse:eventType> +
- xs:any *
+ <emph>xs:any</emph>*
</wse:EventDescriptions></eg>
</example>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -d -r1.89 -r1.90
--- wseventing.html 1 Oct 2009 14:01:00 -0000 1.89
+++ wseventing.html 1 Oct 2009 14:05:45 -0000 1.90
@@ -85,13 +85,13 @@
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
A.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
- A.1.1 <a href="#iddiv3_1_2616">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2632">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2637">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2655">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2646">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2662">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2667">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2685">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2682">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2698">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2712">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2728">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/>
@@ -1683,16 +1683,16 @@
Event Types MAY be described within an EventDescriptions element where
they are defined by Global Element Declarations in XML Schema. The
EventDescriptions element has the following form:
- </p><div class="exampleOuter"><div class="exampleInner"><pre><wse:EventDescriptions targetNamespace="xs:anyURI" ...>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><wse:EventDescriptions targetNamespace="<em>xs:anyURI</em>" ...>
<wse:types>
- [ <xs:import namespace="xs:anyURI" schemaLocation="xs:anyURI"/> ? |
- <xs:schema targetNamespace="xs:anyURI"/> ?] *
- xs:any *
+ [ <xs:import namespace="<em>xs:anyURI</em>" schemaLocation="<em>xs:anyURI</em>"/> ? |
+ <xs:schema targetNamespace="<em>xs:anyURI</em>"/> ?] *
+ <em>xs:any</em>*
</wse:types>
- <wse:eventType name="xs:NCName" element="xs:QName" actionURI="xs:anyURI"? ...>
- xs:any *
+ <wse:eventType name="<em>xs:NCName</em>" element="<em>xs:QName</em>" actionURI="<em>xs:anyURI</em>"? ...>
+ <em>xs:any</em>*
</wse:eventType> +
- xs:any *
+ <em>xs:any</em>*
</wse:EventDescriptions></pre></div></div><p>
The XML Schema for the EventDesciptions element can be found in
<a href="#EDXSD"><b>E XML Schema for EventDescriptions</b></a>. The following describes additional, normative
@@ -1736,7 +1736,7 @@
serve as a description of the Event Type used in
<a href="#Table1">Example 2-1</a> and <a href="#EDExample">Example A-1</a>.
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2606" id="idexample_1_2606"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2636" id="idexample_1_2636"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wse="http://www.w3.org/2009/09/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1756,7 +1756,7 @@
GED for this Event Type is defined on line (08) as being of type
"{http://www.example.org/oceanwatch}:WindReportType".
</p><div class="div3">
-<h4><a name="iddiv3_1_2616" id="iddiv3_1_2616"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2646" id="iddiv3_1_2646"/>A.1.1 Retrieving Event Descriptions</h4><p>
Although there are many ways in which an Event Source can make its
EventDescriptions available, this specification RECOMMENDS the use of
the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1767,7 +1767,7 @@
be equal to the value of its wse:EventDescriptions/@targetNamespace. An
Event Source MUST NOT have more than one EventDescriptions document.
</p></div><div class="div3">
-<h4><a name="iddiv3_1_2632" id="iddiv3_1_2632"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2662" id="iddiv3_1_2662"/>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
@@ -1779,7 +1779,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_2637" id="iddiv4_1_2637"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2667" id="iddiv4_1_2667"/>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>
@@ -1793,7 +1793,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_2655" id="iddiv4_1_2655"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2685" id="iddiv4_1_2685"/>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>
@@ -1817,7 +1817,7 @@
successful Subscribe request that used a particular Format URI. The
following is an example of a Notification WSDL:
</p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2676" id="idexample_1_2676"/>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_2706" id="idexample_1_2706"/>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/"
@@ -1852,7 +1852,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2682" id="iddiv3_1_2682"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2712" id="iddiv3_1_2712"/>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>.
@@ -1868,7 +1868,7 @@
Format URI/@Identifier, there MUST NOT exist more than one
Notification WSDL document.
</p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2698" id="iddiv2_1_2698"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2728" id="iddiv2_1_2728"/>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 Thursday, 1 October 2009 14:05:49 UTC