Ok, I guess I missed that prior discussion (or just completely forgot
about it). I'll go back and review that conversation and Henry's
suggestions. Thanks!
Mark Nottingham wrote:
Hi James,
That was discussed before in the thread whose Subject was "Feed
History -02", starting in mid-July.
My position is that the semantics of fh:prev and those of a "get me a
non-current view of this feed document' are potentially -- and even
often -- orthoganal. fh:prev is a link that allows you to reconstruct
a feed whose entries are *all* current. Because of this, it isn't
good to re-purpose the element for what you want; something separate
would be better.
Also, Henry Story had some interesting thoughts about how to best
model "top 20" lists, which had some impact on the issue you raise.
Cheers,
On 10/09/2005, at 12:31 PM, James M Snell wrote:
Mark, this is looking very good. One point, however.
For non-incremental feeds, it would be helpful to have the option of
being able to reference archived version of the feed (e.g. prior
top-ten-lists). This could be accomplished by allowing fh:prev
elements in a feed with fh:incremental set to false.
<feed>
...
<fh:incremental>false</fh:incremental>
<fh:prev>http://www.example.com/oldfeed</fh:prev>
</feed>
means that http://www.example.com/oldfeed is the previous (I hate to
use the word) "version" of the feed.
thoughts?
- James
Mark Nottingham wrote:
Feed History -04 is out, at:
http://www.ietf.org/internet-drafts/draft-nottingham-atompub-
feed- history-04.txt
Changes:
- fh:stateful -> fh:incremental, with appropriate changes in text
- more explicit cardinality information
- implications of fh:prev being an Absolute URI spelled out
- more explicit white space handling
- Acknowledgements section
More information, including implementation details, at:
http://www.mnot.net/blog/2005/09/05/feed_history
--
Mark Nottingham http://www.mnot.net/
--
Mark Nottingham http://www.mnot.net/
