- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 04 Nov 2009 19:09:14 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv15006
Modified Files:
wseventing.html wseventing.xml wst.html wst.xml
Log Message:
add some hrefs
Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -d -r1.77 -r1.78
--- wst.xml 4 Nov 2009 17:18:11 -0000 1.77
+++ wst.xml 4 Nov 2009 19:09:12 -0000 1.78
@@ -1289,7 +1289,7 @@
</p>
<example>
- <eg>http://www.w3.org/&wstra.nsprefix;/ws-tra/fault</eg>
+ <eg><loc href="http://www.w3.org/&wstra.nsprefix;/ws-tra/fault">http://www.w3.org/&wstra.nsprefix;/ws-tra/fault</loc></eg>
</example>
<p>
@@ -2255,7 +2255,7 @@
</p>
<example>
- <eg>http://www.w3.org/&wstra.nsprefix;/ws-tra/TransferPolicy.xsd</eg>
+ <eg><loc href="http://www.w3.org/&wstra.nsprefix;/ws-tra/TransferPolicy.xsd">http://www.w3.org/&wstra.nsprefix;/ws-tra/TransferPolicy.xsd</loc></eg>
</example>
<p>
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -d -r1.107 -r1.108
--- wseventing.xml 4 Nov 2009 14:50:20 -0000 1.107
+++ wseventing.xml 4 Nov 2009 19:09:12 -0000 1.108
@@ -2050,7 +2050,7 @@
</p>
<example>
- <eg>http://www.w3.org/&wsevt.nsprefix;/ws-evt/fault</eg>
+ <eg><loc href="http://www.w3.org/&wsevt.nsprefix;/ws-evt/fault">http://www.w3.org/&wsevt.nsprefix;/ws-evt/fault</loc></eg>
</example>
<p>
Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -d -r1.79 -r1.80
--- wst.html 4 Nov 2009 17:18:11 -0000 1.79
+++ wst.html 4 Nov 2009 19:09:12 -0000 1.80
@@ -58,12 +58,12 @@
5.3 <a href="#PutDenied">PutDenied</a><br/>
6 <a href="#Security_Considerations">Security Considerations</a><br/>
7 <a href="#metadata">WS-Transfer Metadata</a><br/>
- 7.1 <a href="#iddiv2_1_1379">TransferResource Assertion</a><br/>
- 7.2 <a href="#iddiv2_1_1449">TransferResourceFactory Assertion</a><br/>
+ 7.1 <a href="#iddiv2_1_1384">TransferResource Assertion</a><br/>
+ 7.2 <a href="#iddiv2_1_1454">TransferResourceFactory Assertion</a><br/>
8 <a href="#acks">Acknowledgements</a><br/>
9 <a href="#refs">References</a><br/>
- 9.1 <a href="#iddiv2_1_1502">Normative References</a><br/>
- 9.2 <a href="#iddiv2_1_1675">Informative References</a><br/>
+ 9.1 <a href="#iddiv2_1_1507">Normative References</a><br/>
+ 9.2 <a href="#iddiv2_1_1680">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
@@ -776,7 +776,7 @@
Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults.
The <b>[Action]</b> property below MUST be used for faults
defined in this specification:
- </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/09/ws-tra/fault</pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-tra/fault">http://www.w3.org/2009/09/ws-tra/fault</a></pre></div></div><p>
The definitions of faults in this section use the following properties:
</p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element
is defined for the fault.<br/></p><p>
@@ -900,7 +900,7 @@
indicate a particular security mechanism used to protect the
WS-Transfer operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1379" id="iddiv2_1_1379"/>7.1 TransferResource Assertion</h3><p>
+<h3><a name="iddiv2_1_1384" id="iddiv2_1_1384"/>7.1 TransferResource Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Transfer specification's definition of a Transfer Resource
is through the use of the Web Services
@@ -968,7 +968,7 @@
the Global Element Declaration (GED) or type of this resource. This
QName may be used in order to retrieve the schema of the resource.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1449" id="iddiv2_1_1449"/>7.2 TransferResourceFactory Assertion</h3><p>
+<h3><a name="iddiv2_1_1454" id="iddiv2_1_1454"/>7.2 TransferResourceFactory Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Transfer specification's definition of a Transfer Resource Factory
is through the use of the Web Services
@@ -1040,7 +1040,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>9 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1502" id="iddiv2_1_1502"/>9.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_1507" id="iddiv2_1_1507"/>9.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.
@@ -1108,7 +1108,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_1675" id="iddiv2_1_1675"/>9.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
+<h3><a name="iddiv2_1_1680" id="iddiv2_1_1680"/>9.2 Informative References</h3><dl><dt class="label"><a name="WsFrag" id="WsFrag"/>WS-Fragment</dt><dd><a href="http://www.w3.org/TR/ws-fragment"><cite>
W3C Working Group Draft, "Web Services Fragment (WS-Fragment) 1.0"
</cite></a>
, D. Davis, et al., Editors.
@@ -1332,7 +1332,7 @@
<h2><a name="policyXSD" id="policyXSD"/>C Transfer Policy Schema</h2><p>
A normative copy of the XML Schema description for the Transfer
Policy assertions can be retrieved from the following address:
- </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/09/ws-tra/TransferPolicy.xsd</pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-tra/TransferPolicy.xsd">http://www.w3.org/2009/09/ws-tra/TransferPolicy.xsd</a></pre></div></div><p>
A non-normative copy of the XML schema is listed below for convenience.
</p><div class="exampleOuter"><div class="exampleInner"><pre><xs:schema
targetNamespace="http://www.w3.org/2009/09/ws-trp"
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.115
retrieving revision 1.116
diff -u -d -r1.115 -r1.116
--- wseventing.html 4 Nov 2009 14:50:20 -0000 1.115
+++ wseventing.html 4 Nov 2009 19:09:12 -0000 1.116
@@ -75,22 +75,22 @@
7.2 <a href="#AccessControl">Access Control</a><br/>
8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
9 <a href="#metadata">WS-Eventing Metadata</a><br/>
- 9.1 <a href="#iddiv2_1_2177">EventSource Assertion</a><br/>
- 9.2 <a href="#iddiv2_1_2244">SubscriptionManager Assertion</a><br/>
+ 9.1 <a href="#iddiv2_1_2182">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2249">SubscriptionManager Assertion</a><br/>
10 <a href="#acks">Acknowledgements</a><br/>
11 <a href="#refs">References</a><br/>
- 11.1 <a href="#iddiv2_1_2315">Normative References</a><br/>
- 11.2 <a href="#iddiv2_1_2436">Informative References</a><br/>
+ 11.1 <a href="#iddiv2_1_2320">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2441">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_2742">Retrieving Event Descriptions</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.1.1 <a href="#iddiv3_1_2747">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2768">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2773">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2791">Binding for Wrapped Notifications</a><br/>
A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
- A.2.1 <a href="#iddiv3_1_2813">Retrieving Notification WSDLs</a><br/>
- A.3 <a href="#iddiv2_1_2834">Multiple Event Information Metadata Sections</a><br/>
+ A.2.1 <a href="#iddiv3_1_2818">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2839">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/>
@@ -1294,7 +1294,7 @@
Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults.
The <b>[Action]</b> property below MUST be used for faults
defined in this specification:
- </p><div class="exampleOuter"><div class="exampleInner"><pre>http://www.w3.org/2009/09/ws-evt/fault</pre></div></div><p>
+ </p><div class="exampleOuter"><div class="exampleInner"><pre><a href="http://www.w3.org/2009/09/ws-evt/fault">http://www.w3.org/2009/09/ws-evt/fault</a></pre></div></div><p>
The definitions of faults in this section use the following properties:
</p><p><b>[Code]</b> The fault code.<br/><b>[Subcode]</b> The fault subcode.<br/><b>[Reason]</b> The English language reason element.<br/><b>[Detail]</b> The detail element. If absent, no detail element
is defined for the fault.<br/></p><p>
@@ -1522,7 +1522,7 @@
indicate a particular security mechanism used to protect the
WS-Eventing operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_2177" id="iddiv2_1_2177"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2182" id="iddiv2_1_2182"/>9.1 EventSource Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Eventing specification's definition of an event source
is through the use of the Web Services
@@ -1580,7 +1580,7 @@
When present, this OPTIONAL parameter indicates support for the
specified event delivery format name URI.
</p></dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2244" id="iddiv2_1_2244"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2249" id="iddiv2_1_2249"/>9.2 SubscriptionManager Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Eventing specification's definition of a subscription manager
is through the use of the Web Services
@@ -1664,7 +1664,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2315" id="iddiv2_1_2315"/>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_2320" id="iddiv2_1_2320"/>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.
@@ -1711,7 +1711,7 @@
, A. Vedamuthu, et al., Editors.
World Wide Web Consortium (W3C), 4 September 2007.
Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2436" id="iddiv2_1_2436"/>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_2441" id="iddiv2_1_2441"/>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>
@@ -1901,7 +1901,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_2732" id="idexample_1_2732"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) <wse:EventDescriptions
+<div class="exampleHeader"><a name="idexample_1_2737" id="idexample_1_2737"/>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">
@@ -1921,7 +1921,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_2742" id="iddiv3_1_2742"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2747" id="iddiv3_1_2747"/>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>.
@@ -1932,7 +1932,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_2763" id="iddiv3_1_2763"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2768" id="iddiv3_1_2768"/>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
@@ -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_2768" id="iddiv4_1_2768"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2773" id="iddiv4_1_2773"/>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_2786" id="iddiv4_1_2786"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2791" id="iddiv4_1_2791"/>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_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/"
+<div class="exampleHeader"><a name="idexample_1_2812" id="idexample_1_2812"/>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_2813" id="iddiv3_1_2813"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2818" id="iddiv3_1_2818"/>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_2834" id="iddiv2_1_2834"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2839" id="iddiv2_1_2839"/>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 Wednesday, 4 November 2009 19:09:24 UTC