On 29/7/05 7:57 PM, "Henry Story" <[EMAIL PROTECTED]> wrote:
> 1- The top 20 list: here one wants to move to the previous top 20 list and > think of them as one thing. The link to the next feed is not meant to be > additive. Each feed is to be seen as a whole. I have a little trouble still > thinking of these as feeds, but ... What happens if the publisher realises they have a typo and need to emit an update to an entry? Would the set of 20 entries (with one entry updated) be seen as a complete replacement set? The way I see it, maybe a better way would be to have a sliding window feed where each entry points to another Atom Feed Document with it's own URI, and it is that second Feed Document which contains the individual items (the top 20 list). Someone could subscribe to that second feed and poll for updates, and all they'll ever see are updates to the 20 items there, not the 20 items from the next week/whatever. The idea of feeds linked to feeds has lots of utility -- feeds of comments for one, and even a feed of feeds available on the site. For example: this HTML page <http://www.nature.com/rss/> has an equivalent feed document <http://npg.nature.com/pdf/newsfeeds.rdf>, where each item links to the individual feeds for each publication. That feed doesn't update often, mostly because NPG doesn't add many new feeds to their site all that often. The URIs the entries of that feed link to are redirected to the permanent URIs of the current issue (each issue has it's own feed which is the table of contents for that issue, with a distinct and separate URI for each issue). It's conceivable they could also provide a feed for each publication pointing to the table of contents feeds of each issue. That is, a feed with an entry for each issue. Of the above, the mechanism of a single URI which redirects to the current issue is a situation which would still need a flag indicating that the appropriate thing to do is to not persist older entries. The other structure of feeds linking to feeds would require the aggregator be able to do something useful with such links, but this can be generalised and thus be useful for many purposes. As it is, right now with NNW I can do something useful with such a feed: drag & drop the item headline link to my subscriptions pane to subscribe to that feed and view the entries therein. Both require coding effort. e.
