* Pete Brunet <[EMAIL PROTECTED]> [2008-06-26 19:30]: > <entry> > <summary>A photograph of the Eiffel Tower.</summary> > <link rel="related" type="image/jpeg" href="eiffeltower.jpg" /> > </entry>
That’s just a summary along with an auxiliary link, and that’s how I would expect them to be shown. > 2) Is it expected that enclosures are to be downloaded along > with the feed at the time the reader fetches the feed? Do > readers ever just expose the link and fetch the enclosure later > upon demand by the user, as in case #4? Yes to both questions. User agents are always free to do whatever they want. The purpose of the enclosure relation is so that a publisher can say “this is a potentially large blob of multimedia data that subscribers will probably want to consume in some sort of off-screen/off-line setting” (such as the many people that listen to podcasts during commutes). This is much more to do with human than technical factors; in general, the publisher sets up the expectation for subcribers that periodically produced blobs of multimedia will be advertised using this feed. The `enclosure` relation is just the technical signal by which allows tools to support this use case. > 3) In the cases where links are displayed what is used for the > link text? The obvious first candidate is `atom:link`’s `title` attribute. In general I would expect the `href` to be shown in absence of a title, although there are exceptions. F.ex. in the case of `alternate` links, `atom:link/@title` is redundant. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>
