- From: Nathan <nathan@webr3.org>
- Date: Fri, 20 Nov 2009 16:05:24 +0000
- To: Kingsley Idehen <kidehen@openlinksw.com>
- CC: Ed Summers <ehs@pobox.com>, public-lod@w3.org
Kingsley Idehen wrote: > Ed Summers wrote: >> At the Library of Congress we've been experimenting with using an Atom >> feed to alert subscribers to new resources available at id.loc.gov >> [1]. The approach is similar to what Niklas' is doing, although we >> kind of independently arrived at this approach (which was nice to >> discover). >> >> Creates, updates and deletes happen on a weekly basis, so it's >> important for us to let interested parties know what has changed. We >> ended up using Atom Tombstones [2] for representing the deletes. And >> Atom Feed Paging and Archiving (RFC 5005) [3] to allow clients to >> drill backwards through time. >> >> I just noticed Link Relations for Simple Version Navigation [4] get >> announced on an Atom related discussion list, which looks like it >> could be useful as well, if you maintain a version history. >> >> I'd be interested in any feedback anyone has about using this approach. >> >> //Ed >> >> [1] http://id.loc.gov/authorities/feed/ >> [2] >> http://ietfreport.isoc.org/all-ids/draft-snell-atompub-tombstones-06.txt >> [3] http://tools.ietf.org/rfc/rfc5005.txt >> [4] http://www.ietf.org/id/draft-brown-versioning-link-relations-03.txt >> >> >> > In a nutshell, +1 for this approach. > > is this not the same as (or vi similar to) the court approach outlined here: http://code.google.com/p/court/ by Niklas
Received on Friday, 20 November 2009 16:06:40 UTC