Thomas Broyer wrote:
Mark Nottingham wrote:
Perhaps people could +1/-1 the following options:
* Reconstructing a feed should use:
a) a specific relation, e.g., "prev-archive"
-1, (see James' comments)
b) a generic relation, e.g., "previous"
+1
Hmm, I might have answered a bit too fast…
"previous" might be too generic and thus be used for things other than
paging through a feed (would it be incremental –feed reconstruction– or
not –search result, etc.), so I'd +1 to "previous-page".
On the other hand, if we don't register "previous" now, someone might
register it later for something else (don't know what the IESG can
approve…), with the same potential misuses…
But if we register "archives" or "history" at the same time (or, say,
quite early in Atom the 1.0 deployment), misuses (the most common I
think, using previous/next for inter-"feed state" linking, e.g. linking
from the October Top 100 non-incremental feed to the September Top 100
non-incremental feed) could be prevented… We should then also add a note
in the previous/next description telling people not to use them for such
things as described earlier, maybe also using the term "page" or
"paging" explicitly…
As a result, I'm still -1 on prev-archive and +1 on previous, but add a
+.75 on "previous-page".
--
Thomas Broyer
