Remonter

Définitions des principaux champs de la norme IPTC IIM version 4.1 - 1999

La norme de base que j'utilise est la IPTC IIM soit Information Interchange Model version 4.1 ou en surnom la IPTC Fields. Elle a été publiée en 1999 et est disponible sur le site de l'IPTC à http://www.iptc.org/std/IIM/4.1/specification/IIMV4.1.pdf.

En 2008 la IPTC publie le IPTC Standard - Photo Metadata 2008 composé de 2 partie principales, le IPTC Core version 1.1 et le IPTC Extension version 1.0. Le IPTC Core est en continuité avec la norme de 1999 et assure une compatibilité entre les deux. Le IPTC Extension quand à lui une norme entièrement nouvelle, beaucoup plus complexe et complète mais n'est pas compatible avec la norme de 1999. La nouvelle norme a été approuvée en juillet 2008 et est disponible au http://www.iptc.org/std/photometadata/2008/specification/IPTC-PhotoMetadata-2008.pdf.

J'ai conserver les définitions tel que présentées dans la norme de l'IPTC de 1999.

IPTC - NAA Information Interchange M o d e l Version No. 4, Rev 1 July 1999. Dernière version au 1er janvier 2006 selon le site de http://www.iptc.org. Comité International des Télécommunications de Presse. Une traduction française du document n'existe pas, à ma connaissance.

Chapitre 6

2:00 Record Version
Mandatory, not repeatable, two octets. A binary number identifying the version of the Information Interchange Model, Part II (Record 2:xx), utilised by the provider. Version numbers are assigned by IPTC and NAA. The version number of this record is four (4).

2:03 Object Type Reference
Not repeatable, 3-67 octets, consisting of 2 numeric characters followed by a colon and an optional text part of up to 64 octets. The Object Type is used to distinguish between different types of objects within the IIM. The first part is a number representing a language independent international reference to an Object Type followed by a colon separator. The second part, if used, is a text representation of the Object Type Number (maximum 64 octets) consisting of graphic characters plus spaces either in English, as defined in Appendix G, or in the language of the service as indicated in DataSet 2:135 A list of Object Type Numbers and Names and their corresponding definitions will be maintained by the IPTC. See Appendix G.
Ex: 01 News 02 Data 03 Advisory

2:04 Object Attribute Reference
Repeatable, 4-68 octets, consisting of 3 numeric characters followed by a colon and an optional text part of up to 64 octets. The Object Attribute defines the nature of the object independent of the Subject. The first part is a number representing a language independent international reference to an Object Attribute followed by a colon separator. The second part, if used, is a text representation of the Object Attribute Number ( maximum 64 octets) consisting of graphic characters plus spaces either in English, as defined in Appendix G, or in the language of the service as indicated in DataSet 2:135 A registry of Object Attribute Numbers and Names and their corresponding definitions (if available) will be maintained by the IPTC in different languages, with translations as supplied by members. See Appendix G.

2:05 Object Name
Not repeatable, maximum 64 octets, consisting of graphic characters plus spaces. Used as a shorthand reference for the object. Changes to existing data, such as updated stories or new crops on photos, should be identified in Edit Status.
Examples: "Wall St." "Ferry Sinks"

2:07 Edit Status
Not repeatable. Maximum 64 octets, consisting of graphic characters plus spaces. Status of the objectdata, according to the practice of the provider.
Examples: "Lead" "CORRECTION"

2:08 Editorial Update
Not repeatable, 2 octets, consisting of numeric characters. Indicates the type of update that this object provides to a previous object. The link to the previous object is made using the ARM (DataSets 1:120 and 1:122), according to the practices of the provider. Possible values:
01 Additional language. Signifies that the accompanying Record 2 DataSets repeat information from another object in a different natural language (as indicated by DataSet 2:135).

2:10 Urgency
Not repeatable, one octet, consisting of a numeric character. Specifies the editorial urgency of content and not necessarily the envelope handling priority (see 1:60, Envelope Priority). The '1' is most urgent, '5' normal and '8' denotes the least-urgent copy. The numerals '9' and '0' are reserved for future use.

