|Subject:||Re: [Openexr-devel] EXIF meta data attributes in headers|
|Date:||Tue, 30 Jul 2013 16:44:51 +0000|
Very useful, thanks Lars.
I'll be checking in with our legal team to see what the implications might be .. stay tuned.
From: openexr-devel-bounces+address@hidden [openexr-devel-bounces+address@hidden on behalf of Lars Borg address@hidden
Sent: 30 July 2013 01:17
To: Thomas Mansencal
Subject: Re: [Openexr-devel] EXIF meta data attributes in headers
My colleagues on the XMP team gave the following feedback. Hopefully you find this helpful:
If they take the first approach they will run into the known problem of ambiguity known from not using namespace associations. The second approach is a bit better as it allows that association. We currently use the same approach when storing metadata in the Cloud because the underlying DB does not support namespaces. But then you have to make sure to use standard prefixes and that is in theory also dangerous because prefixes are per definition not standardized but just recommended best practices. How about extensibility in the future? What if EXIF adds new properties, they would need new code to handle those attributes while with XMP they could add them without the need to change anything. Is it also possible in the OpenEXR SDK to ask for all properties for a given namespace, like give me all EXIF or IPTC attributes? That would also be possible with XMP.
If they use XMP the only dependency for the OpenEXR SDK would be on XMPCore (available as part of the SDK under BSD license), which offers parsing/serializing of the data model. If they want they could even take the code from XMPFiles that does the EXIF/XMP mapping and offers parse/serialize of the IFD stuff. It can be used stand-alone.
|[Prev in Thread]||Current Thread||[Next in Thread]|