-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathindex.html
3561 lines (3427 loc) · 137 KB
/
index.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
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
<!DOCTYPE html>
<html lang="en">
<head>
<title>DataCite to DCAT-AP Mapping</title>
<meta charset="utf-8"/>
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<!--
<script class="remove" src="./respec-ec-common.js"></script>
<script class="remove" src="respec-w3c-common.js"></script>
<script class="remove" src="https://www.w3.org/Tools/respec/respec-w3c-common"></script>
-->
<script class="remove" src="https://www.w3.org/Tools/respec/respec-w3c"></script>
<script class="remove" src="./config.js"></script>
<style>
table {width:100%;}
table {font-size:small;}
.disclaimer {font-size:.9em;}
.disclaimer:before {content:"\2605\00a0 Disclaimer: ";font-weight:bold;}
/*
table code, table pre {
overflow-wrap: break-word;
word-wrap: break-word;
word-break: break-all;
}
*/
.code {
margin: 1em auto;
padding: .5em;
border: .5em;
border-left-style: solid;
page-break-inside: avoid;
border-color: #52E052;
background: #E9FBE9;
overflow: auto;
}
</style>
</head>
<body>
<!--
<article>
-->
<!--
<header>
<h1>DataCite to DCAT-AP Mapping</h1>
</header>
-->
<p class="copyright"><a href="https://europa.eu/european-union/abouteuropa/legal_notices_en#copyright-notice">Copyright</a> © 2015-2021 <a href="https://europa.eu/">European Union</a>. This document is licensed under a <a rel="license" href="https://creativecommons.org/licenses/by/4.0/" class="subfoot">Creative Commons Attribution 4.0 License</a>.</p>
<aside id="disclaimer" class="disclaimer">
The views expressed are purely those of the author and may not in any circumstances be regarded as stating an official position of the European Commission.
</aside>
<section id="abstract" class="notoc introductory">
<h2>Abstract</h2>
<p>This document describes the background and methodology for the design of the DataCite profile of DCAT-AP (CiteDCAT-AP), as well as the defined mappings and RDF vocabulary.</p>
<aside class="ednote">
<p>This document is a draft meant to report work in progress concerning an exercise, carried out at the <a href="https://ec.europa.eu/jrc/">Joint Research Centre of the European Commission</a> (Units B.6 & G.I.4), for the alignment of DataCite metadata with DCAT-AP.</p>
<p>As such, it can be updated any time and it must be considered as unstable.</p>
<p>Comments and queries should be sent via <a href="https://github.com/ec-jrc/datacite-to-dcat-ap/issues/">the issue tracker of the dedicated GitHub repository</a>.</p>
</aside>
</section>
<!--
<section id="disclaimer" class="notoc introductory">
<h2>Disclaimer</h2>
<p>The views expressed are purely those of the author and may not in any circumstances be regarded as stating an official position of the European Commission.</p>
</section>
-->
<section id="sotd" class="notoc introductory">
<!--
<h2>Status of this document</h2>
-->
</section>
<nav id="toc">
<!--
<h2>Table of contents</h2>
<ul>
<li><a href="#background">Background</a>
<ul>
<li><a href="#background-dcat-ap">The <em>DCAT Application Profile for Data Portals in Europe</em> (DCAT-AP)</a></li>
<li><a href="#background-datacite">DataCite</a></li>
<li><a href="#background-why">Aligning DataCite with DCAT-AP</a></li>
</ul>
</li>
<li><a href="#methodology">Methodology</a></li>
<li><a href="#comparison-with-dc2ap-and-datacite2rdf">Comparison with DC2AP & DataCite2RDF</a></li>
<li><a href="#comparison">DataCite and DCAT-AP at a glance</a>
<ul>
<li><a href="#comparison-datacite-vs-dcat-ap">DataCite metadata elements supported in DCAT-AP</a></li>
<li><a href="#comparison-dcat-ap-vs-datacite">DCAT-AP classes and properties supported in DataCite</a></li>
</ul>
</li>
<li><a href="#alignment-issues">Summary of alignment issues</a>
-->
<!--
<li><a href="#methodology">Methodology</a></li>
-->
<!--
<li><a href="#used-namespaces">Used namespaces</a></li>
<li><a href="#ref-code-lists">Reference code lists for metadata elements</a></li>
<li><a href="#mapping-summary">Mapping summary</a>
<ul>
<li><a href="#mapping-1st-level">1st-level mappings</a></li>
<li><a href="#mapping-2nd-level">2nd-level mappings</a></li>
<li><a href="#mapping-identifiers">Identifiers</a></li>
</ul>
</li>
-->
<!--
<li><a href="#mapping-individual">Mappings of individual metadata elements</a>
<ul>
<li><a href="#mapping-geo-id">Geographic identifier</a></li>
<li><a href="#mapping-bbox">Geographic bounding box</a></li>
<li><a href="#mapping-spatial-resolution">Spatial resolution</a></li>
<li><a href="#mapping-conformance-result">Conformance result / Conformity (Data quality)</a></li>
<li><a href="#mapping-responsible-party">Responsible party</a></li>
<li><a href="#mapping-crs">Coordinate reference system</a></li>
<li><a href="#mapping-format">Format / Encoding</a></li>
<li><a href="#">...</a></li>
</ul>
</li>
-->
<!--
</ul>
-->
</nav>
<section id="introduction" class="informative">
<h2>Introduction</h2>
<p>This document describes the background and methodology for the design of the DataCite profile of DCAT-AP (CiteDCAT-AP), as well as the defined mappings.</p>
<p>The motivation for investigating the possiblity of aligning DataCite metadata with DCAT-AP is twofold:</p>
<ol>
<li>To identify how to create a DCAT-AP-compliant representation of DataCite metadata, in order to enable their sharing across DCAT-AP-enabled data catalogues. This analysis is not meant to provide a complete representation of all DataCite metadata elements, but only of those included in DCAT-AP.</li>
<li>To identify how to create a DataCite-compliant representation of DCAT-AP metadata, in order to enable their publishing on the DataCite infrastructure. This analysis is meant to develop an extension of DCAT-AP, covering all DataCite metadata elements.</li>
</ol>
<p>The following sections first illustrate the background (<a class="no-sectionRef" href="#background"></a>) and the methodology (<a class="no-sectionRef" href="#methodology"></a>) for the design of CiteDCAT-AP, followed by an analysis of related work (<a class="no-sectionRef" href="#comparison-with-dc2ap-and-datacite2rdf"></a>). Then, a high level overview of the metadata elements supported in DCAT-AP and DataCite is provided (<a class="no-sectionRef" href="#comparison"></a>), along with a summary of mapping issues (<a class="no-sectionRef" href="#alignment-issues"></a>).</p>
<p>The defined mappings are introduced in <a class="no-sectionRef" href="#mapping-summary"></a>, and grouped as follows:</p>
<ul>
<li>1st-level DataCite metadata elements (<a class="no-sectionRef" href="#mapping-1st-level"></a>)</li>
<li>2nd-level DataCite metadata elements (<a class="no-sectionRef" href="#mapping-2nd-level"></a>)</li>
<li>Identifiers used in DataCite records (<a class="no-sectionRef" href="#mapping-identifiers"></a>)</li>
</ul>
<p>The terms (classes and properties) defined in the CiteDCAT-AP namespace and the XSLT-based implementation of the defined mappings is included in appendix (<a class="no-sectionRef" href="#formal-definition-rdf"></a> and <a class="no-sectionRef" href="#formal-definition-xslt"></a>, respectively).</p>
<!--
<ul>
<li>... (<a class="no-sectionRef" href="#background"></a>)</li>
<li>... (<a class="no-sectionRef" href="#methodology"></a>)</li>
<li>... (<a class="no-sectionRef" href="#comparison-with-dc2ap-and-datacite2rdf"></a>)</li>
<li>... (<a class="no-sectionRef" href="#comparison"></a>)</li>
<li>... (<a class="no-sectionRef" href="#alignment-issues"></a>)</li>
<li>... (<a class="no-sectionRef" href="#mapping-summary"></a>)</li>
</ul>
-->
</section>
<section id="background" class="informative">
<h2>Background</h2>
<section id="background-dcat-ap">
<h3>The <em>DCAT Application Profile for Data Portals in Europe</em> (DCAT-AP)</h3>
<p>DCAT-AP [[DCAT-AP]] is a metadata profile developed in the framework of the EU Programme <a href="http://ec.europa.eu/isa/"><em>Interoperability Solutions for European Public Administrations</em></a> (ISA), and based on and compliant with the W3C Data Catalog vocabulary (DCAT) [[VOCAB-DCAT]] - currently, one of the most widely used Semantic Web vocabularies for describing datasets and data catalogues.</p>
<p>The purpose of DCAT-AP is to define a common interchange metadata format for data portals of the EU and of EU Member States. In order to achieve this, DCAT-AP defines a set of classes and properties, grouped into mandatory, recommended and optional. Such classes and properties correspond to information on datasets and data catalogues that are shared by many European data portals, aiding interoperability. Although DCAT-AP is designed to be independent from its actual implementation, RDF [[RDF-CONCEPTS]] and Linked Data [[LD-BOOK]] are the reference technologies.</p>
</section>
<section id="background-datacite">
<h3>DataCite</h3>
<p><a href="https://www.datacite.org/">DataCite</a> is an international initiative meant to enable citation for scientific datasets. To achieve this, DataCite operates a metadata infrastructure, following the same approach used by <a href="https://www.crossref.org/">CrossRef</a> for scientific publications. As such, the DataCite infrastructure is responsible for issuing persistent identifiers (in particular, <abbr title="Digital Object Identifier">DOI</abbr>s) for datasets, and for registering dataset metadata. Such metadata are to be provided according to the DataCite metadata schema [[DataCite]] - which is basically an extension to the DOI one.</p>
<p>Currently, DataCite is the de facto standard for data citation. Therefore, the ability to transform metadata records from and to the DataCite metadata schema would enable, respectively, the harvesting of DataCite records, and the publication of metadata records in the DataCite infrastructure (thus enabling their citation).</p>
</section>
<section id="background-why">
<h3>Aligning DataCite with DCAT-AP</h3>
<p>The motivation for investigating the possiblity of aligning DataCite metadata with DCAT-AP is twofold:</p>
<ol>
<li>To identify how to create a DCAT-AP-compliant representation of DataCite metadata, in order to enable their sharing across DCAT-AP-enabled data catalogues. This analysis is not meant to provide a complete representation of all DataCite metadata elements, but only of those included in DCAT-AP.</li>
<li>To identify how to create a DataCite-compliant representation of DCAT-AP metadata, in order to enable their publishing on the DataCite infrastructure. This analysis is meant to develop an extension of DCAT-AP, covering all DataCite metadata elements.</li>
</ol>
<p>About point (2), the DataCite-based extension of DCAT-AP is also meant to integrate into DCAT-AP all the information required for data citation.</p>
<p>Based on these considerations, two versions of a DataCite profile of DCAT-AP have been defined, namely, CiteDCAT-AP Core (addressing the requirements of point (1)) and CiteDCAT-AP Extended (addressing the requirements of point (2)). More precisely, the core version includes alignments only for the subset of DataCite metadata elements included in the DCAT-AP specification, whereas the extended version tries to defines alignments for all the DataCite metadata elements using DCAT-AP and other Semantic Web vocabularies (whenever DCAT-AP does not offer suitable candidates). As such, CiteDCAT-AP Extended is a superset of CiteDCAT-AP Core, and both are conformant with DCAT-AP.</p>
</section>
</section>
<section id="methodology">
<h2>Methodology</h2>
<p>The reference DCAT-AP and DataCite specifications on which CiteDCAT-AP is based are the following ones:</p>
<ul>
<li>DCAT 2 (<time datetime="2020-02-04">February 2020</time>) [[VOCAB-DCAT-2]]</li>
<li>DCAT-AP 2.0.1 (<time datetime="2020-06-08">June 2020</time>) [[DCAT-AP-20200608]]</li>
<li>GeoDCAT-AP 2.0.0 (<time datetime="2020-12-23">December 2020</time>) [[GeoDCAT-AP-20201223]]</li>
<li>StatDCAT-AP 1.0.1 (<time datetime="2019-05-28">May 2019</time>) [[StatDCAT-AP-20190528]]</li>
<li>DataCite 4.4 (<time datetime="2021-03-30">March 2021</time>) [[DataCite-20210330]]</li>
</ul>
<p>
<p>For the mappings, existing work has been taken into account concerning the mapping of DataCite to other metadata standards. In particular:</p>
<ul>
<!--
<li>The DataCite to Dublin Core mappings defined in <a href="https://schema.datacite.org/meta/kernel-2.2/">version 2.2 of the DataCite metadata schema specification</a> (July 2011)</li>
<li>The RDF bindings defined in the <a href="https://docs.google.com/document/d/1paJgvmCMu3pbM4in6PjWAKO0gP-6ultii3DWQslygq4/edit">DataCite2RDF mapping document</a> (April 2011)</li>
-->
<li>The DataCite to Dublin Core mappings recommended in [[DataCite-20210330]]</li>
<li>DataCite Dublin Core Application Profile (DC2AP). Version 1.8 (February 2016) [[?DC2AP]]</li>
<li>DataCite2RDF: Mapping DataCite Metadata Schema 3.1 Terms to RDF. Version 3.3 (February 2016) [[?DataCite2RDF]]</li>
</ul>
<p>CiteDCAT-AP builds upon these specifications to provide an as much as possible complete mapping of all the metadata elements in version 4.4 of the DataCite metadata schema [[DataCite-20210330]]. Moreover, the defined mappings are backward compatible with earlier versions of the DataCite metadata schema.</p>
<p>The resulting mappings have been grouped into two classes, corresponding to two different CiteDCAT-AP profiles:</p>
<ul>
<li><strong>CiteDCAT-AP Core</strong>: This profile defines alignments for the subset of DataCite metadata elements supported by DCAT-AP.</li>
<li><strong>CiteDCAT-AP Extended</strong>: This profile defines alignments for all the DataCite metadata elements using DCAT-AP and other Semantic Web vocabularies (whenever DCAT-AP does not provide suitable candidates).</li>
</ul>
<p>As far as the extended profile is concerned, the reference vocabularies have been chosen based on the following criteria:</p>
<ol>
<li>They have clear persistence and versioning policies.</li>
<li>Preferably, they should be used across domains and data communities.</li>
</ol>
<p>These criteria are determining the main differences with the mappings defined in [[?DC2AP]] and [[?DataCite2RDF]], that are illustrated in the following section.</p>
</section>
<section id="comparison-with-dc2ap-and-datacite2rdf" class="informative">
<h2>Comparison with DC2AP & DataCite2RDF</h2>
<p>[[DC2AP]] and [[DataCite2RDF]] provide a full mapping of version 3.1 of the DataCite metadata schema. To achieve this, they re-use a number of vocabularies, that can be grouped into two main classes:</p>
<ol>
<li>General purpose and widely used vocabularies, such as Dublin Core, FOAF, GeoSPARQL, and SKOS.</li>
<li>A set of vocabularies developed specifically to model the publishing and academic domains. They include PRISM (<em>Publishing Requirements for Industry Standard Metadata</em>) [[PRISM]] and FRBR (<em>Functional Requirements for Bibliographic Records</em>) [[FRBR]], plus a set of ontologies developed in the framework of the <a href="http://www.sparontologies.net/">SPAR</a> (<em>Semantic Publishing and Referencing Ontologies</em>) project.</li>
</ol>
<p>The current version of CiteDCAT-AP follows the mappings based on the former group of vocabularies, but not the ones based on the latter group. The reason is twofold. First, the persistence and versioning policies of these vocabularies are unclear, and so it has been considered safer to re-consider their use when CiteDCAT-AP is more consolidated. Second, the mappings defined in [[DC2AP]] and [[DataCite2RDF]] are not compliant with the general requirements of DCAT-AP. For instance, despite the resource types defined in DataCite include datasets and metadata records, neither [[DC2AP]] nor [[DataCite2RDF]] make use of DCAT.</p>
<p>It is worth noting that the second group of ontologies, and in particular the ones developed in the SPAR project, provide interesting solutions to modelling some aspects not explicitly addressed in DCAT-AP - e.g., the possibility of associating a temporal dimension to agent roles - but also alternative solutions for specifying the same information - one of the examples being resource identifiers. Complementing and aligning the different approaches would be mutually beneficial.</p>
</section>
<section id="comparison" class="informative">
<h2>DataCite and DCAT-AP at a glance</h2>
<p>The following sections provide a high-level comparison of the metadata elements defined in DataCite and DCAT-AP.</p>
<section id="comparison-datacite-vs-dcat-ap">
<h3>DataCite metadata elements supported in DCAT-AP</h3>
<p>The following table provides the complete list of DataCite metadata elements, and shows whether they are supported in DCAT-AP.</p>
<p>For each of the DataCite metadata elements, the table specifies whether they are mandatory (<strong><abbr title="mandatory">M</abbr></strong>), recommended (<em><abbr title="recommended">R</abbr></em>), or optional (<abbr title="optional">O</abbr>).</p>
<table class="simple">
<thead>
<tr>
<th colspan="2">DataCite</th>
<th rowspan="2">DCAT-AP</th>
<th rowspan="2">Comments</th>
</tr>
<tr>
<th>Elements</th>
<th>Obligation</th>
</tr>
</thead>
<tbody>
<tr>
<td>Identifier</td>
<td><strong>M</strong></td>
<td><em>Partially</em></td>
<td>DataCite <strong>requires</strong> this to be a DOI, whereas DCAT-AP does not have such requirement</td>
</tr>
<tr>
<td>Creator</td>
<td><strong>M</strong></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Title</td>
<td><strong>M</strong></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Publisher</td>
<td><strong>M</strong></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Publication year</td>
<td><strong>M</strong></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Subject</td>
<td><em>R</em></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Contributor</td>
<td><em>R</em></td>
<td><em>Partially</em></td>
<td>
<p>DCAT-AP supports only 1 out of the 21 DataCite contributor types (namely, contact point / person).</p>
<p>GeoDCAT-AP supports 1 additional DataCite contributor type, namely, rights holder, plus a set of roles from [[?ISO-19115]].</p>
</td>
</tr>
<tr>
<td>Date</td>
<td><em>R</em></td>
<td><em>Partially</em></td>
<td>
<p>DCAT-AP supports only 2 out of the 9 DataCite date types (namely, issue date and last modified date)</p>
<p>GeoDCAT-AP supports also an additional date type, namely, creation date.</p>
</td>
</tr>
<tr>
<td>Resource type</td>
<td><em>R</em></td>
<td><em>Partially</em></td>
<td>
<p>DCAT-AP supports 2 resource types, namely, <code>dcat:Dataset</code> and <code>dcat:DataService</code>. All DataCite resource types fall under the definition of <code>dcat:Dataset</code>, with the exception of event, physical object, and service (<code>dcat:DataService</code> has a more specific semantics compared with the service resource type in DataCite).</p>
</td>
</tr>
<tr>
<td>Related identifier</td>
<td><em>R</em></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Description</td>
<td><em>R</em></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Geolocation</td>
<td><em>R</em></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Language</td>
<td>O</td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Alternate identifier</td>
<td>O</td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Size</td>
<td>O</td>
<td>Yes</td>
<td>In DCAT-AP, this is a property of the dataset distribution, and not of the dataset itself</td>
</tr>
<tr>
<td>Format</td>
<td>O</td>
<td>Yes</td>
<td>In DCAT-AP, this is a property of the dataset distribution, and not of the dataset itself</td>
</tr>
<tr>
<td>Version</td>
<td>O</td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Rights</td>
<td>O</td>
<td>Yes</td>
<td>
<p>DataCite does not use specific elements for use conditions (i.e., licences) and access rights, </p>
<p>In DCAT-AP, use conditions are a property of the dataset distribution, whereas access rights are associated with the dataset.</p>
</td>
</tr>
<tr>
<td>Funding Reference</td>
<td>O</td>
<td><strong>No</strong></td>
<td>This element specifies: (a) title, identifier and, possibly, URI of the funding project, and (b) name and identifier of the organisation who awarded that project</td>
</tr>
</tbody>
</table>
</section>
<section id="comparison-dcat-ap-vs-datacite">
<h3>DCAT-AP classes and properties supported in DataCite</h3>
<p>The following table provides the list of classes and properties defined in DCAT-AP, and shows whether they are supported in DataCite.</p>
<p><strong>NB</strong>: The list of DCAT-AP classes and properties is here limited to those that are either mandatory (<strong>M</strong>) or recommended (<em>R</em>).</p>
<table class="simple">
<thead>
<tr>
<th colspan="4">DCAT-AP</th>
<th rowspan="2">DataCite</th>
<th rowspan="2">Comments</th>
</tr>
<tr>
<th>Classes</th>
<th>Obligation</th>
<th>Properties</th>
<th>Obligation</th>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="2">Agent</td>
<td rowspan="2"><strong>M</strong></td>
<td>name</td>
<td><strong>M</strong></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>type</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td rowspan="11">Catalogue</td>
<td rowspan="11"><strong>M</strong></td>
<td>dataset</td>
<td><strong>M</strong></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>description</td>
<td><strong>M</strong></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>publisher</td>
<td><strong>M</strong></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>title</td>
<td><strong>M</strong></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>homepage</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>language</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>licence</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>release date</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>themes</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>spatial / geographic coverage</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>update / modification date</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td rowspan="7">Dataset</td>
<td rowspan="7"><strong>M</strong></td>
<td>description</td>
<td><strong>M</strong></td>
<td>Yes</td>
<td>In DataCite, this property is recommended, not mandatory</td>
</tr>
<tr>
<td>title</td>
<td><strong>M</strong></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>contact point</td>
<td><em>R</em></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>dataset distribution</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>keyword / tag</td>
<td><em>R</em></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>publisher</td>
<td><em>R</em></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>spatial / geographic coverage</td>
<td><em>R</em></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>temporal coverage</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>theme / category</td>
<td><em>R</em></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Category</td>
<td><em>R</em></td>
<td>preferred label</td>
<td><strong>M</strong></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td>Category scheme</td>
<td><em>R</em></td>
<td>title</td>
<td><strong>M</strong></td>
<td>Yes</td>
<td></td>
</tr>
<tr>
<td rowspan="5">Distribution</td>
<td rowspan="5"><em>R</em></td>
<td>accessURL</td>
<td><strong>M</strong></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>availability</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>description</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
<tr>
<td>format</td>
<td><em>R</em></td>
<td>Yes</td>
<td>In DataCite, this is always a property of the resource itself - even when such resource is a dataset</td>
</tr>
<tr>
<td>licence</td>
<td><em>R</em></td>
<td>Yes</td>
<td>In DataCite, this is always a property of the resource itself - even when such resource is a dataset</td>
</tr>
<tr>
<td>Licence document</td>
<td><em>R</em></td>
<td>type</td>
<td><em>R</em></td>
<td><strong>No</strong></td>
<td></td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="alignment-issues" class="informative">
<h2>Summary of alignment issues</h2>
<!--
<p>As shown in the previous section, DCAT-AP is able to represent all DataCite mandatory elements, with the exception of "creator". This poses an issue for the possible use of DCAT-AP for data citation purposes, since element "creator" is one of the required components. Notably, GeoDCAT-AP supports this agent role, so it can re-used for this purpose.</p>
-->
<p>As shown in the previous section, DCAT-AP is able to represent all DataCite mandatory elements.</p>
<p>On the other hand, DataCite includes all the DCAT-AP mandatory classes and related properties, with the only notable exception of <code>dcat:Catalog</code>. However, this does not pose particular compliance issues, since the catalogue description could be obtained separately from the relevant DataCite records. Actually, since DataCite records are supposed to be all available via the DataCite catalogue, the catalogue description can potentially be the same for all DataCite records. Of course, this does not apply for those records following the DataCite schema but not registered in the DataCite infrastructure.</p>
<p>There are however some key differences on the DCAT-AP and DataCite data models that needs to be addressed. The following sections outline the solutions adopted in CiteDCAT-AP, as well as open issues.</p>
<section id="alignment-issues-resource-types">
<h3>Resource types</h3>
<!-- For DataCite v4.3
<p>DataCite supports 15 different resource types - namely: audiovisual, collection, data paper, dataset, event, image, interactive resource, model, physical object, service, software, sound, text, workflow, other. They basically corresponds to the classes included in the DCMI Type vocabulary [[DCTERMS]], with the exception of data paper, model, and workflow.</p>
-->
<!-- For DataCite v4.4 -->
<p>DataCite supports 28 different resource types, 12 of which correspond to the classes included in the DCMI Type vocabulary [[DCTERMS]].</p>
<!-- -->
<p>The definition of <code>dcat:Dataset</code> is broad enough to cover most of the DataCite resource types, the exceptions being event, physical object, service, which are not supported in DCAT-AP (class <code>dcat:DataService</code> is semantically more specific than service DataCite resource type). For these resource types, it is possible to re-use the DCMI Type vocabulary, which includes classes for event (<a href="http://dublincore.org/documents/dcmi-terms/#http://purl.org/dc/dcmitype/Event"><code>dctype:Event</code></a>), physical object (<a href="http://dublincore.org/documents/dcmi-terms/#http://purl.org/dc/dcmitype/PhysicalObject"><code>dctype:PhysicalObject</code></a>), and service (<a href="http://dublincore.org/documents/dcmi-terms/#http://purl.org/dc/dcmitype/Service"><code>dctype:Service</code></a>). Moreover, for compliance with [[VOCAB-DCAT-2]], they are also typed as <a data-cite="VOCAB-DCAT-2#Class:Resource"><code>dcat:Resource</code></a>'s.</p>
<p>CiteDCAT-AP re-uses the approach outlined above. Moreover, in order to preserve the original information, it uses <code>dct:type</code> with the relevant classes of the DCMI Type vocabulary to denote the DataCite resource type.</p>
<!--
<p>As said above, the DCMI Type vocabulary does not include classes for data paper, model, and workflow, and no suitable candidates have been found in the reference vocabularies. As a result, in CiteDCAT-AP are both modelled only as <code>dcat:Dataset</code>'s, thus loosing the original information.</p>
-->
<p>As said above, the DCMI Type vocabulary does not include classes for data paper, model, and workflow, and no suitable candidates have been found in the reference vocabularies. In order to address this issue, CiteDCAT-AP defines specific classes for these resource types (<a href="#DataPaper"><code>citedcat:DataPaper</code></a>, <a href="#Model"><code>citedcat:Model</code></a>, <a href="#Workflow"><code>citedcat:Workflow</code></a>), which are specified in metadata records by using property <code>dct:type</code> (see <a class="no-sectionRef" href="#classes"></a>).</p>
</section>
<section id="alignment-issues-identifiers">
<h3>Identifiers</h3>
<p>The requirements are basically the following ones:</p>
<ul>
<li>DataCite requires the dataset identifier to be a DOI.</li>
<li>DataCite distinguishes between primary and secondary identifiers.</li>
<li>DataCite describes the "type" of identifier (DOIs, <abbr title="Open Research and Contributor Identifier">ORCID</abbr>s, <abbr title="International Standard Name Identifier">ISNI</abbr>s, <abbr title="International Standard Serial Identifier">ISSN</abbr>s, etc.).</li>
</ul>
<p>DCAT-AP already provides a mechanism to specify primary and secondary identifiers, as well as the identifier type. More precisely:</p>
<ul>
<li>Property <a href="http://purl.org/dc/terms/#http://purl.org/dc/terms/identifier"><code>dct:identifier</code></a> is used to specify primary identifiers.</li>
<li>Property <a href="https://www.w3.org/TR/vocab-adms/#adms-identifier"><code>adms:identifier</code></a> is used to specify secondary/alternative identifiers.</li>
<li>Class <a href="https://www.w3.org/TR/vocab-adms/#identifier"><code>adms:Identifier</code></a> allows the specification of information about the identifier - identifier scheme included.</li>
</ul>
<p>Such solutions are basically reflecting the DataCite approach to specify identifiers. However, identifiers specified in this way are of no use for effectively linking the relevant resources. For this purpose, an option would be encoding identifiers as HTTP URIs, whenever possible. This is the case, e.g., for ORCIDs, ISNIs, and DOIs. About the ability to specifying differently primary and secondary/alternative identifiers, the resource URI can denote the primary identifier, whereas URIs corresponding to alternative identifiers can be specified by using <a href="https://www.w3.org/TR/owl-ref/#sameAs-def"><code>owl:sameAs</code></a>.</p>
<p>Based on what said above, CiteDCAT-AP specifies identifiers as follows:</p>
<ul>
<li>Identifiers are encoded as HTTP URIs, whenever possible, or URNs, using <code>owl:sameAs</code> for URIs concerning secondary/alternative identifiers.</li>
<li>In addition:
<ul>
<li>Primary identifiers are specified, as literals, with <code>dct:identifier</code>.</li>
<li>Secondary/alternative identifiers are specified, as literals, with <code>adms:identifier</code>.</li>
</ul>
</li>
</ul>
</section>
<section id="alignment-issues-related-resource">
<h3>Related resource</h3>
<p>DataCite supports the possibility of specifying references to resources related to the described in the metadata record via element RelatedIdentifier, carrying an optional attribute that can be used to express the related resource type.</p>
<p>Roughly half of the supported related resource "types" (34, in total) correspond to the ones defined in Dublin Core. Moreover, with the exception of types "IsIdenticalTo" and "IsPublishedIn", they denote a relationship (e.g., "IsReferencedBy") and its inverse (e.g., "References").</p>
<p>Based on this CiteDCAT-AP specifies this information as follows:</p>
<ul>
<li>The default mapping of element RelatedIdentifier is <code>dct:relation</code></li>
<li>Dublin Core [[DCTERMS]] is used for all the relevant related resource types (i.e., 11, excluding <code>dct:relation</code>)</li>
<li>4 are specified by using FOAF [[FOAF]]</li>
<!-- DEPRECATED
<li>3 are specified by using Schema.org [[SCHEMA-ORG]]</li>
-->
<li>3 are specified by using the BIBO Ontology [[BIBO]]</li>
<li>3 are specified by using the W3C PROV Ontology [[PROV-O]]</li>
<li>1 ("IsIdenticalTo") is specified by using OWL (<code>owl:sameAs</code>) [[OWL-REF]].</li>
<!--
<li>1 ("IsSourceOf") is specified by using the W3C PROV Ontology [[PROV-O]] (<code>prov:hadDerivation</code>).</li>
-->
<li>1 ("IsDescribedBy") is specified by using the W3C POWDER-S Vocabulary [[POWDER-S]] (<code>wdrs:describedby</code>).</li>
<!--
<li>11 are left unmapped, since the reference vocabularies do not provide suitable candidates</li>
-->
<li>The remaining 10 are defined in the CiteDCAT-AP namespace, since the reference vocabularies do not provide suitable candidates (see <a class="no-sectionRef" href="#object-properties"></a>).</li>
</ul>
<p>DCAT-AP supports 7 of the mapped related resource types. All the other ones are supported only in the extended profile of CiteDCAT-AP.</p>
</section>
<section id="alignment-issues-agent-roles">
<h3>Agent roles</h3>
<p>DataCite supports three main types of agent roles, namely, creator, publisher, and contributor. The last can be further specialised by specifying a contributor "type". DataCite supports 22 contributor types, including, e.g., "contact person", "editor", "funder", "producer", "rights holder", "sponsor", "other".</p>
<p>DCAT-AP supports only three agent roles, namely, creator, publisher and contact point (corresponding to contributor type "contact person" in DataCite). GeoDCAT-AP includes another one of the DataCite agent roles - namely, rights holder - plus a set of agent roles defined in [[?ISO-19115]], whose semantics is not aligned with DataCite.</p>
<p>As a result, together, DCAT-AP and GeoDCAT-AP cover publisher, creator, and 2 contributor types, namely, contact point and rights holder. For the other ones, CiteDCAT-AP includes the following mappings:</p>
<ul>
<li><a href="http://purl.org/dc/terms/#http://purl.org/dc/terms/contributor"><code>dct:contributor</code></a> is used when the contributor is untyped, or when the contributor type is "other".</li>
<!-- DEPRECATED
<li><a href="http://schema.org/editor"><code>schema:editor</code></a>, <a href="http://schema.org/funder"><code>schema:funder</code></a>, <a href="http://schema.org/producer"><code>schema:producer</code></a>, and <a href="http://schema.org/sponsor"><code>schema:sponsor</code></a> are used for the corresponding DataCite contributor types.</li>
<li><a href="https://www.w3.org/TR/vocab-duv/#Property:hasDistributor"><code>duv:hasDistributor</code></a> is used for the corresponding DataCite contributor type.</li>
-->
<li><a href="http://purl.org/ontology/bibo/distributor"><code>bibo:distributor</code></a>, <a href="http://purl.org/ontology/bibo/editor"><code>bibo:editor</code></a>, and <a href="http://purl.org/ontology/bibo/producer"><code>bibo:producer</code></a> are used for the corresponding DataCite contributor types.</li>
<li>For the remaining ones, specific properties are defined in the CiteDCAT-AP namespace, since the reference vocabularies do not provide suitable candidate (see <a class="no-sectionRef" href="#object-properties"></a>).</li>
</ul>
<p>It is worth noting that some of the DataCite contributor types cannot be specified with a direct relationship. This is the case of roles "project leader", "project manager", "project member", "researcher", "supervisor", and "workpackage leader". Such roles are not directly describing the relationship between a resource and an agent, but rather the role of the individual in the "activity" that created the resource. E.g., "project leader" can be described as "the leader of the project that created the resource".</p>
<p>In such cases, the approach used in CiteDCAT-AP is as follows:</p>
<ul>
<li>The resource is linked to the agent (<code>foaf:Agent</code>) with property <code>dct:contributor</code>.</li>
<li>The agent is linked to the activity (<code>prov:Activity</code>) with a property denoting the role played.</li>
<li>The activity is linked to the resource with property <code>prov:wasGeneratedBy</code>.</li>
</ul>
<p>In case of roles "project leader", "project manager", and "project member", the activity is additionally typed as a <code>foaf:Project</code>.</p>
<p>The following code snippet shows how contributor type "project member" is specified in CiteDCAT-AP:</p>
<aside id="ex-project-member" class="example" title="Project member">
<pre>
a:Dataset a dcat:Dataset ;
dct:contributor a:Contributor ;
prov:wasGeneratedBy a:Project .
a:Contributor a foaf:Agent .
a:Project a prov:Activity , foaf:Project ;
citedcat:projectMember a:Contributor .
</pre>
</aside>
<!--
<p>The issue is that the reference vocabularies does not provide candidates for specifying such contributor types, with the exception of "project member".</p>
<p>For the remaining 14 DataCite contributor types, no candidates have been found in the reference vocabularies, so they are left unmapped in CiteDCAT-AP.</p>
-->
</section>
<section id="alignment-issues-distributions">
<h3>Distributions</h3>
<p>The DataCite data model does not distinguish between a dataset and its embodiment(s) ("distribution(s)", in the DCAT terminology).</p>
<p>As a consequence, attributes that in DCAT/DCAT-AP are specific to distributions (as format, licence, size), in DataCite are associated with the dataset. Moreover, in DataCite there is no attribute equivalent to <code>dcat:accessURL</code> or <code>dcat:downloadURL</code>. Actually, the only information that can be used to access the dataset, and, possibly, its distribution(s), is the resource DOI.</p>
<p>Based on this, the approach used in CiteDCAT-AP to map DataCite records is as follows:</p>
<ol>
<li>If the described resource is an event, physical object, or service (i.e., if it cannot be typed as a dataset), the notion of "distribution" does not apply. Therefore, all DataCite elements are used in CiteDCAT-AP to describe the resource. Otherwise:</li>
<li>Each record is described in CiteDCAT-AP as a dataset (<code>dcat:Dataset</code>), having exactly 1 distribution.</li>
<li>The resulting distribution gets the relevant DataCite elements (as format, licence, size), as per the DCAT/DCAT-AP schema, whereas the remaining ones are used to describe the dataset.</li>
<li>The dataset DOI is used both as the dataset identifier / URI and as the distribution access URL.</li>
</ol>
</section>
<section id="alignment-issues-use-and-access-conditions">
<h3>Use and access conditions</h3>
<p>DataCite includes a single element, namely, "rights", to specify use and access conditions. This element is also supported in DCAT-AP (<code>dct:rights</code>), but, in addition, specific properties are used for use conditions (<code>dct:license</code>) and access rights (<code>dct:accessRights</code>). Moreover, in DCAT-AP use conditions are associated with distributions, whereas access rights with datasets.</p>
<p>Based on this, CiteDCAT-AP maps by default DataCite "rights" to <code>dct:rights</code>. In addition, they are mapped to <code>dct:license</code> and <code>dct:accessRights</code> when DataCite rights make explicit reference to some known licences and access rights vocabularies. More precisely, the recognised vocabularies are the following ones:</p>
<ul>
<li>For licences:
<ul>
<li><a href="https://creativecommons.org/">Creative Commons licences</a></li>
<li>The licence code list maintained by the Publications Office of the EU [[EUV-LICENCES]]</li>
</ul>
</li>
<li>For access rights:
<ul>
<li>EU-Repo access rights vocabulary [[EU-REPO-AR]]</li>
<li>ePrints access rights vocabulary [[EPRINTS-AR]]</li>
<li>The access rights code list maintained by the Publications Office of the EU [[EUV-AR]]</li>
</ul>
</li>
</ul>
</section>
<section id="alignment-issues-keywords-and-controlled-vocabularies">
<h3>Keywords and controlled vocabularies</h3>
<p>DataCite supports the specification of both free-text keywords and keywords from controlled vocabularies.</p>
<p>For the latter case, DCAT-AP recommends the use of URIs, but in DataCite only textual labels are used.</p>
<p>To comply with the DCAT-AP recommendation, an option is to implement mappings from textual labels to URIs. However, this poses two main issues:</p>
<ol>
<li>DataCite does not require / recommend the use of specific vocabularies, nor a particular format for the textual labels.</li>
<li>It is often the case that no URIs are available for the used vocabularies.</li>
</ol>
<p>Such situation makes it difficult the effective implementation of vocabulary mapping.</p>
<p>For this reason, CiteDCAT-AP preserves keywords from controlled vocabularies as textual labels, unless attribute @valueURI is specified, or the textual label is a URI.</p>
</section>
</section>
<section id="mapping-summary">
<h2>Mapping summary</h2>
<p>The following section summarises the alignments defined in CiteDCAT-AP.</p>
<p>The alignments are grouped as follows:</p>
<ul>
<li>Alignments for 1st-level DataCite metadata elements (<a class="no-sectionRef" href="#mapping-1st-level"></a>)</li>
<li>Alignments for 2nd-level DataCite metadata elements (<a class="no-sectionRef" href="#mapping-2nd-level"></a>)</li>
<li>Alignments for identifiers used in DataCite records (<a class="no-sectionRef" href="#mapping-identifiers"></a>)</li>
</ul>
<p>The alignments supported only in the extended profile of CiteDCAT-AP are in <strong>bold</strong>.</p>
<section id="used-namespaces">
<h2>Used namespaces</h2>
<table class="simple">
<thead>
<tr>
<th>Prefix</th>
<th>Namespace URI</th>
<th>Schema & documentation</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>adms</code></td>
<td><a href="http://www.w3.org/ns/adms#"><code>http://www.w3.org/ns/adms#</code></a></td>
<td>[[VOCAB-ADMS]]</td>
</tr>
<tr>
<td><code>bibo</code></td>
<td><a href="http://purl.org/ontology/bibo/"><code>http://purl.org/ontology/bibo/</code></a></td>
<td>[[BIBO]]</td>
</tr>
<td><code>citedcat</code></td>
<td><a href="https://w3id.org/citedcat-ap/"><code>https://w3id.org/citedcat-ap/</code></a></td>
<td>CiteDCAT-AP</td>
</tr>
<!--
<tr>
<td><code>cnt</code></td>
<td><a href="http://www.w3.org/2011/content#"><code>http://www.w3.org/2011/content#</code></a></td>
<td>[[Content-in-RDF]]</td>
</tr>
<tr>
<td><code>dc</code></td>
<td><a href="http://purl.org/dc/elements/1.1/"><code>http://purl.org/dc/elements/1.1/</code></a></td>
<td>[[DC11]]</td>
</tr>
-->
<tr>
<td><code>dcat</code></td>
<td><a href="http://www.w3.org/ns/dcat#"><code>http://www.w3.org/ns/dcat#</code></a></td>
<td>[[?VOCAB-DCAT]]</td>
</tr>
<tr>
<td><code>dct</code></td>
<td><a href="http://purl.org/dc/terms/"><code>http://purl.org/dc/terms/</code></a></td>
<td>[[DCTERMS]]</td>
</tr>
<tr>
<td><code>dctype</code></td>
<td><a href="http://purl.org/dc/dcmitype/"><code>http://purl.org/dc/dcmitype/</code></a></td>
<td>[[DCTERMS]]</td>
</tr>
<!--
<tr>
<td><code>duv</code></td>
<td><a href="http://www.w3.org/ns/duv#"><code>http://www.w3.org/ns/duv#</code></a></td>
<td>[[VOCAB-DUV]]</td>
</tr>
-->
<!--
<tr>
<td><code>earl</code></td>
<td><a href="http://www.w3.org/ns/earl#"><code>http://www.w3.org/ns/earl#</code></a></td>
<td>[[EARL10]]</td>
</tr>
-->
<tr>
<td><code>foaf</code></td>
<td><a href="http://xmlns.com/foaf/0.1/"><code>http://xmlns.com/foaf/0.1/</code></a></td>
<td>[[FOAF]]</td>
</tr>
<!--
<tr>
<td><code>frapo</code></td>
<td><a href="http://purl.org/cerif/frapo/"><code>http://purl.org/cerif/frapo/</code></a></td>
<td>[[FRAPO]]</td>
</tr>
<tr>
<td><code>geo</code></td>
<td><a href="http://www.w3.org/2003/01/geo/wgs84_pos#"><code>http://www.w3.org/2003/01/geo/wgs84_pos#</code></a></td>
<td>[[W3C-BASIC-GEO]]</td>
</tr>
-->
<tr>
<td><code>gsp</code></td>
<td><a href="http://www.opengis.net/ont/geosparql#"><code>http://www.opengis.net/ont/geosparql#</code></a></td>
<td>[[GeoSPARQL]]</td>
</tr>
<tr>
<td><code>locn</code></td>
<td><a href="http://www.w3.org/ns/locn#"><code>http://www.w3.org/ns/locn#</code></a></td>
<td>[[LOCN]]</td>
</tr>
<tr>
<td><code>org</code></td>
<td><a href="http://www.w3.org/ns/org#"><code>http://www.w3.org/ns/org#</code></a></td>
<td>[[VOCAB-ORG]]</td>
</tr>
<tr>
<td><code>owl</code></td>
<td><a href="http://www.w3.org/2002/07/owl#"><code>http://www.w3.org/2002/07/owl#</code></a></td>
<td>[[OWL-REF]]</td>
</tr>
<tr>
<td><code>prov</code></td>
<td><a href="http://www.w3.org/ns/prov#"><code>http://www.w3.org/ns/prov#</code></a></td>
<td>[[PROV-O]]</td>
</tr>
<tr>
<td><code>rdf</code></td>
<td><a href="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></a></td>
<td>[[RDF-CONCEPTS]]</td>
</tr>
<tr>
<td><code>rdfs</code></td>
<td><a href="http://www.w3.org/2000/01/rdf-schema#"><code>http://www.w3.org/2000/01/rdf-schema#</code></a></td>
<td>[[RDF-SCHEMA]]</td>
</tr>
<!--
<tr>
<td><code>schema</code></td>
<td><a href="http://schema.org/"><code>http://schema.org/</code></a></td>
<td>[[SCHEMA-ORG]]</td>
</tr>
-->
<tr>
<td><code>skos</code></td>
<td><a href="http://www.w3.org/2004/02/skos/core#"><code>http://www.w3.org/2004/02/skos/core#</code></a></td>
<td>[[SKOS-REFERENCE]]</td>
</tr>
<tr>
<td><code>vcard</code></td>
<td><a href="http://www.w3.org/2006/vcard/ns#"><code>http://www.w3.org/2006/vcard/ns#</code></a></td>
<td>[[vCARD-RDF]]</td>
</tr>
<tr>
<td><code>xsd</code></td>
<td><a href="http://www.w3.org/2001/XMLSchema"><code>http://www.w3.org/2001/XMLSchema#</code></a></td>
<td>[[XMLSCHEMA11-2]]</td>
</tr>
<tr>
<td><code>wdrs</code></td>
<td><a href="https://www.w3.org/2007/05/powder-s"><code>https://www.w3.org/2007/05/powder-s#</code></a></td>
<td>[[POWDER-S]]</td>
</tr>
</tbody>
</table>
</section>
<section id="ref-code-lists">
<h2>Reference code lists for metadata elements</h2>
<!--