2:12 Subject Reference
Repeatable. Minimum of 13 and maximum of 236 octets consisting of graphic characters. Colon ‘:’ is only allowed as specified, the asterisk ‘*’ and question mark ‘?’ are not allowed, nor are the octet values 42 and 63. The character encoding used for this dataset must encode the colon ':' using octet value 58, and must not use this octet value for any other purpose. .......

2:15 Category
Not repeatable, maximum three octets, consisting of alphabetic characters. Identifies the subject of the objectdata in the opinion of the provider. A list of categories will be maintained by a regional registry, where available, otherwise by the provider. Note: Use of this DataSet is Deprecated. It is likely that this DataSet will not be included in further versions of the IIM.

2:20 Supplemental Category
Repeatable, maximum 32 octets, consisting of graphic characters plus spaces. Supplemental categories further refine the subject of an objectdata. Only a single supplemental category may be contained in each DataSet. A supplemental category may include any of the recognised categories as used in 2:15. Otherwise, selection of supplemental categories are left to the provider.
Examples: "NHL" (National Hockey League) "Fußball" Note: Use of this DataSet is Deprecated. It is likely that this DataSet will not be included in further versions of the IIM.

2:22 Fixture Identifier
Not repeatable, maximum 32 octets, consisting of graphic characters. Identifies objectdata that recurs often and predictably. Enables users to immediately find or recall such an object.
Example: "EUROWEATHER"

2:25 Keywords
Repeatable, maximum 64 octets, consisting of graphic characters plus spaces. Used to indicate specific information retrieval words.
Each keyword uses a single Keywords DataSet. Multiple keywords use multiple Keywords DataSets. It is expected that a provider of various types of data that are related in subject matter uses the same keyword, enabling the receiving system or subsystems to search across all types of data for related material.
Examples: "GRAND PRIX" "AUTO"

2:26 Content Location Code
Repeatable, 3 octets consisting of alphabetic characters. Indicates the code of a country/geographical location referenced
by the content of the object. Where ISO has established an appropriate country code under ISO 3166, that code will be used. When ISO3166 does not adequately provide for identification of a location or a country, e.g. ships at sea, space, IPTC will assign an appropriate threecharacter code under the provisions of ISO3166 to avoid conflicts. (see Appendix D) . If used in the same object with DataSet 2:27, must immediately precede and correspond to it.

2:27 Content Location Name
Repeatable, maximum 64 octets, consisting of graphic characters plus spaces. Provides a full, publishable name of a country/geographical
location referenced by the content of the object, according to guidelines of the provider. If used in the same object with DataSet 2:26, must immediately follow and correspond to it.

2:30 Release Date
Not repeatable, eight octets, consisting of numeric characters. Designates in the form CCYYMMDD the earliest date the provider intends the object to be used. Follows ISO 8601 standard.
Example: "19890317" indicates data for release on 17 March 1989.

2:35 Release Time
Not repeatable, 11 octets, consisting of graphic characters. Designates in the form HHMMSS±HHMM the earliest time the provider intends the object to be used. Follows ISO 8601 standard.
Example: "090000-0500" indicates object for use after 0900 in New York (five hours behind UTC)

2:37 Expiration Date
Not repeatable, eight octets, consisting of numeric characters. Designates in the form CCYYMMDD the latest date the provider or owner intends the objectdata to be used. Follows ISO 8601 standard.
Example: “19940317” indicates an objectdata that should not be used after 17 March 1994.

2:38 Expiration Time
Not repeatable, 11 octets, consisting of graphic characters. Designates in the form HHMMSS±HHMM the latest time the provider or owner intends the objectdata to be used. Follows ISO 8601 standard.
Example: "090000-0500" indicates an objectdata that should not be used after 0900 in New York (five hours behind UTC).
Expiration date and time have uses beyond audio data. Weather forecasts, for example, typically carry expiration dates and times.

2:40 Special Instructions
Not repeatable, maximum 256 octets, consisting of graphic characters plus spaces. Other editorial instructions concerning the use of the objectdata, such as embargoes and warnings.
Examples: "SECOND OF FOUR STORIES" "3 Pictures follow" "Argentina OUT"

