Thomas Broyer wrote:
How would you use these link relations for feed state reconstruction
(that is, automatic handling by the Atom processor, without user
action –except probably the "please reconstruct this feed's state"
action) if you can't know what's pointed at?
How would you navigate through a paged search result (e.g. OpenSearch
result feed) if previous/next might point at previous/next queries
(e.g. history of what people searched for before you) or previous/next
pages of the result feed?
How would you disambiguate between two "next" link on pointing at the
next chunk of a paged feed and the other pointing at the next archived
feed? (e.g. "August Top 100, page 2" and "September Top 100")
I thought we all agreed that we need a specific definition (related to
paging) of these relations and were previously voting about how to
call them (previous or prev-archive)
I wouldn't disambiguate them as I don't believe it's necessary to.
What's needed is a way of identifying the role|purpose|intent of a feed;
not a way of disambiguating the links between them. An "archive" feed
should be treated differently than a "search" feed which should be
treated differently than a "subscription" feed.
- James
