Re: FWD: I-D ACTION:draft-nottingham-atompub-feed-history-00.txt
Dave Pawson wrote: Any one site could now have n instances, each being a feed, the only variant (apart from entries) being the links to previous feeds. If I'm to say *this* is my feed, I guess I point to the most recent... which will change over time? With the example of 15 entries per, feed1 1..15 feed4 45..60 my 'feed' for my site rolls over from feed1...n as time progresses? I guess the answer is: http://example.com/latest is your feed, e.g. containing the latest 10 entries http://example.com/archive-1 through n are your archive feeds. latest is likely to contain entries which are also archived in archive-n, but I don't see it as a problem (and it doesn't violate Atom Feed Document rules wrt uniqueness of entries), at most I will retrieve 14 entries (if using 15 entries per archive feed document) which I already got from the live feed. You can see latest as an Atom alternate for your home page (or latest news page) and archive-1 through archive-n as Atom alternates for your archive pages. What I'm wondering is, if I had archive feeds on a per-day basis (instead of N entries per archive feed, although what follows also applies) and say I published 3 entries yesterday, 5 entries the day before and no entry yet today: - http://example.net/archive/2005/06/27: 5 entries - http://example.net/archive/2005/06/28: 3 entries - http://example.net/archive/2005/06/29: doesn't exist yet Say I'm having a live feed showing the latest 5 entries: it will contain all the 3 yesterday entries and the 2 latest entries from 2005/06/27. Could I prev-link to archive/2005/06/28 or should I try to figure out the archive feed containing the previous to earliest entry (here, archive/2005/06/27, but it could have been archive/2005/06/25 if I had only 2 entries last monday and not at all on sunday) ? If I can just link to the latest archive feed document, shouldn't we then just have an archive [EMAIL PROTECTED] in the live feeds (similar to the List-Archive header in mail messages) and use prev only between archive feed documents (similar to the Next Page link in the HTML list archive). -- Thomas Broyer
Re: FWD: I-D ACTION:draft-nottingham-atompub-feed-history-00.txt
On Wed, 2005-06-29 at 15:03 +0200, Thomas Broyer wrote: Dave Pawson wrote: Any one site could now have n instances, each being a feed, the only variant (apart from entries) being the links to previous feeds. If I'm to say *this* is my feed, I guess I point to the most recent... which will change over time? With the example of 15 entries per, feed1 1..15 feed4 45..60 my 'feed' for my site rolls over from feed1...n as time progresses? I guess the answer is: http://example.com/latest is your feed, e.g. containing the latest 10 entries http://example.com/archive-1 through n are your archive feeds. Which would mean that the instance at /latest keeps changing? I need to keep swapping old ones out, new ones in, i.e. rebuilding each time? I guess that's another reason it feels like a kludge. You can see latest as an Atom alternate for your home page (or latest news page) and archive-1 through archive-n as Atom alternates for your archive pages. I can see the logic of your suggestion. Doesn't seem clean though? snip/ Other issues. regards DaveP
Re: FWD: I-D ACTION:draft-nottingham-atompub-feed-history-00.txt
Hi Mark, * Mark Nottingham [EMAIL PROTECTED] [2005-06-28 22:40]: This document specifies mechanisms that allow feed publishers to give hints about the nature of the feed's statefulness, and a means of retrieving ^missed^ entries from a stateful feed. I agree with Antone Roundy that the “this” link is unncessary for the reasons already stated. My first thought upon reading the draft was what I assume is what Stefan Eissing said: I would rather have a single, entry-less “archive hub” feed which contains “prev” links to *all* previous instances, leading to a setup like http://example.com/latest └─ http://example.com/archive/feed/ ├─ http://example.com/archive/feed/2005/05/ ├─ http://example.com/archive/feed/2005/04/ ├─ http://example.com/archive/feed/2005/03/ ├─ http://example.com/archive/feed/2005/02/ └─ http://example.com/archive/feed/2005/01/ so that it’s only necessary for the aggregator to fetch one document to find out about all previous versions. It seems cleaner and more robust to keep a global history list, rather than encoding it implicitly as a chain of documents. I don’t see anything in the draft that would preclude this use, and as far as I can tell, aggregators which support the draft should have no trouble handling this scenario correctly. Is it acceptable, or did you intend to outlaw it? If yes, what is the reasoning? In fact, I’d probably go one step further and add a “prev” link to each version, which points back to the archive list feed. http://example.com/latest └─ http://example.com/archive/feed/ ┐ ├─ http://example.com/archive/feed/2005/05/ ─┤ ├─ http://example.com/archive/feed/2005/04/ ─┤ ├─ http://example.com/archive/feed/2005/03/ ─┤ ├─ http://example.com/archive/feed/2005/02/ ─┤ └─ http://example.com/archive/feed/2005/01/ ─┘ In that way, any of the files can be copied around the place, but they never lose their association with the originals. Again, I don’t see anything in the draft that would preclude this use, and as far as I can tell, aggregators which support the draft should have no trouble handling this scenario correctly. Is it acceptable, or did you intend to outlaw it? If yes, what is the reasoning? Note how the archive directory feed being static makes this painlessly possible, while it would be a pain to achive something similar using the paginated approach with local “prev” links (you’d need to go back and change the previously newest old version every time a new one was added). It would in fact require a “prev” link to what is actually the “next” page. Funnily enough, I don’t see anything in the draft that would preclude this counterintuitive use of the “prev” link to point to the “next” version, and as far as I can tell, aggregators which support the draft [etc]? Overall, I must say this feels kludgy to me, any way I turn it. I’d much rather have a single archive feed containing all entries, and use RFC3229+feed to return partial versions of it; as far as I can tell, this is a use case which your draft does *NOT* allow. Is that so? Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/
FWD: I-D ACTION:draft-nottingham-atompub-feed-history-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Feed History: Enabling Stateful Syndication Author(s) : M. Nottingham Filename: draft-nottingham-atompub-feed-history-00.txt Pages : 6 Date: 2005-6-27 This document specifies mechanisms that allow feed publishers to give hints about the nature of the feed's statefulness, and a means of retrieving ^missed^ entries from a stateful feed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-nottingham-atompub-feed- history-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request at ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username anonymous and a password of your e-mail address. After logging in, type cd internet-drafts and then get draft-nottingham-atompub-feed-history-00.txt. A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv at ietf.org. In the body type: FILE /internet-drafts/draft-nottingham-atompub-feed- history-00.txt. NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the mpack utility. To use this feature, insert the command ENCODING mime before the FILE command. To decode the response(s), you will need munpack or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with multipart MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. ___ I-D-Announce mailing list I-D-Announce at ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce -- Mark Nottingham http://www.mnot.net/
Re: FWD: I-D ACTION:draft-nottingham-atompub-feed-history-00.txt
Mark Nottingham wrote: A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Feed History: Enabling Stateful Syndication Author(s) : M. Nottingham Filename: draft-nottingham-atompub-feed-history-00.txt Pages : 6 Date: 2005-6-27 This document specifies mechanisms that allow feed publishers to give hints about the nature of the feed's statefulness, and a means of retrieving ^missed^ entries from a stateful feed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-nottingham-atompub-feed- history-00.txt I imagine someone else has already noticed this, but there's a typo in the example. The open tag uses the prefix 'fh', but the close tag uses 'fs'. Also, why is Stateful capitalized? All the other parts of atom use lower case tag names, IIRC. -garrett
