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.
Yes it does. (Though as was later clarified it's not that OpenSearch specifies any chronological ordering as such, but it is true that anyone who wants to implement OpenSearch in a conventional time-ordered feed will have to have "next" pointing back in time.) I thought it was agreed when we were discussing registering the link relations for prev/next etc. that the registration would not specify whether next meant backwards or forwards in time, but that specs making use of them would be written to be 'sign independent'. E.g. the history spec (or something else) would define an element <nextIsBackwardsInTime value="yes" /> or whatever, that publishers could set and consumers would be required to check. Regards, Peter -- Peter Robinson <http://www.ticketswitch.com/> Concerts, sport and theatre tickets
