IPTC Standard

Photo Metadata(July 2010)
IPTC Core
Specification Version 1.1

IPTC Extension
Specification Version 1.1
Document Revision 1

International Press Telecommunications Council
Copyright © 2010 - All Rights Reserved
www.iptc.org

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Copyrights
Copyright © 2010 IPTC, the International Press Telecommunications Council. All Rights Reserved.
This project intends to use materials that are either in the public domain or are available by the permission for theirrespective copyright holders. Permissions of copyright holders are obtained prior to use of protected material. All
materials of this IPTC standard covered by copyright shall be licensable at no charge.
This document is published under the License Agreement on page 4.

Acknowledgments
This document is the result of a team effort by members of the International Press Telecommunications Council,
with input and assistance from other contributors.
The effort to develop and maintain the IPTC Photo Metadata schemas was lead by Harald Löffler (Ifra) and Michael
Steidl (IPTC) and these persons contributed (ordered by surname):
Karl Csoknyay (Keystone Switzerland), Annette Feldman (AP), Jan Leidicke (BVPA), Cindy Lewis (PLUS), Andrea
de Polo (CEPIC/Alinari), David Riecks (PLUS), Sarah Saunders (BAPLA/CEPIC), Jeff Sedlik (PLUS), Klaus
Sprick (IPTC), Staffan Teste (CEPIC), Andy Williams (Ifra).

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 2 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

About the Standard
IPTC Core Specification Version History
VersionIssue Date

Approved by

1.0
1.1

2004-10-08
2008-07-02

IPTC Standards Committee
IPTC Standards Committee

Remarks

IPTC Extension Specification Version History
VersionIssue Date

Approved by

1.0
1.1

2008-07-02
2009-06-17

IPTC Standards Committee
IPTC Standards Committee

Remarks

Document Revision History
RevisionIssue Date

Author/revised by1

2010-07-08

Photo Md WG/M Steidl

Remarks

About this Document•••

This document specifies metadata properties intended to be used primarily, but not exclusively withphotos.
This document is a specification that may be revised to fix errata. Any changes will be indicated by a new
document revision number.
Any changes to the specification will be reflected by a change of the version of the standard.
This specification document will be supplemented by guidelines for end users and implementers of thisspecification.

Status of this Document

This document is under the governance of the IPTC Photo Metadata Working Group of the IPTC Standards
Committee.
This is a specification document endorsed by IPTC members and may be updated, replaced or made obsolete byother documents at any time.
A public version of this specification document is available at:
http://www.iptc.org/std/photometadata/specificationand of related IPTC documents at
http://www.iptc.org/std/photometadata/documentation
Public comments should be sent to the forum and mailing list at:
http://tech.groups.yahoo.com/group/iptc-photometadata
A page with all errata not covered by the latest version of the Photo Metadata specifications (July 2010, document
revision 1) is available at:
http://www.iptc.org/std/photometadata/specification/PhotoMetadataErrata.html

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 3 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

License Agreement
This document is issued under the
Non-Exclusive License Agreement for International Press Telecommunications Council
Specifications and Related Documentation
IMPORTANT: International Press Telecommunications Council (IPTC) standard specifications for news (theSpecifications) and supporting software, documentation, technical reports, web sites and other material related to
the Specifications (the Materials) including the document accompanying this license (the Document), whether in apaper or electronic format, are made available to you subject to the terms stated below. By obtaining, using and/or
copying the Specifications or Materials, you (the licensee) agree that you have read, understood, and will comply
with the following terms and conditions.
1. The Specifications and Materials are licensed for use only on the condition that you agree to be bound by theterms of this license. Subject to this and other licensing requirements contained herein, you may, on a nonexclusive basis, use the Specifications and Materials.
2. The IPTC openly provides the Specifications and Materials for voluntary use by individuals, partnerships,
companies, corporations, organizations and any other entity for use at the entity's own risk. This disclaimer, license
and release is intended to apply to the IPTC, its officers, directors, agents, representatives, members, contributors,
affiliates, contractors, or co-venturers acting jointly or severally.
3. The Document and translations thereof may be copied and furnished to others, and derivative works thatcomment on or otherwise explain it or assist in its implementation may be prepared, copied, published anddistributed, in whole or in part, without restriction of any kind, provided that the copyright and license notices andreferences to the IPTC appearing in the Document and the terms of this Specifications License Agreement areincluded on all such copies and derivative works. Further, upon the receipt of written permission from the IPTC,
the Document may be modified for the purpose of developing applications that use IPTC Specifications or as
required to translate the Document into languages other than English.
4. Any use, duplication, distribution, or exploitation of the Document and Specifications and Materials in any
manner is at your own risk.
5. NO WARRANTY, EXPRESSED OR IMPLIED, IS MADE REGARDING THE ACCURACY, ADEQUACY,COMPLETENESS, LEGALITY, RELIABILITY OR USEFULNESS OF ANY INFORMATION CONTAINED IN THE
DOCUMENT OR IN ANY SPECIFICATION OR OTHER PRODUCT OR SERVICE PRODUCED OR
SPONSORED BY THE IPTC. THE DOCUMENT AND THE INFORMATION CONTAINED HEREIN AND
INCLUDED IN ANY SPECIFICATION OR OTHER PRODUCT OR SERVICE OF THE IPTC IS PROVIDED ON
AN "AS IS" BASIS. THE IPTC DISCLAIMS ALL WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, ANY ACTUAL OR ASSERTED WARRANTY OF NON-INFRINGEMENT OF
PROPRIETARY RIGHTS, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. NEITHER THE
IPTC NOR ITS CONTRIBUTORS SHALL BE HELD LIABLE FOR ANY IMPROPER OR INCORRECT USE OF
INFORMATION. NEITHER THE IPTC NOR ITS CONTRIBUTORS ASSUME ANY RESPONSIBILITY FOR
ANYONE'S USE OF INFORMATION PROVIDED BY THE IPTC. IN NO EVENT SHALL THE IPTC OR ITSCONTRIBUTORS BE LIABLE TO ANYONE FOR DAMAGES OF ANY KIND, INCLUDING BUT NOT LIMITEDTO, COMPENSATORY DAMAGES, LOST PROFITS, LOST DATA OR ANY FORM OF SPECIAL, INCIDENTAL,
INDIRECT, CONSEQUENTIAL OR PUNITIVE DAMAGES OF ANY KIND WHETHER BASED ON BREACH OF
CONTRACT OR WARRANTY, TORT, PRODUCT LIABILITY OR OTHERWISE.
6. The IPTC takes no position regarding the validity or scope of any Intellectual Property or other rights that might
be claimed to pertain to the implementation or use of the technology described in the Document or the extent towhich any license under such rights might or might not be available. The IPTC does not represent that it has madeany effort to identify any such rights. Copies of claims of rights made available for publication, assurances oflicenses to be made available, or the result of an attempt made to obtain a general license or permission for theuse of such proprietary rights by implementers or users of the Specifications and Materials, can be obtained from
the Managing Director of the IPTC.
7. By using the Specifications and Materials including the Document in any manner or for any purpose, you release
the IPTC from all liabilities, claims, causes of action, allegations, losses, injuries, damages, or detriments of any
nature arising from or relating to the use of the Specifications, Materials or any portion thereof. You further agree
not to file a lawsuit, make a claim, or take any other formal or informal legal action against the IPTC, resulting fromyour acquisition, use, duplication, distribution, or exploitation of the Specifications, Materials or any portion thereof.
Finally, you hereby agree that the IPTC is not liable for any direct, indirect, special or consequential damages
IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 4 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Releasearising from or relating to your acquisition, use, duplication, distribution, or exploitation of the Specifications,
Materials or any portion thereof.
8. Specifications and Materials may be downloaded or copied provided that ALL copies retain the ownership,
copyright and license notices.
9. Materials may not be edited, modified, or presented in a context that creates a misleading or false impression orstatement as to the positions, actions, or statements of the IPTC.
10. The name and trademarks of the IPTC may not be used in advertising, publicity, or in relation to products orservices and their names without the specific, written prior permission of the IPTC. Any permitted use of the
trademarks of the IPTC, whether registered or not, shall be accompanied by an appropriate mark and attribution,
as agreed with the IPTC.
11. Specifications may be extended by both members and non-members to provide additional functionality(Extension Specifications) provided that there is a clear recognition of the IPTC IP and its ownership in the
Extension Specifications and the related documentation and provided that the extensions are clearly identified andprovided that a perpetual license is granted by the creator of the Extension Specifications for other members andnon-members to use the Extension Specifications and to continue extensions of the Extension Specifications. The
IPTC does not waive any of its rights in the Specifications and Materials in this context. The Extension
Specifications may be considered the intellectual property of their creator. The IPTC expressly disclaims any
responsibility for damage caused by an extension to the Specifications.
12. Specifications and Materials may be included in derivative work of both members and non-members provided
that there is a clear recognition of the IPTC IP and its ownership in the derivative work and its related
documentation. The IPTC does not waive any of its rights in the Specifications and Materials in this context.
Derivative work in its entirety may be considered the intellectual property of the creator of the work .The IPTC
expressly disclaims any responsibility for damage caused when its IP is used in a derivative context.
13. This Specifications License Agreement is perpetual subject to your conformance to the terms of thisAgreement. The IPTC may terminate this Specifications License Agreement immediately upon your breach of thisAgreement and, upon such termination you will cease all use, duplication, distribution, and/or exploitation in any
manner of the Specifications and Materials.
14. This Specifications License Agreement reflects the entire agreement of the parties regarding the subject
matter hereof and supersedes all prior agreements or representations regarding such matters, whether written ororal. To the extent any portion or provision of this Specifications License Agreement is found to be illegal or
unenforceable, then the remaining provisions of this Specifications License Agreement will remain in full force andeffect and the illegal or unenforceable provision will be construed to give it such effect as it may properly have thatis consistent with the intentions of the parties.
15. This Specifications License Agreement may only be modified in writing signed by an authorized representativeof the IPTC.
16. This Specifications License Agreement is governed by the law of United Kingdom, as such law is applied tocontracts made and fully performed in the United Kingdom. Any disputes arising from or relating to thisSpecifications License Agreement will be resolved in the courts of the United Kingdom. You consent to thejurisdiction of such courts over you and covenant not to assert before such courts any objection to proceeding insuch forums.
IF YOU DO NOT AGREE TO THESE TERMS YOU MUST CEASE ALL USE OF THE SPECIFICATIONS AND
MATERIALS NOW.
IF YOU HAVE ANY QUESTIONS ABOUT THESE TERMS, PLEASE CONTACT THE MANAGING DIRECTOR
OF THE INTERNATIONAL PRESS TELECOMMUNICATION COUNCIL.
AS OF THE DATE OF THIS REVISION OF THIS SPECIFICATIONS LICENSE AGREEMENT YOU MAYCONTACT THE IPTC at http://www.iptc.org .
License agreement version of: 30 January 2006

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 5 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Table of Contents
Introduction to IPTC Photo Metadata ............................................................................................................................................ 9
Overview ........................................................................................................................................................................................... 9Technical Metadata ........................................................................................................................................................................ 9
History ............................................................................................................................................................................................... 9
Photo Metadata specification notation ........................................................................................................................................10
The specification template..........................................................................................................................................................10
Generic specification notes .......................................................................................................................................................11
The terms Metadata Property and Metadata Structure ...................................................................................................11(legacy) appended to a property name ...............................................................................................................................11(DEPRECATED) appended to a property name...............................................................................................................11
Saving metadata values to files .............................................................................................................................................11
IPTC Core schema 1.1 specifications .........................................................................................................................................12
Names and Identifiers ..................................................................................................................................................................12
Metadata Properties.....................................................................................................................................................................12
City (legacy)...............................................................................................................................................................................12Country (legacy) .......................................................................................................................................................................12Country Code (legacy)............................................................................................................................................................13
Description.................................................................................................................................................................................13
Headline......................................................................................................................................................................................14Intellectual Genre .....................................................................................................................................................................14
Keywords....................................................................................................................................................................................15
Province or State (legacy) ......................................................................................................................................................15
Scene Code ..............................................................................................................................................................................16
Subject Code ............................................................................................................................................................................16
Sublocation (legacy) ................................................................................................................................................................17
Date Created .............................................................................................................................................................................17
Description Writer ....................................................................................................................................................................18
Instructions.................................................................................................................................................................................18
Job Id ...........................................................................................................................................................................................19
Title ..............................................................................................................................................................................................19
Copyright Notice ......................................................................................................................................................................20
Creator ........................................................................................................................................................................................20
Creator's Contact Info .............................................................................................................................................................21
Creator's jobtitle .......................................................................................................................................................................21
Credit Line .................................................................................................................................................................................22
Rights Usage Terms ................................................................................................................................................................22
Source.........................................................................................................................................................................................23

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 6 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Metadata Structure: Contact Information Details .................................................................................................................23
Contact Information Details structure {data type} .............................................................................................................23
Address {contact info detail} ..................................................................................................................................................24
City {contact info detail} ..........................................................................................................................................................24
Country {contact info detail} ..................................................................................................................................................24
Email address(es) {contact info detail} ................................................................................................................................25
Phone number(s) {contact info detail} .................................................................................................................................25
Postal Code {contact info detail} ..........................................................................................................................................26
State/Province {contact info detail} ......................................................................................................................................26
Web URL(s) {contact info detail} ..........................................................................................................................................27“Deprecated” IIM metadata elements ......................................................................................................................................27
Synchronising IIM elements with existing XMP properties .................................................................................................28
Guideline for mapping Category Codes to Subject NewsCodes ....................................................................................29
IPTC Extension schema 1.1 specifications.................................................................................................................................30
Names and Identifiers ..................................................................................................................................................................30
Metadata Properties.....................................................................................................................................................................30
Additional Model Information .................................................................................................................................................30
Artwork or Object in the Image .............................................................................................................................................30
Code of Organisation Featured in the Image ....................................................................................................................31
Controlled Vocabulary Term ..................................................................................................................................................31
Location Shown in the Image ................................................................................................................................................32
Model Age ..................................................................................................................................................................................32
Name of Organisation Featured in the Image ....................................................................................................................32
Person Shown in the Image ...................................................................................................................................................33
Digital Image GUID ..................................................................................................................................................................33
Digital Source File Type (DEPRECATED) .........................................................................................................................34
Digital Source Type .................................................................................................................................................................34
Event............................................................................................................................................................................................35
Image Registry Entry................................................................................................................................................................35
Image Supplier ..........................................................................................................................................................................36
Image Supplier Image ID ........................................................................................................................................................36
IPTC Metadata Last Edited (Legacy) ..................................................................................................................................36
Location created .......................................................................................................................................................................37
Max Avail Height .......................................................................................................................................................................37
Max Avail Width ........................................................................................................................................................................38
PLUS Version ............................................................................................................................................................................38
Copyright Owner ......................................................................................................................................................................39
Image Creator ...........................................................................................................................................................................39
Licensor ......................................................................................................................................................................................39
Minor Model Age Disclosure .................................................................................................................................................40
Model Release Id......................................................................................................................................................................40
IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 7 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Model Release Status .............................................................................................................................................................41
Property Release Id .................................................................................................................................................................41
Property Release Status .........................................................................................................................................................41
Metadata Structure: Artwork or Object in the Image Details .............................................................................................42
Artwork or Object in the Image Details structure {data type} ........................................................................................42
Copyright Notice {Artwork or Object detail} ......................................................................................................................42
Creator {Artwork or Object detail}........................................................................................................................................43
Date Created {Artwork or Object detail}.............................................................................................................................43
Source {Artwork or Object detail} ........................................................................................................................................44
Source Inventory Number {Artwork or Object detail} ......................................................................................................44
Title {Artwork or Object detail} ..............................................................................................................................................44
Metadata Structure: Location Details ......................................................................................................................................45
Location Details structure {data type}..................................................................................................................................45
City {location detail} .................................................................................................................................................................45
Country ISO-Code {location detail} .....................................................................................................................................46
Country Name {location detail}..............................................................................................................................................46
Province or State {location detail} ........................................................................................................................................47
Sublocation {location detail} ..................................................................................................................................................47
World Region {location detail}...............................................................................................................................................47
Metadata Structure: Registry Entry Details ............................................................................................................................48
Registry Entry Details structure {data type}........................................................................................................................48
Item Id {registry entry detail}...................................................................................................................................................48
Organisation Id {registry entry detail}...................................................................................................................................49
References..........................................................................................................................................................................................50
Addendum 1: Persistent Technical Photo Metadata – a recommendation .......................................................................51
Objectives for Technical Photo Metadata...............................................................................................................................51
Photo Workflows ..........................................................................................................................................................................51
Recommendations........................................................................................................................................................................54

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 8 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Introduction to IPTC Photo Metadata
Overview
IPTC Photo Metadata provides data about photographs and the values can be processed by software. Eachindividual metadata entity is called a property and they are grouped into Administrative, Descriptive and Rights
Related properties.
IPTC Photo Metadata properties have photo specific definitions that are widely supported by imaging software.
IPTC Photo Metadata aligns with other IPTC metadata standards that are made for media items of any media-type.
Thus they integrate with media-type agnostic digital asset management systems.
The IPTC Photo Metadata (July 2010) specification is split into two different schemas:- The IPTC Core 1.1 schema which refers back to properties from the IPTC “Information Interchange
Model” (IIM) standard [IPTC IIM].
- The IPTC Extension 1.1 schema extends and complements the IPTC Core schema by a set of moregranular properties and further specialised rights-related properties from the PLUS metadata schema[PLUS].
This allows users to decide whether ...
- ... to use only the IPTC Core schema that has a higher backward compatibility, but less refined metadata- ... or to use the IPTC Core and the IPTC Extension schema with refined and specialised metadata, but
restricted backward compatibility.
This document provides the latest specifications for both schemas.

Technical Metadata
Digital cameras capture metadata at the time the image is taken reflecting technical characteristics. Such
metadata may include, but is not limited to, generic camera metadata, camera manufacturer-specific metadata,
ICC profiles and positioning data. Standards for these metadata are not subject to IPTC Standards, but are under
the control of the camera manufacturers, their associations (such as CIPA) and others. Because the IPTC
acknowledges these technical metadata standards of other bodies and does not wish to duplicate existing
metadata properties, the IPTC Photo Metadata specification does not include any technical metadata.
Beyond that the IPTC Photo Metadata Working Group has studied several photo business processes in theindustry and discussed the requirements for the type of technical metadata and their handling in photo workflows.
As a result, recommendations for persistent Technical Photo Metadata were formulated and are appended to thisdocument as Addendum 1, but are not part of this standard. The recommendations are about the handling of
metadata when photos are stored and processed and may provide useful guidelines for the design of a workflow.

History

In1990, the IPTC developed its “Information Interchange Model” (IIM) metadata property standard for exchanging
news that was, by design, media-type agnostic and thus encouraged users to apply it to photos. A few years later,
the software company Adobe Systems Inc. adopted a subset of IIM properties for its imaging software Photoshop
and developed a metadata storage technology name “Image Resource Block” to embed the metadata properties
in a header section of the image files. From that moment on, millions of photographs were annotated using IIM
metadata.
In September 2001, Adobe introduced its new technical metadata framework “Extensible Metadata Platform(XMP)” [Adobe XMP] that will make the “Image Resource Blocks” sooner or later obsolete. The XML-based XMPtechnology is much more flexible and can deal better with globalisation requirements.
In 2004, the IPTC and Adobe jointly developed the “IPTC Core Schema for XMP” which is actually a redefinitionof the IIM properties in the new XMP environment; only a few properties were added.
In 2007, the IPTC collected requirements from different sectors of the professional photography business – with afocus on news photography and stock photography – and published these requirements in its Photo Metadata
White Paper 2007 [PhMdWP2007]. After receiving wide assent to this paper, the IPTC developed specifications
for the “IPTC Extension Schema” and slightly revised the IPTC Core specifications. Both specifications are
released in one document as “IPTC Photo Metadata” which was last updated in July 2010.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 9 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Photo Metadata specification notation
The specification template
This specification document provides for each photo metadata property a full specification consisting of:- A generic specification of its name, semantics, requirements and text to be used with the user interface ofa software implementing this property- A technical implementation specific for Adobe’s XMP technology [Adobe XMP]
- A technical implementation specific to IPTC’s G2-Standards. [IPTC G2-Standards]
The specifications of a Photo Metadata property are notated by a generic table. Please find below the template
table with explanations for each row in the right column:

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Basic data type
Required CV
Spec change history
XMP implementation
XMP namespace
XMP property id
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)A generic specification of the property which is agnostic to any implementation
technology.
Property Group (in blue): descriptive / administrative / rights related / a data type definition
This property grouping is not normative, only an indicator of general semantics
The reference name of the property used by this specification
This name shall never be translated
A media-type agnostic definition of the semantics of this property that may be translated for
localization.
A photo-specific definition of the semantics of this property that may be translated for localization.
A help text for this property which may be displayed by a generic help system of the user interface,and should be translated for localization.
Any notes that apply to the end user of this property, should be translated for localization.
Any notes that apply to parties implementing this property using any technology.
Text appearing next to the entry field in the user interface, that should be translated for localization.
How often this property may appear in a set of Photo Metadata for an image.
1 = is mandatory, 0..1 = one occurrence is optional, 1..unbounded = multiple occurrences are
optional
A recommended basic data typeThe identifier for a controlled vocabulary that must be used with this property.
A note in which version of the specification or, if there was an error in the specification document,
in which revision of this specification document a property was changed and how.
The implementation specification in the context of the Adobe XMP technology
The XMP namespace alias, see section “Names and Identifiers” of IPTC Core and IPTC Extension.
The identifying name of the property
The value type as per XMP specifications
XMP Category
External/Internal
Any note regarding the XMP-specific implementation
If this XMP property is mapped to an IIM property its IIM Data Set id and name appears in this row.
Any note on how to access an XMP property for mapping it to the corresponding IIM property.
The technical implementation specification for IPTC G2-Standards
If this section is left empty no straightforward mapping is possible or recommended, because ofeither blurred semantics of a photo property or not having an equivalent G2-property.
The property in G2-Standards which corresponds to this Photo Metadata property, expressed by
an XPath for a G2 item.
Attributes of G2 properties as they should be used.
The scheme-URI of a required controlled vocabulary.
Any note regarding the G2-specific implementation.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 10 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Generic specification notes
The terms Metadata Property and Metadata Structure
The term Metadata Property is used for data about the image content. A metadata property can be made to
hold only a single kind of value, or a structure of differ rent values, for which the term Metadata Structure is
used.
Examples:*The metadata property Description is made for only one kind of value, a text string, but may provide this value
in different languages. It is important to understand that language translations are NOT a metadata structure.
* The property Artwork or Object in the Image is providing a structure of 6 sub-fields, and is not designed for
only a single value.
For a property using a structure, the string “structure” is used in the “Basic data type” cell of its specificationtable. In this case, check the XMP Value Type cell of the table and refer to the corresponding structure
identified in it.
For all structures specified by the IPTC this document includes the specification tables for all members of astructure.
For all structures specified by another standardisation body, in particular by PLUS, the specifications of thestructure can only be found in the specification documents (website, PDF document ...) of this body.
(legacy) appended to a property name
This suffix is used if the IPTC Extension provides a better solution to annotate the information about an image
than the IPTC Core does. In this case, the IPTC recommends to phase out the use of the (legacy)-marked
property and to move towards using the IPTC Extension. See the notes on this matter in the particularspecification table.
(DEPRECATED) appended to a property name
This suffix is used for properties which should not be used any longer. A reason for this is given in the spectable of the property and may include a recommendation to use a different property in the future.
Saving metadata values to files
The values of properties may be saved by both the IIM format and the XMP format in a single image file. A
guideline on how to synchronise values existing in parallel is available from the Metadata Working Group[MetadataWG]

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 11 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

