Re: Re: Atom and RDF
Ian Davis <[email protected]>
| Newsgroups | gmane.network.syndication.rss.devel |
|---|---|
| Message-ID | <[email protected]> |
On 13/10/2004 18:08, Julian Bond wrote: > Alex Kolesnichenko <yahoo-KwUv6+pz0nRWk0Htik3J/[email protected]> wrote: > >><enclosure>s are broken from the another side -- I cannot specify more than >>one <enclosure>. And, the worst, I cannot specify alternative <enclosure>s >>(ie. user could have a choice to download radio show in either MP3 record >>format or its script in DOC). > > > Or via BitTorrent. This last one I think is important. I can well > imagine a provider saying, "Please use this BT URL to save my bandwidth, > but if your aggregator can't cope with that, here's the MP3 URL." How's this as a hypothetical RSS module: <rss:item> <rss:title>Ian's Bad Poem</rss:title> <encl:enclosure rdf:resource="http://example.com/torrent" dc:format="application/x-bittorrent" <!-- whatever --> dc:title="Bit torrent link to mp3" /> <encl:enclosure rdf:resource="http://example.com/mp3" dc:format="audio/mpeg" dc:title="MP3 of me reading my poem" /> <encl:enclosure rdf:resource="http://example.com/text" dc:format="text/plain" dc:title="My poem itself" /> </rss:item> Clients can choose to download the most appropriate format, either automatically or by presenting a series of links to the user with the titles supplied. The encl:enclosure elements can be extended with any RDF properties. Some useful ones from Dublin Core include 'license', 'publisher', 'audience'. MusicBrainz define some other interesting ones such as 'duration' which could also add value. Ian Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/rss-dev/ <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/