The standard definition of metadata is data about the data. The concept of metadata that is associated with (audio) program material is not new. The information on tape box labels has been with us for years. The difference now is that with the proliferation of audio formats and encoding methods, the user has to know more about the audio data before it can be used or presented in the way that was originally intended. Some metadata is static in that it applies to an entire program, but other metadata may control how the program is presented and thus changes with time. Synchronization of dynamic metadata is therefore improtant. Much more emphasis is being placed on reusing program material, so asset management has become a major factor in creating, using, and archiving audio. Asset management metadata should not be stored with the audio itself; that would be like storing a library's catalog cards by tucking them into each book before shelving the books. The unique material identified (UMID) is analogous to the number assigned to each book that links it to its description in the catalog. These three main classes of audio metadata are all necessary. All need to be treated and transported differently, but all must be archived with the audio information if the audio is to be useful to others.
Click to purchase paper as a non-member or you can login as an AES member to see more options.
No AES members have commented on this paper yet.
To be notified of new comments on this paper you can
subscribe to this RSS feed.
Forum users should login to see additional options.
If you are not yet an AES member and have something important to say about this paper then we urge you to join the AES today and make your voice heard. You can join online today by clicking here.
