>>From Brian Smith on 05/29/2008 09:08 AM > > Basically, rel="related" should almost never be used. If you need the UA > to display some links to the user then you should put those links in the > atom:content using (X)HTML markup to guarentee (as much as possible) that > they show up (since not all Uas expose "related" links). If you don't want > the UA to display the link then you should use something other than > rel="related" because some UA's will expose all "related" links. > > Brian, What about rel="enclosure"? Listing 4 at > http://www.ibm.com/developerworks/xml/library/x-atom10.html shows > enclosures like > > <link rel="enclosure" > type="audio/mpeg" > title="MP3" > href="http://www.example.org/myaudiofile.mp3"; > length="1234" /> > > Should enclosures also "almost never be used", but exposed via the content > element instead? How would the above enclosure be coded in the content > element? What do UAs do with "enclosure"? Do they display the title as > link text with the href as the target? > > I've been thinking of enclosures as large relateds so that is what lead me > to ask. >
This is really a context dependent question. If you one sees the World solely through the prism of browsers and feed readers it might make sense to pay more attention to the atom:content than to the meta-data carried by the entry. However, there are other people who use Atom in contexts that have nothing to do with that prism and they quite happily use the whole arsenal of features RFC 4287 provides. - Sylvain -- Sylvain Hellegouarch http://www.defuze.org
