IPTC => XMP

[Gilles Caulier-4]

Andreas, Marcel,

I have finalized the new IPTC/IMM metadata editor from kipi-plugin. 90% of all IPTC/IIM tags are now supported.

It's time to study the new XMP metadata editor. I will base the future code from IPTC/IIM editor to support all IPTC4XMP tags.

I have writen an openoffice document where the IPTC/IIM editor dialog pages are described with all IPTC/IIM tags supported and the XMP tags associed. I have based the research using all papers provided by www.iptc.org and Adobe Xmp paper.

A lots of IPTC tags are identified as XMP or not (obsolete). Few one are in unknow... because i have a doubt or i have not found the corresponding entry in XMP papers.

My openoffice document is here : http://websvn.kde.org/trunk/extragear/libs/kipi-plugins/metadataedit/IPTCLIST.ODS?view=log

Please take a look and give me your viewpoint if all IPTC/IIM => XMP map are rights.

Thanks in advance

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Dnia Sunday 14 of October 2007, Gilles Caulier napisał:

> Andreas, Marcel,
>
> I have finalized the new IPTC/IMM metadata editor from kipi-plugin. 90%
> of all IPTC/IIM tags are now supported.
>
> It's time to study the new XMP metadata editor. I will base the future
> code from IPTC/IIM editor to support all IPTC4XMP tags.
>
> I have writen an openoffice document where the IPTC/IIM editor dialog
> pages are described with all IPTC/IIM tags supported and the XMP tags
> associed. I have based the research using all papers provided by
> www.iptc.org and Adobe Xmp paper.
>
> A lots of IPTC tags are identified as XMP or not (obsolete). Few one are
> in unknow... because i have a doubt or i have not found the
> corresponding entry in XMP papers.
>
> My openoffice document is here :
> http://websvn.kde.org/trunk/extragear/libs/kipi-plugins/metadataedit/IPT
>CLIST.ODS?view=log
>
> Please take a look and give me your viewpoint if all IPTC/IIM => XMP map
> are rights.

I am using Iptc4xmpCore 1.0 Spec as reference.

Tab Origin:

There is some mess with location. Iptc.Application2.CountryCode (and/or
LocationCode) should translate into Xmp.Iptc4xmpCore.CountryCode. In
Xmp.photoshop.Country should be full name of country not 3 letter code.

Tab Credits:

Iptc.Application2.Contact isn't totally obsolete:
Xmp.Iptc4xmpCore.CreatorContactInfo

Problem this should be split into total implementation following vCard
structure.

Tab Subjects:

Iptc.Application2.Subject -> Xmp.Iptc4xmpCore.SubjectCode

Tab Status:

Typo in second field: "EditSatus"

According to spec Job identifier field should be translated as
Xmp.photoshop.TransmissionReference but I see conflict here

Also not sure if Title really belongs here. Position suggests it is
title of comment, but this is title of object - not always the same.
I would swap headline and title or even moved title over headline in
Content tab.

Tab Properties:

If you really want some super control over it ReleaseDate and
ExpirationDate should be added to Informations (Status tab) or into
Xmp.xmpRights.UsageRights with automatic comment.

Tab Envelope:

The best place to put it into XMP is some automatic integration into
Instructions.

Some comments. I hope they are not too random :/

m.

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Big thanks Mik. I will review your tip...

Gilles

2007/10/14, Mikolaj Machowski <[hidden email]>:

Dnia Sunday 14 of October 2007, Gilles Caulier napisał:

> Andreas, Marcel,
>
> I have finalized the new IPTC/IMM metadata editor from kipi-plugin. 90%
> of all IPTC/IIM tags are now supported.
>
> It's time to study the new XMP metadata editor. I will base the future
> code from IPTC/IIM editor to support all IPTC4XMP tags.
>
> I have writen an openoffice document where the IPTC/IIM editor dialog
> pages are described with all IPTC/IIM tags supported and the XMP tags
> associed. I have based the research using all papers provided by
> www.iptc.org and Adobe Xmp paper.
>
> A lots of IPTC tags are identified as XMP or not (obsolete). Few one are
> in unknow... because i have a doubt or i have not found the
> corresponding entry in XMP papers.
>
> My openoffice document is here :
> http://websvn.kde.org/trunk/extragear/libs/kipi-plugins/metadataedit/IPT
>CLIST.ODS?view=log
>
> Please take a look and give me your viewpoint if all IPTC/IIM => XMP map
> are rights.

I am using Iptc4xmpCore 1.0 Spec as reference.

Tab Origin:

There is some mess with location. Iptc.Application2.CountryCode (and/or
LocationCode) should translate into Xmp.Iptc4xmpCore.CountryCode . In
Xmp.photoshop.Country should be full name of country not 3 letter code.

Tab Credits:

Iptc.Application2.Contact isn't totally obsolete:
Xmp.Iptc4xmpCore.CreatorContactInfo

Problem this should be split into total implementation following vCard
structure.

Tab Subjects:

Iptc.Application2.Subject -> Xmp.Iptc4xmpCore.SubjectCode

Tab Status:

Typo in second field: "EditSatus"

According to spec Job identifier field should be translated as
Xmp.photoshop.TransmissionReference but I see conflict here

Also not sure if Title really belongs here. Position suggests it is
title of comment, but this is title of object - not always the same.
I would swap headline and title or even moved title over headline in
Content tab.

Tab Properties:

