Feature #941

Upgrade xmpsdk source to Adobe's current version

Added by Robin Mills over 3 years ago. Updated 8 months ago.

Status:AssignedStart date:27 Dec 2013
Priority:NormalDue date:
Assignee:Robin Mills% Done:

0%

Category:xmp
Target version:0.27

Description

http://www.adobe.com/devnet/xmp/sdk/eula-cc201306.html

Issue#940 is concerned with compiler warnings. Most of them come from xmpsdk/src. I've fixed the warnings, however perhaps it is time to refresh this part of the code base.

Robin


Related issues

Related to Exiv2 - Bug #940: Compilation warnings Closed 25 Dec 2013
Related to Exiv2 - Feature #937: Support Darwin Core (DwC) XMP metadata Closed 04 Dec 2013
Related to Exiv2 - Feature #742: External XMPSDK and/or XMPSDK 2014.12 Closed 23 Nov 2010
Related to Exiv2 - Bug #787: xmp handling faults (I) - AKA: policing XMP namespaces Assigned 29 Aug 2011
Related to Exiv2 - Bug #788: xmp handling faults (II) - AKA: policing XMP namespaces Assigned 29 Aug 2011
Related to Exiv2 - Bug #789: xmp handling faults (III) - AKA: policing XMP namespaces Assigned 30 Aug 2011
Related to Exiv2 - Feature #599: XMP packets split across multiple APP1 segments Closed 06 Jan 2009
Related to Exiv2 - Bug #639: Editing existing XMP properties in XMP sidecars does not ... Assigned 14 Jun 2009
Related to Exiv2 - Patch #786: thread safety of xmp toolkit Closed 10 Aug 2011
Related to Exiv2 - Support #1082: Crash when removing property of unregistered XMP namespace Closed 15 May 2015
Related to Exiv2 - Bug #751: adobe xmp namespace Closed 17 Jan 2011
Related to Exiv2 - Feature #1050: Extend exif <> iptc <> xmp conversions Assigned 04 Apr 2015
Related to Exiv2 - Bug #1284: Possible exiv2 0.26-svn bug Closed 13 Mar 2017

History

#1 Updated by Andreas Huggel over 3 years ago

Other related issues are #751, #787, #788, #789

We have subtle changes in our version of the XMP-SDK which make an upgrade a difficult project.

I recall a discussion with someone from Adobe in an XMP forum when I tried to get them to change XMP-SDK a bit but was not able to get them interested. That was related to the per-object namespace registry. It is possible that my understanding of XMP at that time was not complete. Unfortunately, that has not improved in the meantime..

#2 Updated by Robin Mills over 2 years ago

  • Assignee changed from Robin Mills to Andreas Huggel

Andreas volunteered to take on this challenge in 2015.

There is a topic on the forum concerning IPTC checksum/digest. Phil (Harvey) has made a very helpful comment about this. And I think we should investigate if something needs to done about this checksum when we update the XMP support.

#3 Updated by Robin Mills over 2 years ago

  • Target version changed from 0.25 to 0.26

#5 Updated by Andreas Huggel over 1 year ago

  • Target version changed from 0.26 to 1.0

#6 Updated by Robin Mills 11 months ago

  • Assignee changed from Andreas Huggel to Robin Mills
  • Target version changed from 1.0 to 0.27

#7 Updated by Alan Pater 8 months ago

It appears that Adobe has updated the XMP Toolkit again, current version is 2016.07

http://www.adobe.com/devnet/xmp.html

#8 Updated by Robin Mills 8 months ago

Yup. I've started to look at that on August 6.

575 rmills@rmillsmbp:~/gnu/xmpsdk/XMP-Toolkit-SDK-CC201607 $ ls -alt samples/target/macintosh/intel_64/Release/ReadingXMP 
-rwxr-xr-x+ 1 rmills  staff  103668  6 Aug 16:35 samples/target/macintosh/intel_64/Release/ReadingXMP
576 rmills@rmillsmbp:~/gnu/xmpsdk/XMP-Toolkit-SDK-CC201607 $ 
Andreas has said something like "everything concerning XMPsdk is a big pain in the butt". I prefer to tackle difficult stuff early in a project and leave smaller matters to the end. So this is likely to get attention during Fall 2016.

Also available in: Atom PDF

Redmine Appliance - Powered by TurnKey Linux