It has actually been a while since I've looked at this area so I'm not
really up to date on the existing markup options beyond Media RSS and
the itunes extensions. It would be very helpful if someone could
provide a brief overview of existing media metadata options, including
where those options are being used.
- James
Sylvain Hellegouarch wrote:
Peter Keane a écrit :
A use-case, if it's of interest: We have an online digital library
application, which contains images (jpg,png,gif,tiff), also PDFs,
audio files (mp3,wav), video (mpeg4, etc). It's widely used here at UT
Austin, mostly for instructional purposes, but also for
content-managing media rich web sites [0]. It uses Atom extensively
for moving data around and for archiving collections.
I typically get EXIF data from jpegs, id3v2 medatadata from mp3s, and
IPTC
data from images when possible. I can use the content element in Atom to
capture metadata about the primary media file, but it's that metadata
that
varies per media file that I need to deal with (height, width, bitrate,
stereo/mono, aspect ratio, md5 hash, etc.) in atom:link.
I typically use those existing meta-data as well and simply try to map
them to Dublin Core elements, which has proven to be quite hard
considering how generic DC can be. I do not try to extend the Atom
namespace usually but rather re-use an existing one (for instance for
multimedia resources I often try to use Mpeg7).
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?
- Sylvain
