The intent here was to say that the *set* of entries is generally
stable, not that they're set in stone. That's what you want, no? If
so, how about:
- Attribute Value: first
- Description: A stable URI that, when dereferenced, returns a feed
document containing the set of entries furthest preceding those in
the current document at the time it was minted. This can be thought
of as specific to those entries; in other words, it represents a
fixed section of the feed, rather than a sliding window over it. Note
that the exact nature of the ordering between the entries and
documents containing them is not defined by this relation; i.e., this
relation is only relative.
- Expected display characteristics: ...
- Security considerations: ...
It's a hard line to walk.
On 17/10/2005, at 4:42 PM, James M Snell wrote:
"A stable URI" was intended to capture that, but I see that
wasn't good enough. How about:
- Attribute Value: first
- Description: A stable URI that, when dereferenced, returns a
feed document containing the set of entries furthest preceding
those in the current document at the time it was minted. The set
of entries in this document should not change over time; i.e.,
this link points to a stable snapshot of entries, or an archive
of feed entries. Note that the exact nature of the ordering
between the entries and documents containing them is not defined
by this relation; i.e., this relation is only relative.
- Expected display characteristics: ...
- Security considerations: ...
Another thought would be "first-archive", "last-archive", "prev-
archive" and "next-archive" (just expanding a previous thought).
-1. The first/next/prev/last link rels should not specify any
restrictions on how the contents of the feeds should or should not
be updated. If a specific use of these link rels wishes to impose
such a restriction (e.g. for feed history), then great, so-be-it,
but the link rels themselves should not.
--
Mark Nottingham http://www.mnot.net/
