[digikam] [Bug 351625] New: Support xmpMM history

[Alan Pater]

https://bugs.kde.org/show_bug.cgi?id=351625

            Bug ID: 351625
           Summary: Support xmpMM history
           Product: digikam
           Version: 4.12.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Metadata
          Assignee: [hidden email]
          Reporter: [hidden email]

The XMP specification and Adobe products appear to use the  XMP Media
Management Schema to manage the history of a given file, including versioning.

Digikam should implement the same history system to ensure compatibility.

Some related documentation can be found here:

http://wwwimages.adobe.com/content/dam/Adobe/en/products/xmp/pdfs/XMPAssetRelationships.pdf
http://www.hackerfactor.com/blog/index.php?/archives/552-Deep-Dive.html
http://www.exiv2.org/tags-xmp-xmpMM.html

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=351625

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #1 from Gilles Caulier <[hidden email]> ---
This specification is available in Exiv2 since which version exactly ?

Registered versionning info into this spec will work only with digiKam. There
is not advantage to use this Adobe namespace, as tools settings to use between
version are completely different and not compatible.

digiKam use already Xmp to store versionning info :

Xmp.digiKam.ImageHistory

http://dev.exiv2.org/projects/exiv2/repository/entry/tags/0.25/src/properties.cpp#L197

The only think that we can do is to get/put information linking image files to
make a sets of images.

Gilles

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Alan Pater]

https://bugs.kde.org/show_bug.cgi?id=351625

--- Comment #2 from Alan Pater <[hidden email]> ---
(In reply to Gilles Caulier from comment #1)
> This specification is available in Exiv2 since which version exactly ?

I'm not sure how long xmpMM been there, it predates my involvement with exiv2.
The web page listing those properties is dated May 2013.

>
> Registered versionning info into this spec will work only with digiKam.
> There is not advantage to use this Adobe namespace, as tools settings to use
> between version are completely different and not compatible.

You mean it is impossible to decode the field values written by Adobe products
and that other applications would be unable to decode the values written by
digikam?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=351625

--- Comment #3 from Gilles Caulier <[hidden email]> ---
I fear yes.

Example : I patch and image to fix WB. The settings is specific to digiKam
tool. Abode will be completely different. How to join both ?

Gilles

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel