Overview.html
56.2 KB
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
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<title>Ontology for Media Resource 1.0</title>
<style type="text/css">
/**/
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
dt.label { display: run-in; }
li, p { margin-top: 0.3em;
margin-bottom: 0.3em; }
.diff-chg { background-color: yellow; }
.diff-del { background-color: red; text-decoration: line-through;}
.diff-add { background-color: lime; }
table { empty-cells: show; }
table caption {
font-weight: normal;
font-style: italic;
text-align: left;
margin-bottom: .5em;
}
div.issue {
color: red;
}
.rfc2119 {
font-variant: small-caps;
}
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
div.boxedtext {
border: solid #bebebe 1px;
margin: 2em 1em 1em 2em;
}
span.practicelab {
margin: 1.5em 0.5em 1em 1em;
font-weight: bold;
font-style: italic;
}
span.practicelab { background: #dfffff; }
span.practicelab {
position: relative;
padding: 0 0.5em;
top: -1.5em;
}
p.practice
{
margin: 1.5em 0.5em 1em 1em;
}
@media screen {
p.practice {
position: relative;
top: -2em;
padding: 0;
margin: 1.5em 0.5em -1em 1em;
}
}
/**/ </style>
<link rel="stylesheet" type="text/css"
href="http://www.w3.org/StyleSheets/TR/W3C-WD.css" />
</head>
<body>
<div class="head">
<p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home"
alt="W3C" height="48" width="72" /></a></p>
<h1><a name="title" id="title"></a>Ontology for Media Resource 1.0</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Working Draft 09 March
2010</h2>
<dl>
<dt>This version:</dt>
<dd><a
href="http://www.w3.org/TR/2010/WD-mediaont-10-20100309">http://www.w3.org/TR/2010/WD-mediaont-10-20100309</a></dd>
<dt>Latest version:</dt>
<dd><a
href="http://www.w3.org/TR/mediaont-10">http://www.w3.org/TR/mediaont-10</a></dd>
<dt>Previous version:</dt>
<dd><a
href="http://www.w3.org/TR/2009/WD-mediaont-10-20090618">http://www.w3.org/TR/2009/WD-mediaont-10-20090618</a></dd>
<dt>Editors:</dt>
<dd>이원석(WonSuk Lee), Electronics and Telecommunications Research
Institute (ETRI)</dd>
<dd>Tobias Bürger, University of Innsbruck</dd>
<dd>Felix Sasaki, Potsdam University of Applied Sciences</dd>
<dd>Véronique Malaisé, VU University of Amsterdam</dd>
<dd>Florian Stegmaier, University of Passau</dd>
<dd>Joakim Söderberg, Ericsson</dd>
</dl>
<p class="copyright"><a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2010 <a href="http://www.w3.org/"><acronym
title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a
href="http://www.csail.mit.edu/"><acronym
title="Massachusetts Institute of Technology">MIT</acronym></a>, <a
href="http://www.ercim.org/"><acronym
title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a
href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> rules apply.</p>
</div>
<hr />
<div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2>
<p>This document defines the Ontology for Media Resource 1.0, a core vocabulary
to describe media resources on the Web. It is defined based on a core set of
properties which covers basic metadata to describe media resources. Further it
defines syntactic and semantic level mappings between elements from existing
formats. The ontology is supposed to foster the interoperability among various
kinds of metadata formats currently used to describe media resources on the
Web.</p>
</div>
<div>
<h2><a name="status" id="status"></a>Status of this Document</h2>
<p><em>This section describes the status of this document at the time of its
publication. Other documents may supersede this document. A list of current W3C
publications and the latest revision of this technical report can be found in
the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at
http://www.w3.org/TR/.</em></p>
<p>This is the a public Working draft<a
href="http://www.w3.org/2005/10/Process-20051014/tr.html#first-wd"></a> of the
Ontology for Media Resource 1.0 specification. It has been produced by the <a
href="http://www.w3.org/2008/WebVideo/Annotations/">Media Annotations Working
Group</a>, which is part of the <a href="http://www.w3.org/2008/WebVideo/">W3C
Video on the Web Activity</a>. The Working Group expects to advance this
specification to <a
href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsW3C">Recommendation</a>
Status.</p>
<p>Please send comments about this document to <a
href="mailto:public-media-annotation@w3.org">public-media-annotation@w3.org</a>
mailing list (<a
href="http://lists.w3.org/Archives/Public/public-media-annotation/">public
archive</a>).</p>
<p>Publication as a Working Draft does not imply endorsement by the W3C
Membership. This is a draft document and may be updated, replaced or obsoleted
by other documents at any time. It is inappropriate to cite this document as
other than work in progress. </p>
<p>This document was produced by a group operating under the <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C
Patent Policy</a>. W3C maintains a <a
href="http://www.w3.org/2004/01/pp-impl/42786/status">public list of any patent
disclosures</a> made in connection with the deliverables of the group; that
page also includes instructions for disclosing a patent. An individual who has
actual knowledge of a patent which the individual believes contains <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential
Claim(s)</a> must disclose the information in accordance with <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
6 of the W3C Patent Policy</a>.</p>
<p></p>
</div>
<div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2>
<p class="toc">1 <a href="#introduction">Introduction</a><br />
1.1 <a href="#purpose">Purpose of this specification</a><br />
1.2 <a href="#formats-in-scope">Formats in scope</a><br />
1.3 <a href="#formats-out-of-scope">Formats out of scope</a><br />
2 <a href="#Terminology">Terminology</a><br />
3 <a href="#property-value-types-definitions">Property value type
definitions</a><br />
3.1 <a href="#uri-value-type">URI</a><br />
3.2 <a href="#string-value-type">String</a><br />
3.3 <a href="#integer-value-type">Integer</a><br />
3.4 <a href="#float-value-type">Float</a><br />
3.5 <a href="#date-value-type">Date</a><br />
4 <a href="#property-definition">Property definition</a><br />
4.1 <a href="#core-property-definitions">Core property
definitions</a><br />
4.1.1 <a href="#property-approach">Description of the approach
followed for the property definitions</a><br />
4.1.2 <a href="#core-property-lists">Core properties</a><br />
4.2 <a href="#property-mapping-table">Property mapping table</a><br />
4.2.1 <a href="#rationale_mapping_table">Rationale regarding
the mapping table</a><br />
4.2.1.1 <a href="#semantic-level-mappings">Semantic
Level Mappings</a><br />
4.2.1.2 <a href="#syntactic-level-mappings">Syntactic
Level Mappings</a><br />
4.2.1.3 <a href="#mapping-expression">Mapping
expression</a><br />
4.2.2 <a href="#mapping-table">The mapping table</a><br />
</p>
<h3><a name="appendices" id="appendices"></a>Appendices</h3>
<p class="toc">A <a href="#candidate-additional-elements">Candidate Additional
Elements</a><br />
B <a href="#references">References (Normative)</a><br />
C <a href="#idinform-div1122323192">References</a> (Non-Normative)<br />
D <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br />
</p>
</div>
<hr />
<div class="body">
<div class="div1">
<h2><a name="introduction" id="introduction"></a>1 Introduction</h2>
<p><em>This section is informative.</em></p>
<p>This document introduces the Ontology for Media Resource 1.0, a core
vocabulary to describe mapping between different metadata formats of <a
title="media resource" href="#media-resource">media resources</a>, mostly
targeted to media resources on the Web. It is defined based on a core set of <a
title="property" href="#property">properties</a> which covers basic metadata to
describe <a title="media resource" href="#media-resource">media resources</a>.
For example <em>creator</em> is a common property that is supported in several
existing metadata formats, and is therefore part of the core vocabulary. This
vocabulary describes a mapping between different schemas containing this
property. Ideally, the mappings should be semantics-preserving, but this is not
achieved with the first version of the Ontology (Media Ontology 1.0), because
of the difference in nature of the properties in the mapped vocabularies. Their
extension is not exactly overlapping and their values might differ in syntax
too. For example the <a title="property"
href="#property">property</a><em>dc:creator </em> from <cite><a
href="#dc">Dublin Core</a></cite> and the <a title="property"
href="#property">property</a><em>exif:Artist </em> defined in <cite><a
href="#exif">EXIF</a></cite> are both mapped to the property <em>Creator</em>
of our Ontology, but the extension of the property in the exif vocabulary (the
set of values that the property can refer to) is more specific than the one of
Dublin Core. Mapping back and forth with our ontology as reference will hence
induce a certain loss of semantics. This is inevitable if we want to achieve a
certain amount of interoperability. </p>
<p>The Ontology defines mappings between a set of vocabularies and a set of
core properties in our own namespace. Although some of these properties can
seem to be redundant with the Dublin Core set, we defined our own namespace for
several reasons: </p>
<ul>
<li><p>Dublin Core is <em>one of</em> the vocabularies that we take into
account in the mappings.</p>
</li>
<li><p>The Dublin Core set does not cover all of our needs, we would hence
still have to create properties in our own namespace.</p>
</li>
<li><p>More importantly, the Dublin Core properties have been created with a
set of restrictions, although loose, and we might want to apply
<em>other</em> restrictions to our properties. we have to have "our hands
on" the set of properties to be able to control or constrain their
behavior, and cannot be dependant on an external source of authority for
the definition of our core mapping. For a practical use of the Media
Ontology in an API, we define type restrictions for our properties that go
beyond generic Dublin Core specification.</p>
</li>
</ul>
<p>The core set of properties and mappings, i.e. our ontology, provides the
basic information needed by targeted applications (see <a
href="http://www.w3.org/TR/2009/WD-media-annot-reqs-20090119/">Use Cases and
Requirements for Ontology and API for Media Object 1.0</a>) for supporting the
interoperability among the various kinds of metadata formats related to <a
title="media resource" href="#media-resource">media resources</a>, and
particularly media resources on the Web. In addition, the ontology will be
accompanied by an API that provides uniform access to all elements defined by
the ontology. Although the set of properties is now limited, it already
constitutes a proof of concept. </p>
<p>The initial version of this document contains only a limited set of
properties with their corresponding mappings to a subset of the vocabularies
listed in section <a href="#formats-in-scope"><b>1.2 Formats in scope</b></a>.
The mapping was done to a subset of these vocabularies as a starting point, the
subset chosen was voted by the Working Group as the vocabularies at the core of
the gorup participant's expertise. This set of vocabularies can be later
expanded to more or all of the formats in scope of the Ontology. This document
is nevertheless being published at this stage of mappings, with the aspiration
to gather wide feedback on the general direction of the Working Group. In
particular we would like to encourage feedback on section <a
href="#property-definition"><b>4 Property definition</b></a>. </p>
<div class="div2">
<h3><a name="purpose" id="purpose"></a>1.1 Purpose of this specification</h3>
<p>This specification defines an ontology for cross-community data integration
of information related to <a title="media resource"
href="#media-resource">media resources</a>, with a particular focus on media
resources on the Web. The purpose of the ontology is to help circumventing the
current proliferation of video metadata formats by providing full or partial <a
title="mapping" href="#mapping">mappings</a> towards existing formats. </p>
</div>
<div class="div2">
<h3><a name="formats-in-scope" id="formats-in-scope"></a>1.2 Formats in
scope</h3>
<p>The following table lists the formats that were selected by the working
group as in-scope, along with the identifiers which are used as prefixes to
identify them in this specification.</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>This specification is based on a review of existing formats and the <a
title="property" href="#property">properties</a> they provide. This review does
not aim to be complete, and this specification does not aim to cover all
properties defined in these formats. The choice of properties is motivated by
their wide usage.</p>
</div>
<table border="1" width="100%">
<tbody>
<tr>
<td align="center">Identifier</td>
<td align="center">Format</td>
<td align="center">Example</td>
<td align="center">Reference</td>
</tr>
<tr>
<td>cl11</td>
<td>CableLabs 1.1</td>
<td>cl11:Writer_Display</td>
<td><cite><a href="#cablelabs1">Cablelabs 1.1</a></cite></td>
</tr>
<tr>
<td>cl20</td>
<td>CableLabs 2.0</td>
<td>cl20:Producer</td>
<td><cite><a href="#cablelabs2">Cablelabs 2.0</a></cite></td>
</tr>
<tr>
<td>dig35</td>
<td>DIG35</td>
<td>dig35:ipr_name/ipr_person@description='Image Creator'</td>
<td><cite><a href="#dig35">DIG35</a></cite></td>
</tr>
<tr>
<td>dc</td>
<td>Dublin Core</td>
<td>dc:creator</td>
<td><cite><a href="#dc">Dublin Core</a></cite></td>
</tr>
<tr>
<td>ebucore</td>
<td>EBUCore</td>
<td>ebuc:creator</td>
<td><cite><a href="#ebucore">EBUCore</a></cite></td>
</tr>
<tr>
<td>pmeta</td>
<td>EBU P-Meta</td>
<td>pmeta:Contribution</td>
<td><cite><a href="#ebup">EBU P-META</a></cite></td>
</tr>
<tr>
<td>exif</td>
<td>EXIF 2.2</td>
<td>exif:Artist</td>
<td><cite><a href="#exif">EXIF</a></cite></td>
</tr>
<tr>
<td>frbr</td>
<td>FRBR</td>
<td>frbr:Person</td>
<td><cite><a href="#frbr">FRBR</a></cite></td>
</tr>
<tr>
<td>id3</td>
<td>ID3</td>
<td>id3:TCOM </td>
<td><cite><a href="#id3">ID3</a></cite></td>
</tr>
<tr>
<td>iptc</td>
<td>IPTC</td>
<td>iptc:Creator</td>
<td><cite><a href="#iptc">IPTC</a></cite></td>
</tr>
<tr>
<td>it</td>
<td>iTunes</td>
<td>it:©ART</td>
<td><cite><a href="#itunes">iTunes</a></cite></td>
</tr>
<tr>
<td>lom21</td>
<td>LOM 2.1</td>
<td>lom21:LifeCycle/Contribute/Entity</td>
<td><cite><a href="#lom">LOM</a></cite></td>
</tr>
<tr>
<td>ma</td>
<td>Core properties of MA WG</td>
<td>ma:creator</td>
<td><a href="#property-definition"><b>4 Property definition</b></a></td>
</tr>
<tr>
<td>media</td>
<td>Media RDF</td>
<td>media:Recording</td>
<td><cite><a href="#mediardf">Media RDF</a></cite></td>
</tr>
<tr>
<td>mrss</td>
<td>Media RSS</td>
<td>mrss:credit@role='author'</td>
<td><cite><a href="#mediarss">Media RSS</a></cite></td>
</tr>
<tr>
<td>mets</td>
<td>METS</td>
<td>mets:agency</td>
<td><cite><a href="#mets">METS</a></cite></td>
</tr>
<tr>
<td>mpeg7</td>
<td>MPEG-7</td>
<td>mpeg7:CreationInformation/Creation/Creator/Agent</td>
<td><cite><a href="#mpeg7">MPEG-7</a></cite></td>
</tr>
<tr>
<td>nmix</td>
<td>NISO MIX</td>
<td>nmix:ImageCreation/ImageProducer</td>
<td><cite><a href="#mix">MIX</a></cite></td>
</tr>
<tr>
<td>qt</td>
<td>Quicktime</td>
<td>qt:©dir</td>
<td><cite><a href="#quictime">QuickTime</a></cite></td>
</tr>
<tr>
<td>media</td>
<td>SearchMonkey Media</td>
<td>media:type</td>
<td><cite><a href="#mediamonkey">MediaMonkey</a></cite></td>
</tr>
<tr>
<td>dms</td>
<td>DMS-1</td>
<td>dms:Participant/Person</td>
<td><cite><a href="#dms">DMS-1</a></cite></td>
</tr>
<tr>
<td>tva</td>
<td>TV-Anytime</td>
<td>tva:CredistsList/CredistItem</td>
<td><cite><a href="#tvanytime">TV-Anytime</a></cite></td>
</tr>
<tr>
<td>txf</td>
<td>TXFeed</td>
<td>txf:author</td>
<td><cite><a href="#txfeed">TXFeed</a></cite></td>
</tr>
<tr>
<td>vra40</td>
<td>VRA Core 4.0</td>
<td>vra40:agent</td>
<td><cite><a href="#vra">VRA</a></cite></td>
</tr>
<tr>
<td>xmp</td>
<td>XMP</td>
<td>xmpDM:composer</td>
<td><cite><a href="#xmp">XMP</a></cite></td>
</tr>
<tr>
<td>yt</td>
<td>YouTube Data API Protocol</td>
<td>yt:author</td>
<td><cite><a href="#youtube-data-api">YouTube Data API
Protocol</a></cite></td>
</tr>
</tbody>
</table>
</div>
<div class="div2">
<h3><a name="formats-out-of-scope" id="formats-out-of-scope"></a>1.3 Formats
out of scope</h3>
<p>The following formats have been decided to be out of scope for this
specification.</p>
<ul>
<li><p><cite><a href="#mpeg21">MPEG-21</a></cite>: It is not media
description in narrower sense.</p>
</li>
</ul>
</div>
</div>
<div class="div1">
<h2><a name="Terminology" id="Terminology"></a>2 Terminology</h2>
<p><em>This section is normative.</em></p>
<dl>
<dt class="label">[<a name="media-resource" id="media-resource"
title="media resource">Definition</a>: <b>Media Resource</b>]</dt>
<dd><p>Any Resource (as defined by [<cite><a href="#rfc3986">RFC
3986</a></cite>]) related to a media content. Note that [<cite><a
href="#rfc3986">RFC 3986</a></cite>] points out that a resource may be
retrievable or not. Hence, this term encompasses the abstract notion of a
movie (e.g. Notting Hill) as well as the binary encoding of this movie
(e.g. the MPEG-4 encoding of Notting Hill on my DVD), or any intermediate
levels of abstraction (e.g. the director's cut or the plane version of
Notting Hill). Although some ontologies (<cite><a
href="#frbr">FRBR</a></cite>, <a
href="http://www.bbc.co.uk/ontologies/">BBC</a>) define concepts for
different such levels of abstraction, our ontology does not commit to any
classification of media resources.</p>
</dd>
<dt class="label">[<a name="property" id="property"
title="property">Definition</a>: <b>Property</b>]</dt>
<dd><p>A property is an element from an existing metadata format for
describing <a title="media resource" href="#media-resource">media
resources</a>, or an element from the core vocabulary defined in this
Working Group. For example, the <cite><a href="#dc">Dublin
Core</a></cite><em>creator</em> element and the Media Ontology
<em>creator</em> element are properties. A property links a <a
title="media resource" href="#media-resource">Media Resource</a> with a
value: <em>dc:creator</em> links a given resource with the value of its
creator (Dublin Core specifies: "Examples of a Creator include a person,
an organization, or a service."). The properties can have structured
and/or unstructured values. The set of properties selected to be part of
the Media Ontology Core vocabulary is listed in section <a
href="#property-definition"><b>4 Property definition</b></a>.</p>
</dd>
<dt class="label">[<a name="mapping" id="mapping"
title="mapping">Definition</a>: Mapping]</dt>
<dd><p>The notion of Mapping refers to the description of relations between
elements of metadata schemas; in our case the mapping concerns a subset
of the "in scope" Vocabularies, and the <a title="property"
href="#property">properties</a> of the core vocabulary of the Media
Ontology. These Mappings are presented in section <a
href="#property-mapping-table"><b>4.2 Property mapping table</b></a>.</p>
</dd>
<dt class="label">[<a name="property-value-types" id="property-value-types"
title="property value types">Definition</a>: Property value types]</dt>
<dd><p>Property value types are the types of values used in a <a
title="property" href="#property">property</a>. For example, the property
dc:creator can have either string or URI as value types. Property value
types are defined in sec. <a
href="#property-value-types-definitions"><b>3 Property value type
definitions</b></a>. They are relying mostly on XML Schema data types
[<cite><a href="#xmlschema2">XML Schema 2</a></cite>].</p>
</dd>
</dl>
</div>
<div class="div1">
<h2><a name="property-value-types-definitions"
id="property-value-types-definitions"></a>3 Property value type definitions</h2>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>Currently the data types are defined in terms of XML Schema, part 2. The
Working Group intends to check and potentially modify these definitions, to
ensure compatibility with the return types defined in <a
href="http://www.w3.org/TR/mediaont-api-1.0/">API for Media Resources
1.0</a>.</p>
</div>
<div class="div2">
<h3><a name="uri-value-type" id="uri-value-type"></a>3.1 URI</h3>
<p>URI "Uniform Resource Identifier" is defined in [<cite><a
href="#rfc3986">RFC 3986</a></cite>]. In this specification the term URI is
used since it is well known. However the term is used as meaning IRIs
"Internationalized Resource Identifiers (IRIs)" [<cite><a href="#rfc3987">RFC
3987</a></cite>], that is URIs which may contain non-escaped characters other
than ASCII. The data type is <a
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#anyURI">anyURI</a> .
</p>
</div>
<div class="div2">
<h3><a name="string-value-type" id="string-value-type"></a>3.2 String</h3>
<p>A <code>String</code> value is represented using the XML Schema <a
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#string">string</a>
data type.</p>
</div>
<div class="div2">
<h3><a name="integer-value-type" id="integer-value-type"></a>3.3 Integer</h3>
<p>A <code>Integer</code> value is represented using the XML Schema <a
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#integer">integer</a>
data type.</p>
</div>
<div class="div2">
<h3><a name="float-value-type" id="float-value-type"></a>3.4 Float</h3>
<p>A <code>Float</code> value is represented using the XML Schema <a
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#float">float</a> data
type.</p>
</div>
<div class="div2">
<h3><a name="date-value-type" id="date-value-type"></a>3.5 Date</h3>
<p>A <code>Date</code> value is represented using the XML Schema <a
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#dateTime">dateTime</a>
data type.</p>
</div>
</div>
<div class="div1">
<h2><a name="property-definition" id="property-definition"></a>4 Property
definition</h2>
<p><em>This section is normative.</em></p>
<div class="div2">
<h3><a name="core-property-definitions" id="core-property-definitions"></a>4.1
Core property definitions</h3>
<div class="div3">
<h4><a name="property-approach" id="property-approach"></a>4.1.1 Description of
the approach followed for the property definitions</h4>
<p>This list of core properties has been defined by making an initial set of
mapping propositions from the list of <a href="#formats-in-scope">vocabularies
in scope</a>. From this original mapping table, it has been checked which of
the properties were supported by most of the vocabularies, and which ones were
judged useful by WG resolution. A list of properties by a cross validation
between the member's opinion and the popularity of the properties across the
vocabularies has been selected in order to get some level of objectiveness.</p>
<p>The following information is available for each property:</p>
<ul>
<li><p>Rough description of purpose</p>
</li>
<li><p><a href="#property-value-types-definitions">Property value
types</a></p>
</li>
<li><p><a title="mapping" href="#mapping">Mappings</a> to existing formats</p>
</li>
</ul>
</div>
<div class="div3">
<h4><a name="core-property-lists" id="core-property-lists"></a>4.1.2 Core
properties</h4>
<table border="1" summary="Editorial note">
<tbody>
<tr>
<td align="left" valign="top" width="50%"><b>Editorial note</b></td>
<td align="right" valign="top" width="50%"> </td>
</tr>
<tr>
<td colspan="2" align="left" valign="top">This core list of properties is
neither closed, nor pretend to be exhaustive and that the group still
looks at rationale for including properties to be considered in the
final list of properties. The candidate additional properties taken
into account by the WG are summarized in <a
href="#candidate-additional-elements"><b>A Candidate Additional
Elements</b></a>. In addition this table will be elaborated for further
information.</td>
</tr>
</tbody>
</table>
<table border="1" width="100%">
<tbody>
<tr>
<td align="center">Name</td>
<td align="center">DataType</td>
<td align="center">Description</td>
</tr>
<tr>
<td colspan="3">Descriptive Properties (Core Set)</td>
</tr>
<tr>
<td colspan="3"><em>Identification</em></td>
</tr>
<tr>
<td>ma:identifier</td>
<td align="center">{ identifier:URI, type:String }</td>
<td>The URI identifying a resource, which can be either an abstract
concept (Hamlet) or a "Representation" (an instance or file accessible
at a given URL). See <a
href="http://www.w3.org/TR/2009/WD-media-frags-reqs-20090430/#uc4">use
case 4.4 of the Annotating Media Fragments Use Case document</a>.</td>
</tr>
<tr>
<td>ma:title</td>
<td align="center">{ title:String, type:String }</td>
<td>The title of the document, or the name given to the resource.</td>
</tr>
<tr>
<td>ma:language</td>
<td align="center">String([<cite><a href="#bcp47">BCP 47</a></cite>])</td>
<td>The language used in the resource. Recommended best practice is to
use a controlled vocabulary such as [<cite><a href="#bcp47">BCP
47</a></cite>].</td>
</tr>
<tr>
<td>ma:locator</td>
<td align="center">URI</td>
<td>The URI at which the resource can be accessed (e.g. a URL, or a DVB
URI).</td>
</tr>
<tr>
<td colspan="3"><em>Creation</em></td>
</tr>
<tr>
<td>ma:contributor</td>
<td align="center">{ identifier:URI|String, role:String }</td>
<td>A pair identifying the contributor and the nature of the
contribution. E.g.actor, cameraman, dirctor,singer, author, artist
(Note: subject see addition of contributor type).</td>
</tr>
<tr>
<td>ma:creator</td>
<td align="center">{ identifier:URI|String, role:String }</td>
<td>The authors of the resource (listed in order of precedence, if
significant).</td>
</tr>
<tr>
<td>ma:createDate</td>
<td align="center">{ date:Date, type:String }</td>
<td>The date and time the resource was originally created. (for
commercial purpose there might be an annotation of publication
date).</td>
</tr>
<tr>
<td>ma:location</td>
<td align="center">{ [name:String], [longitude:Float, latitude:Float,
altitude:Float], [geoLocation:String] }</td>
<td>A location where the resource has been shot/recorded.</td>
</tr>
<tr>
<td colspan="3"><em>Content description</em></td>
</tr>
<tr>
<td>ma:description</td>
<td align="center">String</td>
<td>A textual description of the content of the resource.</td>
</tr>
<tr>
<td>ma:keyword</td>
<td align="center">String</td>
<td>A descriptive phrase or keyword that specify the topic of the content
of the resource.</td>
</tr>
<tr>
<td>ma:genre</td>
<td align="center">String</td>
<td>The genre of the resource. Recommended best practice is to use a
controlled vocabulary such as the EBU vocabulary.</td>
</tr>
<tr>
<td>ma:rating</td>
<td align="center">{ identifier:URI, value:Float, max:Float, min:Float,
context:String }</td>
<td>A pair identifying the rating person or organization and the rating
(real value). The scale of the rating should be provided.</td>
</tr>
<tr>
<td colspan="3"><em>Relational</em></td>
</tr>
<tr>
<td>ma:relation</td>
<td align="center">{ identifier:URI, relation:String }</td>
<td>A pair identifying the resource and the nature of the realtionship.
E.g. transcript, original_work.</td>
</tr>
<tr>
<td>ma:collection</td>
<td align="center">URI|String</td>
<td>A name of the collection from which the resource originates or to
which it belongs.</td>
</tr>
<tr>
<td colspan="3"><em>Rights</em></td>
</tr>
<tr>
<td>ma:copyright</td>
<td align="center">{ copyright:String, identifier:URI }</td>
<td>The copyright statement. Identification of the copyrights holder
(Digital Right Management is out of scope for MAWG, see the [<cite><a
href="#pling">PLING</a></cite>] for more information on this
topic).</td>
</tr>
<tr>
<td>ma:policy</td>
<td align="center">{ policy:String, type:String, identifier:URI }</td>
<td>Description of the policy of the media resource or reference. see the
[<cite><a href="#pling">PLING</a></cite>] for more information on this
topic.</td>
</tr>
<tr>
<td colspan="3"><em>Distribution</em></td>
</tr>
<tr>
<td>ma:publisher</td>
<td align="center">URI|String</td>
<td>The publisher of a resource. Examples of a Publisher include a
person, an organization, or a service.</td>
</tr>
<tr>
<td>ma:targetAudience</td>
<td align="center">{ identifier:URI, classification:String }</td>
<td>A pair identifying the issuer of the classification (parental guide
and issuing agency, targeted geographical region) and the value given
in this classification.</td>
</tr>
<tr>
<td colspan="3"><em>Fragments</em></td>
</tr>
<tr>
<td>ma:fragments</td>
<td align="center">{ role:String, identifier:URI }</td>
<td>A list of pairs of fragment role and fragment identifier. Fragment
types can be spatial, temporal or tracks (e.g. chapters, favourite
scenes, subtitles).</td>
</tr>
<tr>
<td>ma:namedFragments</td>
<td align="center">{ label:String, identifier:URI }</td>
<td>The list of named fragments annotated for this resource (pairs of
label and fragment identifier).</td>
</tr>
<tr>
<td colspan="3">Technical Properties</td>
</tr>
<tr>
<td>ma:frameSize</td>
<td align="center">{ width:Float, height:Float }</td>
<td>The frame size. For example: w:720, h: 480. It is required to use a
pixel unit.</td>
</tr>
<tr>
<td>ma:compression</td>
<td align="center">String</td>
<td>The compression type used, e.g. H264. Note: it is possible to use
extended <cite><a href="#mime">MIME</a></cite> type as value for this
property, see [<cite><a href="#rfc4281">RFC 4281</a></cite>].</td>
</tr>
<tr>
<td>ma:duration</td>
<td align="center">Float</td>
<td>The actual duration of the resource. It is required to use a second
unit.</td>
</tr>
<tr>
<td>ma:format</td>
<td align="center">String</td>
<td><cite><a href="#mime">MIME</a></cite> type of the resource (wrapper,
bucket media types).</td>
</tr>
<tr>
<td>ma:samplingrate</td>
<td align="center">Float</td>
<td>Audio sampling rate. It is required to use a sample/second unit.</td>
</tr>
<tr>
<td>ma:framerate</td>
<td align="center">Float</td>
<td>Video frame rate. It is required to use a frame/second unit.</td>
</tr>
<tr>
<td>ma:bitrate</td>
<td align="center">Float</td>
<td>Average bit rate. It is required to use a kbps unit.</td>
</tr>
<tr>
<td>ma:numTracks</td>
<td align="center">Integer</td>
<td>Number of tracks.</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="div2">
<h3><a name="property-mapping-table" id="property-mapping-table"></a>4.2
Property mapping table</h3>
<div class="div3">
<h4><a name="rationale_mapping_table" id="rationale_mapping_table"></a>4.2.1
Rationale regarding the mapping table</h4>
<p>As a first step to build the Media ontology, a set of commonly supported
properties by the aforementioned vocabularies (metatdata schemas) has been
listed. This list, henceforth referred to as "the Media Ontology", is the basis
for vocabularies matching. Its namespace is "ma", for Media Annotation. We
provide a first set of mapping propositions between the Media Ontology and a
subset of vocabularies taken into account in this Working Group. These mappings
specify both the semantic and some elements of the syntactic correspondances
between the Media Ontology and the considered vocabularies' properties. </p>
<div class="div4">
<h5><a name="semantic-level-mappings" id="semantic-level-mappings"></a>4.2.1.1
Semantic Level Mappings</h5>
<p>The presented mappings are "one way" so far, i.e. the semantics is of a
relationship between one Media Ontology property and one or more property/ies
of considered vocabularies. For example, <em>ma:copyright</em> is mapped to
both <em>xmpDM:copyright</em> and <em>dc:rights</em> (as part of the XMP
standard [<cite><a href="#xmp">XMP</a></cite>]); the same property is mapped to
<em>exif:Copyright</em> (see [<cite><a href="#exif">EXIF</a></cite>]).
Unfortunately, no semantic relationship can be thereof inferred between the
properties in XMP and in EXIF. The mappings that have been taken into account
have different semantics: the properties of the different vocabularies can be:
</p>
<ul>
<li><p>Exact matches: the semantics of the two properties are equivalent in
most of the possible contexts. For example, <em>ma:title</em> matches
exactly <em>vra:title</em>.</p>
</li>
<li><p>More specific: the property of the vocabulary taken into account has a
semantic that takes into account only a subset of the possibilities
expressed by the property defined in this Working Group. For example in
<cite><a href="#dig35">DIG35</a></cite>, <em>ipr_names@description</em> and
<em>ipr_person@description</em> are more specific than the property
<em>ma:publisher</em> to which it is mapped.</p>
</li>
<li><p>More generic: the inverse of the above, the property of the vocabulary
taken into account has a semantic that is broader than the property defined
in this Working Group. For example, the <cite><a
href="#dig35">DIG35</a></cite><em>location</em> is more general than the
<em>ma:location</em>.</p>
</li>
<li><p>Related: the two properties are related in a way that is relevant for
some use cases, but this relation has no defined semantics. For example, in
<cite><a href="#mediarss">Media RSS</a></cite>, <em>media:credit</em> is
related to <em>ma:creator</em>.</p>
</li>
</ul>
<p>This list of relations between vocabularies (or informal mappings) and the
"Core Media Properties list" is published as a table; its purpose is to get
feedback from the communities that are currently using the different
vocabularies: the people or companies actually using the different vocabularies
could proof-read our interpretation of the vocabularies and comment on the
proposed mappings. </p>
</div>
<div class="div4">
<h5><a name="syntactic-level-mappings"
id="syntactic-level-mappings"></a>4.2.1.2 Syntactic Level Mappings</h5>
<p>Syntactic level mappings declare the correspondence between two semantically
equivalent properties but with a different syntactic expression. Its most
evident case is the date formatting, but some others may appear. </p>
<table border="1" summary="Editorial note">
<tbody>
<tr>
<td align="left" valign="top" width="50%"><b>Editorial note</b></td>
<td align="right" valign="top" width="50%"> </td>
</tr>
<tr>
<td colspan="2" align="left" valign="top">Currently the mapping table for
some of the formats does not contain information about syntactic
mapping, but this information will be added in the following
version.</td>
</tr>
</tbody>
</table>
</div>
<div class="div4">
<h5><a name="mapping-expression" id="mapping-expression"></a>4.2.1.3 Mapping
expression</h5>
<p>The mapping expression corresponds to the concrete implementation or
representation of the mappings defined in the previous paragraph, both at a
semantic level and at syntactic one. </p>
<p><a href="http://www.w3.org/TR/2009/CR-skos-reference-20090317/">SKOS</a>
(acronym for Simple Knowledge Organization System) is currently a
Recommendation of the W3C Semantic Web activity that defines a vocabulary for
representing Knowledge Organization Systems (i.e. vocabularies) and
relationships amongst them. In <a
href="http://www.w3.org/TR/2009/CR-skos-reference-20090317/">SKOS</a> the
mapping properties that we take into account in the mapping table are expressed
as: <em>skos:exactMatch</em>, <em>skos:narrowMatch</em>,
<em>skos:broadMatch</em> and <em>skos:relatedMatch</em>. Some more fine grained
definition of the properties has still to be done: we need to define their
formal properties (if they are symmetric, etc) to enhance more efficient
concrete mappings. The mappings have to be as precise as possible to be
efficiently used in the related API. </p>
</div>
</div>
<div class="div3">
<h4><a name="mapping-table" id="mapping-table"></a>4.2.2 The mapping table</h4>
<p>The following mappings are established from the Media Ontology's core
properties to various multimedia metadata formats. This list of formats is not
closed, nor pretends to be exhaustive. The group still looks at rationale for
including and excluding formats to be considered in the final mapping table;</p>
<ol>
<li><p><a href="XMP.html">XMP</a></p>
</li>
<li><p><a href="ID3.html">ID3</a></p>
</li>
<li><p><a href="iTunes.html">iTunes</a></p>
</li>
<li><p><a href="Quicktime.html">QT</a></p>
</li>
<li><p><a href="SearchMonkey.html">SearchMonkey</a></p>
</li>
<li><p><a href="MediaRDF.html">MediaRDF</a></p>
</li>
<li><p><a href="LOM.html">LOM</a></p>
</li>
<li><p><a href="METS.html">METS</a></p>
</li>
<li><p><a href="EXIF.html">EXIF</a></p>
</li>
<li><p><a href="CableLabs1.html">CableLabs 1.1</a></p>
</li>
<li><p><a href="CableLabs2.html">CableLabs 2.0</a></p>
</li>
<li><p><a href="DIG.html">DIG35</a></p>
</li>
<li><p><a href="MIX.html">MIX</a></p>
</li>
<li><p><a href="FRBR.html">FRBR</a></p>
</li>
<li><p><a href="MediaRSS.html">MediaRSS</a></p>
</li>
<li><p><a href="TXFeed.html">TXFeed</a></p>
</li>
<li><p><a href="YouTube.html">YouTube</a></p>
</li>
<li><p><a href="VRA.html">VRA</a></p>
</li>
<li><p><a href="IPTC.html">IPTC</a></p>
</li>
<li><p><a href="TVA.html">TVA</a></p>
</li>
<li><p><a href="EBUCore.html">EBUCore</a></p>
</li>
<li><p><a href="EBUP.html">EBUP</a></p>
</li>
<li><p><a href="MPEG7.html">MPEG7</a></p>
</li>
<li><p><a href="SMTPD.html">SMTPD</a></p>
</li>
</ol>
</div>
</div>
</div>
</div>
<div class="back">
<div class="div1">
<h2><a name="candidate-additional-elements"
id="candidate-additional-elements"></a>A Candidate Additional Elements</h2>
<p>Below table shows the considered candidates for extending the core
properties. In addtion, concerning to addtional information of candidate
additional elements, see the <a
href="http://www.w3.org/2008/WebVideo/Annotations/wiki/Candidate_Additional_Elements">wiki
page</a> of the MA WG.</p>
<table border="1" width="100%">
<tbody>
<tr>
<td align="center">Name</td>
<td align="center">Description</td>
</tr>
<tr>
<td colspan="2">Descriptive Properties (Core Set)</td>
</tr>
<tr>
<td>Accessibility metadata</td>
<td>This is concerned to annotative material for accessibility. E.g. link
to transcript, what 'axes' the media can be adapted -- such as closed
captions, audio description of video, video contrast.</td>
</tr>
<tr>
<td>Fictional character</td>
<td>Specify fictional character impersonated by a contributor with role
"actor". This is supported in the metadata set of the Timed Text WG.
</td>
</tr>
<tr>
<td colspan="2">Technical Properties</td>
</tr>
<tr>
<td>Media types</td>
<td>Media types for which certain technical properties are relevant. If
necessary, this could evolve into media specific profiles.</td>
</tr>
</tbody>
</table>
</div>
<div class="div1">
<h2><a name="references" id="references"></a>B References (Normative)</h2>
<dl>
<dt class="label"><a name="bcp47"></a>[BCP 47] </dt>
<dd><a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt"><cite>BCP 47
(Tags for Identifying Languages)</cite></a>, A. Phillips and M. Davis,
Editors. Available at http://www.rfc-editor.org/rfc/bcp/bcp47.txt. </dd>
<dt class="label"><a name="cablelabs1"></a>[Cablelabs 1.1] </dt>
<dd><a
href="http://www.cablelabs.com/specifications/MD-SP-VOD-CONTENT1.1-I05-060831.pdf"><cite>CableLabs
VOD Content Specification Version 1.1</cite></a>. Available at
http://www.cablelabs.com/specifications/MD-SP-VOD-CONTENT1.1-I05-060831.pdf
. </dd>
<dt class="label"><a name="cablelabs2"></a>[Cablelabs 2.0] </dt>
<dd><a
href="http://www.cablelabs.com/specifications/MD-SP-VOD-CONTENT2.0-I02-070105.pdf"><cite>CableLabs
VOD Content Specification Version 2.0</cite></a>. Available at
http://www.cablelabs.com/specifications/MD-SP-VOD-CONTENT2.0-I02-070105.pdf
. </dd>
<dt class="label"><a name="dig35"></a>[DIG35] </dt>
<dd><a
href="http://www.bgbm.org/TDWG/acc/Documents/DIG35-v1.1WD-010416.pdf"><cite>DIG35
Specification - Metadata for Digital Image</cite></a>. April 2001.
Available at
http://www.bgbm.org/TDWG/acc/Documents/DIG35-v1.1WD-010416.pdf . </dd>
<dt class="label"><a name="dms"></a>[DMS-1] </dt>
<dd><a href="http://www.smpte.org/standards"><cite>DMS-1</cite></a> (SMPTE
380M-2004). April 2001. Available at http://www.smpte.org/standards .
</dd>
<dt class="label"><a name="dc"></a>[Dublin Core] </dt>
<dd><a
href="http://dublincore.org/documents/2008/01/14/dcmi-terms/"><cite>DCMI
Metadata Terms</cite></a>. January 2008. Available at
http://dublincore.org/documents/2008/01/14/dcmi-terms/ . The <a
href="http://dublincore.org/documents/dcmi-terms/">latest version of DCMI
Metadata Terms</a> is available at
http://dublincore.org/documents/dcmi-terms/ . </dd>
<dt class="label"><a name="ebucore"></a>[EBUCore] </dt>
<dd><a href="http://tech.ebu.ch/docs/tech/tech3293-2008.pdf"><cite>EBUCore
v.1.0</cite></a>. December 2008. Available at
http://tech.ebu.ch/docs/tech/tech3293-2008.pdf . </dd>
<dt class="label"><a name="ebup"></a>[EBU P-META] </dt>
<dd><a href="http://tech.ebu.ch/docs/tech/tech3295v2.pdf"><cite>EBU P-META
2.0 Metadata Library</cite></a>. July 2007. Available at
http://tech.ebu.ch/docs/tech/tech3295v2.pdf . </dd>
<dt class="label"><a name="exif"></a>[EXIF] </dt>
<dd><a href="http://www.exif.org/Exif2-2.PDF"><cite>EXIF 2.2</cite></a>.
Specification by <a href="http://www.jeita.or.jp/">JEITA</a>, April 2002.
Available at http://www.exif.org/Exif2-2.PDF . </dd>
<dt class="label"><a name="frbr"></a>[FRBR] </dt>
<dd><a href="http://vocab.org/"><cite>A URI space for
vocabularies</cite></a>. October 2005. Available at http://vocab.org/ .
</dd>
<dt class="label"><a name="lom"></a>[LOM] </dt>
<dd><a
href="http://ltsc.ieee.org/wg12/files/LOM_1484_12_1_v1_Final_Draft.pdf"><cite>Draft
Standard for Learning Object Metadata</cite></a>. July 2002. Available at
http://ltsc.ieee.org/wg12/files/LOM_1484_12_1_v1_Final_Draft.pdf . </dd>
<dt class="label"><a name="mix"></a>[MIX] </dt>
<dd><a href="http://www.loc.gov/standards/mix/"><cite>MIX 1.0</cite></a>.
Available at http://www.loc.gov/standards/mix/ . </dd>
<dt class="label"><a name="id3"></a>[ID3] </dt>
<dd><a href="http://www.id3.org/Developer_Information"><cite>ID3 tag
version 2.4.0</cite></a>. February 1999. Available at
http://www.id3.org/Developer_Information . </dd>
<dt class="label"><a name="iptc"></a>[IPTC] </dt>
<dd><a
href="http://www.iptc.org/std/photometadata/2008/specification/IPTC-PhotoMetadata-2008.pdf"><cite>IPTC
Standard Photo Metadata 2008</cite></a>. IPTC Core Specification Version
1.1, IPTC Extension Specification Version 1.0, Document Revision 2, June
2008. Available at
http://www.iptc.org/std/photometadata/2008/specification/IPTC-PhotoMetadata-2008.pdf
</dd>
<dt class="label"><a name="newsml"></a>[IPTC NewsML] </dt>
<dd><a href="http://www.iptc.org/cms/site/"><cite>IPTC
NewsML-G2</cite></a>. Available at http://www.iptc.org/cms/site/ . </dd>
<dt class="label"><a name="itunes"></a>[iTunes] </dt>
<dd><a href="http://connect.apple.com/"><cite>iTunes Metadata
Specification</cite></a>. Available at http://connect.apple.com/ . </dd>
<dt class="label"><a name="mediamonkey"></a>[MediaMonkey] </dt>
<dd><a
href="http://developer.yahoo.com/searchmonkey/smguide/searchmonkey-media-details.html"><cite>MediaMonkey
Media</cite></a>. Available at
http://developer.yahoo.com/searchmonkey/smguide/searchmonkey-media-details.html
. </dd>
<dt class="label"><a name="mets"></a>[METS] </dt>
<dd><a href="http://www.loc.gov/standards/mets/"><cite>Metadata Encoding
& Transmission Standard 1.7</cite></a>. Available at
http://www.loc.gov/standards/mets/ . </dd>
<dt class="label"><a name="mediardf"></a>[Media RDF] </dt>
<dd><a href="http://digitalbazaar.com/media/video"><cite>Media
RDF</cite></a>. Available at http://digitalbazaar.com/media/video . </dd>
<dt class="label"><a name="mediarss"></a>[Media RSS] </dt>
<dd><a href="http://video.search.yahoo.com/mrss"><cite>Yahoo! Media RSS
Module - RSS 2.0 Module</cite></a>. March 2008. Available at
http://video.search.yahoo.com/mrss . </dd>
<dt class="label"><a name="mime"></a>[MIME] </dt>
<dd>Freed, N., Borenstein, N. <a
href="http://www.ietf.org/rfc/rfc2046.txt"><cite>Multipurpose Internet
Mail Extensions (MIME) Part Two: Media Types</cite></a>. November 1996.
Available at http://www.ietf.org/rfc/rfc2046.txt . </dd>
<dt class="label"><a name="mpeg7"></a>[MPEG-7] </dt>
<dd><a
href="http://www.chiariglione.org/mpeg/working_documents/mpeg-07/schema_def/cd.zip"><cite>Information
technology — Multimedia content description interface — Part 10:
Schema definition</cite></a>. Available at
http://www.chiariglione.org/mpeg/working_documents/mpeg-07/schema_def/cd.zip
. </dd>
<dt class="label"><a name="pling"></a>[PLING] </dt>
<dd><a href="http://www.w3.org/Policy/pling/wiki/Main_Page"><cite>PLING W3C
Open Forum</cite></a> The W3C Policy Languages Interest Group - PLING -
is an open forum to discuss use cases, languages, and frameworks around
information governance policies. </dd>
<dt class="label"><a name="quictime"></a>[QuickTime] </dt>
<dd><a
href="http://developer.apple.com/mac/library/documentation/QuickTime/QTFF/QTFFPreface/qtffPreface.html"><cite>Introduction
to QuickTime File Format Specification</cite></a>. September 2007.
Available at
http://developer.apple.com/mac/library/documentation/QuickTime/QTFF/QTFFPreface/qtffPreface.html
. </dd>
<dt class="label"><a name="rfc3986"></a>[RFC 3986] </dt>
<dd>Berners-Lee, T., R. Fielding, L. Masinter. <a
href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource
Identifier (URI): Generic Syntax</cite></a>. RFC 3986, January 2005.
Available at http://www.ietf.org/rfc/rfc3986.txt </dd>
<dt class="label"><a name="rfc3987"></a>[RFC 3987] </dt>
<dd>Dürst, M. and M. Suignard. <a
href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized
Resource Identifiers (IRIs)</cite></a>. RFC 3987, January 2005. Available
at http://www.ietf.org/rfc/rfc3987.txt. </dd>
<dt class="label"><a name="rfc4281"></a>[RFC 4281] </dt>
<dd>Gellens, R., Singer, D., and P. Frojdh. <a
href="http://www.ietf.org/rfc/rfc4281.txt"><cite>The Codecs Parameter for
"Bucket" Media Types</cite></a>. RFC 4281, November 2005. Available at
http://www.ietf.org/rfc/rfc4281.txt. </dd>
<dt class="label"><a name="smpte"></a>[SMPTE] </dt>
<dd><a
href="http://www.smpte-ra.org/mdd/RP210v11-pub-20080415.2048.xls"><cite>SMPTE
Metadata</cite></a>. Available at
http://www.smpte-ra.org/mdd/RP210v11-pub-20080415.2048.xls . </dd>
<dt class="label"><a name="txfeed"></a>[TXFeed] </dt>
<dd><a
href="http://clearerchannel.org/docs/tx_metadata_standard_0_9.pdf"><cite>TXFeed
standard 0.9</cite></a>. December 2007. Available at
http://clearerchannel.org/docs/tx_metadata_standard_0_9.pdf . </dd>
<dt class="label"><a name="tvanytime"></a>[TV-Anytime] </dt>
<dd><cite>ETSI 102 822-3-1 V1.4.1</cite>. November 2007. Broadcast and
On-line Services: Search, select, and rightful use of content on personal
storage systems("TV-Anytime"). Part 3: Metadata, Sub-part 1: Phase 1 -
Metadata schemas . </dd>
<dt class="label"><a name="vra"></a>[VRA] </dt>
<dd><a href="http://www.vraweb.org/projects/vracore4/index.html"><cite>VRA
Core 4.0</cite></a>. Available at
http://www.vraweb.org/projects/vracore4/index.html . </dd>
<dt class="label"><a name="xmlschema2"></a>[XML Schema 2] </dt>
<dd>Biron, P. V. and A. Malhotra. <a
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"><cite>XML
Schema Part 2: Datatypes Second Edition</cite></a>. W3C Recommendation,
October 2004. Available at
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/ . The <a
href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
Part 2</a> is available at http://www.w3.org/TR/xmlschema-2/ . </dd>
<dt class="label"><a name="xmp"></a>[XMP] </dt>
<dd><a
href="http://www.adobe.com/devnet/xmp/pdfs/XMPSpecificationPart2.pdf"><cite>XMP
Specification Part 2 - Standard Schemas</cite></a>. Adobe, 2008.
Available at
http://www.adobe.com/devnet/xmp/pdfs/XMPSpecificationPart2.pdf . </dd>
<dt class="label"><a name="youtube-data-api"></a>[YouTube Data API Protocol]
</dt>
<dd><a
href="http://code.google.com/intl/en/apis/youtube/2.0/reference.html"><cite>YouTube
Data API Protocol</cite></a>. April 2008. Available at
http://code.google.com/intl/en/apis/youtube/2.0/reference.html .</dd>
</dl>
</div>
<div class="div1">
<h2><a name="idinform-div1122323192" id="idinform-div1122323192"></a>C
References (Non-Normative)</h2>
<dl>
<dt class="label"><a name="html5"></a>[HTML 5] </dt>
<dd>Hickson, I., and D. Hyatt. <a
href="http://www.w3.org/TR/2008/WD-html5-20080610/"><cite>HTML 5. A
vocabulary and associated APIs for HTML and XHTML</cite></a>. W3C Working
Draft, June 2008. Available at
http://www.w3.org/TR/2008/WD-html5-20080610/ . The <a
href="http://www.w3.org/TR/html5/">latest version of HTML 5</a> is
available at http://www.w3.org/TR/html5/ . </dd>
<dt class="label"><a name="mpeg21"></a>[MPEG-21] </dt>
<dd><a
href="http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=30819"><cite>ISO/IEC
TR 21000-1:2001 - Information technology -- Multimedia framework
(MPEG-21) -- Part 1: Vision, Technologies and Strategy</cite></a>.
Available at
http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=30819
. </dd>
<dt class="label"><a name="mwg_guidance_image"></a>[MWG Guidelines Image]
</dt>
<dd><a href=""><cite>Guidelines for handling image metadata, version
1.0.</cite></a>. Metadata Working Group, September 2008. Available at
http://www.metadataworkinggroup.com/pdf/mwg_guidance.pdf . </dd>
<dt class="label"><a name="rfc2119"></a>[RFC 2119] </dt>
<dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>RFC 2119: Key words
for use in RFCs to Indicate Requirement Levels</cite></a>. Internet
Engineering Task Force, 1997. </dd>
<dt class="label"><a name="rfc4646"></a>[RFC 4646] </dt>
<dd>Phillips, A., Ed. and M. Davis, Ed. <a
href="http://www.rfc-editor.org/rfc/rfc4646.txt"><cite>Tags for
Identifying Languages</cite></a>. RFC 4646, September 2006. Available at
http://www.rfc-editor.org/rfc/rfc4646.txt. </dd>
</dl>
</div>
<div class="div1">
<h2><a name="acknowledgments" id="acknowledgments"></a>D Acknowledgements
(Non-Normative)</h2>
<p>This document is the work of the <a
href="http://www.w3.org/2008/WebVideo/Annotations/">W3C Media Annotations
Working Group</a>.</p>
<p>Members of the Working Group are (at the time of writing, and by
alphabetical order): Werner Bailer (JOANNEUM RESEARCH), Tobias Bürger
(University of Innsbruck), Eric Carlson (Apple, Inc.), Pierre-Antoine Champin
((public) Invited expert), Ashish Chawla ((public) Invited expert), Jaime
Delgado (Universitat Politècnica de Catalunya), Jean-Pierre EVAIN ((public)
Invited expert), Philip Jägenstedt (Opera Software), Ralf Klamma ((public)
Invited expert), WonSuk Lee (Electronics and Telecommunications Research
Institute (ETRI)), Véronique Malaisé (Vrije Universiteit), Erik Mannens
(IBBT), Hui Miao (Samsung Electronics Co., Ltd.), Thierry Michel (W3C/ERCIM),
Frank Nack (University of Amsterdam), Soohong Daniel Park (Samsung Electronics
Co., Ltd.), Silvia Pfeiffer (W3C Invited Experts), Chris Poppe (IBBT), Víctor
Rodríguez (Universitat Politècnica de Catalunya), Felix Sasaki (Potsdam
University of Applied Sciences), David Singer (Apple, Inc.), Florian Stegmaier
((public) Invited expert), John Strassner ((public) Invited expert), Joakim
Söderberg (ERICSSON), Thai Wey Then (Apple, Inc.), Ruben Tous (Universitat
Politècnica de Catalunya), Raphaël Troncy (CWI), Vassilis Tzouvaras
(K-Space), Davy Van Deursen (IBBT). </p>
<p>The people who have contributed to <a
href="http://lists.w3.org/Archives/Public/public-media-annotation/">discussions
on public-media-annotation@w3.org</a> are also gratefully acknowledged. </p>
</div>
</div>
</body>
</html>