W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > October 2009

WWW/2002/ws/ra/edcopies wsenum.html,1.78,1.79 wsenum.xml,1.71,1.72 wseventing.html,1.106,1.107 wseventing.xml,1.98,1.99

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 27 Oct 2009 23:33:58 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1N2vY6-0005pp-IG@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv22245

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
Log Message:
7586, 7588, 7828


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -d -r1.98 -r1.99
--- wseventing.xml	20 Oct 2009 23:59:21 -0000	1.98
+++ wseventing.xml	27 Oct 2009 23:33:56 -0000	1.99
@@ -959,6 +959,35 @@
         @max attribute values, it MUST generate a 
         wse:ExpirationTimeExceeded fault. 
        </p>
+
+       <p>
+        The value of the wse:Expires element as well as those of its @min and 
+        @max attributes MAY be either a duration (xs:duration) or a specific 
+        time (xs:dateTime). Event Sources and Subscription Managers MUST 
+        accept duration values and MAY accept specific time values. Upon 
+        receiving a request that contains specific time values, an Event 
+        Source or Subscription Manager that does not support such value 
+        types MUST fail the request and generate a 
+        wse:UnsupportedExpirationType fault.
+       </p>
+
+       <p>
+        The value types in a wse:Expires element MAY differ among the 
+        element and its attributes. For example, the element value may be a 
+        duration while the @max attribute may be a specific time. Regardless 
+        of the value types, it must be true that wse:Expires/@min &lt;= 
+        wse:Expires &lt;= wse:Expires/@max as interpreted by the Event Source 
+        or Subscription manager at the time the wse:Subscribe request is 
+        processed. If this is not true, the request MUST fail and the 
+        receiver MUST generate a wse:InvalidExpirationTime fault.
+       </p>
+
+       <p>
+        If a Subscriber chooses to use specific time values in a request, 
+        it is RECOMMENDED that these values include a time zone component. 
+        Specific time values that lack a time zone will be interpreted in 
+        the local time zone of the receiver.
+       </p>
       </def>
      </gitem>
 
@@ -1186,10 +1215,21 @@
       <label> <kw>[Body]</kw>/wse:SubscribeResponse/wse:GrantedExpires </label>
       <def>
        <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
-        (if any).
+        The expiration time assigned by the Event Source. The
+        expiration time MAY be either a specific time or a duration
+        but MUST be of the same type as the wse:Expires element of
+        the corresponding request. If the corresponding request
+        did not contain a wse:Expires element, this element MUST be
+        a duration (xs:duration).
+       </p>
+
+       <p>
+        When expressed as a duration, the wse:GrantedExpires element 
+        designates a time interval that began at the moment the 
+        Subscription is created. Although this specification cannot dictate 
+        when, during the processing of a Subscribe request, a Subscription is 
+        created, the Event Source MUST start the expiration interval at or 
+        before it transmits the wse:SubscribeResponse message.
        </p>
 
        <p>
@@ -4560,7 +4600,7 @@
      <tr>
       <td> 2009/10/05 </td>
       <td> DD </td>
-      <td> Added resolution of issue 
+      <td> Added resolution of issues
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6402">6402</loc>,
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6721">6721</loc>
       </td>
@@ -4607,6 +4647,15 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/27 </td>
+      <td> DD </td>
+      <td> Added resolution of issues
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7586">7586</loc>,
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7588">7588</loc>,
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7828">7828</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -d -r1.106 -r1.107
--- wseventing.html	20 Oct 2009 23:59:21 -0000	1.106
+++ wseventing.html	27 Oct 2009 23:33:56 -0000	1.107
@@ -75,22 +75,22 @@
 &nbsp;&nbsp;&nbsp;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/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2177">EventSource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2244">SubscriptionManager Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2185">EventSource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2252">SubscriptionManager Assertion</a><br/>
 10 <a href="#acks">Acknowledgements</a><br/>
 11 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2315">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2436">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2323">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2444">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/>
 &nbsp;&nbsp;&nbsp;A.1 <a href="#ETypes">Event Types &amp; Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2742">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2758">Bindings for Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2763">Binding for Unwrapped Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2781">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2750">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2766">Bindings for Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2771">Binding for Unwrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2789">Binding for Wrapped Notifications</a><br/>
 &nbsp;&nbsp;&nbsp;A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2808">Retrieving Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2824">Multiple Event Information Metadata Sections</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2816">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2832">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/>
@@ -555,6 +555,29 @@
         able to grant an expiry time within range indicated by the @min and 
         @max attribute values, it MUST generate a 
         wse:ExpirationTimeExceeded fault. 
