[Registry-dev] Feeds for (non-collection) resources

[Glen Daniels]

Hi folks!

So with the new APP implementation, we've changed what comes back when 
you GET the URL for a resource like atom/r1.  It used to be a <feed>, 
which wasn't really right in terms of Atom, which wants it to be an 
<entry>.  So here's how it looks:

1) POST some text/plain content to registry/atom/ with slug "r1", get 
back an <entry> (a media entry) with Location: registry/atom/r1, and the 
"edit" link pointing to the same place.  The content is 
src="..resource/r1", and it has an edit-media link to ...resource/r1 as 
well.

2) GET registry/atom/r1, and receive back the same <entry>.

3) PUT a new <entry> to r1 to change metadata about the resource, 
properties, etc.

So now we want to enable subscribing to changes on a particular 
resource, for which we want a feed.  We could do one of two things as I 
see it.

OPTION 1 - have a new top-level "feed/" in parallel with "atom/" and 
"resource/", so "registry/feed/r1" would get R1's change feed.

OPTION 2 - use "r1;changes" to get the feed.

I was originally thinking along the lines of option 1, but now I like 
option 2 much better, since it's clear what the feed is for (i.e. change 
logs) and it more obviously associates the feed with the resource, just 
like ";comments" and ";tags" do.

So I'm proposing to implement ";changes" tonight/tomorrow.

Comments / thoughts?

Thanks,
--Glen