-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathgeodcat-ap_version_1.0_1.rst
4709 lines (4194 loc) · 674 KB
/
geodcat-ap_version_1.0_1.rst
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
Version 1.0
Document Metadata
+--------------+--------------------------------------------------------------------------------------------------------------------------------+
| Date | 2015-12-23 |
+--------------+--------------------------------------------------------------------------------------------------------------------------------+
| Status | Final (amended: 2016-04-08) |
+--------------+--------------------------------------------------------------------------------------------------------------------------------+
| Version | 1.0 |
+--------------+--------------------------------------------------------------------------------------------------------------------------------+
| Access URL | https://joinup.ec.europa.eu/node/148281 |
+--------------+--------------------------------------------------------------------------------------------------------------------------------+
| Rights | © 2015 European Union |
+--------------+--------------------------------------------------------------------------------------------------------------------------------+
| Licence | ISA Open Metadata Licence v1.1, retrievable from https://joinup.ec.europa.eu/category/licence/isa-open-metadata-licence-v11. |
+--------------+--------------------------------------------------------------------------------------------------------------------------------+
**Disclaimer:**
This specification was prepared for the ISA Programme by: PwC EU
Services.
The views expressed in this specification are purely those of the
authors and may not, in any circumstances, be interpreted as stating an
official position of the European Commission.
The European Commission does not guarantee the accuracy of the
information included in this study, nor does it accept any
responsibility for any use thereof.
Reference herein to any specific products, specifications, process, or
service by trade name, trademark, manufacturer, or otherwise, does not
necessarily constitute or imply its endorsement, recommendation, or
favouring by the European Commission.
All care has been taken by the author to ensure that s/he has obtained,
where necessary, permission to use any parts of manuscripts including
illustrations, maps, and graphs, on which intellectual property rights
already exist from the titular holder(s) of such rights or from her/his
or their legal representative.
**Note on this document (2016-04-08)**
This version of the GeoDCAT-AP 1.0 has been amended with respect to the
original one in order to correct a typo concerning the URIs of the code
lists of the INSPIRE Registry.
No other changes have been done on the original specification
**
**
Table of contents
`1 Introduction 7 <#_Toc447881017>`__
`1.1 Objectives 7 <#_Toc447881018>`__
`1.2 Structure of this document 8 <#_Toc447881019>`__
`2 Related standards and work 9 <#_Toc447881020>`__
`2.1 ISO 19115:2003, ISO 19139 and ISO 19115-1:2014
9 <#_Toc447881021>`__
`2.2 OGC Catalog Service for the Web 9 <#_Toc447881022>`__
`2.3 INSPIRE Metadata Regulation and INSPIRE Metadata Technical
Guidelines 9 <#_Toc447881023>`__
`2.4 DCAT and DCAT-AP 10 <#_Toc447881024>`__
`2.5 Alignment of INSPIRE metadata with Dublin Core
10 <#_Toc447881025>`__
`2.6 Alignment of INSPIRE metadata with DCAT-AP 10 <#_Toc447881026>`__
`2.7 Alignment of EuroVoc – GEMET – INSPIRE themes
11 <#_Toc447881027>`__
`2.8 GeoDCAT-AP XSLT script and API 11 <#_Toc447881028>`__
`3 Motivation and use cases 12 <#motivation-and-use-cases>`__
`4 Methodology and summary of results 13 <#_Toc447881030>`__
`4.1 Alignment criteria and requirements
13 <#alignment-criteria-and-requirements>`__
`4.2 Metadata elements to be covered by GeoDCAT-AP
13 <#_Toc447881032>`__
`4.3 Alignments defined in GeoDCAT-AP 14 <#_Toc447881033>`__
`5 RDF syntax bindings for INSPIRE and ISO 19115 metadata elements
16 <#_Toc447881034>`__
`5.1 Used namespaces 16 <#_Toc447881035>`__
`5.2 Overview of bindings for GeoDCAT-AP Core
18 <#overview-of-bindings-for-geodcat-ap-core>`__
`5.3 Overview of bindings for GeoDCAT-AP Extended
23 <#overview-of-bindings-for-geodcat-ap-extended>`__
`6 Controlled vocabularies 27 <#_Toc447881038>`__
`Acknowledgements 31 <#_Toc447881039>`__
`References 35 <#references>`__
`Annex I Overview of metadata elements covered by GeoDCAT-AP
39 <#_Toc447881041>`__
`Annex II Detailed usage notes and examples 42 <#_Toc447881042>`__
`II.1 Resource title - \*Dataset title 42 <#_Toc447881043>`__
`II.2 Resource abstract - \*Abstract describing the dataset
42 <#_Toc447881044>`__
`II.3 Resource type - \*not in ISO 19115 core 43 <#_Toc447881045>`__
`II.4 Resource locator - \*On-line resource 45 <#_Toc447881046>`__
`II.5 Unique resource identifier - \*not in ISO 19115 core
47 <#_Toc447881047>`__
`II.6 Coupled resource - \*not in ISO 19115 core 49 <#_Toc447881048>`__
`II.7 Resource language and metadata language - \*Dataset language and
Metadata language 50 <#_Toc447881049>`__
`II.8 Topic category, originating controlled vocabulary, and keyword
value - \*Dataset topic category 51 <#_Toc447881050>`__
`II.8.1 Topic category and keyword in datasets and dataset series
52 <#topic-category-and-keyword-in-datasets-and-dataset-series>`__
`II.8.2 Keyword in services 53 <#_Toc447881052>`__
`II.9 Spatial data service type - \*not in ISO 19115 core
57 <#_Toc447881053>`__
`II.10 Geographic bounding box - \*Geographic location of the dataset
(by 4 coordinates or by geographic identifier) 57 <#_Toc447881054>`__
`II.11 Temporal reference and metadata date –\*Additional extent
information for the dataset (vertical and temporal) and \*Metadata date
stamp 59 <#_Toc447881055>`__
`II.12 Lineage - \*Lineage 61 <#_Toc447881056>`__
`II.13 Spatial resolution – Spatial resolution of the dataset
62 <#_Toc447881057>`__
`II.14 Conformity and data quality - \*not in ISO 19115 core
63 <#_Toc447881058>`__
`II.15 Conditions for access and use and limitations on public access –
Use limitation and access / other constraints 65 <#_Toc447881059>`__
`II.16 Responsible party and metadata point of contact - \*Dataset
responsible party and \*Metadata point of contact 66 <#_Toc447881060>`__
`II.17 \*Metadata file identifier 70 <#_Toc447881061>`__
`II.18 \*Metadata standard name, \*Metadata standard version
70 <#_Toc447881062>`__
`II.19 \*Metadata characterset 72 <#_Toc447881063>`__
`II.20 Metadata point of contact - \*Metadata point of contact
72 <#_Toc447881064>`__
`II.21 Metadata date - \*Metadata date stamp 72 <#_Toc447881065>`__
`II.22 Metadata language - \*Metadata language 72 <#_Toc447881066>`__
`II.23 Coordinate reference systems and Temporal reference systems –
\*Reference System 72 <#_Toc447881067>`__
`II.24 Character encoding - \*Dataset character set and \*Metadata
character set 74 <#_Toc447881068>`__
`II.25 Encoding - \*Distribution format 77 <#_Toc447881069>`__
`II.26 Spatial representation type – \*Spatial representation type
78 <#_Toc447881070>`__
`II.27 Maintenance information - \*not in ISO 19115 core
79 <#_Toc447881071>`__
`Annex III Comparison between INSPIRE and ISO 19115-1:2014
81 <#_Toc447881072>`__
`III.1 Spatial dataset and spatial dataset series 81 <#_Toc447881073>`__
`III.2 Services 84 <#_Toc447881074>`__
List of tables
`Table 1: Namespace prefixes 16 <#_Toc447881075>`__
`Table 2: Element bindings for GeoDCAT-AP Core 18 <#_Toc447881076>`__
`Table 3: Element bindings for GeoDCAT-AP Extended
23 <#_Toc447881077>`__
`Table 4: Controlled vocabularies to be used 27 <#_Toc447881078>`__
`Table 5: Overview of covered metadata elements 39 <#_Toc447881079>`__
`Table 6: Mappings for metadata element ‘originating controlled
vocabulary’ 53 <#_Toc447881080>`__
`Table 7: Mappings for metadata element ‘conformity’
63 <#_Toc447881081>`__
`Table 8: Mappings for metadata element ‘responsible party’
67 <#_Toc447881082>`__
`Table 9: Responsible party roles 67 <#_Toc447881083>`__
`Table 10: Metadata standard name and metadata standard version
71 <#_Toc447881084>`__
`Table 11: Metadata elements used for discovery of geographic datasets
and series 81 <#_Toc447881085>`__
`Table 12: Metadata elements used for discovery of service resources
84 <#_Toc447881086>`__
Abbreviations used in this document
+--------------+--------------------------------------------------------------------+
| ARE3NA | Reusable INSPIRE Reference Platform |
+--------------+--------------------------------------------------------------------+
| CRS | Coordinate Reference System |
+--------------+--------------------------------------------------------------------+
| CSW | Catalog Services for the Web |
+--------------+--------------------------------------------------------------------+
| DCAT | Data Catalog Vocabulary |
+--------------+--------------------------------------------------------------------+
| DCAT-AP | DCAT Application Profile for Data Portals in Europe |
+--------------+--------------------------------------------------------------------+
| DCMI | Dublin Core Metadata Initiative |
+--------------+--------------------------------------------------------------------+
| EARL | Evaluation and Report Language |
+--------------+--------------------------------------------------------------------+
| EU | European Union |
+--------------+--------------------------------------------------------------------+
| EuroVoc | Multilingual Thesaurus of the European Union |
+--------------+--------------------------------------------------------------------+
| GEMET | GEneral Multilingual Environmental Thesaurus |
+--------------+--------------------------------------------------------------------+
| GML | Geography Markup Language |
+--------------+--------------------------------------------------------------------+
| GeoDCAT-AP | Geographical extension of DCAT-AP |
+--------------+--------------------------------------------------------------------+
| IANA | Internet Assigned Numbers Authority |
+--------------+--------------------------------------------------------------------+
| INSPIRE | Infrastructure for Spatial Information in the European Community |
+--------------+--------------------------------------------------------------------+
| ISO | International Standardisation Organisation |
+--------------+--------------------------------------------------------------------+
| JRC | European Commission - Joint Research Centre |
+--------------+--------------------------------------------------------------------+
| MDR | Metadata Registry |
+--------------+--------------------------------------------------------------------+
| NAL | Named Authority Lists |
+--------------+--------------------------------------------------------------------+
| OGC | Open Geospatial Consortium |
+--------------+--------------------------------------------------------------------+
| RDF | Resource Description Framework |
+--------------+--------------------------------------------------------------------+
| RFC | Request for Comments |
+--------------+--------------------------------------------------------------------+
| SPARQL | SPARQL Protocol and RDF Query |
+--------------+--------------------------------------------------------------------+
| URI | Uniform Resource Identifier |
+--------------+--------------------------------------------------------------------+
| W3C | World Wide Web Consortium |
+--------------+--------------------------------------------------------------------+
| WG | Working Group |
+--------------+--------------------------------------------------------------------+
| WKT | Well Known Text |
+--------------+--------------------------------------------------------------------+
| XML | eXtensible Markup Language |
+--------------+--------------------------------------------------------------------+
| XSLT | eXtensible Stylesheet Language Transformations |
+--------------+--------------------------------------------------------------------+
Introduction
=============
This document contains the specification for GeoDCAT-AP, an extension of
the DCAT application profile for data portals in Europe (DCAT-AP)
[DCAT-AP] for describing geospatial datasets, dataset series, and
services.
Its basic use case is to make spatial datasets, dataset series, and
services searchable on general data portals, thereby making geospatial
information better searchable across borders and sectors. This can be
achieved by the exchange of descriptions of data sets among data
portals. GeoDCAT-AP provides an RDF syntax binding for the union of
metadata elements of the core profile of ISO 19115:2003 [ISO19115] and
those defined in the framework of the INSPIRE Directive [INSPIRE-DIR].
**The GeoDCAT-AP specification does not replace the INSPIRE Metadata
Regulation** [INSPIRE-MD-REG] **nor the INSPIRE Metadata technical
guidelines** [INSPIRE-MD-TG] **based on ISO 19115 and ISO 19119.** Its
purpose is to give owners of geospatial metadata the possibility to
achieve more by providing the means of an *additional* implementation
through harmonised RDF syntax bindings. Conversion rules to RDF syntax
would allow Member States to maintain their collections of
INSPIRE-relevant datasets following the INSPIRE Metadata technical
guidelines based on ISO 19115 and ISO 19119 [ISO19119], while at the
same time publishing these collections on DCAT-AP-conformant data
portals. A conversion to RDF syntax allows additional metadata elements
to be displayed on general-purposed data portals, provided that such
data portals are capable of displaying additional metadata elements.
Additionally, data portals may be capable of providing
machine-to-machine interfaces where additional metadata could be
provided.
Objectives
----------
The objective of this work is to define an *RDF syntax* that can be used
for the exchange of descriptions of *spatial* datasets, dataset series,
and services among data portals. The RDF syntax should extend the DCAT
Application Profile for data portals in Europe [DCAT-AP].
- To provide an RDF syntax binding for the *union* of the elements in
the INSPIRE metadata schema and the core profile of ISO 19115:2003.
The guiding design principle is to make the resulting RDF syntax as
simple as possible; thereby maximally using existing RDF vocabularies
– such as the Dublin Core and DCAT-AP –, and as much as possible
avoiding minting new terms. The defined syntax binding must enable
the conversion of metadata records *from* ISO 19115 / INSPIRE *to* a
harmonised RDF representation. The ability to convert metadata
records from RDF to ISO 19115 / INSPIRE is not a requirement.
- To formulate recommendations to the Working Group dealing with the
revision of the DCAT-AP, to maximally align DCAT-AP and GeoDCAT-AP.
- To take into account and refer to alignment of relevant controlled
vocabularies (e.g., the alignments between GEMET, INSPIRE themes,
EuroVoc carried out by the Publications Office of the EU [1]_).
Additionally, the following outcomes may be achieved, outside the
context of this specification:
- To define new controlled vocabularies or define mappings between
controlled vocabularies;
- To design executable transformation rules (i.e., an XSLT script
[GEODCAT-XSLT]), as a reference implementation of the mappings
defined in the GeoDCAT-AP specification.
- To define an RDF syntax binding for the elements in ISO 19115-1:2014.
1. .. rubric:: Structure of this document
:name: structure-of-this-document
This document consists of the following sections:
- Section 1 introduces this document;
- Section 2 provides an overview of related work;
- Section 3 provides the use cases that motivate the creation of a
GeoDCAT-AP specification;
- Section 4 provides a description of the methodology used in terms of
alignment of criteria and requirement, metadata elements covered by
GeoDCAT-AP, and a summary of the results;
- Section 5 provides the suggested RDF syntax bindings for metadata
elements;
- Section 6 provides an overview of controlled vocabularies with
relevant URI sets;
This specification is accompanied by a set of annexes, providing
additional reference and support material. More precisely:
- Annex I provides a summary of the INSPIRE and ISO 19115 elements
covered by GeoDCAT-AP;
- Annex II provides detailed usage notes and examples for each of the
metadata elements covered by GeoDCAT-AP;
- Annex III carries out a comparison of INSPIRE metadata with
ISO 19115-1:2014.
Related standards and work
==========================
This section contains an overview of related standards and work.
ISO 19115:2003, ISO 19139 and ISO 19115-1:2014
----------------------------------------------
ISO 19115:2003 [ISO19115], a standard of the International Organization
for Standardization (ISO), defines how to describe geographical
information. ISO 19139 [ISO19139] defines the XML-based implementation
for ISO 19115.
ISO 19115-1:2014 [ISO19115-1] has superseded ISO 19115:2003. At the date
of publication of this document, the XML-based implementation of
ISO 19115-1:2014 (namely, ISO 19115-3), was finalised but not yet
officially released. Annex III contains an overview of the most
important changes.
As documented in the INSPIRE Metadata Technical Guidelines
[INSPIRE-MD-TG], the conformance of a metadata set to the core profile
of ISO 19115 does not guarantee conformance to the INSPIRE metadata
specifications, although there is a large correspondence.
OGC Catalog Service for the Web
-------------------------------
Catalog Service for the Web (CSW) [CSW] is a standard of the Open
Geospatial Consortium (OGC) for exposing a catalogue of geospatial
records on the Web. It specifies *the interfaces, bindings, and a
framework for defining application profiles required to publish and
access digital catalogues of metadata for geospatial data, services, and
related resource information. *
A profile of CSW is used in the INSPIRE Technical Guidance on
Discovery Services [INSPIRE-DS-TG].
INSPIRE Metadata Regulation and INSPIRE Metadata Technical Guidelines
---------------------------------------------------------------------
The INSPIRE Metadata Technical Guidelines [INSPIRE-MD-TG] include rules
for the description of resources based on ISO 19115 (datasets and
series) and ISO 19119 (services), and by using their XML-based
implementation defined in ISO 19139.
INSPIRE [2]_ [INSPIRE-DIR] is a Directive of the European Parliament and
of the Council aiming to establish a EU-wide spatial data infrastructure
to give cross-border access to information that can be used to support
EU environmental policies, as well as other policies or activities
having an impact on the environment. The actual scope of this
information corresponds to 34 environmental themes, covering also areas
having cross-sector relevance – e.g., addresses, buildings, population
distribution and demography.
In order to ensure cross-border interoperability of data infrastructures
operated by EU Member States, INSPIRE sets out a framework based on
common specifications for metadata, data, network services, data and
service sharing, monitoring and reporting. Such specifications consist
of a set of implementing rules (which take the form of Commission
Regulations, i.e., they are legally binding in the EU Member States),
along with the corresponding technical guidelines, defined by a
regulatory committee composed of representatives of both EU Member
States and European Union bodies and institutions.
DCAT and DCAT-AP
----------------
The DCAT Application profile for data portals in Europe (DCAT-AP)
[DCAT-AP] is a specification based on the W3C’s Data Catalogue
vocabulary (DCAT) [DCAT] for describing public sector datasets in
Europe. Its basic use case is to enable cross-data portal search for
data sets and make public sector data better searchable across borders
and sectors. This can be achieved by the exchange of descriptions of
datasets among data portals.
The application profile is a specification for metadata records to meet
the specific application needs of data portals in Europe, while
providing semantic interoperability with other applications on the basis
of reuse of established controlled vocabularies (e.g. EuroVoc) and
mappings to existing metadata vocabularies (e.g., Dublin Core, SDMX,
INSPIRE metadata, etc.).
Alignment of INSPIRE metadata with Dublin Core
----------------------------------------------
In 2008, JRC published a report [INSPIRE-DC] on the progress made in
defining the proper way of expressing elements of INSPIRE metadata in
conformance with ISO 15836 (Dublin Core).
Alignment of INSPIRE metadata with DCAT-AP
------------------------------------------
The GeoDCAT-AP specification builds upon prior work conducted by the
European Commission’s Joint Research Centre in 2014. This work consisted
of an alignment exercise between INSPIRE metadata and DCAT-AP (version
1.0) in the framework of ISA Action 1.17 [INSPIRE-DCAT]. The results of
this alignment exercise, referred to as INSPIRE+DCAT-AP, are divided in
two parts:
- A Core version which defines alignments for the *subset* of INSPIRE
metadata elements supported by DCAT-AP.
- An Extended version which defines alignments for *all* the INSPIRE
metadata elements using DCAT-AP and other vocabularies whenever
DCAT-AP is not relevant.
However, INSPIRE+DCAT-AP did not define alignments for the following
elements:
- Some of the metadata elements in the core profile of ISO 19115 –
i.e., those related to the metadata character set, metadata
identifier and metadata standard. *The GeoDCAT-AP Extended profile–
in this document – does provide an RDF syntax binding for these
metadata elements.*
- The INSPIRE metadata elements recommended in the data specifications
technical guidelines, summarised in Appendix B.2 to INSPIRE Metadata
Technical Guidelines (version 1.3) [INSPIRE-MD-TG]. *The GeoDCAT-AP
Extended profile– in this document –provides a partial syntax binding
for data quality (limited to conformity) and maintenance information
(limited to maintenance and update frequency).*
1. .. rubric:: Alignment of EuroVoc – GEMET – INSPIRE themes
:name: alignment-of-eurovoc-gemet-inspire-themes
EuroVoc is a multilingual, multidisciplinary thesaurus covering the
activities of the EU, and it is one of the controlled vocabularies
recommended in DCAT-AP.
The Publications Office of the EU has defined and published alignments
between EuroVoc and other vocabularies, including those typically used
in geospatial metadata – in particular, AGROVOC, GEMET, the INSPIRE
themes and the INSPIRE feature concept dictionary. It is worth noting
that the use of the INSPIRE themes is a legal obligation in INSPIRE
metadata.
These alignments are available from the Metadata Registry of the EU
Publications Office:
http://publications.europa.eu/mdr/eurovoc/
GeoDCAT-AP XSLT script and API
------------------------------
In the context of ISA Action 1.17 (ARE3NA – Reusable INSPIRE Reference
Platform) an XSLT script [GEODCAT-XSLT] was created, that can be used to
transform ISO 19139 metadata into Geo/DCAT-AP. This XSLT is maintained
on the Commission’s Git repository:
https://webgate.ec.europa.eu/CITnet/stash/projects/ODCKAN/repos/iso-19139-to-dcat-ap/
The XSLT is complemented with documentation summarising how the
GeoDCAT-AP specification has been implemented. This documentation
includes:
- A summary of the mappings, accompanied with detailed examples for
some metadata elements. [3]_
- Where the XSLT expects to find HTTP URIs, and how they are used. [4]_
An experimental API has been also developed, as a proof-of-concept for
the CSW-based implementation of GeoDCAT-AP. The API uses the GeoDCAT-AP
XSLT to transform ISO 19139 records into Geo/DCAT-AP. It supports HTTP
content negotiation and multiple RDF serialisation formats (namely,
RDF/XML, Turtle, N3, N-Triples, JSON-LD, HTML+RDFa).
The source code of the API is available from the Commission’s Git
repository:
https://webgate.ec.europa.eu/CITnet/stash/projects/ODCKAN/repos/iso-19139-to-dcat-ap/browse/api
Motivation and use cases
========================
The basic use case that GeoDCAT-AP intends to enable is a cross-domain
data portal search for datasets, as documented in the DCAT-AP
specification [DCAT-AP]. GeoDCAT-AP will make it easier to share
descriptions of spatial datasets between spatial data portals and
general data portals, and thus help increase public and cross-sector
access to such high value datasets. The datasets could include:
- **Datasets on the INSPIRE Geoportal**. The INSPIRE Geoportal
aggregates metadata for over 100k datasets across Europe. It provides
the means to search for spatial data sets and spatial data services,
and subject to access restrictions, to view spatial data sets from
the EU Member States within the framework of the INSPIRE Directive.
The metadata stored on this portal is structured according to the
INSPIRE Metadata Technical Guidelines [INSPIRE-MD-TG]. In order to
maximise visibility and re-use, spatial datasets could also be listed
on general-purpose Open Data Portals, such as the European Union Open
Data Portal (EU ODP) [5]_ and the European Data Portal (EDP) [6]_.
- **Datasets on national SDIs**. GeoDCAT-AP would facilitate the
integration of SDIs operated by EU Member States with any data
catalogue able to consume DCAT-AP-compliant metadata.
- **General geospatial datasets**. The geospatial community shares a
common background and makes consistent use of consolidated standards
and technologies. In particular, as far as metadata are concerned, it
is widespread to use standards like ISO 19115 / 19139, for the
representation and encoding of metadata, and OGC’s CSW (Catalog
Service for the Web) for accessing and querying metadata records.
These standards are also those currently recommended in INSPIRE.
An additional RDF syntax for INSPIRE and ISO 19115 metadata elements is
beneficial, especially when other data portals support the DCAT-AP
metadata elements only.
Conversion rules to RDF syntax would allow Member States to maintain
their collections of INSPIRE-relevant datasets following the INSPIRE
Metadata Technical Guidelines based on ISO 19115 and ISO 19119, while at
the same time publishing these collections on DCAT-AP-conformant data
portals. A conversion to RDF syntax – using for example the GeoDCAT-AP
XSLT script [GEODCAT-XSLT] - allows additional metadata elements to be
displayed on general-purposed data portals, provided that such data
portals are capable of displaying of additional metadata elements.
Furthermore, data portals frequently are complemented by a triple store,
making that the full set of GeoDCAT-AP metadata can be queried through a
SPARQL endpoint.
Methodology and summary of results
==================================
Methodologically, the development of GeoDCAT-AP implied three main
interrelated tasks:
1. Definition of alignment criteria and requirements.
2. Identification of the metadata elements to be covered by GeoDCAT-AP.
3. Definition of alignments for the metadata elements to be covered by
GeoDCAT-AP.
These tasks and their results are described in the following sections.
Alignment criteria and requirements
-----------------------------------
The objective of the GeoDCAT-AP is twofold:
1. Provide a DCAT-AP-conformant representation of geospatial metadata.
2. Provide an as much as possible comprehensive RDF-based representation
of geospatial metadata, based on widely used vocabularies (as
DCAT-AP), trying, at the same time, to avoid semantic loss and to
promote cross-domain re-use.
These two goals, having a different scope and applying to different use
cases (see Section 3), are reflected in the two profiles of GeoDCAT-AP,
core and extended, described in Section 5.
Note that point (1) implies that:
- GeoDCAT-AP must include, at least, all the mandatory DCAT-AP
elements.
- Vocabularies different from DCAT-AP can be used only for those
geospatial metadata elements not supported in DCAT-AP.
Another key criterion was to base as much as possible the defined
alignments on existing practices, in particular those contributed by the
GeoDCAT-AP WG. The objective was to build upon experiences having
already addressed issues in scope of GeoDCAT-AP, and to avoid a negative
impact on existing implementations.
Finally, as already mentioned in Section 1.1, whenever no suitable
candidates were available in existing vocabularies to represent
geospatial metadata elements, the possibility of defining new terms was
not excluded. However, this option needed to be carefully assessed, and
discarded whenever it might have led to a specification that was
conflicting with standards under preparation. For example, this was the
case of the work carried out by the W3C Data on the Web Best Practices
Working Group and the joint W3C/OG Spatial Data on the Web Working
Group.
As it will be explained in Section 4.3, no new terms have been defined
in the current version of GeoDCAT-AP.
Metadata elements to be covered by GeoDCAT-AP
---------------------------------------------
The general criterion used for this task was that GeoDCAT-AP would
ideally cover *all* the metadata elements of the core profile of
ISO 19115 and those defined in INSPIRE, with the requirement that only
*optional* elements *might* be excluded.
Based on this, the current version of GeoDCAT-AP covers the following
set of metadata elements:
- All the metadata elements in the core profile of ISO 19115.
- All the metadata elements defined in INSPIRE, with the exclusion of
those not common to all the INSPIRE spatial data themes.
More precisely, the supported INSPIRE metadata elements include:
- The set of metadata elements defined in the INSPIRE Metadata
Regulation [INSPIRE-MD-REG].
- The set of metadata elements defined in the INSPIRE Data and Services
Regulation (Article 13: “Metadata required for Interoperability”)
[INSPIRE-D&S-REG]. These elements are also listed in Appendix B.1 to
the INSPIRE Metadata Technical Guidelines (version 1.3)
[INSPIRE-MD-TG].
- The set of metadata elements recommended as common to all the INSPIRE
spatial data themes in the INSPIRE Data Specifications Technical
Guidelines, and listed in the first table included in Appendix B.2 to
version 1.3 of the INSPIRE Metadata Technical Guidelines (version
1.3) [INSPIRE-MD-TG]. These elements are the following ones:
- Conceptual and domain consistency (Data quality – Logical
consistency).
- Maintenance information.
The full list of metadata elements covered by the current version of
GeoDCAT-AP is available in Annex I to this document.
The metadata elements not supported in the current version of GeoDCAT-AP
are those recommended only for *specific* INSPIRE spatial data themes in
the INSPIRE Data Specifications Technical Guidelines, and listed in the
second, third and fourth table included in Appendix B.2 to the INSPIRE
Metadata Technical Guidelines (version 1.3) [INSPIRE-MD-TG].
These elements have been excluded in the current version of GeoDCAT-AP
for the following reasons:
- The priority was to support all those elements relevant to any
dataset.
- These elements are all optional.
Support to these metadata elements might be provided in future versions
of GeoDCAT-AP.
Alignments defined in GeoDCAT-AP
--------------------------------
The alignments defined in the current version of GeoDCAT-AP are the
result of an iterative revision process, following the criteria
illustrated in the previous sections and the review of the GeoDCAT-AP
WG.
The work started with the review of the suite of specifications
concerning the INSPIRE profile of DCAT-AP (INSPIRE+DCAT-AP)
[INSPIRE-DCAT], and of the preliminary proposals concerning the metadata
elements not covered by INSPIRE+DCAT-AP.
In two specific cases, feedback has been asked to relevant
standardisation bodies, in order to validate the proposal made in
GeoDCAT-AP. In particular, this concerned feedback provided by the W3C
Provenance Working Group on the use of the W3C PROV ontology to model
responsible party roles and conformance results (data quality).
Finally, the GeoDCAT-AP WG has worked in close coordination with the
DCAT-AP WG, in order to ensure mutual compliance of the proposed
solutions.
The results of this work, reflected in the current version of
GeoDCAT-AP, can be summarised as follows:
- Compliance with DCAT-AP is ensured: The geospatial metadata elements
covered by GeoDCAT-AP include all those that in DCAT-AP are
mandatory, plus a subset of those that are recommended and optional.
- GeoDCAT-AP offers alignments for all the metadata elements
illustrated in Section 4.2, by using existing vocabularies, and
without defining new terms.
The majority of the alignments defined in GeoDCAT-AP provide a complete
representation of the corresponding geospatial metadata elements, but
some metadata elements have open issues:
- Partial mappings: For some metadata elements, only a partial mapping
is available. This concerns data quality and maintenance information,
for which only the mandatory components have been mapped (for more
details, see Annex II, Sections II.14 and II.27, respectively). This
decision was taken because existing vocabularies did not offer the
ability to represent all the components of these metadata elements.
- Provisional mappings: For some metadata elements, no suitable
candidate has been found to model them also partially. This concerns
the following elements:
- spatial resolution (see Annex II, Section II.13);
- data quality and conformity (Annex II, Section II.14);
- (coordinate and temporal) reference systems (Annex II,
Section II.23).
The alignments for these elements defined in the current version
of GeoDCAT-AP must then be considered as unstable, and are meant
to be replaced by appropriate terms defined in standard
vocabularies (whether and when available). Notably, both the W3C
Data on the Web Best Practices WG and the joint W3C/OGC Spatial
Data on the Web Working Group planned to standardise the
representation of data granularity (which includes spatial
resolution), data quality and conformity, and reference systems.
The details of the alignments defined in GeoDCAT-AP are illustrated in
the following section.
RDF syntax bindings for INSPIRE and ISO 19115 metadata elements
================================================================
The following sections provide the list of the bindings defined in
GeoDCAT-AP for the RDF representation of INSPIRE metadata and the core
profile of ISO 19115:2003.
For detailed usage notes and examples of each of the metadata elements
covered by GeoDCAT-AP, we refer the reader to Annex II (the relevant
section is specified in the “comments” column of the mapping table).
Used namespaces
---------------
Table 1 gives an overview of the namespaces (and prefixes) used in the
remainder of this document.
Table : Namespace prefixes
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| Prefix | Namespace | RDF Vocabulary |
+==========+===============================================+======================================================================+
| adms | http://www.w3.org/ns/adms# | Asset Description Metadata Schema |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| cnt | http://www.w3.org/2011/content# | Representing Content in RDF 1.0 |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| dc | http://purl.org/dc/elements/1.1/ | Dublin Core Metadata Element Set, Version 1.1 |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| dcat | http://www.w3.org/ns/dcat# | Data Catalog Vocabulary |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| dct | http://purl.org/dc/terms/ | DCMI Metadata Terms |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| dctype | http://purl.org/dc/dcmitype/ | DCMI Type Vocabulary |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| foaf | http://xmlns.com/foaf/0.1/ | FOAF Vocabulary |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| gsp | http://www.opengis.net/ont/geosparql# | OGC GeoSPARQL |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| locn | http://www.w3.org/ns/locn# | ISA Programme Core Location Vocabulary |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| owl | http://www.w3.org/2002/07/owl# | OWL Web Ontology Language |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| prov | http://www.w3.org/ns/prov# | PROV-O: The PROV Ontology |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| rdf | http://www.w3.org/1999/02/22-rdf-syntax-ns# | Resource Description Framework (RDF): Concepts and Abstract Syntax |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| rdfs | http://www.w3.org/2000/01/rdf-schema# | RDF Vocabulary Description Language 1.0: RDF Schema |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| schema | http://schema.org/ | schema.org |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| skos | http://www.w3.org/2004/02/skos/core# | SKOS Simple Knowledge Organization System - Reference |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| vcard | http://www.w3.org/2006/vcard/ns# | vCard Ontology |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
| xsd | http://www.w3.org/2001/XMLSchema# | XML Schema Part 2: Datatypes Second Edition |
+----------+-----------------------------------------------+----------------------------------------------------------------------+
Overview of bindings for GeoDCAT-AP Core
----------------------------------------
Table 2 provides an overview of **GeoDCAT-AP Core**. This includes
bindings for metadata elements of the INSPIRE metadata and metadata
elements in the core profile of ISO 19115:2003 core *for which DCAT-AP
provides an RDF syntax binding*. Those metadata elements for which
DCAT-AP does not provide a binding are part of the GeoDCAT-AP Extended
profile described in Section 5.3.
GeoDCAT-AP Core is meant to enable the harvesting and re-use of spatial
metadata records through DCAT-AP-conformant applications and services,
including data portals and APIs. The alignments for INSPIRE and
ISO 19115:2003 metadata elements that are not included in GeoDCAT-AP
Core are defined in GeoDCAT-AP Extended, see Section 5.3.
In addition to this, GeoDCAT-AP Core does not provide alignments from
metadata records concerning services, with the only exception of
catalogue or discovery services, which are the only one supported in
DCAT-AP.
In Table 2 the starred elements (\*) are used to indicate the
corresponding metadata element in the core profile of ISO 19115:2003.
For each element, it is indicated whether the element is mandatory (M),
optional (O), conditional (C), or recommended (R) in either
specification.
Table : Element bindings for GeoDCAT-AP Core
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| INSPIRE metadata | DCAT-AP Property | Domain | Range | Comments |
| | | | | |
| \*ISO19115:2003 Core Profile | | | | |
+==============================================================================================+============================================================+============================+===================================+=================================================================================================================================================================================================================================================+
| Resource title (M) | dct:title (M) | - | rdf:PlainLiteral | See Annex II, Section II.1 |
| | | | | |
| \*Dataset title (M) | | (dcat:Dataset (M), | | |
| | | | | |
| | | dcat:Catalog (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Resource abstract (M) | dct:description (M) | - | rdf:PlainLiteral | See Annex II, Section II.2 |
| | | | | |
| \*Abstract describing the dataset (M) | | (dcat:Dataset (M), | | |
| | | | | |
| | | dcat:Catalog (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Resource type (M) | rdf:type (M) | - | rdfs:Class (values dcat:Dataset | See Annex II, Section II.3. DCAT-AP does not distinguish between datasets and dataset series. dcat:Catalog can be used for catalogue / discovery services. |
| | | | | |
| \*not in ISO19115 core | (see also binding for GeoDCAT-AP Extended) | (dcat:Dataset (M), | dcat:Catalog) | |
| | | | | |
| | | dcat:Catalog (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Resource locator (C) | | | | See Annex II, Section II.4. The proposed encoding depends whether the resource is a service or a dataset or data series. Also, the value of the function code (CI\_OnlineFunctionCode) must be taken into account. |
| | | | | |
| \*On-line resource (O) | | | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| For services | foaf:homepage | - | foaf:Document | See Annex II, Section II.4. |
| | | | | |
| | | (dcat:Catalog (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| For dataset and data series (function code not provided) | dcat:landingPage (O) | dcat:Dataset (M) | foaf:Document | See Annex II, Section II.4. |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| For dataset and data series (‘download’ function code) | dcat:accessURL (M) | dcat:Distribution (R) | rdfs:Resource | See Annex II, Section II.4. |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| For dataset and data series (‘information’ function code) | foaf:page (not in DCAT-AP!) | - | foaf:Document | See Annex II, Section II.4. |
| | | | | |
| | | (dcat:Dataset (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| For dataset and data series (‘offlineAccess’ function code) | dcat:accessURL (M) | dcat:Distribution (R) | rdfs:Resource | See Annex II, Section II.4. |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| For dataset and data series (‘order’ function code) | dcat:accessURL (M) | dcat:Distribution (R) | rdfs:Resource | See Annex II, Section II.4. |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| For dataset and data series (‘search’ function code) | foaf:page | - | foaf:Document | See Annex II, Section II.4. |
| | | | | |
| | | (dcat:Dataset) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Unique resource identifier (M) | dct:identifier (O) | - | rdfs:Literal | See Annex II, Section II.5. In RDF, this could also be represented as the URI of the dataset. |
| | | | | |
| \*not in ISO19115 core | | (dcat:Dataset (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Resource language (C) | dct:language (O for dcat:Dataset and R for dcat:Catalog) | - | dct:LinguisticSystem | See Annex II, Section II.7. |
| | | | | |
| \*Dataset language (M) | | (dcat:Dataset (M), | | |
| | | | | |
| | | dcat:Catalog (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Spatial data service type (M) | rdf:type | - | rdfs:Class (values | See Annex II, Section II.3. DCAT-AP foresees only one type of services - i.e., data catalogues. |
| | | | | |
| \*not in ISO19115 core | | | dcat:Catalog) | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Keyword value (M) | dcat:keyword (R) | dcat:Dataset (M) | rdfs:Literal | See Annex II, Section II.8. For datasets and data series, dcat:keyword is used for free keywords; dcat:theme for controlled vocabularies. |
| | | | | |
| \*not in ISO19115 core | dcat:theme (R) | | | Keywords whose controlled vocabulary is the one of the INSPIRE spatial data themes are mapped to dcat:theme, and expressed by the corresponding URI in the INSPIRE Registry. See controlled vocabulary for theme in Section 6. |
| | | | | |
| | (see also binding for GeoDCAT-AP Extended) | | | For services a syntax binding is provided in GeoDCAT-AP Extended only. |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Geographic bounding box (M) | dct:spatial (O) | - | dct:Location | See Annex II, Section II.10 on the preferred format to be used in RDF for the representation of geometries. |
| | | | | |
| \*Geographic location of the dataset (by four coordinates or by geographic identifier) (C) | | (dcat:Dataset (M), | | |
| | | | | |
| | | dcat:Catalog (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Temporal extent (C) | dct:temporal (O) | - | dct:PeriodOfTime | See Annex II, Section II.11. |
| | | | | |
| \*Additional extent information for the dataset (vertical and temporal) (O) | | (dcat:Dataset | | |
| | | | | |
| | | (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Date of publication (C) | dct:issued (R for dcat:Catalog and O for dcat:Dataset) | - | xsd:date | See Annex II, Section II.11. |
| | | | | |
| \*Dataset reference date (M) – publication | | (dcat:Dataset (M), | | |
| | | | | |
| | | dcat:Catalog (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Date of last revision (C) | dct:modified (R for dcat:Catalog and O for dcat:Dataset) | - | xsd:date | See Annex II, Section II.11. |
| | | | | |
| \*Dataset reference date (M) – revision | | (dcat:Dataset (M), | | |
| | | | | |
| | | dcat:Catalog (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Lineage (M) | dct:provenance | - | dct:ProvenanceStatement | See Annex II, Section II.12. |
| | | | | |
| \*Lineage (O) | | - | | |
| | | | | |
| | | (dcat:Dataset (M), | | |
| | | | | |
| | | dcat:Catalog (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Conformity (M) | dct:conformsTo (O) | - | dct:Standard | See Annex II, Section II.14. dct:conformsTo can model only one of the cases foreseen in INSPIRE. i.e., when the degree of conformity is “conformant”. |
| | | | | |
| \*not in ISO19115 core | (see also binding for GeoDCAT-AP Extended) | (dcat:Dataset | | |
| | | | | |
| | | (M)) | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Conformity Specification (M) | dct:title | rdfs:Resource | rdf:PlainLiteral | See Annex II, Section II.14. |
| | | | | |
| \*not in ISO19115 core | dct:issued, dct:modified, dct:created | | xsd:date | |
| | | | | |
| | (see also binding for GeoDCAT-AP Extended) | | | |
+----------------------------------------------------------------------------------------------+------------------------------------------------------------+----------------------------+-----------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Conditions for access and use (M) | dct:license (O) | - | dct:LicenseDocument | See Annex II, Section II.15. |