Given that folks are already accustomed to using alternate links to
discover subscription feeds, I think it would be reasonable for us to
include some statement that within a collection feed, an alternate link
with a type of "application/atom+xml" SHOULD be used to point to the
public representation of a feed.
e.g.,
<feed>
...
<id>tag:example.org,2006:foo</id>
<link type="application/atom+xml"
href="http://example.org/feed.xml"; />
<link type="application/atom+xml"
rel="self"
href="http://edit.example.org/app/foo"; />
...
</feed>
This would go nicely with the use of the alternate link in member
entries to point to the public representation of the entry.
As Tim suggested, using the alternate link in the service doc would be
appropriate.
<service>
<workspace>
<atom:title>My Workspace</atom:title>
<collection href="http://edit.example.org/app/foo";>
...
<atom:link type="application/atom+xml"
href="http://example.org/feed.xml"; />
...
</collection>
</workspace>
</service>
I'd suspect that a lot of existing feed auto-discovery code could be
adapted to support this without much difficulty.
- James
Mark Nottingham wrote:
> I also noticed the split that Lisa mentions when reviewing the draft.
>
> I agree that they're not always separate, but it should be pointed out
> that they can be separate. I didn't see any mechanism to discover what
> the URI of the "normal" feed is, beyond a link/@rel=alternate in the
> collection feed; did I miss something?
>
> If that's the way to do it, it would be good to call it out (it might be
> preferable to have a separate link relation, as the semantic isn't just
> "alternate", but "public", etc.). It might also be good to have
> something that allows distinguishing between the two (without forcing
> it) in the service document.
>
> Cheers,
>
>
> On 2006/10/17, at 4:40 PM, James M Snell wrote:
>
>> My assumption: The separation between "subscription feeds" and
>> "collection feeds" is not always clear. There are at least two deployed
>> implementations I am aware of that use the same feeds for both and I'm
>> currently working on a third. In Google's new Blogger Beta, for
>> instance, the subscription feed is also the collection feed.
>>
>> I believe that any assumption that the subscription and collections
>> feeds will always be different is incorrect and dangerous.
>
>
> --
> Mark Nottingham http://www.mnot.net/
>
>
