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

WWW/2002/ws/ra/edcopies wsenum.html,1.165,1.166 wsenum.xml,1.156,1.157

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 22 Mar 2011 23:54:13 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1Q2BOv-0006KU-Ph@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv24213

Modified Files:
	wsenum.html wsenum.xml 
Log Message:
12112


Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.165
retrieving revision 1.166
diff -u -d -r1.165 -r1.166
--- wsenum.html	18 Feb 2011 00:25:58 -0000	1.165
+++ wsenum.html	22 Mar 2011 23:54:11 -0000	1.166
@@ -637,18 +637,13 @@
         XML canonicalization or alternate XML serialization algorithms can
         change the size of the representation.
        </p><p>
-        It can happen that the next item the data
-        source would return to the consumer is larger than MaxCharacters.
-        In this case, the data source MAY skip the item, or MAY return an
-        abbreviated representation of the item that fits inside
-        MaxCharacters. If the data source skips the item, it MAY return it
-        as part of the response to a future Enumerate request with a larger
-        value of MaxCharacters, or it MAY omit it entirely from the
-        enumeration. If the oversized item is the last item to be returned
-        for this enumeration context and the data source skips it, it MUST
-        include the wsen:EndOfSequence item in the Enumerate response and
-        invalidate the enumeration context.
-        See the discussion of wsen:EndOfSequence below.
+        When compiling the list of items to return, if the next item would 
+        cause the wsen:Items array to be larger than the MaxCharacters 
+        value and the wsen:Items array is not empty then the data source 
+        MUST return the current list of items back to the client, saving 
+        that next item for a subsequent enumerate request. If, however, 
+        the wsen:Items array is empty the data source MUST skip the item 
+        and MUST NOT return it as part of the enumeration.
        </p></dd></dl><p>
      Other components of the outline above are not
      further constrained by this specification.
@@ -2107,4 +2102,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11894">11894</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12063">12063</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11990">11990</a></td></tr><tr><td> 2011/02/15 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11949">11949</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=11949">11949</a></td></tr><tr><td> 2011/03/22 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12112">12112</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.156
retrieving revision 1.157
diff -u -d -r1.156 -r1.157
--- wsenum.xml	18 Feb 2011 00:25:58 -0000	1.156
+++ wsenum.xml	22 Mar 2011 23:54:11 -0000	1.157
@@ -1067,6 +1067,7 @@
         based on the wsen:MaxTime timeout, the wsen:MaxElements limit, or
         implementation-specific constraints.
        </p>
+
        <p>
         Even if a Enumerate request contains a
         MaxCharacters element, the consumer MUST be prepared to receive a
@@ -1074,19 +1075,15 @@
         XML canonicalization or alternate XML serialization algorithms can
         change the size of the representation.
        </p>
+
        <p>
-        It can happen that the next item the data
-        source would return to the consumer is larger than MaxCharacters.
-        In this case, the data source MAY skip the item, or MAY return an
-        abbreviated representation of the item that fits inside
-        MaxCharacters. If the data source skips the item, it MAY return it
-        as part of the response to a future Enumerate request with a larger
-        value of MaxCharacters, or it MAY omit it entirely from the
-        enumeration. If the oversized item is the last item to be returned
-        for this enumeration context and the data source skips it, it MUST
-        include the wsen:EndOfSequence item in the Enumerate response and
-        invalidate the enumeration context.
-        See the discussion of wsen:EndOfSequence below.
+        When compiling the list of items to return, if the next item would 
+        cause the wsen:Items array to be larger than the MaxCharacters 
+        value and the wsen:Items array is not empty then the data source 
+        MUST return the current list of items back to the client, saving 
+        that next item for a subsequent enumerate request. If, however, 
+        the wsen:Items array is empty the data source MUST skip the item 
+        and MUST NOT return it as part of the enumeration.
        </p>
       </def>
      </gitem>
@@ -4044,6 +4041,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=11949">11949</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2011/03/22 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=12112">12112</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Tuesday, 22 March 2011 23:54:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 March 2011 23:54:15 GMT