If you really want some super control over it ReleaseDate and
ExpirationDate should be added to Informations (Status tab) or into
Xmp.xmpRights.UsageRights with automatic comment.

Tab Envelope:

The best place to put it into XMP is some automatic integration into
Instructions.

Some comments. I hope they are not too random :/

m.

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

I am using Iptc4xmpCore 1.0 Spec as reference.

Tab Origin:

There is some mess with location. Iptc.Application2.CountryCode (and/or
LocationCode) should translate into Xmp.Iptc4xmpCore.CountryCode. In
Xmp.photoshop.Country should be full name of country not 3 letter code.

Right. Fixed.
 

Tab Credits:

Iptc.Application2.Contact isn't totally obsolete:
Xmp.Iptc4xmpCore.CreatorContactInfo

Right. Fixed. 

Problem this should be split into total implementation following vCard
structure.

Right. planed.
 

Tab Subjects:

Iptc.Application2.Subject -> Xmp.Iptc4xmpCore.SubjectCode

Right. Fixed.

Note : Xmp.dc.subject != Xmp.iptc.SubjectCode.

Xmp.dc.subject are the famous Iptc.Application2.Keywords

Tab Status:

Typo in second field: "EditSatus"

Fixed
 

According to spec Job identifier field should be translated as
Xmp.photoshop.TransmissionReference but I see conflict here

Right for a tool dedicaced to transfert IPTC to XMP. For an XMP editor, the field disappears...

IPTC to XMP will be implemented into Exiv2 core (by Andreas)
 

Also not sure if Title really belongs here. Position suggests it is
title of comment, but this is title of object - not always the same.
I would swap headline and title or even moved title over headline in
Content tab.

Well, current layout is inspired from Photoshop 7.01 file info panel witch work like this...
 

Tab Properties:

If you really want some super control over it ReleaseDate and
ExpirationDate should be added to Informations (Status tab) or into
Xmp.xmpRights.UsageRights with automatic comment.

Andreas ?
 

Tab Envelope:

The best place to put it into XMP is some automatic integration into
Instructions.

I don't know this one yet from XMP. Andreas ?

After to read a full description of Dublin Core spec, the Iptc.Envelope.UNO must be stored in Xmp.dc.identifier

I have updated open office doc accordingly on svn...

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Gilles,

Here are some comments to your document. Since I am more concerned with
the formal aspects of the metadata, they may not be particularly
useful. I used the IPTC core XMP schema specs as a basis.

Tab Content:

Caption: Xmp.dc.description is a language alternative, i.e., digikam can
set the language of the caption, or allow the user to specify the
language or even allow for multiple captions in different languages.
One of them can be the default. (The same goes for all other properties
which are defined as language alternatives of course)

Tab Origin:

Creation date: The IPTC core XMP standard suggests to default this to
the corresponding Exif timestamp

Location: There is an Xmp.iptc.Location property. Not sure if it is
suitable.

Tab Credits:

Contact: There is an Xmp.iptc.CreatorContactInfo property and subfields
Ci* which may be suitable for this.

Tab Properties:

Release date/time: There is an XMP property Xmp.xmpDM.releaseDate, maybe
it can be used


Andreas
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

Andreas,

Revision #725474 of this document is already fixed in this way following tips from Mik.

http://websvn.kde.org/*checkout*/trunk/extragear/libs/kipi-plugins/metadataedit/IPTCLIST.ODS?revision=725474

See below :

2007/10/15, Andreas Huggel <[hidden email]>:

Gilles,

Here are some comments to your document. Since I am more concerned with
the formal aspects of the metadata, they may not be particularly
useful. I used the IPTC core XMP schema specs as a basis.

Tab Content:

Caption: Xmp.dc.description is a language alternative, i.e., digikam can
set the language of the caption, or allow the user to specify the
language or even allow for multiple captions in different languages.
One of them can be the default. (The same goes for all other properties
which are defined as language alternatives of course)

yes. Current dialog is based on IPTC/IIM editor not XMP. This is why multiple language description do not exist yet. of course, i will based the new XMP editor dialog on IPTC/IIM plus few improvements duing XMP new features. Lang-alt is one of this.

Note : new digiKam Database schema will include multiple comments from different authors and language. This will come with 0.10.0 release dedicaced to KDE4
 

Tab Origin:

Creation date: The IPTC core XMP standard suggests to default this to
the corresponding Exif timestamp

Yes, i have thinking about, but i would not touch Xmp.exif info  by default  and only dc, iptc, photoshop. It still in my todo.

Location: There is an Xmp.iptc.Location property. Not sure if it is
suitable.

Xmp.iptc.Location is not dedicaced to remplace Iptc.Application2.SubLocation and not Iptc.Application2.LocactionName/LocationCode ? Look on new revision on document. I have annoted Iptc.Application2.LocactionName /LocationCode as obsolete... It's fine ?
 

Tab Credits:

Contact: There is an Xmp.iptc.CreatorContactInfo property and subfields
Ci* which may be suitable for this.

==> already fixed in new document.
 

Tab Properties:

Release date/time: There is an XMP property Xmp.xmpDM.releaseDate, maybe
it can be used

Right. I have not take a care about xmpDM space.

And about expiratoin date, there is an XMP alternative ?

Gilles

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Dnia Thursday 25 of October 2007, Gilles Caulier napisał:
>
> And about expiratoin date, there is an XMP alternative ?
>

The only qualifying I found is Xmp.xmpRights.UsageTerms

m.


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel