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
