W3C home > Mailing lists > Public > public-media-annotation@w3.org > March 2009


From: Joakim Söderberg <joakim.soderberg@ericsson.com>
Date: Sun, 15 Mar 2009 20:45:02 +0100
Message-ID: <4055256AED9D224D9442B19BF1C4C49003633E3B@esealmw118.eemea.ericsson.se>
To: <public-media-annotation@w3.org>
I would like to summarize DynamicMediaXMPPartnerGuide as follows:

- XMP follows an ingredient/pantry metaphor:
A composed dish has ingredients (xmpMM:Ingredients). The ingredients are the assets used in the composition. A composed document contains a pantry (defined as an array of entries), where you can find the metadata for ingredients.
-When document composition occur its metadata retain its original association.
 The specification of media "Parts" are crucial. If you have a tree of nested documents you must perform a search operation recursively to get the metadata of all the documents.
=> A search result can be a list of metadata from all ingredients. 

- Recording change events. E.g. converted, copied, cropped. Modifying actions are represented by the ResourceEvent data type. Event information includes the instance ID of the modified resource, a timestamp, and the application (agent) that performed the action.	

- Identifying documents and parts. GUIDS are used to identify objects unambiguously. The XMP Media Management schema defines different identifiers: xmpMM:DocumentID  when a document is copied to a new file and xmpMM:InstanceiD to track a documents editing history.

- Temporal information is used to track temporal relationships using 'tracks' and 'markers'

Other:  Adobe them selves think that work-flow descriptions are important since it significantly impact the work for the end user.

Received on Sunday, 15 March 2009 19:45:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:17:33 UTC