IPTC Core schema 1.1 specifications
Names and Identifiers
The XML namespace URI for the “IPTC Core” versions 1.0 and 1.1 is:
http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/
The preferred XML namespace-prefix for “IPTC Core” related XMP properties is: Iptc4xmpCore
The use of this namespace-prefix is not mandatory, but highly recommended for interoperability support.
These other namespaces are used in the scope of IPTC Core:
Name
URI
Dublin Core
http://purl.org/dc/elements/1.1/
Photoshop
http://ns.adobe.com/photoshop/1.0/

Recommended/used Prefixdc
photoshop

User interfaces (like the custom panels in Adobe CS products) showing “IPTC Core” properties must refer to thisschema as an “IPTC Core” or “IPTC” panel.

Metadata Properties
Generic Specification

Name
Definition

Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descr

City (legacy)
Name of the city the content is focussing on -- either the place shown in visual media orreferenced by text or audio media. This element is at the third level of a top-down
geographical hierarchy.
Name of the city of the location shown in the image. This element is at the third level of a
top-down geographical hierarchy.
Enter the name of the city pictured in this image
This is a detail of a location with blurred semantics as it does not clearly indicate whether
it is the location in the image or the location the photo was taken - which can be different.
Two more concise properties are available in IPTC Extension with Location Created andLocation Shown in the Image.
City
0..1

Definition

Photo Definition

free-text

XMP property id
XMP Category

City
External

Legacy status assigned in v 1.1
photoshop
Text
2:90 City

Do not map this property. Use either Location Created or Location Shown in the Image of
the IPTC Extension schema if available.

Generic Specification

Name

Basic data type2descrCountry (legacy)
Full name of the country the content is focussing on -- either the country shown in visualmedia or referenced in text or audio media. This element is at the top/first level of a topdown geographical hierarchy. The full name should be expressed as a verbal name andnot as a code, a code should go to the element "CountryCode"Full name of the country of the location shown in the image. This element is at the top/firstlevel of a top-down geographical hierarchy. The full name should be expressed as averbal name and not as a code, a code should go to the element "CountryCode"

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 12 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Production - Public Release

Enter the name of the country pictured in this image
This is a detail of a location with blurred semantics as it does not clearly indicate whether
it is the location in the image or the location the photo was taken - which can be different.
Two more concise properties are available in IPTC Extension with Location Created andLocation Shown in the Image.
Country
0..1

Basic data typefree-text

XMP property id
XMP Category

Country
External

Legacy status assigned in v 1.1
photoshop
Text

2:101 Country/Primary Location Name

Do not map this property. Use either Location Created or Location Shown in the Image of
the IPTC Extension schema if available.

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descrCountry Code (legacy)
Code of the country the content is focussing on -- either the country shown in visual media
or referenced in text or audio media. This element is at the top/first level of a top-down
geographical hierarchy. The code should be taken from ISO 3166 two or three letter code.
The full name of a country should go to the "Country" element.
Code of the country of the location shown in the image. This element is at the top/firstlevel of a top-down geographical hierarchy. The code should be taken from ISO 3166 twoor three letter code. The full name of a country should go to the "Country" element.
Enter the 2 or 3 letter ISO 3166 Country Code of the Country pictured in this image
This is a detail of a location with blurred semantics as it does not clearly indicate whether
it is the location in the image or the location the photo was taken - which can be different.
Two more concise properties are available in IPTC Extension with Location Created andLocation Shown in the Image.
ISO Country Code
0..1
Basic data typeISO 3166-1 - 2 or 3 characters (see Definition)
Legacy status assigned in v 1.1

XMP property id CountryCode
Iptc4xmpCore
closed choice Text
XMP Category External
Note 1: an implementer would have to derive from the length of the value string whether
this is the country code from the two or three letter scheme as no explicit indication can beprovided.
2:100 Country/Primary Location Code

Do not map this property. Use either Location Created or Location Shown in the Image of
the IPTC Extension schema if available.

Generic Specification

Name
Definition
Photo Definition
Photo Help Text

CV-code2descrDescription
A textual description, including captions, of the item's content, particularly used where theobject is not text.
A textual description, including captions, of the image.
Enter a "caption" describing the who, what, and why of what is happening in this image,

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 13 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

this might include names of people, and/or their role in the action that is taking place
within the image.
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Caption/Description
0..1

Basic data typefree-text

