Have you looked at the license-free XMP SDK at adobe.com? Maybe it's good enough? If not, how can Adobe improve it? Sure would like some feedback.
An advantage of using XMP as the native metadata format, is that you can move the entire XMP blob into other file formats that support XMP. You don't need to gather individual items, find the appropriate XMP name, deal with new EXIF tags that you've never seen before but need to carry forward, etc.
Lars
+1
As XMP, it's just an ordinary string (though potentially a big one) and the naming conventions are already decided by others. Though it does beg the question of a portable, compact, nicely licensed parser for XMP. (I rolled my own but am not especially
happy about it. Does anybody have a good recommendation?)
As an alternative, what I do in OIIO when saving EXIF data into OpenEXR files is simply to name it all "Exif:Foo" or "IPTC:Foo", with Foo being the official Exif or IPTC names, and the prefix making it pretty easy to distinguish from ordinary exr user
metadata.
On Jul 17, 2013, at 10:09 AM, Lars Borg wrote: Thomas,
Why not use XMP instead? XMP includes all of EXIF + Dublin Core ++
Lars
Hi,
I'm resurrecting that thread after 7 years, I basically wanted to know if there has been more discussions about that matter in the recent years.
The fact there is no standard attributes for common camera data prevents a bit the format to be used as a solid input container for photo processing applications or anything relying on EXIF data. For instance if you want to stitch EXR files with PTGui
you will have to enter your data manually.
I think it would be really important trying to establishing a standard list of attributes as suggested by Thomas Lock, the exrstdattr already provides a list of them, maybe completing / updating this one?
Cheers,
Thomas
|