Re: FYI: Feed History extension

Hi guys -

I'm mostly a lurker on this group, but thought this post was pretty
interesting. My name is David Hall, and I work at Yahoo on Multimedia
Search. As Lucas mentioned, we wanted a similar thing for Media RSS.
At first glance, this satisfies what we were after with our suggestion
and would be happy if this was adopted.

I'll dig into it more to see if there's anything that it doesn't do
for us, but so far so good! Works well for us, and I think it works
well for the people that don't want/need to construct "full" feeds. 

The term "stateful" is a little confusing at first, but the examples
do well to explain it. (And, nope, I couldn't think of a better term
either...)

I'll chew on it more over the weekend.

-David

--- In [email protected], Lucas Gonze <lgonze@p...> wrote:
> A related issue came up in the Media RSS group.  Yahoo wanted an 
> 'archive' element to signify that a feed was either complete or
partial, 
> partial meaning that there were entries not included in the feed.  The 
> purpose was to be able to retrieve (and publish) a complete copy of the 
> feed.  The main difference between their proposal and yours was that 
> there were two feed documents -- a current view of the feed with a 
> partial collection of entries and an archive view with a complete 
> collection.
> 
> If your fh:prev element allowed the archive to be complete, meaning
that 
> it includes both previous entries and entries in the current feed, then 
> these proposals would be almost the same.
> 
> The fh:stateful element seems redundant.  My reading is that you can 
> safely infer that a feed is stateful when you see an fn:prev element -- 
> are there situations where that's not true?
> 
> Mark Nottingham wrote:
> 
> >I've put together the draft announced below as a way to allow feeds'
> >history to be 
> >reconstructed; e.g., if Scripting News supported this (by adding one
> >tag to the feed and 
> >archived feed headers), you could track Dave's writings back to the
> >very beginning, 
> >automatically.
> >
> >Note that it's submitted to the Atom WG, but it's equally applicable
> >to RSS; there are RSS 
> >examples, and there shouldn't be any overhead or problem.
> >
> >I've modified my blog feed to demonstrate it:
> >  http://www.mnot.net/blog/index.rdf
> >
> >Comments and suggestions much appreciated,
> >
> >[[[
> >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-01.txt
> >        Pages           : 10
> >        Date            : 2005-7-1
> >        
> >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-nottingh
> >am-atompub-feed-history-01.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/l
> >istinfo/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-01.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-at
> >ompub-feed-history-01.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.
> >                
> >                
> >Below is the data which will enable a MIME compliant mail reader
> >implementation to automatically retrieve the ASCII version of the
> >Internet-Draft.
> ><ftp://ftp.ietf.org/internet-drafts/draft-nottingh
> >am-atompub-feed-history-01.txt>
> >]]]
> >--- End forwarded message ---
> >
> >
> >
> >
> > 
> >Yahoo! Groups Links
> >
> >
> >
> > 
> >
> >
> >.
> >
> >  
> >






 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rss-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/