- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 06 Oct 2009 16:42:05 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv15264
Modified Files:
wseventing.html wseventing.xml wsenum.html wsenum.xml
Log Message:
typo
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -d -r1.91 -r1.92
--- wseventing.xml 6 Oct 2009 16:20:31 -0000 1.91
+++ wseventing.xml 6 Oct 2009 16:42:03 -0000 1.92
@@ -1166,11 +1166,6 @@
<label> <kw>[Body]</kw>/wse:SubscribeResponse/wse:GrantedExpires </label>
<def>
<p>
- The value of this OPTIONAL element indicates the expiration time (or
- duration) granted by the event source. If this element is missing the
- granted expiration time is indefinite.
- </p>
- <p>
The expiration time assigned by the event source. The
expiration time MAY be either an absolute time or a duration
but SHOULD be of the same type as the requested expiration
@@ -2181,7 +2176,7 @@
<tr>
<td><kw>[Subcode]</kw></td>
- <td>wse:InvalidExpirationTime</td>
+ <td>wse:ExpirationTimeExceeded</td>
</tr>
<tr>
@@ -3696,7 +3691,7 @@
<xs:sequence>
<xs:element name="SubscriptionManager"
type="wsa:EndpointReferenceType" />
- <xs:element name="Expires" type="tns:ExpirationType" />
+ <xs:element name="GrantedExpires" type="tns:MiniExpirationType" />
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
@@ -3727,7 +3722,7 @@
<xs:element name="RenewResponse">
<xs:complexType>
<xs:sequence>
- <xs:element name="Expires" type="tns:ExpirationType"
+ <xs:element name="GrantedExpires" type="tns:MiniExpirationType"
minOccurs="0" />
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded" />
@@ -3751,7 +3746,7 @@
<xs:element name="GetStatusResponse">
<xs:complexType>
<xs:sequence>
- <xs:element name="Expires" type="tns:ExpirationType"
+ <xs:element name="GrantedExpires" type="tns:MiniExpirationType"
minOccurs="0" />
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded" />
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -d -r1.99 -r1.100
--- wseventing.html 6 Oct 2009 16:20:31 -0000 1.99
+++ wseventing.html 6 Oct 2009 16:42:03 -0000 1.100
@@ -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_2175">EventSource Assertion</a><br/>
+ 9.2 <a href="#iddiv2_1_2242">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_2313">Normative References</a><br/>
+ 11.2 <a href="#iddiv2_1_2434">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_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.1 <a href="#iddiv3_1_2740">Retrieving Event Descriptions</a><br/>
+ A.1.2 <a href="#iddiv3_1_2756">Bindings for Event Descriptions</a><br/>
+ A.1.2.1 <a href="#iddiv4_1_2761">Binding for Unwrapped Notifications</a><br/>
+ A.1.2.2 <a href="#iddiv4_1_2779">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_2806">Retrieving Notification WSDLs</a><br/>
+ A.3 <a href="#iddiv2_1_2822">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/>
@@ -658,10 +658,6 @@
reference parameter to distinguish among the active
subscriptions.
</p></dd><dt class="label"><b>[Body]</b>/wse:SubscribeResponse/wse:GrantedExpires </dt><dd><p>
- The value of this OPTIONAL element indicates the expiration time (or
- duration) granted by the event source. If this element is missing the
- granted expiration time is indefinite.
- </p><p>
The expiration time assigned by the event source. The
expiration time MAY be either an absolute time or a duration
but SHOULD be of the same type as the requested expiration
@@ -1322,7 +1318,7 @@
<h3><a name="ExpirationTimeExceeded" id="ExpirationTimeExceeded"/>6.3 ExpirationTimeExceeded</h3><p>
This fault is generated when a request specifies an
expiration that is not within the min/max range.
- </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:InvalidExpirationTime</td></tr><tr><td><b>[Reason]</b></td><td>The expiration time requested is not within the min/max range.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
+ </p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:ExpirationTimeExceeded</td></tr><tr><td><b>[Reason]</b></td><td>The expiration time requested is not within the min/max range.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="UnsupportedExpirationType" id="UnsupportedExpirationType"/>6.4 UnsupportedExpirationType</h3><p>
This fault is generated when a Subscribe request specifies an
expiration time and the event source is only capable of accepting
@@ -1492,7 +1488,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_2175" id="iddiv2_1_2175"/>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
@@ -1550,7 +1546,7 @@
When present, this 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_2242" id="iddiv2_1_2242"/>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
@@ -1634,7 +1630,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_2313" id="iddiv2_1_2313"/>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.
@@ -1681,7 +1677,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_2434" id="iddiv2_1_2434"/>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>
@@ -1871,7 +1867,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_2730" id="idexample_1_2730"/>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">
@@ -1891,7 +1887,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_2740" id="iddiv3_1_2740"/>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>.
@@ -1902,7 +1898,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_2758" id="iddiv3_1_2758"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2756" id="iddiv3_1_2756"/>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
@@ -1914,7 +1910,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_2761" id="iddiv4_1_2761"/>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>
@@ -1928,7 +1924,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_2779" id="iddiv4_1_2779"/>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>
@@ -1952,7 +1948,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_2800" id="idexample_1_2800"/>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/"
@@ -1987,7 +1983,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_2806" id="iddiv3_1_2806"/>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>.
@@ -2003,7 +1999,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_2822" id="iddiv2_1_2822"/>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
@@ -2133,7 +2129,7 @@
<xs:sequence>
<xs:element name="SubscriptionManager"
type="wsa:EndpointReferenceType" />
- <xs:element name="Expires" type="tns:ExpirationType" />
+ <xs:element name="GrantedExpires" type="tns:MiniExpirationType" />
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
@@ -2164,7 +2160,7 @@
<xs:element name="RenewResponse">
<xs:complexType>
<xs:sequence>
- <xs:element name="Expires" type="tns:ExpirationType"
+ <xs:element name="GrantedExpires" type="tns:MiniExpirationType"
minOccurs="0" />
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded" />
@@ -2188,7 +2184,7 @@
<xs:element name="GetStatusResponse">
<xs:complexType>
<xs:sequence>
- <xs:element name="Expires" type="tns:ExpirationType"
+ <xs:element name="GrantedExpires" type="tns:MiniExpirationType"
minOccurs="0" />
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded" />
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -d -r1.71 -r1.72
--- wsenum.html 6 Oct 2009 16:40:20 -0000 1.71
+++ wsenum.html 6 Oct 2009 16:42:03 -0000 1.72
@@ -68,11 +68,11 @@
4.10 <a href="#UnusableEPR">UnusableEPR</a><br/>
5 <a href="#Security">Security Considerations</a><br/>
6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
- 6.1 <a href="#iddiv2_1_1996">Enumeration Assertion</a><br/>
+ 6.1 <a href="#iddiv2_1_1994">Enumeration Assertion</a><br/>
7 <a href="#acks">Acknowledgements</a><br/>
8 <a href="#refs">References</a><br/>
- 8.1 <a href="#iddiv2_1_2085">Normative References</a><br/>
- 8.2 <a href="#iddiv2_1_2271">Informative References</a><br/>
+ 8.1 <a href="#iddiv2_1_2083">Normative References</a><br/>
+ 8.2 <a href="#iddiv2_1_2269">Informative References</a><br/>
</p>
<h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
B <a href="#WSDL">WSDL</a><br/>
@@ -490,10 +490,6 @@
The following describes additional, normative
constraints on the outline listed above:
</p><dl><dt class="label"><b>[Body]</b>/wsen:EnumerateResponse/wsen:GrantedExpires </dt><dd><p>
- The value of this OPTIONAL element indicates the expiration time (or
- duration) granted by the event source. If this element is missing the
- granted expiration time is indefinite.
- </p><p>
The expiration time assigned by the data
source. The expiration time MAY be either an absolute time or a
duration but SHOULD be of the same type as the requested expiration
@@ -1276,7 +1272,7 @@
indicate a particular security mechanism used to protect the
WS-Enumeration operations supported by this endpoint.
</p><div class="div2">
-<h3><a name="iddiv2_1_1996" id="iddiv2_1_1996"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_1994" id="iddiv2_1_1994"/>6.1 Enumeration Assertion</h3><p>
The mechanism for indicating that a binding or endpoint conforms to the
WS-Enumeration specification is through the use of the Web Services
Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1365,7 +1361,7 @@
Yves Lafon (W3C).
</p></div><div class="div1">
<h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2085" id="iddiv2_1_2085"/>8.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_2083" id="iddiv2_1_2083"/>8.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.
@@ -1437,7 +1433,7 @@
, J. Clark, S. DeRose, Editors.
World Wide Web Consortium (W3C), 16 November 1999.
Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2271" id="iddiv2_1_2271"/>8.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_2269" id="iddiv2_1_2269"/>8.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
OASIS Standard, "Web Services Secure Conversation
(WS-SecureConversation) 1.4"
</cite></a>
Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -d -r1.64 -r1.65
--- wsenum.xml 6 Oct 2009 16:40:20 -0000 1.64
+++ wsenum.xml 6 Oct 2009 16:42:03 -0000 1.65
@@ -855,11 +855,6 @@
<label> <kw>[Body]</kw>/wsen:EnumerateResponse/wsen:GrantedExpires </label>
<def>
<p>
- The value of this OPTIONAL element indicates the expiration time (or
- duration) granted by the event source. If this element is missing the
- granted expiration time is indefinite.
- </p>
- <p>
The expiration time assigned by the data
source. The expiration time MAY be either an absolute time or a
duration but SHOULD be of the same type as the requested expiration
Received on Tuesday, 6 October 2009 16:42:08 UTC