Mark Nottingham wrote:
My concern is that if there is more than one use of a link relation
like 'next' or 'prev', those uses could conflict. For example, if I
use 'prev' for Feed History, will that cause a problem with feeds
using Amazon OpenSearch if they want to use it in a slightly different
way? To put it in Thomas' terms, what if there are different concepts
of paging using the same terms -- which there seem to be already?
I don't think there are different concepts of paging.
Paging is navigation through subsets (chunks) of a complete set of entries.
If the complete set represents all the entries ever published through an
ever-changing feed document (what a feed currently is, you subscribe
with an URI and the document you get when dereferencing the URI changes
as a sliding-window upon a set of entries), then paging allows for feed
state reconstruction.
In other terms, feed state reconstruction is a facet of paging, an
application to non-incremental feeds.
I think it's worth waiting consensus on previous/next or
forwards/backwards, first/last or head/tail, etc. and having a "paging"
spec (or just IANA registration, I don't really matter), and
orthogonally define an fh:incremental extension (fh:incremental will
just change newsreaders behavior, not the paging concept).
It seems James is having the same feeling…
--
Thomas Broyer
