-
Notifications
You must be signed in to change notification settings - Fork 0
/
iptc.html
919 lines (903 loc) · 26.8 KB
/
iptc.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <!--*- sgml -*-->
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta name="author" content="Exiv2 contributors">
<meta name="description" content="Open Source Exif, IPTC and XMP metadata library and tools with Exif MakerNote and read/write support">
<meta name="keywords" content="exif, iptc, xmp, metadata, makernote, manipulation, manipulate, read and write, write, change, update, jpeg, jpg, ifd, image file directory, thumbnail, thumbnails, tag, tags, canon, fujifilm, sigma/foveon, nikon, open source, opensource">
<link rel="apple-touch-icon" sizes="57x57" href="/icons/apple-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="/icons/apple-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="/icons/apple-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="/icons/apple-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="/icons/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="/icons/apple-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="/icons/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="/icons/apple-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="/icons/apple-icon-180x180.png">
<link rel="icon" type="image/png" sizes="192x192" href="/icons/android-icon-192x192.png">
<link rel="icon" type="image/png" sizes="32x32" href="/icons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="96x96" href="/icons/favicon-96x96.png">
<link rel="icon" type="image/png" sizes="16x16" href="/icons/favicon-16x16.png">
<link rel="manifest" href="/icons/manifest.json">
<meta name="msapplication-TileColor" content="#ffffff">
<meta name="msapplication-TileImage" content="/icons/ms-icon-144x144.png">
<meta name="theme-color" content="#ffffff">
<title>Exiv2 - Image metadata library and tools</title>
<!-- Doxygen styles -->
<link href="doc/doxygen.css" rel="stylesheet" type="text/css">
<link href="doc/customdoxygen.css" rel="stylesheet" type="text/css">
<!-- Bootstrap core CSS -->
<link href="dist/css/bootstrap.min.css" rel="stylesheet">
<!-- Bootstrap theme -->
<link href="dist/css/bootstrap-theme.min.css" rel="stylesheet">
<!-- Custom styles for this template -->
<link href="include/exiv2.css" rel="stylesheet">
<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
</head>
<body>
<nav class="navbar navbar-default navbar-static-top">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar" aria-expanded="false" aria-controls="navbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.html">
<img alt="Exiv2" src="include/exiv2-logo-small.png">
</a>
</div>
<div id="navbar" class="collapse navbar-collapse">
<ul class="nav navbar-nav">
<li><a href="getting-started.html">Getting started</a></li>
<li><a href="download.html">Download</a></li>
<li><a href="whatsnew.html">What's New</a></li>
<li><a href="metadata.html">Metadata</a></li>
<li><a href="makernote.html">Makernote</a></li>
<li><a href="doc/examples.html">Examples</a></li>
<li><a href="doc/index.html">API</a></li>
<li><a href="manpage.html">Manual</a></li>
<li><a href="book/index.html">Book</a></li>
<li><a href="https://github.com/exiv2/exiv2" target="_blank">GitHub</a></li>
</ul>
</div><!--/.nav-collapse -->
</div>
</nav>
<div class="container">
<div class="page-header">
<h1>Metadata reference tables</h1>
</div>
<div><h2>IPTC datasets defined in Exiv2</h2></div>
<p>Datasets are defined according to the specification of the IPTC
<a href="https://iptc.org/standards/iim/">Information Interchange Model (IIM)</a>.</p>
<table class="table table-striped">
<thead><tr>
<th>Tag (hex)</th>
<th>Tag (dec)</th>
<th>Key</th>
<th>Type</th>
<th><abbr title="Mandatory">M.</abbr></th>
<th><abbr title="Repeatable">R.</abbr></th>
<th>Min. bytes</th>
<th>Max. bytes</th>
<th>Tag description</th>
</tr></thead>
<tbody>
<tr>
<td>0x0000</td>
<td>0</td>
<td>Iptc.Envelope.ModelVersion</td>
<td>Short</td>
<td>Yes</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>A binary number identifying the version of the Information Interchange Model, Part I, utilised by the provider. Version numbers are assigned by IPTC and NAA organizations.</td>
</tr>
<tr>
<td>0x0005</td>
<td>5</td>
<td>Iptc.Envelope.Destination</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>1024</td>
<td>This DataSet is to accommodate some providers who require routing information above the appropriate OSI layers.</td>
</tr>
<tr>
<td>0x0014</td>
<td>20</td>
<td>Iptc.Envelope.FileFormat</td>
<td>Short</td>
<td>Yes</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>A binary number representing the file format. The file format must be registered with IPTC or NAA with a unique number assigned to it. The information is used to route the data to the appropriate system and to allow the receiving system to perform the appropriate actions there to.</td>
</tr>
<tr>
<td>0x0016</td>
<td>22</td>
<td>Iptc.Envelope.FileVersion</td>
<td>Short</td>
<td>Yes</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>A binary number representing the particular version of the File Format specified by <FileFormat> tag.</td>
</tr>
<tr>
<td>0x001e</td>
<td>30</td>
<td>Iptc.Envelope.ServiceId</td>
<td>String</td>
<td>Yes</td>
<td>No</td>
<td>0</td>
<td>10</td>
<td>Identifies the provider and product</td>
</tr>
<tr>
<td>0x0028</td>
<td>40</td>
<td>Iptc.Envelope.EnvelopeNumber</td>
<td>String</td>
<td>Yes</td>
<td>No</td>
<td>8</td>
<td>8</td>
<td>The characters form a number that will be unique for the date specified in <DateSent> tag and for the Service Identifier specified by <ServiceIdentifier> tag. 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.</td>
</tr>
<tr>
<td>0x0032</td>
<td>50</td>
<td>Iptc.Envelope.ProductId</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>32</td>
<td>Allows a provider to identify subsets of its overall service. Used to provide receiving organisation data on which to select, route, or otherwise handle data.</td>
</tr>
<tr>
<td>0x003c</td>
<td>60</td>
<td>Iptc.Envelope.EnvelopePriority</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>1</td>
<td>1</td>
<td>Specifies the envelope handling priority and not the editorial urgency (see <Urgency> tag). "1" indicates the most urgent, "5" the normal urgency, and "8" the least urgent copy. The numeral "9" indicates a User Defined Priority. The numeral "0" is reserved for future use.</td>
</tr>
<tr>
<td>0x0046</td>
<td>70</td>
<td>Iptc.Envelope.DateSent</td>
<td>Date</td>
<td>Yes</td>
<td>No</td>
<td>8</td>
<td>8</td>
<td>Uses the format CCYYMMDD (century, year, month, day) as de-fined in ISO 8601 to indicate year, month and day the service sent the material.</td>
</tr>
<tr>
<td>0x0050</td>
<td>80</td>
<td>Iptc.Envelope.TimeSent</td>
<td>Time</td>
<td>No</td>
<td>No</td>
<td>11</td>
<td>11</td>
<td>Uses the format HHMMSS:HHMM where HHMMSS refers to local hour, minute and seconds and HHMM refers to hours and minutes ahead (+) or behind (-) Universal Coordinated Time as described in ISO 8601. This is the time the service sent the material.</td>
</tr>
<tr>
<td>0x005a</td>
<td>90</td>
<td>Iptc.Envelope.CharacterSet</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>32</td>
<td>This tag consisting of one or more control functions used for the announcement, invocation or designation of coded character sets. The control functions follow the ISO 2022 standard and may consist of the escape control character and one or more graphic characters.</td>
</tr>
<tr>
<td>0x0064</td>
<td>100</td>
<td>Iptc.Envelope.UNO</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>14</td>
<td>80</td>
<td>This tag provide a globally unique identification for objects as specified in the IIM, independent of provider and for any media form. The provider must ensure the UNO is unique. Objects with the same UNO are identical.</td>
</tr>
<tr>
<td>0x0078</td>
<td>120</td>
<td>Iptc.Envelope.ARMId</td>
<td>Short</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>The DataSet identifies the Abstract Relationship Method identifier (ARM) which is described in a document registered by the originator of the ARM with the IPTC and NAA organizations.</td>
</tr>
<tr>
<td>0x007a</td>
<td>122</td>
<td>Iptc.Envelope.ARMVersion</td>
<td>Short</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>This tag consisting of a binary number representing the particular version of the ARM specified by tag <ARMId>.</td>
</tr>
<tr>
<td>0x0000</td>
<td>0</td>
<td>Iptc.Application2.RecordVersion</td>
<td>Short</td>
<td>Yes</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>A binary number identifying the version of the Information Interchange Model, Part II, utilised by the provider. Version numbers are assigned by IPTC and NAA organizations.</td>
</tr>
<tr>
<td>0x0003</td>
<td>3</td>
<td>Iptc.Application2.ObjectType</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>3</td>
<td>67</td>
<td>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 consisting of graphic characters plus spaces either in English or in the language of the service as indicated in tag <LanguageIdentifier></td>
</tr>
<tr>
<td>0x0004</td>
<td>4</td>
<td>Iptc.Application2.ObjectAttribute</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>4</td>
<td>68</td>
<td>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 consisting of graphic characters plus spaces either in English, or in the language of the service as indicated in tag <LanguageIdentifier></td>
</tr>
<tr>
<td>0x0005</td>
<td>5</td>
<td>Iptc.Application2.ObjectName</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>64</td>
<td>Used as a shorthand reference for the object. Changes to exist-ing data, such as updated stories or new crops on photos, should be identified in tag <EditStatus>.</td>
</tr>
<tr>
<td>0x0007</td>
<td>7</td>
<td>Iptc.Application2.EditStatus</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>64</td>
<td>Status of the object data, according to the practice of the provider.</td>
</tr>
<tr>
<td>0x0008</td>
<td>8</td>
<td>Iptc.Application2.EditorialUpdate</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>Indicates the type of update that this object provides to a previous object. The link to the previous object is made using the tags <ARMIdentifier> and <ARMVersion>, according to the practices of the provider.</td>
</tr>
<tr>
<td>0x000a</td>
<td>10</td>
<td>Iptc.Application2.Urgency</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>1</td>
<td>1</td>
<td>Specifies the editorial urgency of content and not necessarily the envelope handling priority (see tag <EnvelopePriority>). The "1" is most urgent, "5" normal and "8" denotes the least-urgent copy.</td>
</tr>
<tr>
<td>0x000c</td>
<td>12</td>
<td>Iptc.Application2.Subject</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>13</td>
<td>236</td>
<td>The Subject Reference is a structured definition of the subject matter.</td>
</tr>
<tr>
<td>0x000f</td>
<td>15</td>
<td>Iptc.Application2.Category</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>3</td>
<td>Identifies the subject of the object data in the opinion of the provider. A list of categories will be maintained by a regional registry, where available, otherwise by the provider.</td>
</tr>
<tr>
<td>0x0014</td>
<td>20</td>
<td>Iptc.Application2.SuppCategory</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>32</td>
<td>Supplemental categories further refine the subject of an object data. A supplemental category may include any of the recognised categories as used in tag <Category>. Otherwise, selection of supplemental categories are left to the provider.</td>
</tr>
<tr>
<td>0x0016</td>
<td>22</td>
<td>Iptc.Application2.FixtureId</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>32</td>
<td>Identifies object data that recurs often and predictably. Enables users to immediately find or recall such an object.</td>
</tr>
<tr>
<td>0x0019</td>
<td>25</td>
<td>Iptc.Application2.Keywords</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>64</td>
<td>Used to indicate specific information retrieval words. 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.</td>
</tr>
<tr>
<td>0x001a</td>
<td>26</td>
<td>Iptc.Application2.LocationCode</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>3</td>
<td>3</td>
<td>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 ISO 3166 does not adequately provide for identification of a location or a country, e.g. ships at sea, space, IPTC will assign an appropriate three-character code under the provisions of ISO 3166 to avoid conflicts.</td>
</tr>
<tr>
<td>0x001b</td>
<td>27</td>
<td>Iptc.Application2.LocationName</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>64</td>
<td>Provides a full, publishable name of a country/geographical location referenced by the content of the object, according to guidelines of the provider.</td>
</tr>
<tr>
<td>0x001e</td>
<td>30</td>
<td>Iptc.Application2.ReleaseDate</td>
<td>Date</td>
<td>No</td>
<td>No</td>
<td>8</td>
<td>8</td>
<td>Designates in the form CCYYMMDD the earliest date the provider intends the object to be used. Follows ISO 8601 standard.</td>
</tr>
<tr>
<td>0x0023</td>
<td>35</td>
<td>Iptc.Application2.ReleaseTime</td>
<td>Time</td>
<td>No</td>
<td>No</td>
<td>11</td>
<td>11</td>
<td>Designates in the form HHMMSS:HHMM the earliest time the provider intends the object to be used. Follows ISO 8601 standard.</td>
</tr>
<tr>
<td>0x0025</td>
<td>37</td>
<td>Iptc.Application2.ExpirationDate</td>
<td>Date</td>
<td>No</td>
<td>No</td>
<td>8</td>
<td>8</td>
<td>Designates in the form CCYYMMDD the latest date the provider or owner intends the object data to be used. Follows ISO 8601 standard.</td>
</tr>
<tr>
<td>0x0026</td>
<td>38</td>
<td>Iptc.Application2.ExpirationTime</td>
<td>Time</td>
<td>No</td>
<td>No</td>
<td>11</td>
<td>11</td>
<td>Designates in the form HHMMSS:HHMM the latest time the provider or owner intends the object data to be used. Follows ISO 8601 standard.</td>
</tr>
<tr>
<td>0x0028</td>
<td>40</td>
<td>Iptc.Application2.SpecialInstructions</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>256</td>
<td>Other editorial instructions concerning the use of the object data, such as embargoes and warnings.</td>
</tr>
<tr>
<td>0x002a</td>
<td>42</td>
<td>Iptc.Application2.ActionAdvised</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>Indicates the type of action that this object provides to a previous object. The link to the previous object is made using tags <ARMIdentifier> and <ARMVersion>, according to the practices of the provider.</td>
</tr>
<tr>
<td>0x002d</td>
<td>45</td>
<td>Iptc.Application2.ReferenceService</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>10</td>
<td>Identifies the Service Identifier of a prior envelope to which the current object refers.</td>
</tr>
<tr>
<td>0x002f</td>
<td>47</td>
<td>Iptc.Application2.ReferenceDate</td>
<td>Date</td>
<td>No</td>
<td>Yes</td>
<td>8</td>
<td>8</td>
<td>Identifies the date of a prior envelope to which the current object refers.</td>
</tr>
<tr>
<td>0x0032</td>
<td>50</td>
<td>Iptc.Application2.ReferenceNumber</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>8</td>
<td>8</td>
<td>Identifies the Envelope Number of a prior envelope to which the current object refers.</td>
</tr>
<tr>
<td>0x0037</td>
<td>55</td>
<td>Iptc.Application2.DateCreated</td>
<td>Date</td>
<td>No</td>
<td>No</td>
<td>8</td>
<td>8</td>
<td>Represented in the form CCYYMMDD to designate the date the intellectual content of the object data was created rather than the date of the creation of the physical representation. Follows ISO 8601 standard.</td>
</tr>
<tr>
<td>0x003c</td>
<td>60</td>
<td>Iptc.Application2.TimeCreated</td>
<td>Time</td>
<td>No</td>
<td>No</td>
<td>11</td>
<td>11</td>
<td>Represented in the form HHMMSS:HHMM to designate the time the intellectual content of the object data current source material was created rather than the creation of the physical representation. Follows ISO 8601 standard.</td>
</tr>
<tr>
<td>0x003e</td>
<td>62</td>
<td>Iptc.Application2.DigitizationDate</td>
<td>Date</td>
<td>No</td>
<td>No</td>
<td>8</td>
<td>8</td>
<td>Represented in the form CCYYMMDD to designate the date the digital representation of the object data was created. Follows ISO 8601 standard.</td>
</tr>
<tr>
<td>0x003f</td>
<td>63</td>
<td>Iptc.Application2.DigitizationTime</td>
<td>Time</td>
<td>No</td>
<td>No</td>
<td>11</td>
<td>11</td>
<td>Represented in the form HHMMSS:HHMM to designate the time the digital representation of the object data was created. Follows ISO 8601 standard.</td>
</tr>
<tr>
<td>0x0041</td>
<td>65</td>
<td>Iptc.Application2.Program</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>32</td>
<td>Identifies the type of program used to originate the object data.</td>
</tr>
<tr>
<td>0x0046</td>
<td>70</td>
<td>Iptc.Application2.ProgramVersion</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>10</td>
<td>Used to identify the version of the program mentioned in tag <Program>.</td>
</tr>
<tr>
<td>0x004b</td>
<td>75</td>
<td>Iptc.Application2.ObjectCycle</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>1</td>
<td>1</td>
<td>Used to identify the editorial cycle of object data.</td>
</tr>
<tr>
<td>0x0050</td>
<td>80</td>
<td>Iptc.Application2.Byline</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>32</td>
<td>Contains name of the creator of the object data, e.g. writer, photographer or graphic artist.</td>
</tr>
<tr>
<td>0x0055</td>
<td>85</td>
<td>Iptc.Application2.BylineTitle</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>32</td>
<td>A by-line title is the title of the creator or creators of an object data. Where used, a by-line title should follow the by-line it modifies.</td>
</tr>
<tr>
<td>0x005a</td>
<td>90</td>
<td>Iptc.Application2.City</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>32</td>
<td>Identifies city of object data origin according to guidelines established by the provider.</td>
</tr>
<tr>
<td>0x005c</td>
<td>92</td>
<td>Iptc.Application2.SubLocation</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>32</td>
<td>Identifies the location within a city from which the object data originates, according to guidelines established by the provider.</td>
</tr>
<tr>
<td>0x005f</td>
<td>95</td>
<td>Iptc.Application2.ProvinceState</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>32</td>
<td>Identifies Province/State of origin according to guidelines established by the provider.</td>
</tr>
<tr>
<td>0x0064</td>
<td>100</td>
<td>Iptc.Application2.CountryCode</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>3</td>
<td>3</td>
<td>Indicates the code of the country/primary location where the intellectual property of the object data 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 ISO 3166 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 ISO 3166 to avoid conflicts.</td>
</tr>
<tr>
<td>0x0065</td>
<td>101</td>
<td>Iptc.Application2.CountryName</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>64</td>
<td>Provides full, publishable, name of the country/primary location where the intellectual property of the object data was created, according to guidelines of the provider.</td>
</tr>
<tr>
<td>0x0067</td>
<td>103</td>
<td>Iptc.Application2.TransmissionReference</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>32</td>
<td>A code representing the location of original transmission according to practices of the provider.</td>
</tr>
<tr>
<td>0x0069</td>
<td>105</td>
<td>Iptc.Application2.Headline</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>256</td>
<td>A publishable entry providing a synopsis of the contents of the object data.</td>
</tr>
<tr>
<td>0x006e</td>
<td>110</td>
<td>Iptc.Application2.Credit</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>32</td>
<td>Identifies the provider of the object data, not necessarily the owner/creator.</td>
</tr>
<tr>
<td>0x0073</td>
<td>115</td>
<td>Iptc.Application2.Source</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>32</td>
<td>Identifies the original owner of the intellectual content of the object data. This could be an agency, a member of an agency or an individual.</td>
</tr>
<tr>
<td>0x0074</td>
<td>116</td>
<td>Iptc.Application2.Copyright</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>128</td>
<td>Contains any necessary copyright notice.</td>
</tr>
<tr>
<td>0x0076</td>
<td>118</td>
<td>Iptc.Application2.Contact</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>128</td>
<td>Identifies the person or organisation which can provide further background information on the object data.</td>
</tr>
<tr>
<td>0x0078</td>
<td>120</td>
<td>Iptc.Application2.Caption</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>2000</td>
<td>A textual description of the object data.</td>
</tr>
<tr>
<td>0x007a</td>
<td>122</td>
<td>Iptc.Application2.Writer</td>
<td>String</td>
<td>No</td>
<td>Yes</td>
<td>0</td>
<td>32</td>
<td>Identification of the name of the person involved in the writing, editing or correcting the object data or caption/abstract.</td>
</tr>
<tr>
<td>0x007d</td>
<td>125</td>
<td>Iptc.Application2.RasterizedCaption</td>
<td>Undefined</td>
<td>No</td>
<td>No</td>
<td>7360</td>
<td>7360</td>
<td>Contains the rasterized object data description and is used where characters that have not been coded are required for the caption.</td>
</tr>
<tr>
<td>0x0082</td>
<td>130</td>
<td>Iptc.Application2.ImageType</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>Indicates the color components of an image.</td>
</tr>
<tr>
<td>0x0083</td>
<td>131</td>
<td>Iptc.Application2.ImageOrientation</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>1</td>
<td>1</td>
<td>Indicates the layout of an image.</td>
</tr>
<tr>
<td>0x0087</td>
<td>135</td>
<td>Iptc.Application2.Language</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>3</td>
<td>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.</td>
</tr>
<tr>
<td>0x0096</td>
<td>150</td>
<td>Iptc.Application2.AudioType</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>Indicates the type of an audio content.</td>
</tr>
<tr>
<td>0x0097</td>
<td>151</td>
<td>Iptc.Application2.AudioRate</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>6</td>
<td>6</td>
<td>Indicates the sampling rate in Hertz of an audio content.</td>
</tr>
<tr>
<td>0x0098</td>
<td>152</td>
<td>Iptc.Application2.AudioResolution</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>Indicates the sampling resolution of an audio content.</td>
</tr>
<tr>
<td>0x0099</td>
<td>153</td>
<td>Iptc.Application2.AudioDuration</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>6</td>
<td>6</td>
<td>Indicates the duration of an audio content.</td>
</tr>
<tr>
<td>0x009a</td>
<td>154</td>
<td>Iptc.Application2.AudioOutcue</td>
<td>String</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>64</td>
<td>Identifies the content of the end of an audio object data, according to guidelines established by the provider.</td>
</tr>
<tr>
<td>0x00c8</td>
<td>200</td>
<td>Iptc.Application2.PreviewFormat</td>
<td>Short</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>A binary number representing the file format of the object data preview. The file format must be registered with IPTC or NAA organizations with a unique number assigned to it.</td>
</tr>
<tr>
<td>0x00c9</td>
<td>201</td>
<td>Iptc.Application2.PreviewVersion</td>
<td>Short</td>
<td>No</td>
<td>No</td>
<td>2</td>
<td>2</td>
<td>A binary number representing the particular version of the object data preview file format specified in tag <PreviewFormat>.</td>
</tr>
<tr>
<td>0x00ca</td>
<td>202</td>
<td>Iptc.Application2.Preview</td>
<td>Undefined</td>
<td>No</td>
<td>No</td>
<td>0</td>
<td>256000</td>
<td>Binary image preview data.</td>
</tr>
</tbody>
</table>
</div><!-- /.container -->
<div id="footer">
<footer>
<div class="container">
<div class="row">
<div class="page-footer">
<div class="col-sm-5">
Exiv2 v0.27.5.3
</div><!-- /.col-sm-5 -->
<div class="col-sm-2"></div><!-- /.col-sm-2 -->
<div class="col-sm-5">
<span class="visible-xs-block text-center"><p>Last modified 2022-02-18 16:45 UTC</p></span>
<span class="hidden-xs pull-right"><p>Last modified 2022-02-18 16:45 UTC</p></span>
</div><!-- /.col-sm-5 -->
</div>
</div><!-- /.row -->
</div><!-- /.container -->
</footer>
</div><!-- closes footer -->
<!-- Bootstrap core JavaScript
================================================== -->
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>
<script src="dist/js/bootstrap.min.js"></script>
<!-- IE10 viewport hack for Surface/desktop Windows 8 bug -->
<script src="dist/assets/js/ie10-viewport-bug-workaround.js"></script>
</body>
</html>