- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 12 May 2010 18:37:10 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv21995
Modified Files:
wseventing.html wseventing.xml
Log Message:
fix some specrefs to be more readable
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.187
retrieving revision 1.188
diff -u -d -r1.187 -r1.188
--- wseventing.xml 12 May 2010 16:12:39 -0000 1.187
+++ wseventing.xml 12 May 2010 18:37:07 -0000 1.188
@@ -2689,14 +2689,14 @@
</wse:FilterDialect> *
<wse:MaxExpires ...> <emph>xs:duration</emph> </wse:MaxExpires> ?
<wse:FormatName URI="<emph>xs:anyURI</emph>" ...>
- <!-- Notification WSDL can go here - see <specref ref="Advertising"/> -->
+ <!-- Notification WSDL can go here - see <specref show="title" ref="Advertising"/> -->
<emph>xs:any</emph>*
</wse:FormatName> *
<wse:EndToSupported .../> ?
<wse:NotificationPolicy ...>
<emph>xs:any</emph>
</wse:NotificationPolicy> ?
- <!-- EventDescription data can go here - see <specref ref="Advertising"/> -->
+ <!-- EventDescription data can go here - see <specref show="title" ref="Advertising"/> -->
<emph>xs:any</emph>*
</wse:EventSource></eg>
</example>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.194
retrieving revision 1.195
diff -u -d -r1.194 -r1.195
--- wseventing.html 12 May 2010 16:12:39 -0000 1.194
+++ wseventing.html 12 May 2010 18:37:07 -0000 1.195
@@ -78,20 +78,20 @@
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
9 <a href="#metadata">WS-Eventing Metadata</a><br/>
9.1 <a href="#iddiv2_1_2139">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2246">SubscriptionManager Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2248">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2306">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2453">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2308">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2455">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
A.1 <a href="#ETypes">Event Types & Event Descriptions</a><br/>
- A.1.1 <a href="#iddiv3_1_2642">Retrieving Event Descriptions</a><br/>
- A.1.2 <a href="#iddiv3_1_2679">Bindings for Event Descriptions</a><br/>
- A.1.2.1 <a href="#iddiv4_1_2684">Binding for Unwrapped Notifications</a><br/>
- A.1.2.2 <a href="#iddiv4_1_2705">Binding for Wrapped Notifications</a><br/>
+ A.1.1 <a href="#iddiv3_1_2644">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2681">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2686">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2707">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2732">Retrieving Notification WSDLs</a><br/>
+ A.2.1 <a href="#iddiv3_1_2734">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/>
@@ -1525,14 +1525,14 @@
</wse:FilterDialect> *
<wse:MaxExpires ...> <em>xs:duration</em> </wse:MaxExpires> ?
<wse:FormatName URI="<em>xs:anyURI</em>" ...>
- <!-- Notification WSDL can go here - see <a href="#Advertising"><b>A Advertising Event Information</b></a> -->
+ <!-- Notification WSDL can go here - see <a href="#Advertising"><b>Advertising Event Information</b></a> -->
<em>xs:any</em>*
</wse:FormatName> *
<wse:EndToSupported .../> ?
<wse:NotificationPolicy ...>
<em>xs:any</em>
</wse:NotificationPolicy> ?
- <!-- EventDescription data can go here - see <a href="#Advertising"><b>A Advertising Event Information</b></a> -->
+ <!-- EventDescription data can go here - see <a href="#Advertising"><b>Advertising Event Information</b></a> -->
<em>xs:any</em>*
</wse:EventSource></pre></div></div><p>
The following describes additional, normative constraints on the
@@ -1596,7 +1596,7 @@
If the Event Source advertises EventDescription data then it
MUST appear as a child of the EventSource element.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2246" id="iddiv2_1_2246"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2248" id="iddiv2_1_2248"/>9.2 SubscriptionManager Assertion</h3><p>
Services indicate support for the
WS-Eventing's definition of a subscription manager
through the use of the Web Services
@@ -1665,7 +1665,7 @@
Yves Lafon (W3C/ERCIM).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2306" id="iddiv2_1_2306"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h3><a name="iddiv2_1_2308" id="iddiv2_1_2308"/>11.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
Key words for use in RFCs to Indicate Requirement Levels
</cite></a>
, S. Bradner, Author.
@@ -1722,7 +1722,7 @@
, E. Christensen, et al., Editors.
World Wide Web Consortium (W3C), 15 March 2001
Available at <a href="http://www.w3.org/TR/2001/NOTE-wsdl-20010315">http://www.w3.org/TR/2001/NOTE-wsdl-20010315</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2453" id="iddiv2_1_2453"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+<h3><a name="iddiv2_1_2455" id="iddiv2_1_2455"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
Web Services Make Connection (WS-MakeConnection)
</cite></a>
@@ -1821,7 +1821,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_2632" id="idexample_1_2632"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2634" id="idexample_1_2634"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) <wsevd:EventDescriptions
(02) targetNamespace="http://www.example.org/oceanwatch/notifications"
(03) xmlns:wsevd="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
(04) xmlns:ow="http://www.example.org/oceanwatch">
@@ -1841,7 +1841,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_2642" id="iddiv3_1_2642"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2644" id="iddiv3_1_2644"/>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>.
@@ -1879,7 +1879,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_2679" id="iddiv3_1_2679"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2681" id="iddiv3_1_2681"/>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
@@ -1891,7 +1891,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_2684" id="iddiv4_1_2684"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2686" id="iddiv4_1_2686"/>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>
@@ -1906,7 +1906,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="iddiv4_1_2705" id="iddiv4_1_2705"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2707" id="iddiv4_1_2707"/>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>
@@ -1932,7 +1932,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_2726" id="idexample_1_2726"/>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="idexample_1_2728" id="idexample_1_2728"/>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/"
@@ -1967,7 +1967,7 @@
(33) </wsdl:operation>
(34) </wsdl:binding>
(35) </wsdl:definitions></pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2732" id="iddiv3_1_2732"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2734" id="iddiv3_1_2734"/>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>.
Received on Wednesday, 12 May 2010 18:37:11 UTC