2:42 Action Advised
Not repeatable, 2 octets, consisting of numeric characters. Indicates the type of action that this object provides to a previous object. The link to the previous object is made using the ARM (DataSets 1:120 and 1:122), according to the practices of the provider. Possible values:
01 Object Kill. Signifies .....

2:45 Reference Service
Optional, repeatable, format identical with 1:30. Identifies the Service Identifier of a prior envelope to which the current object refers. Must be followed by 2:47 and 2:50 with repetition occurring in sequential triplets. Used together, 2:45, 2:47 and 2:50 indicate
that the current object refers to the content of a prior envelope. (1:30 Service Identifier Mandatory, not repeatable. Up to 10 octets, consisting of graphic characters. Identifies the provider and product.)

2:47 Reference Date
Mandatory if 2:45 exists and otherwise not allowed. Repeatable, format identical with 1:70 Identifies the date of a prior envelope to which the current object refers. (1:70 Date Sent Mandatory, not repeatable. Eight octets, consisting of numeric characters. Uses the format CCYYMMDD (century, year, month, day) as defined in ISO 8601 to indicate year, month and day the service sent the material.)

2:50 Reference Number
Mandatory if 2:45 exists and otherwise not allowed. Repeatable, format identical with 1:40. Identifies the Envelope Number of a prior envelope to which the current object refers. (1:40 Envelope Number Mandatory, not repeatable, eight octets, consisting of numeric characters.
The characters form a number that will be unique for the date specified in 1:70 and for the Service Identifier specified in 1:30. If identical envelope numbers appear with the same date and with the same Service Identifier, records 2-9 must be unchanged from the original. This is not intended to be a sequential serial number reception check.)

2:55 Date Created
Not repeatable, eight octets, consisting of numeric characters. Represented in the form CCYYMMDD to designate the date the intellectual content of the objectdata was created rather than the date of the creation of the physical representation. Follows ISO 8601 standard. Where the month or day cannot be determined, the information will be represented by “00”. Where the year cannot be determined, the information for century and year will be represented by “00”. Thus a photo taken during the American Civil War would carry a creation date during that epoch (1861-1865) rather than the date the photo was digitised for archiving.
Example: "19900127" indicates the intellectual content created on 27th January 1990.

2:60 Time Created
Not repeatable, 11 octets, consisting of graphic characters. Represented in the form HHMMSS±HHMM to designate the time the intellectual content of the objectdata current source material was created rather than the creation of the physical representation. Follows ISO 8601 standard. Where the time cannot be precisely determined, the closest approximation should be used.
Example: "133015+0100" indicates that the object intellectual content was created at 1:30 p.m. and 15 seconds Frankfurt time, one hour ahead of UTC.

2:62 Digital Creation Date
Not repeatable, eight octets, consisting of numeric characters. Represented in the form CCYYMMDD to designate the date the digital representation of the objectdata was created. Follows ISO 8601 standard. Thus a photo taken during the American Civil War would carry a Digital Creation Date within the past several years rather than the date where the image was captured on film, glass plate or other substrate during that epoch (1861-1865).
Example: "19900127" indicates digital form of the objectdata was created on 27th January 1990.

2:63 Digital Creation Time
Not repeatable, 11 octets, consisting of graphic characters. Represented in the form HHMMSS±HHMM to designate the time the digital representation of the objectdata was created. Follows ISO 8601 standard.
Example: "133015+0100" indicates that the digital form of the objectdata was created at 1:30 p.m. and 15 seconds Frankfurt time, one hour ahead of UTC.

2:65 Originating Program
Not repeatable, maximum of 32 octets, consisting of graphic characters plus spaces. Identifies the type of program used to originate the objectdata.
Examples: "Word Perfect" "SCITEX" "MacDraw"

2:70 Program Version
Not repeatable, maximum of 10 octets, consisting of graphic characters plus spaces. Used to identify the version of the program mentioned in 2:65. DataSet 2:70 is invalid if 2:65 is not present.

2:75 Object Cycle
Not repeatable, one octet, consisting of an alphabetic character. Where: 'a' = morning 'p' = evening 'b' = both Virtually only used in North America.

2:80 By-line
Repeatable, maximum 32 octets, consisting of graphic characters plus spaces. Contains name of the creator of the objectdata, e.g. writer, photographer or graphic artist.
Examples: "Robert Capa" "Ernest Hemingway" "Pablo Picasso"

