Re: Feed History -04

[Mark Nottingham <mnot@xxxxxxxx>]

I already get the same results with just one link relation -- 'prev- 
archive' -- instead of three.

The algorithm for combining results is an important issue, but an  
orthogonal one.


On 17/10/2005, at 12:37 PM, James M Snell wrote:

> Mark, I honestly believe that feed history can be achieved using a  
> very simple model:
>
> a. incremental=true... which means that entries (posted at any  
> time) may exist in other feed documents
> b. start/next/prev... points to other feeds where entries may be found
>
> if I point my newsreader to a feed document that has a  
> incremental=true, I would look for a start link.  I would process  
> the start feed then begin walking my way through the next links to  
> build the history.  The start feed MAY have the most recent entries  
> or MAY have the oldest entries, it doesn't matter.  My Atom  
> processor would just Do The Right Thing with whatever entries it  
> finds in the feeds as it walks through the linked list of feed  
> documents.  How does the Atom processor know when it has the  
> complete history?  Either a) the user tells it to stop or b) it  
> reaches a feed without a "next" link.
>
> There shouldn't be any requirement that the entries in a feed (or  
> even the feed documents themselves) have to be in a specific order  
> in order to reconstruct the history.  The minimum requirement is  
> only that we're able to find the feed documents we need.  The Atom  
> processor can figure the rest out from there.
>
> - James
>
> Mark Nottingham wrote:
>
>
> > Exactly.
> >
> > I don't want this draft to become the all-singing, all-dancing  
> > feed  model review; although there's lots of interesting stuff  
> > there, it's  way too ambitious for my tastes (and I think I detect  
> > the smell of a  tarpit faintly wafting...). The feed history case  
> > gets us to a nice 80 +% point; the rest can come in separate  
> > vehicles.
> >
> > Any response to 'prev-archive'?
> >
> > Cheers,
> >
> >
> > On 17/10/2005, at 11:49 AM, Thomas Broyer wrote:
> >
> >
> > > James Holderness wrote:
> > >
> > >
> > > > > > 5. Is the issue of whether a feed is incremental or not (the   
> > > > > > fh:incremental
> > > > > > element) relevant to this proposal?
> > > > >
> > > > > non-incremental feeds wouldn't be paged, by definition, would  
> > > > > they?
> > > >
> > > > This has been debated. There have been those who have expressed  
> > > > an  interest in having next and prev links traverse an archive  
> > > > of old  non-incremental feeds. Say you have a feed with the top  
> > > > 10 books  for this month. The next link (or prev link, depending  
> > > > on your  preference) would point to the archive document with  
> > > > the top 10  books from last month.
> > > I think that Mark's concerns were that readers/aggregators   
> > > generally keep a local history of the feeds they're subscribed  
> > > to.  fh:incremental=no would explicitly tell them not to do so.
> > >
> > > --
> > > Thomas Broyer
> >
> >
> > --
> > Mark Nottingham   Principal Technologist
> > Office of the CTO   BEA Systems
> >
> > _____________________________________________________________________ 
> > ___________
> > BEAWorld 2005: coming to a city near you.  Everything you need for  
> > SOA and enterprise infrastructure success.
> >
> >
> > Register now at http://www.bea.com/4beaworld
> >
> >
> > London 11-12 Oct| Paris13-14 Oct| Prague18-19 Oct |Tokyo 25-26  
> > Oct| Beijing 7-8 Dec


--
Mark Nottingham     http://www.mnot.net/