Eric Scheid wrote:
On 11/5/05 1:41 AM, "Robert Sayre" <[EMAIL PROTECTED]> wrote:

I don't understand what the "feed" relation indicates. What benefit
does it have over
<a href="..." type="application/atom+xml">...</a>

It indicates that the @href resource is a feed in the sense that it is a source of notifications of updated content (and is the place to watch for updates the current page) to which one might wish to subscribe, and furthermore it suggests that the resource of @type="application/atom+xml" is an Atom Feed Document, and not an Atom Entry Document.

Links you might *not* want to use @rel="feed" on would be...

    <a href="...">example of a broken feed</a>
    <a href="...">archives for June 2002</a>
    <a href="...">Tom's feed, very interesting</a>

Without @rel="feed", a browser with autodiscovery support might well suggest
those links as being worthy of subscription. (The third case iffy -- I rule
it not @rel="feed" because Tom is quite unlikely to include an entry which
is an alternate for this particular page).

IMO, autodiscovery should occur only when a @rel (or @rev) is provided (and, ideally, understood). Don't forget HTML does not define a default value for @rel or @rev when they are not provided.


This is a link to an Atom document:
<a href="..." type="application/atom+xml">...</a>

These are links to Atom documents which indicate a relation between the containing document and the feed pointed to by the @href and should therefor trigger autodiscovery:
Linking to the news feed from the "news" page:
<a href="..." rel="alternate" type="application/atom+xml">...</a>
Linking to the news feed from another page (e.g. the Mozilla home):
<a href="..." rel="related" type="application/atom+xml">...</a>


--
Thomas Broyer



Reply via email to