2:85 By-line Title
Repeatable, maximum 32 octets, consisting of graphic characters plus spaces. A by-line title is the title of the creator or creators of an objectdata. Where used, a by-line title should follow the by-line it modifies.
Examples: "Staff Photographer" "Corresponsal" "Envoyé Spécial"

2:90 City
Not repeatable, maximum 32 octets, consisting of graphic characters plus spaces. Identifies city of objectdata origin according to guidelines established by the provider.
Examples: "Zürich" "Milano" "New York"

2:92 Sublocation
Not repeatable, maximum 32 octets, consisting of graphic characters plus spaces. Identifies the location within a city from which the objectdata originates, according to guidelines established by the provider.
Examples: "Capitol Hill" "Maple Leaf Gardens" "Strandgateparken"
Note: The location used as a dateline for audio reports often refers not to a city, but a place within a city, such as "Strandgateparken."

2:95 Province/State
Not repeatable, maximum 32 octets, consisting of graphic characters plus spaces. Identifies Province/State of origin according to guidelines established by the provider.
Examples: "WA" "Sussex" "Baden-Württenberg"

2:100 Country/Primary Location Code
Not repeatable, three octets consisting of alphabetic characters. Indicates the code of the country/primary location where the intellectual property of the objectdata was created, e.g. a photo was taken, an event occurred. Where ISO has established an appropriate country code under ISO 3166, that code will be used. When ISO3166 does not adequately provide for identification of a location or a new country, e.g. ships at sea, space, IPTC will assign an appropriate three-character code under the provisions of ISO3166 to avoid conflicts. (see Appendix D)
Examples: "USA" (United States) "FRA" (France) “XUN” (United Nations)

2:101 Country/Primary Location Name
Not repeatable, maximum 64 octets, consisting of graphic characters plus spaces. Provides full, publishable, name of the country/primary location where the intellectual property of the objectdata was created, according to guidelines of the provider.

2:103 Original Transmission Reference
Not repeatable. Maximum 32 octets, consisting of graphic characters plus spaces. A code representing the location of original transmission according to practices of the provider.
Examples: BER-5 PAR-12-11-01

2:105 Headline
Not repeatable, maximum of 256 octets, consisting of graphic characters plus spaces. A publishable entry providing a synopsis of the contents of the objectdata.
Example: "Lindbergh Lands In Paris"

2:110 Credit
Not repeatable, maximum of 32 octets, consisting of graphic characters plus spaces. Identifies the provider of the objectdata, not necessarily the owner/creator.

2:115 Source
Not repeatable, maximum of 32 octets, consisting of graphic characters plus spaces. Identifies the original owner of the intellectual content of the objectdata. This could be an agency, a member of an agency or an individual.

2:116 Copyright Notice
Not repeatable, maximum of 128 octets, consisting of graphic characters plus spaces. Contains any necessary copyright notice.

2:118 Contact
Repeatable, maximum of 128 octets, consisting of graphic characters plus spaces. Identifies the person or organisation which can provide further background information on the objectdata.

2:120 Caption/Abstract
Not repeatable, maximum of 2000 octets, consisting of graphic characters plus carriage-returns, linefeeds and spaces. A textual description of the objectdata, particularly used where the object is not text.

2:122 Writer/Editor
Repeatable, maximum 32 octets, consisting of graphic characters plus spaces. Identification of the name of the person involved in the writing, editing or correcting the objectdata or caption/abstract.

2:125, 2:130, 2:131 Données d'images

2:135 Language Identifier
Not repeatable, two or three octets, consisting of alphabetic characters.Describes the major national language of the object, according to the 2-letter codes of ISO 639:1988. Does not define or imply any coded character set, but is used for internal routing, e.g. to various editorial desks. Implementation note: Programmers should provide for three octets for Language Identifier because the ISO is expected to provide for 3-letter codes in the future.

2:150, 2:151, 2:152, 2:153, 2:154 Données audio

2:200, 2:201, 2:202 Données binaires

 

mwl

Au besoin Cliques ici pour m'envoyer un courriel.

Dernière modification : 10 janvier 2017.