[Bug 12112] MaxCharacters behavior is ambiguous

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12112

--- Comment #1 from Nathan Burkhart <nathan.burkhart@microsoft.com> 2011-02-17 23:25:18 UTC ---
Proposal to amed the second part of that paragraph:


"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 data source skipped one or more oversized items that can be returned as
part of a response to a future Enumerate request, it MUST NOT include the
wsen:EndOfSequence item in the Enumerate response.

If all of the skipped items were omitted entirely from the enumeration, the
data source MUST include the wsen:EndOfSequence item in the Enumerate response
and invalidate the enumeration context.

If all items are skipped so that there are zero items in the Enumerate
response, the data source MUST include the wsen:EndOfSequence item in the
Enumerate response and invalidate the enumeration context."

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

Received on Thursday, 17 February 2011 23:25:19 UTC