On 1/5/06 2:25 PM, "James M Snell" <[EMAIL PROTECTED]> wrote:
> While I'm sure the other James may have his own particular set of > issues, the one pain point for me with the history spec is the use of > the "previous" link to point back in time. This runs counter to the use > of the previous link in both OpenSearch, APP and Gdata. I thought OpenSearch results are not sorted by chronological age at all, but instead by relevance? Using "next" with OpenSearch makes sense in that context. Using "previous" for stepping back thru time in a data store arranged chronologically makes sense. I'm not familiar with how Gdata arranges it's data, but briefly scanning the API docs it's modelled on OpenSearch, and furthermore it says "Result ordering is up to the implementation" ... thus I would think it would be right for it to use 'next' to get the next page, but wrong to assume that this would imply stepping backwards chronologically. e.
