FWIW, quite some time ago I had proposed a set of "Atom link extensions"
that, at the time, failed to get any momentum. Some details here:
http://www.snellspace.com/wp/?p=247.
One of the criticisms of that work was that while rfc4287 allowed the
atom:link element to have child elements, it was not clear how many
implementations would actually be able to do anything with them. Another
issue was whether implementations that could get to the extensions
actually would do anything with them.
- James
Peter Keane wrote:
On Thu, 17 Jan 2008, Sylvain Hellegouarch wrote:
I'm not sure however to understand what the atom:link could provide.
If it was to specify a given taxonomy, why not define it in terms of
atom:category/@term in a given scheme instead?
Actually, I was thinking of using atom:link to capture the bits of
metadata that would vary per media file. Ex:
<entry>
...
<link rel="enclosure" href="1234.mp3" type="audio/mpeg">
<x:channelMode>mono</x:channelMode>
<x:bitrate>128<x:bitrate>
</link>
<link rel="enclosure" href="1234.mp3" type="audio/wav">
<x:channelMode>stereo</x:channelMode>
<x:samplingRate>44.1<x:samplingRate>
</link>
<link rel="http://xxxxx/thumbnail"; href="1234.jpg" type="image/jpeg">
<x:height>120</x:height>
<x:width>120</x:width>
</link>
</entry>
--peter
- Sylvain
