- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 10 Feb 2010 00:54:27 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv24906
Modified Files:
wsenum.html wsenum.xml
Log Message:
8304
Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -d -r1.113 -r1.114
--- wsenum.html 10 Feb 2010 00:46:56 -0000 1.113
+++ wsenum.html 10 Feb 2010 00:54:25 -0000 1.114
@@ -126,9 +126,8 @@
enumerations of the same data source can produce different results;
this can happen even for two enumeration contexts created
concurrently by a single consumer using identical Enumerate
- requests. In general, the consumer of an enumeration SHOULD NOT
- make any assumptions about the ordering or completeness of the
- enumeration; the returned data items represent a selection by the
+ requests. The ordering or completeness of the enumeration
+ is undefined; the returned data items represent a selection by the
data source of items it wishes to present to that consumer at that
time in that order, with no guarantee that every available item is
returned or that the order in which items is returned has any
@@ -320,7 +319,7 @@
<h2><a name="EnumMsgs" id="EnumMsgs"/>3 Enumeration Messages</h2><p>
Enumeration contexts represent a specific
traversal through a sequence of XML information items. An Enumerate
- operation MAY be used to establish an enumeration context from a
+ operation can be used to establish an enumeration context from a
data source. A Pull operation is used to fetch information items
from a data source according to a specific enumeration context. A
Release operation is used to tell a data source that the consumer
@@ -372,8 +371,6 @@
<h3><a name="Enumerate" id="Enumerate"/>3.1 Enumerate</h3><p>
This specification defines the Enumerate operation to start an enumeration.
This operation MUST be supported by compliant data sources.
- A data source MAY provide other mechanisms for starting an enumeration and
- receiving an enumeration context.
</p><p>
The Enumerate operation is initiated by sending
an Enumerate request message to the data source. The Enumerate
@@ -545,9 +542,9 @@
message.
</p><p>
Upon successful processing of an Enumerate
- request message, a data source is expected to create an enumeration
- context and return that context in an Enumerate response message,
- which MUST adhere to the following form:
+ request message, a data source MUST create an enumeration
+ context and return that context in an Enumerate response message
+ of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
http://www.w3.org/2002/ws/ra/edcopies/ws-enu/EnumerateResponse
@@ -750,8 +747,8 @@
requests using this enumeration context after receiving this fault.
</p><p>
Upon successful processing of a Pull request
- message, a data source is expected to return a Pull response
- message, which MUST adhere to the following form:
+ message, a data source MUST return a Pull response
+ message of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
http://www.w3.org/2002/ws/ra/edcopies/ws-enu/PullResponse
@@ -857,11 +854,11 @@
element (line (24)) indicates that no more elements are available
and that the enumeration context is now invalid.
</p><p>
- The consumer SHOULD NOT issue additional Pull
+ The consumer MUST NOT issue additional Pull
request messages after a Pull response containing a
- wsen:EndOfSequence element has been returned. Similarly, upon
+ wsen:EndOfSequence element has been received. Similarly, upon
receipt of a Pull response containing a wsen:EndOfSequence element,
- the consumer SHOULD NOT issue a Release operation to signal that
+ the consumer MUST NOT issue a Release operation to signal that
the enumeration context is no longer needed.
</p></div><div class="div2">
<h3><a name="Renew" id="Renew"/>3.3 Renew</h3><p>
@@ -987,8 +984,8 @@
further constrained by this specification.
</p><p>
Upon successful processing of a Release request
- message, a data source is expected to return a Release response
- message, which MUST adhere to the following form:
+ message, a data source MUST return a Release response
+ message of the following form:
</p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
http://www.w3.org/2002/ws/ra/edcopies/ws-enu/ReleaseResponse
@@ -1021,9 +1018,8 @@
(22) </s:Body>
(23) </s:Envelope></pre></div></div><p>
Lines (05-07) in <a href="#releaseReq">Example 3-5</a> indicate this message
- is a Release request and that the data source is expected to
- respond with a Release response message. Line (20) identifies the
- enumeration context to be released.
+ is a Release request.
+ Line (20) identifies the enumeration context to be released.
</p><p><a href="#releaseRes">Example 3-6</a> lists a response to the request in
<a href="#releaseReq">Example 3-5</a>.
</p><div class="exampleOuter">
@@ -2093,4 +2089,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</a></td></tr><tr><td> 2010/02/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6436">6436</a></td></tr><tr><td> 2010/02/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</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=8160">8160</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8304">8304</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.105
retrieving revision 1.106
diff -u -d -r1.105 -r1.106
--- wsenum.xml 10 Feb 2010 00:46:58 -0000 1.105
+++ wsenum.xml 10 Feb 2010 00:54:25 -0000 1.106
@@ -142,9 +142,8 @@
enumerations of the same data source can produce different results;
this can happen even for two enumeration contexts created
concurrently by a single consumer using identical Enumerate
- requests. In general, the consumer of an enumeration SHOULD NOT
- make any assumptions about the ordering or completeness of the
- enumeration; the returned data items represent a selection by the
+ requests. The ordering or completeness of the enumeration
+ is undefined; the returned data items represent a selection by the
data source of items it wishes to present to that consumer at that
time in that order, with no guarantee that every available item is
returned or that the order in which items is returned has any
@@ -556,7 +555,7 @@
<p>
Enumeration contexts represent a specific
traversal through a sequence of XML information items. An Enumerate
- operation MAY be used to establish an enumeration context from a
+ operation can be used to establish an enumeration context from a
data source. A Pull operation is used to fetch information items
from a data source according to a specific enumeration context. A
Release operation is used to tell a data source that the consumer
@@ -642,8 +641,6 @@
<p>
This specification defines the Enumerate operation to start an enumeration.
This operation MUST be supported by compliant data sources.
- A data source MAY provide other mechanisms for starting an enumeration and
- receiving an enumeration context.
</p>
<p>
The Enumerate operation is initiated by sending
@@ -937,9 +934,9 @@
<p>
Upon successful processing of an Enumerate
- request message, a data source is expected to create an enumeration
- context and return that context in an Enumerate response message,
- which MUST adhere to the following form:
+ request message, a data source MUST create an enumeration
+ context and return that context in an Enumerate response message
+ of the following form:
</p>
<example>
@@ -1238,8 +1235,8 @@
<p>
Upon successful processing of a Pull request
- message, a data source is expected to return a Pull response
- message, which MUST adhere to the following form:
+ message, a data source MUST return a Pull response
+ message of the following form:
</p>
<example>
@@ -1400,11 +1397,11 @@
</p>
<p>
- The consumer SHOULD NOT issue additional Pull
+ The consumer MUST NOT issue additional Pull
request messages after a Pull response containing a
- wsen:EndOfSequence element has been returned. Similarly, upon
+ wsen:EndOfSequence element has been received. Similarly, upon
receipt of a Pull response containing a wsen:EndOfSequence element,
- the consumer SHOULD NOT issue a Release operation to signal that
+ the consumer MUST NOT issue a Release operation to signal that
the enumeration context is no longer needed.
</p>
</div2>
@@ -1620,8 +1617,8 @@
<p>
Upon successful processing of a Release request
- message, a data source is expected to return a Release response
- message, which MUST adhere to the following form:
+ message, a data source MUST return a Release response
+ message of the following form:
</p>
<example>
@@ -1678,9 +1675,8 @@
<p>
Lines (05-07) in <specref ref="releaseReq"/> indicate this message
- is a Release request and that the data source is expected to
- respond with a Release response message. Line (20) identifies the
- enumeration context to be released.
+ is a Release request.
+ Line (20) identifies the enumeration context to be released.
</p>
<p>
@@ -3931,6 +3927,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/02/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8304">8304</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Received on Wednesday, 10 February 2010 00:54:29 UTC