| Version 3 has the following changes from version 2:
- Added requirement that, if used, ETag values for the collection resource must refer to the entire collection and not just the subset represented by that collection resource. This is important if Consumers are to use ETags to detect when the collection has changed while they are paging.
- Added separate requirements for "total_items", "items_per_page", and "start_index" stating that each must be a non-negative integer.
- Added a requirement stating that, if provided, the 'start_index' query parameter must be a non-negative integer.
- Added a requirement stating that, if provided, the 'max_page' query parameter must be a positive integer.
- Added discussion on what Consumers can do to detect and mitigate the effects of statelessness on paging.
- Added a requirement stating that, if the Consumer sends a request with a 'start_index' query parameter value that is equal to or greater than the number of item in the collection, the Provider must return a 400 response.
The material on sort order for String and URI values still needs to be sorted out. Once we get that done, we should be good to go on this crucial proposal.
~ gp Submitter's message
Version 3 of proposal.
-- Gilbert Pilz
|