XMP property id descriptiondcLang AltXMP Category External
Note: the XMP property (dc:description) which stores the value of this IPTC Core property
is of type Lang Alt. Hence any software agent dealing with this property must abide to theprocessing rules for Lang Alt value type as specified by the XMP specifications.
2:120 Caption/Abstract
Use this XPath: dc:description/*[@xml:lang='x-default']/newsItem/contentMeta/description@role="drol:caption"

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descrHeadline
A brief synopsis of the caption. Headline is not the same as Title.
A brief synopsis of the caption. Headline is not the same as Title.
Enter a brief publishable synopsis or summary of the contents of the image

Headline
0..1

Basic data typefree-text

photoshop
Text

XMP property id
XMP Category

Headline
External

2:105 Headline/newsItem/contentMeta/headline

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history

2descrIntellectual Genre
Describes the nature, intellectual, artistic or journalistic characteristic of a item, notspecifically its content.
Describes the nature, intellectual, artistic or journalistic characteristic of an image.
Enter a term to describe the nature of the image in terms of its intellectual or journalistic
characteristics, such as daybook, or feature (examples at: http://www.newscodes.org/)
The IPTC recognizes that the corresponding IPTC Genre NewsCodes needs photospecific extension to be better usable with this field (as of the release of this standard in
the year 2008).
Intellectual genre
0..1
Basic data type
Optional: IPTC Genre NewsCodes

free-text

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 14 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)IntellectualGenre
External

Iptc4xmpCore
Text
Note / Examples:

XMP property id
XMP Category

Journalistic genres: actuality, interview, background, feature, summary, wrapup
News category related genres: daybook, obituary, press release, transcript

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)It is advised to use terms from a controlled vocabulary.
2:04 Object Attribute Reference/newsItem/contentMeta/genre/@literal

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descr

Keywords
Keywords to express the subject of the content. Keywords may be free text and don't
have to be taken from a controlled vocabulary. Codes from the controlled vocabulary
IPTC Subject NewsCodes must go to the "Subject Code" field.
Keywords to express the subject of the image. Keywords may be free text and don't haveto be taken from a controlled vocabulary. Codes from the controlled vocabulary IPTC
Subject NewsCodes must go to the "Subject Code" field.
Enter any number of keywords, terms or phrases used to express the subject matter in
the image.
Single values of this field should not be restricted to single words but must allow forphrases as well.
Keywords
0..unbounded
Basic data type free-textdc
bag Text

XMP property id
XMP Category

subject
External

2:25 Keywords/newsItem/contentMeta/subject/@literal

Generic Specification

Name
Definition

Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV

2descr

Province or State (legacy)
Name of the subregion of a country -- either called province or state or anything else -- thecontent is focussing on -- either the subregion shown in visual media or referenced by text
or audio media. This element is at the second level of a top-down geographical hierarchy.
Name of the subregion of a country of the location shown in the image. This element is at
the second level of a top-down geographical hierarchy.
Enter the name of the province or state pictured in this image
This is a detail of a location with blurred semantics as it does not clearly indicate whether
it is the location in the image or the location the photo was taken - which can be different.
Two more concise properties are available in IPTC Extension with Location Created andLocation Shown in the Image.
Province/State
0..1

Basic data typestring

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 15 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Production - Public Release

Legacy status assigned in v 1.1
photoshop
Text

XMP property id
XMP Category

State
External

2:95 Province/State

Do not map this property. Use either Location Created or Location Shown in the Image of
the IPTC Extension schema if available.

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)2descrScene CodeDescribes the scene of a news content. Specifies one or more terms from the IPTC
"Scene-NewsCodes". Each Scene is represented as a string of 6 digits in an unordered
list.
Describes the scene of a photo content. Specifies one ore more terms from the IPTC
"Scene-NewsCodes". Each Scene is represented as a string of 6 digits in an unordered
list.
Enter only values from the IPTC Scene NewsCodes Controlled Vocabulary (see:http://www.newscodes.org/)

IPTC Scene Code0..unbounded
IPTC Scene NewsCodes

Basic data typeCV-codeXMP property id Scene
Iptc4xmpCore
bag closed choice Text
XMP Category External
Note: Only Scene values from this IPTC taxonomy should be used here. More about the
IPTC Scene-NewsCodes at www.newscodes.org.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)/newsItem/contentMeta/genre/@qcode
IPTC Scene NewsCodes

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history

2descrSubject CodeSpecifies one or more Subjects from the IPTC Subject-NewsCodes taxonomy tocategorise the content. Each Subject is represented as a string of 8 digits in an unordered
list.
Specifies one or more Subjects from the IPTC Subject-NewsCodes taxonomy tocategorise the image. Each Subject is represented as a string of 8 digits in an unordered
list.
Enter only values from the IPTC Subject NewsCode Controlled Vocabulary (see:http://www.newscodes.org/)

IPTC Subject Code0..unbounded
IPTC Subject NewsCodes

Basic data typeCV-codeIPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 16 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Production - Public Release

XMP property id SubjectCode
Iptc4xmpCore
bag closed choice Text
XMP Category External
Note: Only Subjects from a controlled vocabulary should be used here, free text has to be
put into the Keyword element. More about IPTC Subject-NewsCodes atwww.newscodes.org.
2:12 Subject Reference/newsItem/contentMeta/subject/@qcode
IPTC Subject NewsCodes

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descr

Sublocation (legacy)
Name of a sublocation the content is focussing on -- either the location shown in visualmedia or referenced by text or audio media. This location name could either be the nameof a sublocation to a city or the name of a well known location or (natural) monument
outside a city. In the sense of a sublocation to a city this element is at the fourth level of a
top-down geographical hierarchy.
Exact name of the sublocation shown in the image. This sublocation name could either be
the name of a sublocation to a city or the name of a well known location or (natural)monument outside a city. In the sense of a sublocation to a city this element is at the
fourth level of a top-down geographical hierarchy.
Enter the name of the Sublocation pictured in this image
This is a detail of a location with blurred semantics as it does not clearly indicate whether
it is the location in the image or the location the photo was taken - which can be different.
Two more concise properties are available in IPTC Extension with Location Created andLocation Shown in the Image.
Sublocation
0..1

Name
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality

free-text

XMP property id
XMP Category

Location
External

Legacy status assigned in v 1.1
Iptc4xmpCore
Text
2:92 Sublocation

Do not map this property. Use either Location Created or Location Shown in the Image of
the IPTC Extension schema if available.

Generic Specification
Definition

Basic data type3adminDate Created
Designates the date and optionally the time the intellectual content was created rather
than the date of the creation of the physical representation.
Designates the date and optionally the time the content of the image was created rather
than the date of the creation of the digital representation.
Enter the Date the image was taken
If a software system requires explicit time values and no time is given by the Date Createdproperty the softwaresystem should default the time to 00:00:00. If the software system does not require an
explicit time value the time part should be left empty as it is.
Date Created
0..1
Basic data type DateTime (preferred: truncated
DateTime)

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 17 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)XMP property id DateCreatedphotoshop
Date
XMP Category External
Note 1: Any content of the IIM dataset 2:60, Time Created, should be merged to thiselement.
Note 2: Implementers are encouraged to provide the creation date and time from the EXIF
data of a digital camera to the user for entering this date for the first time.
2:55 Date Created/newsItem/contentMeta/contentCreatedGeneric Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)3adminDescription Writer
Identifier or the name of the person involved in writing, editing or correcting the descriptionof the content.
Identifier or the name of the person involved in writing, editing or correcting the descriptionof the image.
Enter the name of the person involved in writing, editing or correcting the description of
the image

Caption/Description writer
0..1

photoshop
Text

Basic data type

XMP property id
XMP Category

free-text

CaptionWriter
External

2:122 Writer/Editor/newsitem/contentMeta/contributor@role="ctrol:descrWriter"

Generic Specification

Name
Definition
Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history

3adminInstructions
Any of a number of instructions from the provider or creator to the receiver of the item.
Any of a number of instructions from the provider or creator to the receiver of the image
which might include any of the following: embargoes (NewsMagazines OUT) and otherrestrictions not covered by the "Rights Usage Terms" field; information regarding theoriginal means of capture (scanning notes, colourspace info) or other specific text
information that the user may need for accurate reproduction; additional permissions
required when publishing; credits for publishing if they exceed the IIM length of the credit
fieldEnter information about embargoes, or other restrictions not covered by the Rights Usage
field

Instructions
0..1

Basic data typefree-text

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 18 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)photoshop
Text

XMP property id
XMP Category

Production - Public Release
Instructions
External

2:40 Special Instruction/newsItem/itemMeta/edNote

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)3adminJob IdNumber or identifier for the purpose of improved workflow handling. This is a user created
identifier related to the job for which the item is supplied.
Number or identifier for the purpose of improved workflow handling. This is a user created
identifier related to the job for which the image is supplied.
Enter a number or identifier needed for workflow control or tracking

Job Identifier
0..1

Basic data typefree-text

XMP property id TransmissionReference
photoshop
Text
XMP Category External
Note: As this identifier references a job of the receiver's workflow it must first be issued by
the receiver, then transmitted to the creator or provider of the news object and finallyadded by the creator to this field.
2:103 Original Transmission Reference/newsItem/itemMeta/memberOf/@literal

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)3adminTitle
A shorthand reference for the item. Title provides a short human readable name which
can be a text and/or numeric reference. It is not the same as Headline.
A shorthand reference for the digital image. Title provides a short human readable namewhich can be a text and/or numeric reference. It is not the same as Headline.
Enter a short verbal and human readable name for the image, this may be the file nameMany use the Title field to store the filename of the image, though the field may be usedin many ways. Formal identifiers are provided by the Digital Image Id, or the Registry
Entry property of the IPTC Extension.
Title
0..1

Basic data typefree-text

XMP property id titledcLang AltXMP Category External
Note 1: This element aligns with the use of Dublin Core's "Title" element.
Note 2: the XMP property (dc:title) which stores the value of this IPTC Core property is oftype Lang Alt. Hence any software agent dealing with this property must abide to theprocessing rules for Lang Alt value type as specified by the XMP specifications.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 19 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Production - Public Release

2:05 Object Name
Use this XPath: dc:title/*[@xml:lang='x-default']/newsItem/itemMeta/title

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

Copyright Notice
Contains any necessary copyright notice for claiming the intellectual property for this itemand should identify the current owner of the copyright for the item. Other entities like thecreator of the item may be added in the corresponding field. Notes on usage rights should
be provided in "Rights usage terms".
Contains any necessary copyright notice for claiming the intellectual property for thisphotograph and should identify the current owner of the copyright for the photograph.
Other entities like the creator of the photograph may be added in the corresponding field.
Notes on usage rights should be provided in "Rights usage terms".
Enter a Notice on the current owner of the Copyright for this image, such as ©2008 JaneDoe
Copyright ownership can be expressed in a more controlled way using the PLUS fields"Copyright Owner", "Copyright Owner ID", "Copyright Owner Name" of the IPTC
Extension. It is the user's responsibility to keep the values of the four fields in sync.
Copyright Notice
0..1

Basic data typefree-text

XMP property id rights
dc
Lang AltXMP Category External
Note: the XMP property (dc:rights) which stores the value of this IPTC Core property is oftype Lang Alt. Hence any software agent dealing with this property must abide to theprocessing rules for Lang Alt value type as specified by the XMP specifications.
2:116 Copyright Notice
Use this XPath: dc:rights/*[@xml:lang='x-default']/newsItem/rightsInfo/copyrightNotice

Generic Specification

Name
Definition

Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace

4rightrel

CreatorContains the name of the person who created the content of this item, a photographer forphotos, a graphic artist for graphics, or a writer for textual news, but in cases where thephotographer should not be identified the name of a company or organisation may beappropriate.
Contains the name of the photographer, but in cases where the photographer should not
be identified the name of a company or organisation may be appropriate.
Enter the name of the person that created this image
The creator can be expressed in a more controlled way using the "Image Creator" of
PLUS in the IPTC Extension additionally. It is the user's responsibility to keep the valuesof the IPTC Core and the PLUS fields in sync.
Synchronising this Creator property with PLUS' Image Creator Name should be supported
by software.
Creator0..unbounded
Basic data type string
Specs (July 2010): mapping IIM <-> XMP aligned to the unbounded cardinality of both the
IIM and the XMP propertydc

XMP property id

creator

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 20 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Seq ProperName

XMP Category

Production - Public Release
External

2:80 By-line/newsItem/contentMeta/creator/name

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)4rightrel

Creator's Contact Info
The creator's contact information provides all necessary information to get in contact withthe creator of this item and comprises a set of sub-properties for proper addressing.
The creator's contact information provides all necessary information to get in contact withthe creator of this image and comprises a set of sub-properties for proper addressing.
The IPTC Extension Licensor fields should be used instead of these Creator's Contact
Info fields if you are using IPTC Extension fields. If the creator is also the licensor his or
her contact information should be provided in the Licensor fields.
The structure of Creator's Contact Info should not be visible to the user.
Creator's Contact info
0..1
Basic data type struct

XMP property id CreatorContactInfo
Iptc4xmpCore
struct ContactInfo
XMP Category External
Note 1 to user interface implementers: All sub-properties of "Creator's contact
information" should be shown as group on the form.
Note 2: the CreatorContactInfo sub-properties' naming aligns with the vCard specification
RFC 2426.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)/newsItem/contentMeta/creator/personDetails ....

Generic Specification

Name
Definition

Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)4rightrel

Creator's jobtitle
Contains the job title of the person who created the content of this item. As this is sort of aqualifier the Creator element has to be filled in as mandatory prerequisite for using
Creator's Jobtitle.
Contains the job title of the photographer. As this is sort of a qualifier the Creator element
has to be filled in as mandatory prerequisite for using Creator's Jobtitle.
Enter the Job Title of the person listed in the Creator field

Creator's Jobtitle
0..1

Basic data typestring

XMP property id AuthorsPosition
photoshop
Text
XMP Category External
Note 1 {added in (July 2010)}: corresponds to the first entry in a sequence of creators
2:85 By-line Title

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 21 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Production - Public Release/newsItem/contentMeta/creator/facet

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

Credit LineThe credit to person(s) and/or organisation(s) required by the supplier of the item to be
used when published. This is a free-text field.
The credit to person(s) and/or organisation(s) required by the supplier of the image to be
used when published. This is a free-text field.
Enter who should be credited when this image is published
Note 1: For more formal identifications of the creator or the owner of the copyrights of thisimage other rights properties may be used.
Note 2: This property was named "Credit" by the IIM metadata, then it was renamed to"Provider" in IPTC Core 1.0. In IPTC Core 1.1. it has been renamed to "Credit Line" as thefield is used for this purpose by many users.
Credit Line
0..1

Basic data typefree-text

Renamed from Provider to Credit Line in v 1.1
photoshop
Text

XMP property id
XMP Category

CreditExternal

2:110 Credit/newsItem/contentMeta/creditline

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

Rights Usage Terms
The licensing parameters of the item expressed in free-text.
The licensing parameters of the image expressed in free-text.
Enter instructions on how this image can legally be used
The PLUS fields of the IPTC Extension can be used in parallel to express the licensed
usage in more controlled terms.
Rights Usage Terms
0..1

xmpRights
Lang Alt

Basic data type

XMP property id
XMP Category

free-text

UsageTerms
External/newsItem/rightsInfo/usageTerms

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 22 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

SourceIdentifies the original owner of the copyright for the intellectual content of the item. This
could be an agency, a member of an agency or an individual. Source could be different
from Creator and from the entities in the CopyrightNotice.
Identifies the original owner of the copyright for the intellectual content of the image. This
could be an agency, a member of an agency or an individual. Source could be different
from Creator and from the entities in the CopyrightNotice.
Enter the original owner of the copyright of this image
This field may be used primarily in syndication workflows.
Source0..1

Basic data typefree-text

XMP property id Source
photoshop
Text
XMP Category External
The original owner can never change. For that reason the content of this property should
never be changed or deleted after the information is entered following the news object's
initial creation.
2:115 Source/newsItem/rightsInfo/copyrightHolder

Metadata Structure: Contact Information Details
Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)9type-ContInfo

Contact Information Details structure {data type}
A generic structure providing a basic set of information to get in contact with a person ororganisation. It includes an Address, a City, a Country, Email address, Phone number, aPostal Code, a State or Province and Web URL.
A generic structure providing a basic set of information to get in contact with a person ororganisation. It includes an Address, a City, a Country, Email address, Phone number, aPostal Code, a State or Province and Web URL.

Contact Information
Basic data typestructure

XMP property id ContactInfoDetails
Iptc4xmpCore
structure
XMP Category
Adoption of an appropriate person information scheme discussed - decision on 9
September.
2:118 Contact
NONE

Maps to the "contactInfo" common component

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 23 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)9type-ContInfo

Address {contact info detail}The contact information address part. Comprises an optional company name and all
required information to locate the building or postbox to which mail should be sent. To that
end, the address is a multiline field.
The contact information address part. Comprises an optional company name and all
required information to locate the building or postbox to which mail should be sent. To that
end, the address is a multiline field.
Enter Address for the person that created this image(Contact Info detail:) Address
0..unbounded

Basic data typestring

XMP property id CiAdrExtadr
Iptc4xmpCore
Text
XMP Category External
Note 1: to user interface implementers: This field should be part of a "Contact information"group on the form.
Note 2: the ContactInfo naming aligns with the vCard specification RFC 2426.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s).../contactInfo/address/line

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)9type-ContInfo

City {contact info detail}The contact information city part.
The contact information city part.
Enter the City for the address of the person that created this image(Contact Info detail:) City
0..1

Basic data typestring

XMP property id CiAdrCity
Iptc4xmpCore
Text
XMP Category External
Note 1: to user interface implementers: This field should be part of a "Contact information"group on the form.
Note 2: the ContactInfo naming aligns with the vCard specification RFC 2426.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s).../contactInfo/address/locality/name

Generic Specification

Name
Definition
Photo Definition
Photo Help Text

9type-ContInfo

Country {contact info detail}The contact information country part.
The contact information country part.
Enter the Country name for the address of the person that created this image

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 24 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)(Contact Info detail:) Country
0..1

Basic data type

Production - Public Releasestring

XMP property id CiAdrCtry
Iptc4xmpCore
Text
XMP Category External
Note 1: to user interface implementers: This field should be part of a "Contact information"group on the form.
Note 2: the ContactInfo naming aligns with the vCard specification RFC 2426.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s).../contactInfo/address/country/name

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)9type-ContInfo

Email address(es) {contact info detail}The contact information email address part.
The contact information email address part.
Enter the work Email address(es) for the person that created this image, such as
name@domain.com
Multiple email addresses can be given. May have to be separated by a comma in the userinterface.
(Contact Info detail:) Email(s)0..unbounded

Basic data typestring

XMP property id CiEmailWork
Iptc4xmpCore
Text
XMP Category External
Note 1 to user interface implementers: This field should be part of a "Contact information"group on the form.
Note 2 to user interface implementers: provide sufficient space to fill in multiple e-mailaddresses.
Note 3: the ContactInfo naming aligns with the vCard specification RFC 2426.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s).../contactInfo/email

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV

9type-ContInfo

Phone number(s) {contact info detail}The contact information phone number part.
The contact information phone number part.
Enter the work Phone number(s) for the person that created this image, using theinternational format, such as +1 (123) 456789
Multiple numbers can be given. May have to be separated by a comma in the userinterface.
(Contact Info detail:) Phone(s)0..unbounded

Basic data typestring

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 25 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)XMP property id CiTelWork
Iptc4xmpCore
Text
XMP Category External
Note 1 to user interface implementers: This field should be part of a "Contact information"group on the form.
Note 2 to user interface implementers: provide sufficient space to fill in multiple
international numbers.
Note 3: the ContactInfo naming aligns with the vCard specification RFC 2426.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s).../contactInfo/phone

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)9type-ContInfo

Postal Code {contact info detail}The contact information part denoting the local postal code.
The contact information part denoting the local postal code.
Enter the Postal Code for the address of the person that created this image(Contact Info detail:) Postal Code
0..1
Basic data typestring

XMP property id CiAdrPcode
Iptc4xmpCore
Text
XMP Category External
Note 1: to user interface implementers: This field should be part of a "Contact information"group on the form.
Note 2: the ContactInfo naming aligns with the vCard specification RFC 2426.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s).../contactInfo/address/postalCode

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)9type-ContInfo

State/Province {contact info detail}The contact information part denoting regional information such as state or province.
The contact information part denoting regional information such as state or province.
Enter the State for the address of the person that created this image(Contact Info detail:) State/Province
0..1
Basic data typestring

XMP property id CiAdrRegion
Iptc4xmpCore
Text
XMP Category External
Note 1: to user interface implementers: This field should be part of a "Contact information"group on the form.
Note 2: the ContactInfo naming aligns with the vCard specification RFC 2426.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 26 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s).../contactInfo/address/area

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)9type-ContInfo

Web URL(s) {contact info detail}The contact information web address part. Multiple addresses can be given, separated by
a comma.
The contact information web address part. Multiple addresses can be given. May have to
be separated by a comma in the user interface.
Enter the work Web URL(s) for the person that created this image, such as
http://www.domain.com/(Contact Info detail:) Web URL(s)0..unbounded
Basic data typeURL

XMP property id CiUrlWork
Iptc4xmpCore
Text
XMP Category External
Note 1 to user interface implementers: This field should be part of a "Contact information"group on the form.
Note 2 to user interface implementers: provide sufficient space to fill in multiple URLs.
Note 3: the ContactInfo naming aligns with the vCard specification RFC 2426.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s).../contactInfo/web“Deprecated” IIM metadata elements

Not all of the IIM datasets adopted by Adobe to be used for the Photoshop File Info have been adopted for the
IPTC Core schema. In terms of mapping and transferring metadata from the legacy IIM-based headers, thesedatasets must to be considered as deprecated:
Urgency: As this metadata element pertains to distribution management, it was not adopted. However, this data is
still synchronised with the XMP property “photoshop:Urgency”, and hence, available for future use, but outside
the IPTC Core.
Category: As this metadata element was earmarked as deprecated already for IIM 4.1, it was not adopted.
However, this data is still synchronised with the XMP property “photoshop:Category”, and hence available for
future use – but outside the IPTC Core.
For migrating from Category codes to Subject Codes please read the Guideline for mapping Category Codes
to Subject NewsCodes section below.
Supplemental Categories: As this metadata element was earmarked as deprecated already for IIM 4.1, it was
not adopted. However, this data is still synchronised with the XMP property“photoshop:SupplementalCategories”, and hence available for future use – but outside the IPTC Core.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 27 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Synchronising IIM elements with existing XMP properties
This table shows how legacy metadata elements from the “IPTC header” – which were taken from the IPTC
Information Interchange Model IIM are synchronised by Adobe Photoshop CS with XMP properties.
<--legacy IPTC headers--->
Photoshop name
IIM name
Title
2:05 Object Name
Urgency
2:10 Urgency
Category
2:15 Category
Supplemental Categories 2:20 Supplemental Category
Keywords
2:25 Keywords
Instructions
2:40 Special Instruction
Date Created
2:55 Date CreatedAuthor2:80 By-line
AuthorsPosition
2:85 By-line Title
City
2:90 City
State/Province
2:95 Province/StateCountry
2:101 Country/Primary Location NameTransmission Reference
2:103 Original Transmission Reference
Headline
2:105 Headline
Credit2:110 Credit
Source2:115 Source
Copyright Notice
2:116 Copyright Notice
Description
Description Writer

2:120 Caption/Abstract
2:122 Writer/Editor

XMP
Mapping (XPath expression)
dc:title/*[@xml:lang='x-default']
photoshop:Urgency
photoshop:Category
photoshop:SupplementalCategories
dc:subject
photoshop:Instructions
photoshop:DateCreateddc:creator
photoshop:AuthorsPosition
photoshop:City
photoshop:State
photoshop:Country
photoshop:TransmissionReference
photoshop:Headline
photoshop:Credit
photoshop:Source
dc:rights/*[@xml:lang='x-default']
dc:description/*[@xml:lang='xdefault']
photoshop:CaptionWriter

As of July 2010.
For the exact processing while synchronising metadata values please read the Guidelines for Handling Image
Metadata from the Metadata Working Group. The document can be obtained fromhttp://www.metadataworkinggroup.org/specs/

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 28 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Guideline for mapping Category Codes to Subject NewsCodes
Early versions of IIM included the Datasets 2:15 “Category” and 2:20 “Supplemental Category”. But these two
fields were replaced in IIM version 4 (released in 1999) by the Dataset 2:12 “Subject Reference” which must be
populated by values from the Subject NewsCodes controlled vocabulary. In version 4 of the IIM specification
document the Datasets Category and Supplemental Category were indicated as “deprecated” which meant thatafter the time of this release these two Datasets should not be populated with values any longer.
To support the move from the three letter codes used with the Category Dataset to the Subject NewsCodes thistable provides a reference for mapping.
Category Subject
Name and definition of the code
Code
NewsCode
ACE
01000000
arts, culture and entertainment
Matters pertaining to the advancement and refinement of the human mind, ofinterests, skills, tastes and emotions
CLJ
02000000
crime, law and justice
Establishment and/or statement of the rules of behaviour in society, the enforcementof these rules, breaches of the rules and the punishment of offenders. Organizations
and bodies involved in these activities.
DIS
03000000
disaster and accident
Man made and natural events resulting in loss of life or injury to living creatures
and/or damage to inanimate objects or property.
FIN
04000000
economy, business and financeAll matters concerning the planning, production and exchange of wealth.
EDU
05000000
education
All aspects of furthering knowledge of human individuals from birth to death.
EVN
06000000
environmental issue
All aspects of protection, damage, and condition of the ecosystem of the planet earth
and its surroundings.
HTH
07000000
healthAll aspects pertaining to the physical and mental welfare of human beings.
HUM
08000000
human interest
Lighter items about individuals, groups, animals or objects.
LAB
09000000
labourSocial aspects, organizations, rules and conditions affecting the employment of
human effort for the generation of wealth or provision of services and the economic
support of the unemployed.
LIF
10000000
lifestyle and leisure
Activities undertaken for pleasure, relaxation or recreation outside paid employment,
including eating and travel.
POL
11000000politics
Local, regional, national and international exercise of power, or struggle for power,
and the relationships between governing bodies and states.
REL
12000000
religion and belief
All aspects of human existence involving theology, philosophy, ethics and spirituality.
SCI
13000000
science and technology
All aspects pertaining to human understanding of nature and the physical world andthe development and application of this knowledge
SOI
14000000
social issue
Aspects of the behaviour of humans affecting the quality of life.
SPO
15000000
sport
Competitive exercise involving physical effort. Organizations and bodies involved inthese activities.
WAR
16000000unrest, conflicts and war
Acts of socially or politically motivated protest and/or violence.
WEA
17000000
weather
The study, reporting and prediction of meteorological phenomena.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 29 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

IPTC Extension schema 1.1 specifications
Names and Identifiers
The XML namespace URI for the “IPTC Extension” versions 1.0 and 1.1 is:
http://iptc.org/std/Iptc4xmpExt/2008-02-29/
The preferred XML namespace-prefix for “IPTC Extension”-related XMP properties is: Iptc4xmpExt
The use of this namespace-prefix is not mandatory but highly recommended for interoperability support.
User interfaces (like the custom panels in Adobe CS products) showing “IPTC Extension” properties must refer
to it as an “IPTC Extension” or “IPTC …” panel.
This other namespace is used in the scope of IPTC Extension:
Name
URI
PLUS
http://ns.useplus.org/ldf/xmp/1.0/

Recommended Prefix
plus

Metadata Properties
Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descrAdditional Model Information
Information about the ethnicity and other facets of the model(s) in a model-released
image.
Information about the ethnicity and other facets of the model(s) in a model-released
image.
Enter information like ethnicity or other details about the model(s) in this image
Use the Model Age field for the age of model(s).
Additional model info
0..1

Iptc4xmpExt
Text

Basic data type

XMP property id
XMP Category

free-text

AddlModelInfo
External/newsItem/contentMeta/description@role="drol:modelInfo"

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type2descrArtwork or Object in the Image
A set of metadata about artwork or an object in the item
A set of metadata about artwork or an object in the image
Enter details about artwork or objects shown in this image

Artwork or object in the image
0..unbounded

Basic data typeIptc4xmpExt
bag ArtworkOrObjectDetails

XMP property id
XMP Category

structure

ArtworkOrObject
External

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 30 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Mapping rules are pending.

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descrCode of Organisation Featured in the Image
Code from a controlled vocabulary for identifying the organisation or company which isfeatured in the content.
Code from a controlled vocabulary for identifying the organisation or company which isfeatured in the image.
Enter an identifier for the controlled vocabulary, then a colon, and finally the code from thevocabulary assigned to the organisation shown in this image (e.g. nasdaq:companyA)
For example a stock ticker symbol may be used.
Code of featured Organisation
0..unbounded
Open to any CV

Iptc4xmpExt
bag Text

Basic data type

XMP property id
XMP Category

CV-codeOrganisationInImageCode
External/newsItem/contentMeta/subject/@qcode@type="cpnat:organisation"

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descrControlled Vocabulary Term
A term to describe the content of the image by a value from a Controlled Vocabulary.
A term to describe the content of the image by a value from a Controlled Vocabulary.
Enter an identifier for the controlled vocabulary, then a colon, and finally the code from thevocabulary assigned to the termThis property is part of the Photo Metadata 2008 specifications, but should not released tothe public on the standard Adobe Custom Panels for IPTC metadata or other userinterfaces unless agreed by the IPTC.
Controlled Vocabulary Term
0..unbounded
Basic data type CV-code
Any Controlled Vocabulary registered with the IPTC for this field.

Iptc4xmpExt
bag URI

XMP property id
XMP Category

CVtermExternal/newsItem/contentMeta/subject/@qcode

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 31 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descrLocation Shown in the Image
A location the content of the item is about. For photos that is a location shown in theimage.
A location shown in the image.
Enter the details about a location which is shown in this image
If the location the image was taken in is different from this location the property Location
Created should be used too.
Location shown
0..unbounded

Iptc4xmpExt
bag LocationDetails

Basic data type

XMP property id
XMP Category

structure

LocationShown
External/newsItem/contentMeta/subject/....
@type="cpnat:geoArea"

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descrModel AgeAge of the human model(s) at the time this image was taken in a model released image.
Age of the human model(s) at the time this image was taken in a model released image.
Enter the age of the human model(s) at the time this image was madeThe user should be aware of any legal implications of providing ages for young models.
Ages below 18 years should not be included.
Model age
0..unbounded

Basic data typenumeric

Iptc4xmpExt
bag Integer

XMP property id
XMP Category

ModelAge
External/newsItem/contentMeta/description@role="drol:modelAge"

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history

2descrName of Organisation Featured in the Image
Name of the organisation or company which is featured in the content.
Name of the organisation or company which is featured in the image.
Enter the name of the organisation which is featured by this image
May be supplemented by values from a controlled vocabulary in the Organisation Codefield.
Name of featured Organisation
0..unbounded

Basic data typefree-text

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 32 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Iptc4xmpExt
bag Text

XMP property id
XMP Category

Production - Public Release
OrganisationInImageName
External/newsItem/contentMeta/subject/name@type="cpnat:organisation"

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)2descr

Person Shown in the Image
Name of a person the content of the item is about. For photos that is a person shown in
the image.
Name of a person shown in the image.
Enter the name of the person shown in this image

Person shown
0..unbounded

Basic data typeIptc4xmpExt
bag Text

XMP property id
XMP Category

Name
Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)PersonInImage
External/newsItem/contentMeta/subject/name@type="cpnat:person"

Generic Specification
Definition

free-text

3adminDigital Image GUID
Globally unique identifier for the item. It is created and applied by the creator of the item atthe time of its creation . This value shall not be changed after that time.
Globally unique identifier for this digital image. It is created and applied by the creator ofthe digital image at the time of its creation . This value shall not be changed after thattime.
If an ID already exists, don't change - otherwise enter a globally unique identifier for this
digital image
The identifier will probably be generated by the technical means of an imaging device orsoftware and should be applied to the digital image file as early as possible in its life cycle.
This identifier does not identify any pictured content, particularly in case of a scan of nondigital images, only this digital representation.
Any algorithm to create this identifier has to comply with the technical requirements tocreate a globally unique id. Any device creating digital images - e.g. still image cameras,
video cameras, scanners - should create such an identifer right at the time of the creationof the digital data and add the id to the set of metadata without compromising
performance. It is recommended that this image identifier allows identifying the device bywhich the image data and the GUID were created.
IPTC's basic requirements for unique ids are:* It must be globally unique. Algorithms for this purpose exist.
* It should identify the camera body.
* It should identify each individual photo from this camera body.
* It should identify the date and time of the creation of the picture.
* It should be secured against tampering.
This field should be implemented in a way to prove it has not been changed since its
value has been applied.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 33 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Production - Public Release

If the identifier has been created by the imaging device its type and brand can be found in
the Exif/technical metadata.
Digital Image Identifier
0..1
Basic data type string
Specs (July 2010): XMP Category changed to Internal
Iptc4xmpExt
text

XMP property id
XMP Category

DigImageGUID
Internal/newsItem/contentMeta/altId@type="altidtype:imageGUID"

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV

Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)3adminDigital Source File Type (DEPRECATED)The type of the source digital file.
The type of the source digital file.
The IPTC recommends not to implement this property any longer.
Physical type of original photo
0..1
Basic data type CV-code
Values are: Scan from film {scanfilm}, scan from transparency (including slide){scantransparancy}, scan from print {scanprint}, camera raw {cameraraw}, camera tiff
{cameratiff}, camera jpeg {camerajpeg}
Deprecated in v 1.1
Iptc4xmpExt
URI

XMP property id
XMP Category

DigitalSourcefileType
External/newsItem/contentMeta/Iptc4xmpExt:digSourceFileTyp/@qcode

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)3adminDigital Source TypeThe type of the source of this digital image
The type of the source of this digital image
Select one of the values for identifying the type of the source of the digital image from thecontrolled vocabulary

Type of source for this photo
0..1
Basic data type CV-code
Digital Source Type NewsCodes - http://cv.iptc.org/newscodes/digitalsourcetype/
Added in v 1.1
Iptc4xmpExt
URI

XMP property id
XMP Category

DigitalSourceType
External

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 34 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Production - Public Release/newsItem/contentMeta/Iptc4xmpExt:digSourceType/@qcode

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)3adminEventNames or describes the specific event the content relates to.
Names or describes the specific event at which the photo was taken.
Enter the name or description of the event where this image was taken
Examples are: a press conference, dedication ceremony, etc. If this is a sub-event of alarger event both can be provided by the field: e.g. XXXIX Olympic Summer Games(Beijing): opening ceremony. Unplanned events could be named by this property too.
Event
0..1

Iptc4xmpExt
Lang Alt

Basic data typefree-text

XMP property id
XMP Category

Event
External/newsItem/contentMeta/subject/@type="cpnat:event"

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)3adminImage Registry Entry
Both a Registry Item Id and a Registry Organisation Id to record any registration of thisitem with a registry.
Both a Registry Item Id and a Registry Organisation Id to record any registration of this
digital image with a registry.
Enter IDs for this image and the registry issuing the image ID
Typically an id from a registry is negotiated and applied after the creation of the digital
image.
Any user interface implementation must show both sub-properties - Item Id andOrganisation Id - as corresponding values. Further an input to both fields should be mademandatory.
Registry Entry
0..unbounded
Basic data type structure

Iptc4xmpExt
bag RegistryEntryDetails

XMP property id
XMP Category

RegistryId
External/newsItem/contentMeta/altId

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 35 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)3adminImage Supplier
Identifies the most recent supplier of the item, who is not necessarily its owner or creator.
Identifies the most recent supplier of the image, who is not necessarily its owner orcreator.
Enter the identifier for the most recent supplier of this image - note that this might not be
the creator or owner of the image
For identifying the supplier either a well known and/or registered company name or a URLof the company's web site may be used.
This property succeeds the Provider property of IPTC Core 1.0 by its semantics as that
Provider was renamed to Credit Line.
This is a PLUS version 1.2 property included in the IPTC Extension schema.
Image Supplier
0..1
Basic data type structureplus
Seq ImageSupplierDetail

XMP property id
XMP Category

ImageSupplier
External/newsItem/rightsInfo/ExtPoint

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)3adminImage Supplier Image ID
Optional identifier assigned by the Image Supplier to the image.
Optional identifier assigned by the Image Supplier to the image.
Enter the unique identifier created by the image supplier.
This is a PLUS version 1.2 property included in the IPTC Extension schema.
Image Supplier Image Id
0..1
Basic data type string
Specs (July 2010): property added
plus
Text

XMP property id
XMP Category

ImageSupplierImageID
External

G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)3adminIPTC Metadata Last Edited (Legacy)
The date and optionally time when any of the IPTC photo metadata fields has been lasteditedThe date and optionally time when any of the IPTC photo metadata fields has been lastedited.
The public use of this property is deprecated by IPTC Extension version 1.1. It may only
still be used by a private user interface for a use scoped to a company.
If used this field should be a timestamp of the latest change applied to any of the fields.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 36 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Production - Public Release

One may infer no metadata value has been applied after this date.
The value of this property should never be set by software. XMP-aware software shouldreflect any changes to metadata by the xmp:MetadataDate property of the XMP Basic
scheme.
IPTC Fields Last Edited
0..1
Basic data type DateTime
Legacy status assigned in v 1.1
XMP property id IptcLastEdited
Iptc4xmpExt
Date
XMP Category External/Internal
The value of this property can either be entered by the user or be set by a metadata
editing software

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)3adminLocation created
The location the content of the item was created.
The location the photo was taken.
Enter the details about a location where this image was created
If the location in the image is different from the location the photo was taken the IPTC
Extension property Location Shown in the Image should be used.
Location Created
0..1

Basic data typeIptc4xmpExt
Bag LocationDetails

XMP property id
XMP Category

structure

LocationCreatedExternal/newsItem/contenteMeta/located/POIdetails/contactInfo/address/....(locality,area,country)

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type

3adminMax Avail Height
The maximum available height in pixels of the original photo from which this photo has
been derived by downsizing.
The maximum available height in pixels of the original photo from which this photo has
been derived by downsizing.
Enter the maximum available height in pixels of the original photo from which this photo
has been derived by downsizing

Maximum available height
0..1

Iptc4xmpExt
Integer

Basic data type

XMP property id
XMP Category

integer

MaxAvailHeight
External

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 37 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)/newsItem/contentSet[rendition='rnd:highRes']/height

Only mapping out of G2!

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)3adminMax Avail Width
The maximum available width in pixels of the original photo from which this photo has
been derived by downsizing.
The maximum available width in pixels of the original photo from which this photo has
been derived by downsizing.
Enter the maximum available width in pixels of the original photo from which this photo
has been derived by downsizing

Maximum available width
0..1

Iptc4xmpExt
Integer

Basic data type

XMP property id
XMP Category

integer

MaxAvailWidth
External/newsItem/contentSet[rendition='rnd:highRes']/width

Only mapping out of G2!

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)3admin

PLUS Version
The version number of the PLUS standards in place at the time of the transaction.
The version number of the PLUS standards in place at the time of the transaction.
In the event of a misunderstanding between the parties, PLUS Version provides areference to the version of the PLUS standards that was in place at the time of thetransaction. PLUS standards are updated periodically.
This property was included into the IPTC Extension schema from PLUS version 1.2 as allother PLUS properties. To reflect this the value of "PLUS Version" should be set to thestring "1.2.0"
PLUS Version
0..1
Basic data type

plus
Text

XMP property id
XMP Category

VersionInternal

G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 38 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

Copyright Owner
Owner or owners of the copyright in the licensed image.
Owner or owners of the copyright in the licensed image.
Enter the owner or owners of the copyright in the licensed image
Serves to identify the rights holder/s for the image. The Copyright Owner, Image Creatorand Licensor may be the same or different entities.
This is a PLUS version 1.2 property included in the IPTC Extension schema.
Copyright owner
0..3
Basic data type structureplus
Seq CopyrightOwnerDetail

XMP property id
XMP Category

CopyrightOwner
External/newsItem/rightsInfo/CopyrightHolder/@qcode + /name

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

Image Creator
Creator or creators of the image.
Creator or creators of the image
Enter details about the creator or creators of this image
The creator can be additionally expressed in free-text using the IPTC Core Creator field.
In many countries, the Image Creator must be attributed in association with any use of theimage. The Image Creator, Copyright Owner, Image Supplier and Licensor may be thesame or different entities.
This is a PLUS version 1.2 property included in the IPTC Extension schema.
Image Creator
0..3
Basic data type structureplus
Seq ImageCreatorDetail

XMP property id
XMP Category

ImageCreator
External/newsItem/contentMeta/creator/@qcode + /name

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality

4rightrel

Licensor
A person or company that should be contacted to obtain a licence for using the item or
who has licensed the item.
A person or company that should be contacted to obtain a licence for using the item or
who has licensed the item.
Enter the person or company that should be contacted for obtaining a license for thisimageThis is a PLUS version 1.2 property included in the IPTC Extension schema.
Licensor
0..3
Basic data type struct

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 39 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)plusbag LicensorDetail

XMP property id
XMP Category

Licensor
External/newsItem/rightsInfo/ExtPoint

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

Minor Model Age Disclosure
Age of the youngest model pictured in the image, at the time that the image was made.
Age of the youngest model pictured in the image, at the time that the image was made.
Enter the age of the youngest model pictured in this image, at the time that this image
was made.
This age should not be displayed to the public on open web portals and the like. But it
may be used by image repositories in a B2B enviroment.
This is a PLUS version 1.2 property included in the IPTC Extension schema.
Minor Model Age Disclosure
0..1
Basic data type CV-code
CV defined by PLUS
Specs (July 2010): XMP Value type corrected
plus
URL

XMP property id
XMP Category

MinorModelAgeDisclosure
External/newsItem/rightsInfo/ExtPoint

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

Model Release Id
Optional identifier associated with each Model Release.
Optional identifier associated with each Model Release.
Enter an identifier for each Model Release
This is a PLUS version 1.2 property included in the IPTC Extension schema.
Model Release Id
0..unbounded
Basic data type IdentifierSpecs (July 2010): definition aligned with PLUS specs
plus
Bag Text

XMP property id
XMP Category

ModelReleaseID
External/newsItem/rightsInfo/ExtPoint

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 40 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

Model Release Status
Summarizes the availability and scope of model releases authorizing usage of thelikenesses of persons appearing in the photograph.
Summarises the availability and scope of model releases authorising usage of thelikenesses of persons appearing in the photograph.
Select one of the values for summarising the availability and scope of model releases
authorising usage of the likenesses of persons appearing in the photograph
It is recommended to apply the PLUS controlled value Unlimited Model Releases (MRUMR) very carefully and to check the wording of the model release thoroughly before
applying it.
This is a PLUS version 1.2 property included in the IPTC Extension schema.
Model Release Status
0..1
Basic data type CV-code
CV defined by PLUS
Specs (July 2010): XMP Value type corrected
plus
URL

XMP property id
XMP Category

ModelReleaseStatus
External/newsItem/rightsInfo/ExtPoint

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)4rightrel

Property Release Id
Optional identifier associated with each Property Release.
Optional identifier associated with each Property Release.
Enter an identifier for each Property Release
This is a PLUS version 1.2 property included in the IPTC Extension schema.
Property Release Id
0..unbounded
Basic data type IdentifierSpecs (July 2010): definition aligned with PLUS specs
plus
Bag Text

Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)PropertyReleaseID
External/newsItem/rightsInfo/ExtPoint

Generic SpecificationName

XMP property id
XMP Category

4rightrel

Property Release Status
Summarises the availability and scope of property releases authorizing usage of theproperties appearing in the photograph.
Summarises the availability and scope of property releases authorising usage of theproperties appearing in the photograph.
Select one of the values for summarising the availability and scope of property releases
authorising usage of the properties appearing in the photograph
It is recommended to apply the value PR-UPR very carefully and to check the wording of
the property release thoroughly before applying it.
This is a PLUS version 1.2 property included in the IPTC Extension schema.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 41 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Property Release Status
0..1
Basic data typeCV defined by PLUS
Specs (July 2010): XMP Value type corrected
plus
URL

XMP property id
XMP Category

Production - Public Release
CV-codePropertyReleaseStatus
External/newsItem/rightsInfo/ExtPoint

Metadata Structure: Artwork or Object in the Image Details
Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)9type-artobj

Artwork or Object in the Image Details structure {data type}
A structured datatype for details about artwork or an object in an image. Includes a
Copyright Notice, a Creator, a Date Created, a Source, a Source Inventory Number and a
Title.
A structured datatype for details about artwork or an object in an image. Includes a
Copyright Notice, a Creator, a Date Created, a Source, a Source Inventory Number and a
Title.
-

N/A
Basic data typeIptc4xmpExt
structure

XMP property id
XMP Category

structure

ArtworkOrObjectDetails
External

Mapping rules are pending.

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history

9type-artobj

Copyright Notice {Artwork or Object detail}Contains any necessary copyright notice for claiming the intellectual property for artworkor an object in the image and should identify the current owner of the copyright of thiswork with associated intellectual property rights.
Contains any necessary copyright notice for claiming the intellectual property for artworkor an object in the image and should identify the current owner of the copyright of thiswork with associated intellectual property rights.
Enter any necessary copyright notice for claiming the intellectual property for artwork or
an object in this image(Artwork or Object detail:) Copyright notice
0..1
Basic data typefree-text

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 42 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Iptc4xmpExt
Text

XMP property id
XMP Category

Production - Public Release
AOCopyrightNotice
External

Mapping rules are pending.

Generic Specification

Name
Definition
Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)9type-artobj

Creator {Artwork or Object detail}Contains the name of the artist who has created artwork or an object in the image.
Contains the name of the artist who has created artwork or an object in the image. In
cases where the artist could or should not be identified the name of a company ororganisation may be appropriate.
Enter the name of the artist who has created artwork or an object in this image(Artwork or Object detail:) Creator
0..unbounded
Basic data typeIptc4xmpExt
Seq ProperName

XMP property id
XMP CategorystringAOCreator
External

Mapping rules are pending.

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality

9type-artobj

Date Created {Artwork or Object detail}Designates the date and optionally the time the artwork or object in the image wascreated. This relates to artwork or objects with associated intellectual property rights.
Designates the date and optionally the time the artwork or object in the image wascreated. This relates to artwork or objects with associated intellectual property rights.
Enter the date and optionally the time when the artwork or object in this image wascreated(Artwork or Object detail:) Date created
0..1
Basic data type

DateTime (preferred: truncated
DateTime)

Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)Iptc4xmpExt
Date

XMP property id
XMP Category

AODateCreatedExternal

G2 implementation
Property name (XPath)
Property-attribute(s)IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 43 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
QCode scheme
Implementation note(s)Production - Public Release

Mapping rules are pending.

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)9type-artobj

Source {Artwork or Object detail}The organisation or body holding and registering the artwork or object in the image forinventory purposes.
The organisation or body holding and registering the artwork or object in the image forinventory purposes.
Enter the name of the organisation or body holding and registering the artwork or object inthis image for inventory purposes(Artwork or Object detail:) Source
0..1
Basic data typeIptc4xmpExt
Text

XMP property id
XMP Category

free-text

AOSource
External

Mapping rules are pending.

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)9type-artobj

Source Inventory Number {Artwork or Object detail}The inventory number issued by the organisation or body holding and registering theartwork or object in the image.
The inventory number issued by the organisation or body holding and registering theartwork or object in the image.
Enter the inventory number issued by the organisation or body holding and registering theartwork or object in this image(Artwork or Object detail:) Source inventory number
0..1
Basic data type string

Iptc4xmpExt
Text

XMP property id
XMP Category

Mapping rules are pending.

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)AOSourceInvNo
External

9type-artobj

Title {Artwork or Object detail}A reference for the artwork or object in the image.
A reference for the artwork or object in the image.
Enter the verbal and human readable name of the artwork or object in this image

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 44 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)(Artwork or Object detail:) Title
0..1

Iptc4xmpExt
Lang Alt

Production - Public Release

Basic data typefree-text

XMP property id
XMP Category

AOTitleExternal

Mapping rules are pending.

Metadata Structure: Location Details
Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)9type-location

Location Details structure {data type}
A structured datatype for details of a location. It includes a Sublocation, a City, a Provinceor State, a Country (Name and ISO-Code) and a World Region.
A structured datatype for details of a location. It includes a Sublocation, a City, a Provinceor State, a Country (Name and ISO-Code) and a World Region.
-

N/A
Basic data typeIptc4xmpExt
Text

XMP property id
XMP Category

structure

LocationDetails
External

G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property

9type-location

City {location detail}Name of the city of a location. This element is at the fourth level of a top-down
geographical hierarchy.
Name of the city of a location. This element is at the fourth level of a top-down
geographical hierarchy.
Enter the name of the City

(Location detail:) City
0..1

Iptc4xmpExt
Text

Basic data typestring

XMP property id
XMP Category

City
External

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 45 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)/newsItem/contentMeta/subject/@type="cpnat:geoArea"+@facet="fct:city"
Mapping for Location Shown in the Image only

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)9type-location

Country ISO-Code {location detail}The ISO code of a country of a location. This element is at the second level of a top-down
geographical hierarchy.
The ISO code of a country of a location. This element is at the second level of a top-down
geographical hierarchy.
Enter the 2 or 3 letter ISO 3166 Country Code of the Country(Location detail:) Country ISO-Code
0..1
Basic data typeISO 3166-1 - 2 or 3 characters (see Definition)
Specs (201007): XMP ValueType corrected

CV-codeXMP property id CountryCode
Iptc4xmpExt
closed choice
XMP Category External
Note 1: an implementer would have to derive from the length of the value string whether
this is the country code from the two or three letter scheme as no explicit indication can beprovided.

Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)/newsItem/contentMeta/subject/@qcode@type="cpnat:geoArea"+@facet="fct:country"
Mapping for Location Shown in the Image only

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)9type-location

Country Name {location detail}The name of a country of a location. This element is at the second level of a top-down
geographical hierarchy.
The name of a country of a location. This element is at the second level of a top-down
geographical hierarchy.
Enter the name of the Country(Location detail:) Country Name
0..1

Iptc4xmpExt
Text

Basic data type

XMP property id
XMP CategorystringCountryName
External/newsItem/contentMeta/subject/name@type="cpnat:geoArea"+@facet="fct:country"
Mapping for Location Shown in the Image only

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 46 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)9type-location

Province or State {location detail}The name of a subregion of a country - a province or state - of a location. This element is
at the third level of a top-down geographical hierarchy.
The name of a subregion of a country - a province or state - of a location. This element is
at the third level of a top-down geographical hierarchy.
Enter the name of the Province or State(Location detail:) Province/State
0..1

Iptc4xmpExt
Text

Basic data type

XMP property id
XMP CategorystringProvinceState
External/newsItem/contentMeta/subject/@type="cpnat:geoArea"+@facet="fct:provState"
Mapping for Location Shown in the Image only

Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)9type-location

Sublocation {location detail}Name of a sublocation. This sublocation name could either be the name of a sublocation
to a city or the name of a well known location or (natural) monument outside a city. In thesense of a sublocation to a city this element is at the fifth level of a top-down geographicalhierarchy.
Name of a sublocation. This sublocation name could either be the name of a sublocation
to a city or the name of a well known location or (natural) monument outside a city. In thesense of a sublocation to a city this element is at the fifth level of a top-down geographicalhierarchy.
Enter the name of the Sublocation(Location detail:) Sublocation
0..1

Iptc4xmpExt
Text

Basic data type

XMP property id
XMP Category

Definition
Photo Definition
Photo Help Text

Sublocation
External/newsItem/contentMeta/subject/@type="cpnat:geoArea"+@facet="fct:subLoc"
Mapping for Location Shown in the Image only

Generic SpecificationNamestring9type-location

World Region {location detail}The name of a world region of a location. This element is at the first (topI) level of a topdown geographical hierarchy.
The name of a world region of a location. This element is at the first (topI) level of a topdown geographical hierarchy.
Enter the name of the World Region

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 47 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)(Location detail:) World Region
0..1

Iptc4xmpExt
Text

Basic data type

XMP property id
XMP Category

Production - Public ReleasestringWorldRegion
External/newsItem/contentMeta/subject/@type="cpnat:geoArea"+@facet="fct:worldReg"

Metadata Structure: Registry Entry Details
Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)9type-registryid

Registry Entry Details structure {data type}
A structured datatype for an entry in a registry, includes the id issued by the registry andthe registry's id.
A structured datatype for an entry in a registry, includes the id for the image issued by theregistry and the registry's id.
-

N/A
Basic data typeIptc4xmpExt
structure

XMP property id
XMP Category

structure

RegistryEntryDetails
External

G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Generic Specification

Name
Definition

Photo Definition

Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV

9type-registryid

Item Id {registry entry detail}A unique identifier created by a registry and applied by the creator of the item. This value
shall not be changed after being applied. This identifier is linked to a corresponding
Registry Organisation Identifier.
A unique identifier created by a registry and applied by the creator of the digital image.
This value shall not be changed after being applied. This identifier is linked to acorresponding Registry Organisation Identifier.
Enter the unique identifier created by a registry and applied by the creator of the digital
image. This value shall not be changed after being applied.
This identifier may be globally unique by itself, but it must be unique for the issuingregistry.
(Registry Entry detail:) Item Identifier
1
Basic data typestring

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 48 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)Iptc4xmpExt
Text

XMP property id
XMP Category

RegItemId
External/newsItem/contentMeta/altId

Generic Specification

Name
Definition
Photo Definition
Photo Help Text
User Note(s)Implementation Note(s)Field label/title
Cardinality
Required CV
Spec change history
XMP implementation
XMP namespace
XMP Value Type
Implementation note(s)Maps to this IIM property
XMP/IIM mapping note(s)G2 implementation
Property name (XPath)
Property-attribute(s)QCode scheme
Implementation note(s)9type-registryid

Organisation Id {registry entry detail}An identifier for the registry which issued the corresponding Registry Image Id.
An identifier for the registry which issued the corresponding Registry Image Id.
Enter the identifier for the registry which issued the corresponding Registry Image ID(Registry Entry detail:) Organisation Identifier
1
Basic data typeIptc4xmpExt
Text

XMP property id
XMP Categorystring

RegOrgId
External/newsItem/contentMeta/altId/@type="RegOrgId"

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 49 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

References
Name
Adobe XMPDC
IPTC G2-Standards
IPTC IIM
PhMdWP2007
PLUS
MetadataWG

SourceAdobe Extensible Metadata Platform (XMP)
http://www.adobe.com/products/xmp/
Latest specification as of April 2010
This document includes the specification of the metadata schemas Dublin Core, XMP
Rights management and Photoshop which are referenced in this specification.
Dublin Core metadata schema:
http://www.dublincore.org/
IPTC G2-Standards: EventsML-G2 and NewsML-G2 (as of 2010)
http://www.iptc.org/G2-Standards/
IPTC Information Interchange Model: http://www.iptc.org/IIM/ andhttp://www.iptc.org/std/IIM/4.1/specification/IIMV4.1.pdf
IPTC Photo Metadata White Paper 2007
http://www.iptc.org/goto?phmdwp2007
Picture Licensing Universal System – PLUS: http://www.useplus.org
PLUS specifications: http://www.useplus.com/useplus/standards.asp
Guidelines for Handling Image Metadata v 1.1
http://www.metadataworkinggroup.com/specs/

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 50 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Addendum 1:
Persistent Technical Photo Metadata – a recommendation
Objectives for Technical Photo Metadata
Technical photo metadata within the scope of this paper are:
- Digital camera manufacturers’ metadata, including all Exif and MakerNote metadata that record the camera
settings and image capture conditions- ICC metadata in the form of ICC profiles, if embedded, that define the colours of the image in a standard way- Other third-party application metadata, for example, Photoshop and Fotoware metadata, and face detection
metadata- File format metadata like that in Exif DCF2, camera RAW, JPEG 2000 or JPEG XR.
All these forms of technical metadata should be persistent, along with metadata contained in the IPTC Core, IPTC
Extension or IIM metadata.
Why do we need persistent technical metadata?
Technical metadata must be viewed as being just as important as descriptive (content oriented) metadata
standards defined by the IPTC. Both types of metadata are essential to the business of picture agencies, news
reporting, and cultural heritage works.
The prime reason to preserve and maintain technical metadata is to take advantage of technical developments indigital photography. Workflows need to be faster and more efficient, saving time and money whenever andwherever possible, image quality needs to be higher, and search and retrieval for images needs to be morediscerning and more fruitful.
The digital present and the digital future require a general all-round improvement in the use of resources anddigital assets.
A more complete discussion regarding the benefits of keeping technical metadata is given in an extended version
iof “Persisting Technical Photo Metadata” available on the Ifra web site . After reading this document, it should
become clear that there is much to be gained by keeping all metadata and the highest advantages can beobtained at low cost through automatic software procedures.

Photo Workflows
Whenever photos are captured by digital cameras, metadata is written into the image file. Subsequently, additional
metadata is written by the photographer, picture desk editor, picture librarians and also automatically by
application and system software.
Software applications need to be aware of metadata that has been added to the image by, firstly, the digital
camera and, secondly, by other people or another application, so that a complete record of metadata is preserved
and persisted with each image as it passes through every stage of the workflow.
How to persist metadata in different workflows
Workflow diagrams are shown here for the persistence of technical metadata for:a) the general caseb) a news picture agencyc) a newspaper
The workflow diagrams have red asterisks to show where metadata can be invalidated or lost, if the software
application does not fully support technical metadata by updating certain fields after processing and correctly
writing the metadata into the image file on saving.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 51 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Generalised Photo Value Chain

AdvertisingNews

Photographer

Stock photoagencyArchive

Archive

Photographer

News orstock photoagencyImage files withmultiple metadata

Media- oradvertising
agencyPublisher

Archive

Syndication

Publisher

Image handlingsoftware persists alltechnical metadata

At every stage in the value chain, starting with downloading images from the camera to a storage device, and at
every further stage of picture annotation and editing, only software that persists and maintains all photo metadatashould be used.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 52 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

News Agency Workflow(example from dpa, Deutsche Presse-Agentur)
Syndication

Partneragencies

Local
scanners

FTP

Automatic date:time metadata added

Photographers

Web

Picture desk

Archive

Editorial
captioning& archiving
IT system

Archive
Satellite
Manually add
captions& IPTC fields

Metadata
added bylibrarianE-mailImage editinge.g. Photoshop

Image files withmultiple metadata

Image handlingsoftware persists alltechnical metadata

U.S. Newspaper's Workflow( a typical example )Specials fromothernewspapers

Negative print/scannerStaffphotosAutomatic date:time metadata added

Wireservices

Clerks correct& append
metadata

Photo editor
selects image &writes caption

Confirm
payment tophotographer
or agency

Photo
database

Newspaper
Assistant editor
crops & adjusts
colourPhoto added
to layout &paginated

Publishing
Web site or
e-media
editorFreelance
photosArchive
Metadata
added bylibrarian

Image files withmultiple metadata

Archive

Copy sent to
Associated
Press

Image handlingsoftware persists alltechnical metadata

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 53 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

Recommendations
1. “Persisting technical metadata” means that all metadata properties and their values relating to:- Basic file management (e.g. file type, image dimensions in pixels, orientation, image data compression
parameters) MUST BE PERSISTED AND MAINTAINED to record the current state of the image- Administration (e.g. date and time of capture, creator, copyright holder, GPS, unique image ID) MUST
BE PERSISTED AND MAINTAINED- Camera settings (e.g. auto- or manual exposure, auto- or manual focus, colour space and colour profile,
ISO setting, scene type, camera ID, lens ID) MUST BE PERSISTED AND NOT CHANGED- Image capture conditions (e.g. exposure time, lens aperture, distance to subject) MUST BE PERSISTEDAND NOT CHANGED, and- Descriptions (e.g. comments, title) are to be added and ARE OPTIONALLY PERSISTED AND EDITED.
2. All metadata (descriptive and technical), should be persisted in accordance with the first recommendation,
above, as long as each image file remains digitally accessible. All JPEG-based Exif, TIFF/EP and camera
RAW files contain technical camera metadata. PDF files also contain technical metadata, as do the newgeneration of file formats, JPEG 2000 and JPEG XR.
3. All technical metadata should be persisted, even if they are not required for use by the current application
in a workflow step. Any application should not be limited by inadequate metadata processing of software
in a previous workflow step. It should not remove any property.
4. Versioning metadata, to historically record all modifications to the image, is optional. Similarly, anapplication must be able to update standard metadata, where appropriate.
5. If the picture data is edited, for example through orientation, colour characterisation, sizing or cropping,then the pertinent metadata (e.g. pixel height and width) and the thumbnail image need to be updated in
the file to be commensurate with the main picture data.
6. Image suppliers should persist all of the technical metadata, both standard and proprietary, in its existingand standardised form within the respective image files (Exif, TIFF, JPEG 2000, RAW, PDF, DNG etc.).
Not just one schema for metadata has to be supported today, but several - IPTC IIM and IPTC Core, IPTC
Extension, TIFF, Dublin Core, Exif, ICC and others.
7. In order for the technical metadata to be usable by the widest range of existing applications, technicalmetadata is required in its original schema. The Exif format, for example, is by far the most common digital
camera format and schema for digital pictures. All automatic image processing applications cater first andforemost to this format and schema, while extending their capabilities to other less common formats aswell. Technical metadata originating from the camera-, ICC profiles-, GPS information- and face detection
metadata, should remain in the schema in which it was originally created by the camera or application. This
would ensure maximum compatibility with clients' and customers' systems and workflows today.
If technical metadata is repeated in another schema within the same file, the metadata should still bepersisted to its fullest extent in its original schema. Additionally, any updating of a metadata property that
becomes necessary in one schema, for example because of, image processing or administration, should
be automatically replicated by the software in each of the other metadata schemas where the same
property appears in that file. Without this assistance, photo sources have problems in keeping multiple
sets of the same metadata current and synchronised within the file.
8. in the future, the use of a single schema for all metadata should be recommended, but not until such aschema is approved by all bodies that issue imaging file standards (e.g. ISO, IEC, ITU, JEITA, JPEG, ICC).
9. Archived images should be a copy of the original picture data and full metadata so that, as technicalmetadata develops, it shall become possible to take advantage of new algorithms to further improve image
quality, the use of image resources, and the implementation of asset management.

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 54 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved

IPTC Photo Metadata: Core 1.1/Extension 1.1 (July 2010) - Doc Rev 1

Production - Public Release

10. Technical metadata and the associated image pixel data should always be kept together or be linked
together in an unambiguous manner.
11. While the persistence of all metadata is the prime goal, metadata that contravenes personal information
data protection, or personal-, state- or national security may be removed because of legal requirements.
Software that captures all metadata must contain functions that allow the deletion of sensitive metadata, if
it contravenes just one of these principles. For example, under some circumstances, a personal ID and
GPS information could both be considered safety hazards to a photojournalist in the field and must be
removed before distribution.
12. When organisations create or support formats for photos or picture standards, they should ensure that therespective schema or format can be read or be written by freely available software, preferably under anOpen Source Licence.
This would enable the reading and writing of image data and metadata so that the aboveii
recommendations are met, while obtaining such software should not then become expensive . Only whensuch software is freely available and easily integrated into picture-handling programs, can the agencies
and organisations which are currently unable to take advantage of the technical developments in digital
photography expect to participate effectively in an international trading of pictures.
i

http://www.ifra.com/Persisting_Technical_Photo_Metadata.pdf
An example of such software is Phil Harvey’s ExifTool to be found at:
http://www.sno.phy.queensu.ca/~phil/exiftool/ii

IPTC-PhotoMetadata-201007_1.docx
www.iptc.org
Page 55 of 55
Copyright © 2010 International Press Telecommunications Council. All Rights Reserved