+       </p><p>
+        The value of the wse:Expires element as well as those of its @min and 
+        @max attributes MAY be either a duration (xs:duration) or a specific 
+        time (xs:dateTime). Event Sources and Subscription Managers MUST 
+        accept duration values and MAY accept specific time values. Upon 
+        receiving a request that contains specific time values, an Event 
+        Source or Subscription Manager that does not support such value 
+        types MUST fail the request and generate a 
+        wse:UnsupportedExpirationType fault.
+       </p><p>
+        The value types in a wse:Expires element MAY differ among the 
+        element and its attributes. For example, the element value may be a 
+        duration while the @max attribute may be a specific time. Regardless 
+        of the value types, it must be true that wse:Expires/@min &lt;= 
+        wse:Expires &lt;= wse:Expires/@max as interpreted by the Event Source 
+        or Subscription manager at the time the wse:Subscribe request is 
+        processed. If this is not true, the request MUST fail and the 
+        receiver MUST generate a wse:InvalidExpirationTime fault.
+       </p><p>
+        If a Subscriber chooses to use specific time values in a request, 
+        it is RECOMMENDED that these values include a time zone component. 
+        Specific time values that lack a time zone will be interpreted in 
+        the local time zone of the receiver.
        </p></dd><dt class="label"><b>[Body]</b>/wse:Subscribe/wse:Expires@min </dt><dd><p>
         The implied default is PT0S. This specifies the minimum expiration 
         time that the event subscriber is willing to accept.
@@ -674,10 +697,19 @@
         reference parameter to distinguish among the active
         subscriptions. 
        </p></dd><dt class="label"><b>[Body]</b>/wse:SubscribeResponse/wse:GrantedExpires </dt><dd><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
-        (if any).
+        The expiration time assigned by the Event Source. The
+        expiration time MAY be either a specific time or a duration
+        but MUST be of the same type as the wse:Expires element of
+        the corresponding request. If the corresponding request
+        did not contain a wse:Expires element, this element MUST be
+        a duration (xs:duration).
+       </p><p>
+        When expressed as a duration, the wse:GrantedExpires element 
+        designates a time interval that began at the moment the 
+        Subscription is created. Although this specification cannot dictate 
+        when, during the processing of a Subscribe request, a Subscription is 
+        created, the Event Source MUST start the expiration interval at or 
+        before it transmits the wse:SubscribeResponse message.
        </p><p>
         If this element does not appear, then the subscription
         will not expire. That is, the subscription has an indefinite
@@ -1495,7 +1527,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_2185" id="iddiv2_1_2185"/>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
@@ -1553,7 +1585,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_2252" id="iddiv2_1_2252"/>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
@@ -1637,7 +1669,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_2323" id="iddiv2_1_2323"/>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.
@@ -1684,7 +1716,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_2444" id="iddiv2_1_2444"/>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>
@@ -1874,7 +1906,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) &lt;wse:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2740" id="idexample_1_2740"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;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"&gt;
@@ -1894,7 +1926,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_2750" id="iddiv3_1_2750"/>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>.
@@ -1905,7 +1937,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_2766" id="iddiv3_1_2766"/>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 
@@ -1917,7 +1949,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_2771" id="iddiv4_1_2771"/>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>
@@ -1931,7 +1963,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_2789" id="iddiv4_1_2789"/>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>
@@ -1955,7 +1987,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) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2810" id="idexample_1_2810"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;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/"
@@ -1990,7 +2022,7 @@
 (33)     &lt;/wsdl:operation&gt;
 (34)   &lt;/wsdl:binding&gt;
 (35) &lt;/wsdl:definitions&gt;</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_2816" id="iddiv3_1_2816"/>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>.
@@ -2006,7 +2038,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_2832" id="iddiv2_1_2832"/>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 

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -d -r1.78 -r1.79
--- wsenum.html	26 Oct 2009 15:38:01 -0000	1.78
+++ wsenum.html	27 Oct 2009 23:33:56 -0000	1.79
@@ -67,11 +67,11 @@
 &nbsp;&nbsp;&nbsp;4.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
 5 <a href="#Security">Security Considerations</a><br/>
 6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_1943">Enumeration Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_1951">Enumeration Assertion</a><br/>
 7 <a href="#acks">Acknowledgements</a><br/>
 8 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_2032">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2218">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_2040">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2226">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/>
@@ -385,24 +385,47 @@
         message.  The endpoint to which the EndTo EPR 
         refers MUST support the EnumerationEndPortType portType.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:Expires </dt><dd><p>
-        This OPTIONAL element can be used by the Subscriber to indicate the
-        expiration time of the requested Subscription. The value of this
-        element indicates the desired expiration time for the subscription.
+        This OPTIONAL element can be used by the consumer to indicate the
+        expiration time of the requested enumeration. The value of this
+        element indicates the desired expiration time for the enumeration.
         The implied default is indefinite (no expiry). The value of this
         element MUST be between the values of the @min and @max attributes
-        inclusive. If the request is malformed, the event source
+        inclusive. If the request is malformed, the data source
         MUST generate a wsen:InvalidExpirationTime fault.
        </p><p>
-        If the wsen:Expires element is present and the event source is not
+        If the wsen:Expires element is present and the data source is not
         able to grant an expiry time within range indicated by the @min and
         @max attribute values, it MUST generate a
         wsen:ExpirationTimeExceeded fault.
+       </p><p>
+        The value of the wsen:Expires element as well as those of its @min and
+        @max attributes MAY be either a duration (xs:duration) or a specific
+        time (xs:dateTime). Data sources MUST
+        accept duration values and MAY accept specific time values. Upon
+        receiving a request that contains specific time values, a data
+        source that does not support such value
+        types MUST fail the request and generate a
+        wsen:UnsupportedExpirationType fault.
+       </p><p>
+        The value types in a wsen:Expires element MAY differ among the
+        element and its attributes. For example, the element value may be a
+        duration while the @max attribute may be a specific time. Regardless
+        of the value types, it must be true that wsen:Expires/@min &lt;=
+        wsen:Expires &lt;= wsen:Expires/@max as interpreted by the data source
+        at the time the wsen:Enumerate request is
+        processed. If this is not true, the request MUST fail and the
+        receiver MUST generate a wsen:InvalidExpirationTime fault.
+       </p><p>
+        If a consumer chooses to use specific time values in a request,
+        it is RECOMMENDED that these values include a time zone component.
+        Specific time values that lack a time zone will be interpreted in
+        the local time zone of the receiver.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:Expires@min </dt><dd><p>
         The implied default is PT0S. This specifies the minimum expiration
-        time that the event subscriber is willing to accept.
+        time that the consumer is willing to accept.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:Expires@max </dt><dd><p>
         The implied default is indefinite (no expiry). This specifies the
-        maximum expiration time that the event subscriber is willing to accept.
+        maximum expiration time that the consumer is willing to accept.
        </p></dd><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:Expires@exact </dt><dd><p>
         The default value is "false" in which case this attribute has no
         effect. If this attribute value is "true" both @min and @max
@@ -473,7 +496,7 @@
      wsa:Address IRI.
      Detecting these errors during Enumerate processing will lessen the chances
      of the consumer creating an unusable enumeration.  If this check is
-     performed and a problem is detected then the event source MUST generate
+     performed and a problem is detected then the data source MUST generate
      a wsen:UnusableEPR fault rather than returning the EnumerateResponse
      message.
     </p><p>
@@ -495,10 +518,19 @@
      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 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
-        (if any).
+        The expiration time assigned by the data source. The
+        expiration time MAY be either a specific time or a duration
+        but MUST be of the same type as the wsen:Expires element of
+        the corresponding request. If the corresponding request
+        did not contain a wsen:Expires element, this element MUST be
+        a duration (xs:duration).
+       </p><p>
+        When expressed as a duration, the wsen:GrantedExpires element
+        designates a time interval that began at the moment the
+        enumeration is created. Although this specification cannot dictate
+        when, during the processing of a Enumerate request, an enumeration is
+        created, the data source MUST start the expiration interval at or
+        before it transmits the wsen:EnumerateResponse message.
        </p><p>
         If this element does not appear, then the
         enumeration will not expire. That is, the enumeration has an
@@ -886,7 +918,7 @@
     </p></div><div class="div2">
 <h3><a name="GetStatus" id="GetStatus"/>3.4 GetStatus</h3><p>
      To get the status of an enumeration, the
-     subscriber sends a request of the following form to the data
+     consumer sends a request of the following form to the data
      source:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/09/ws-enu/GetStatus
@@ -1267,7 +1299,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_1943" id="iddiv2_1_1943"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_1951" id="iddiv2_1_1951"/>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 - 
@@ -1356,7 +1388,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_2032" id="iddiv2_1_2032"/>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_2040" id="iddiv2_1_2040"/>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. 
@@ -1428,7 +1460,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_2218" id="iddiv2_1_2218"/>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_2226" id="iddiv2_1_2226"/>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>
@@ -1923,4 +1955,7 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7827">7827</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7068">7068</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7811">7811</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</a></td></tr><tr><td> 2009/10/20 </td><td> DD </td><td> Added resolution of issues
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7586">7586</a>,
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7588">7588</a>,
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7828">7828</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -d -r1.71 -r1.72
--- wsenum.xml	26 Oct 2009 15:38:01 -0000	1.71
+++ wsenum.xml	27 Oct 2009 23:33:56 -0000	1.72
@@ -656,22 +656,51 @@
       <label> <kw>[Body]</kw>/wsen:Enumerate/wsen:Expires </label>
       <def>
        <p>
-        This OPTIONAL element can be used by the Subscriber to indicate the
-        expiration time of the requested Subscription. The value of this
-        element indicates the desired expiration time for the subscription.
+        This OPTIONAL element can be used by the consumer to indicate the
+        expiration time of the requested enumeration. The value of this
+        element indicates the desired expiration time for the enumeration.
         The implied default is indefinite (no expiry). The value of this
         element MUST be between the values of the @min and @max attributes
-        inclusive. If the request is malformed, the event source
+        inclusive. If the request is malformed, the data source
         MUST generate a wsen:InvalidExpirationTime fault.
        </p>
 
        <p>
-        If the wsen:Expires element is present and the event source is not
+        If the wsen:Expires element is present and the data source is not
         able to grant an expiry time within range indicated by the @min and
         @max attribute values, it MUST generate a
         wsen:ExpirationTimeExceeded fault.
        </p>
 
+       <p>
+        The value of the wsen:Expires element as well as those of its @min and
+        @max attributes MAY be either a duration (xs:duration) or a specific
+        time (xs:dateTime). Data sources MUST
+        accept duration values and MAY accept specific time values. Upon
+        receiving a request that contains specific time values, a data
+        source that does not support such value
+        types MUST fail the request and generate a
+        wsen:UnsupportedExpirationType fault.
+       </p>
+
+       <p>
+        The value types in a wsen:Expires element MAY differ among the
+        element and its attributes. For example, the element value may be a
+        duration while the @max attribute may be a specific time. Regardless
+        of the value types, it must be true that wsen:Expires/@min &lt;=
+        wsen:Expires &lt;= wsen:Expires/@max as interpreted by the data source
+        at the time the wsen:Enumerate request is
+        processed. If this is not true, the request MUST fail and the
+        receiver MUST generate a wsen:InvalidExpirationTime fault.
+       </p>
+
+       <p>
+        If a consumer chooses to use specific time values in a request,
+        it is RECOMMENDED that these values include a time zone component.
+        Specific time values that lack a time zone will be interpreted in
+        the local time zone of the receiver.
+       </p>
+
       </def>
      </gitem>
 
@@ -680,7 +709,7 @@
       <def>
        <p>
         The implied default is PT0S. This specifies the minimum expiration
-        time that the event subscriber is willing to accept.
+        time that the consumer is willing to accept.
        </p>
       </def>
      </gitem>
@@ -690,7 +719,7 @@
       <def>
        <p>
         The implied default is indefinite (no expiry). This specifies the
-        maximum expiration time that the event subscriber is willing to accept.
+        maximum expiration time that the consumer is willing to accept.
        </p>
       </def>
      </gitem>
@@ -827,7 +856,7 @@
      wsa:Address IRI.
      Detecting these errors during Enumerate processing will lessen the chances
      of the consumer creating an unusable enumeration.  If this check is
-     performed and a problem is detected then the event source MUST generate
+     performed and a problem is detected then the data source MUST generate
      a wsen:UnusableEPR fault rather than returning the EnumerateResponse
      message.
     </p>
@@ -863,11 +892,23 @@
       <label> <kw>[Body]</kw>/wsen:EnumerateResponse/wsen:GrantedExpires </label>
       <def>
        <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
-        (if any).
+        The expiration time assigned by the data source. The
+        expiration time MAY be either a specific time or a duration
+        but MUST be of the same type as the wsen:Expires element of
+        the corresponding request. If the corresponding request
+        did not contain a wsen:Expires element, this element MUST be
+        a duration (xs:duration).
+       </p>
+
+       <p>
+        When expressed as a duration, the wsen:GrantedExpires element
+        designates a time interval that began at the moment the
+        enumeration is created. Although this specification cannot dictate
+        when, during the processing of a Enumerate request, an enumeration is
+        created, the data source MUST start the expiration interval at or
+        before it transmits the wsen:EnumerateResponse message.
        </p>
+
        <p>
         If this element does not appear, then the
         enumeration will not expire. That is, the enumeration has an
@@ -1472,7 +1513,7 @@
 
     <p>
      To get the status of an enumeration, the
-     subscriber sends a request of the following form to the data
+     consumer sends a request of the following form to the data
      source:
     </p>
 
@@ -3453,6 +3494,15 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7207">7207</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/10/20 </td>
+      <td> DD </td>
+      <td> Added resolution of issues
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7586">7586</loc>,
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7588">7588</loc>,
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7828">7828</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Tuesday, 27 October 2009 23:34:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 23:34:13 GMT