search

shshankjain / webm

Automatically exported from code.google.com/p/webm
0 stars 0 forks source link

Support XMP metadata in WebM files #242

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The XMP SDK from Adobe supports several different media types, including AVI 
and FLV.  We shouuld work with Adobe to support XMP-style metadata in WebM 
files.

Original issue reported on code.google.com by matthewj...@google.com on 7 Dec 2010 at 9:05

GoogleCodeExporter commented 9 years ago 
I don't intend to spam but for the record  i'd like to point out this 
discussion which is related ( 
http://groups.google.com/a/webmproject.org/group/webm-discuss/browse_thread/thre
ad/97533a137ae26cf7# )

Steve Lhomme :
WebM uses Matroska and as such can skip elements it doesn't
understand. Google doesn't have to make a formal statement for things
to evolve. If you add the regular Matroska tags in a WebM file, it
will still be usable as WebM and any Matroska aware program that can
make use of these tags will do. So there is no technical issue here.
And you can already use tags today.
The only possible issue is if the tagging system used in WebM (I can't
imagine there won't be one) is incompatible with the Matroska one. 

Frank Galligan :
To add metadata to WebM someone needs to make a proposal of what to
add and how it should be laid out in WebM files. The proposal can come from
anyone and post on this list so everyone can talk about it. 

fishor :
xmp:Rating -> for rating
dc:subject -> for labels

dc:relation or xmp:Label -> for events

xmp:MetadataDate -> last date metadata was modifyed

dc:source -> where we got this file from (path or storage name or
website (youtube), just some thing to help find where is it from)

xmpRights:*  -> this is mostly interesting on publishing or export.

xmpMM:DocumentID  -> uuid of the new image, if we get file which
 contain same DocumentID like one from say my database, it should try
to compare
 it (md5sum or some thing like this) if file checksum is not same it
is
 some modification of file what we have.

And to keep track of modifications:
 xmpMM:History
 xmpMM:VersionID
 xmpMM:Versions

For recording devices you will probably will all exif:* fields.

all of this are fields according xmp specification: 
http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf

Original comment by thibaut....@gmail.com on 13 Jan 2011 at 11:42

GoogleCodeExporter commented 9 years ago 
hi,
I think that the (entire?) dc: set of metadata names is a good choice.

Original comment by arpus...@gmail.com on 31 Jan 2011 at 9:58

GoogleCodeExporter commented 9 years ago 
We have tenatively decided to use Matroska tags as the mechanism for metadata 
support in WebM.

Original comment by matthewj...@google.com on 16 Feb 2012 at 10:20