GeoDCAT-AP - Version 2.0.0

A geospatial extension for the DCAT application profile for data portals in Europe

SEMIC Recommendation

This version:
https://semiceu.github.io/GeoDCAT-AP/releases/2.0.0/
Latest published version:
https://semiceu.github.io/GeoDCAT-AP/releases/
Latest editor's draft:
https://semiceu.github.io/GeoDCAT-AP/drafts/latest/
Previous version:
https://semiceu.github.io/GeoDCAT-AP/drafts/2.0.0-draft-0.1/
Previous Recommendation:
https://semiceu.github.io/GeoDCAT-AP/releases/1.0.1/
Editors:
Andrea Perego (External Consultant, European Commission, Joint Research Centre)
Bert van Nuffelen (TenForce)
Former editors:
Andrea Perego (European Commission, Joint Research Centre)
Stijn Goedertier (PwC EU Services)
Antonio Rotundo (Agenzia per l'Italia Digitale)
Author:
GeoDCAT-AP Working Group (EU ISA² Programme)
Participate:
GitHub semiceu/geodcat-ap
File a bug
Commit history
Pull requests
Document status:
Completed
Document version:
1.0
Reviewed by:
Pavlina Fragkou (European Commission)
Seth van Hooland (European Commission)
Approved by:
Pavlina Fragkou (European Commission)
Seth van Hooland (European Commission)

Please check the errata for any errors or issues reported since publication.

This document is also available in these non-normative formats: RDF/XML, Turtle, JSON-LD, and SHACL (Turtle)


Abstract

GeoDCAT-AP is an extension of the DCAT application profile for data portals in Europe (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 findable across borders and sectors. For this purpose, GeoDCAT-AP provides an RDF vocabulary and the corresponding RDF syntax binding for the union of metadata elements of the core profile of ISO 19115:2003 and those defined in the framework of the INSPIRE Directive of the European Union.

This document is the result of the major change release process described in the Change and Release Management Policy for DCAT-AP and was built starting from GeoDCAT-AP version 1.0.1.

Comments and queries should be sent via the issue tracker of the dedicated GitHub repository.

Disclaimer

The views expressed in this document are purely those of the Author(s) 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.

Status of This Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document.

This document was published by the GeoDCAT-AP Working Group as a Recommendation.

GitHub Issues are preferred for discussion of this specification.

A Recommendation is a specification that, after extensive consensus-building, has received the endorsement of the Working Group. The Working Group recommends the wide deployment of this specification.

This document is governed by the Change and Release Management Policy for DCAT-AP.

Document History

Version Date Description Action Change Log
1.0 23/12/2020 Recommendation Publication § C.1 Changes since first public working draft of 12 October 2020
0.1 12/10/2020 First Public Working Draft Creation § C.2 Changes since GeoDCAT-AP 1.0.1 (2 August 2016)

1. Introduction

This section is non-normative.

This document contains version 2.0.0 of 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 findable across borders and sectors. For this purpose, GeoDCAT-AP provides an RDF vocabulary and the corresponding RDF syntax binding for the union of metadata elements of the core profile of ISO 19115:2003 [ISO-19115] 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] 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], while at the same time publishing these collections on [DCAT-AP]-conformant data portals. A conversion to an RDF representation 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.

1.1 Context

With a view to fostering Europe's digital transformation, the European Commission is investing in frameworks and agreements to provide governments and businesses with the appropriate resources to digitalise their services. There are, for instance, building blocks available for creating a single market for data, where data flows freely within the EU and across sectors for the benefit of businesses, researchers and public administrations.

To this direction, the European Commission launched the European Data Strategy [DataStrategy], as part of the European Commission's priorities for 2019-2024 in order to make the EU a leader in a data-driven society.

Studies previously conducted on behalf of the European Commission (e.g., [Vickery]) shed light on the importance of having data findable and available in machine readable format in order to stimulate its reuse. This vision led to several legislative actions to reduce barriers and promote data sharing, such as the Open Data Directive [OPENDATA-DIR], which turned out to be a driving force towards a more transparent and fair access to government data.

With this regard, the wide range of (open) data portals developed by European public administrations is the result of this mission. These Web-based interfaces allow access to data by providing users means to explore a catalogue of datasets. To facilitate the sharing, discovery and re-use of the data beyond the (open) data portal, common agreements for the exchange of catalogues of datasets are needed. These interoperability agreements enable to connect (open) data catalogues into a pan-european catalogue of datasets.

The DCAT-AP application profile specifies the generic agreements for (open) data portals operated by public administrations in Europe. This specification extends DCAT-AP with additional requirements for geospatial data.

The current document is the result of the major semantic change release process described in the Change and Release Management Policy for DCAT-AP [DCAT-AP-CRMP] and was built starting from GeoDCAT-AP version 1.0.1 [GeoDCAT-AP-20160802], with the purpose of aligning it with DCAT-AP version 2.0.1 [DCAT-AP-20200608] and with version 2.0.1 of the INSPIRE Metadata Technical Guidelines [INSPIRE-MD-20170302].

This work has been carried out in the context of Action 1.1 – Improving semantic interoperability in European eGovernment systems [SEMIC] of the European Commission’s Interoperability solutions for public administrations, businesses and citizens (ISA²) Programme [ISA2], and it is the result of the major semantic change release process described in the Change and Release Management Policy for DCAT-AP [DCAT-AP-CRMP] and was built starting from GeoDCAT-AP version 1.0.1 [GeoDCAT-AP-20160802], with the purpose of aligning it with DCAT-AP version 2.0.1 [DCAT-AP-20200608] and with version 2.0.1 of the INSPIRE Metadata Technical Guidelines [INSPIRE-MD-20170302].

1.2 Scope of the revision

The objective of this work is to produce an updated release of GeoDCAT-AP based on requests for change coming from real-world implementations of the specification and an alignment with [DCAT-AP-20200608] and [INSPIRE-MD-20170302].

As [DCAT-AP-20200608], the Application Profile specified in this document is based on the specification of the Data Catalog Vocabulary (DCAT), originally developed under the responsibility of the Government Linked Data Working Group [GLD] at W3C, and significantly revised in 2020 by the W3C Dataset Exchange Working Group [DXWG]. DCAT is an RDF [RDF11-CONCEPTS] vocabulary designed to facilitate interoperability between data catalogues published on the Web. Additional classes and properties from other well-known vocabularies are re-used where necessary.

The work does not cover implementation issues like mechanisms for exchange of data and expected behaviour of systems implementing the Application Profile other than what is defined in the Conformance Statement in § 6. Conformance.

The Application Profile is intended to facilitate data exchange and therefore the classes and properties defined in this document are only relevant for the data to be exchanged; there are no requirements for communicating systems to implement specific technical environments. The only requirement is that the systems can export and import data in RDF in conformance with this Application Profile.

1.3 A DCAT-AP extension

The GeoDCAT-AP specification is designed as an extension of DCAT-AP in conformance with the guidelines for the creation of DCAT-AP extensions [DCAT-AP-EG]. The DCAT-AP Application Profile on which this document is based is the DCAT-AP specification of 8 June 2020 [DCAT-AP-20200608]. According to the same principles DCAT-AP is in itself an extension of DCAT.

This dependency must be taken into account while reading and using this specification. When implementing GeoDCAT-AP, these specifications should be consulted first, to fill in any missing gaps in this document.

2. Terminology used in the Application Profile

A Vocabulary is a specification that determines the semantics of terms (classes and properties) in a broad context of information exchange. The defined terms are higly reusable.

A Controlled Vocabulary is an organised arrangement of words and phrases used to index content and/or to retrieve content through browsing or searching. It typically includes preferred and variant terms and has a defined scope or describes a specific domain [GETTY]. Within this specification, it is also used as a synonym for a codelist.

An Application Profile is a specification that re-uses terms from one or more base standards (vocabularies), adding more specificity by identifying mandatory, recommended and optional elements to be used for a particular application, as well as recommendations for controlled vocabularies to be used.

In the following sections, classes and properties are grouped under headings ‘mandatory’, ‘recommended’ and ‘optional’. These terms have the following meaning:

The meaning of the terms MUST, MUST NOT, SHOULD and MAY in this section and in the following sections are as defined in [RFC2119].

In the given context, the term "processing" means that receivers must accept incoming data and transparently provide these data to applications and services. It does neither imply nor prescribe what applications and services finally do with the data (parse, convert, store, make searchable, display to users, etc.).

Classes are classified as ‘Mandatory’ in § 3.1 Mandatory Classes if they appear as the range of one of the mandatory properties in § 4. Application Profile Properties per Class.

The class ‘Distribution’ is classified as ‘Recommended’ in § 3.2 Recommended Classes to allow for cases that a particular Dataset does not have a downloadable Distribution, and in such cases the sender of data would not be able to provide this information. However, it can be expected that in the majority of cases Datasets do have downloadable Distributions, and in such cases the provision of information on the Distribution is mandatory.

All other classes are classified as ‘Optional’ in § 3.3 Optional Classes. A further description of the optional classes is only included as a sub-section in § 4. Application Profile Properties per Class if the Application Profile specifies mandatory or recommended properties for them.

Classes no longer included in this version of the specification, or replaced with other ones, are classified as ‘Deprecated’ in § 3.4 Deprecated Classes.

Finally, classes and properties added in this Application Profile and extending [DCAT-AP] are marked with a prepended “plus” sign (+), and summarised in the reference table in § A.1 Classes and properties added by GeoDCAT-AP.

2.1 Namespaces

The namespace for GeoDCAT-AP is: http://data.europa.eu/930/

The suggested namespace prefix is: geodcat

The Application Profile reuses terms from various existing specifications, following established best practices [DWBP]. The following table indicates the full list of corresponding namespaces used in this document.

Prefix Namespace URI Specification
adms http://www.w3.org/ns/adms# [VOCAB-ADMS]
cnt http://www.w3.org/2011/content# [Content-in-RDF10]
dc http://purl.org/dc/elements/1.1/ [DC11]
dcat http://www.w3.org/ns/dcat# [VOCAB-DCAT-2]
dcatap http://data.europa.eu/r5r/ [DCAT-AP]
dct http://purl.org/dc/terms/ [DCTERMS]
dctype http://purl.org/dc/dcmitype/ [DCTERMS]
dqv http://www.w3.org/ns/dqv# [VOCAB-DQV]
foaf http://xmlns.com/foaf/0.1/ [FOAF]
geodcat http://data.europa.eu/930/ [GeoDCAT-AP]
gsp http://www.opengis.net/ont/geosparql# [GeoSPARQL]
locn http://www.w3.org/ns/locn# [LOCN]
odrl http://www.w3.org/ns/odrl/2/ [VOCAB-ODRL]
org http://www.w3.org/ns/org# [VOCAB-ORG]
owl http://www.w3.org/2002/07/owl# [OWL-REF]
prov http://www.w3.org/ns/prov# [PROV-O]
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns# [RDF11-CONCEPTS]
rdfs http://www.w3.org/2000/01/rdf-schema# [RDF-SCHEMA]
schema http://schema.org/ [SCHEMA-ORG]
sdmx-attribute http://purl.org/linked-data/sdmx/2009/attribute# [VOCAB-DATA-CUBE]
skos http://www.w3.org/2004/02/skos/core# [SKOS-REFERENCE]
spdx http://spdx.org/rdf/terms# [SPDX]
time http://www.w3.org/2006/time# [OWL-TIME]
vcard http://www.w3.org/2006/vcard/ns# [VCARD-RDF]
xsd http://www.w3.org/2001/XMLSchema# [XMLSCHEMA11-2]

2.2 Application Profile Overview

This Application Profile extends [DCAT-AP-20200608] by including

These extensions are meant to provide a DCAT-AP-conformant representation of geospatial metadata, identified by defining RDF syntax mappings covering the union of the elements in the INSPIRE metadata schema [INSPIRE-MD-REG] [INSPIRE-MD] and the core profile of [ISO-19115], following the criteria illustrated in § B. INSPIRE and ISO 19115 Mappings.

The current specification does not change the set of geospatial metadata elements already covered in its previous version [GeoDCAT-AP-20160802], but rather it updates some of the corresponding mappings based on the new classes and properties included in [DCAT-AP-20200608], following the release of version 2 of the W3C Data Catalog (DCAT) Vocabulary [VOCAB-DCAT-2], and aligns them with version 2.0.1 of the INSPIRE Metadata Technical Guidelines [INSPIRE-MD-20170302]. With the same objective, new terms have been defined in the GeoDCAT-AP namespace for the specification of agent roles (see § 7. Agent Roles) and spatial resolution (see § 4.20.1 Instances of Metric). As a result, some of the classes and properties defined in [GeoDCAT-AP-20160802] have been deprecated and replaced by the equivalent ones in [DCAT-AP-20200608] and by the newly defined terms.

The list of deprecated classes and properties is summarised in § A.2 Deprecated classes and properties.

Figure 1 shows a UML diagram of the classes and properties included in the Application Profile.

Note
GeoDCAT-AP UML Class Diagram
Figure 1 GeoDCAT-AP UML Class Diagram

3. Application Profile Classes

3.1 Mandatory Classes

Class name

Usage note for the Application Profile

URI

Reference

Agent

An entity (e.g., an individual or an organisation) that is associated with Catalogues, Catalogue Records, Data Services, or Datasets. If the Agent is an organisation, the use of the Organization Ontology [VOCAB-ORG] is recommended. See § 7. Agent Roles for a discussion on Agent roles.

foaf:Agent

§ Class: foaf:Agent [FOAF]

[VOCAB-ORG]

Catalogue

A catalogue or repository that hosts the resources (as Data Services, Datasets, or other Catalogues) being described.

dcat:Catalog

§ 6.3 Class: Catalog [VOCAB-DCAT-2]

Dataset

A conceptual entity that represents the information published.

dcat:Dataset

§ 6.6 Class: Dataset [VOCAB-DCAT-2]

Literal

A literal value such as a string or integer; Literals may be typed, e.g. as a date according to xsd:date. Literals that contain human-readable text have an optional language tag as defined by [BCP47].

rdfs:Literal

§ 3.3 Literals [RDF11-CONCEPTS]

Resource

Anything described by RDF.

rdfs:Resource

§ 2.1 rdfs:Resource [RDF-SCHEMA]

3.3 Optional Classes

Note

Class name

Usage note for the Application Profile

URI

Reference

+Activity

An activity carried out by an Agent over an entity, according to a plan, and generating another entity.

In GeoDCAT-AP, this class SHOULD be used to specify a testing activity over a resource, against a given Standard, producing as output a conformance degree.

prov:Activity

§ (2) Class: prov:Activity [PROV-O]; § 12.2.2 Relationships between datasets and agents [VOCAB-DCAT-2]

+Address (Agent)

A postal address of the Agent.

locn:Address

§ Class Address [LOCN]

+Address (Kind)

A postal address of the Kind.

vcard:Address

§ Address [VCARD-RDF]

+Attribution

A responsibility of an Agent for a resource.

prov:Attribution

§ (50) Class: prov:Attribution [PROV-O]; § 13.1 Relationships between datasets and agents [VOCAB-DCAT-2]

Catalogue Record

A description of a Catalogue's, Data Service's, or Dataset's entry in the Catalogue.

dcat:CatalogRecord

§ 6.5 Class: Catalog Record [VOCAB-DCAT-2]

Checksum

A value that allows the contents of a file to be authenticated. This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented.

spdx:Checksum

§ checksum [SPDX]

Data Service

A collection of operations that provides access to one or more datasets or data processing functions.

dcat:DataService

§ 6.8 Class: Data Service [VOCAB-DCAT-2]

Document

A textual resource intended for human consumption that contains information, e.g., a Web page about a Dataset.

foaf:Document

§ Class: foaf:Document [FOAF]

Frequency

A rate at which something recurs, e.g., the publication of a Dataset.

dct:Frequency

§ Term name: Frequency [DCTERMS]

Identifier

An identifier in a particular context, consisting of the string that is the identifier; an optional identifier for the identifier scheme; an optional identifier for the version of the identifier scheme; an optional identifier for the agency that manages the identifier scheme

adms:Identifier

§ 5.2.6 Identifier [VOCAB-ADMS]

Kind

A description following the [VCARD-RDF] specification, e.g. to provide telephone number and e-mail address for a contact point. Note that the class vcard:Kind is the parent class for the four explicit types of vCards (vcard:Individual, vcard:Organization, vcard:Location, vcard:Group).

vcard:Kind

§ Kind [VCARD-RDF]

Linguistic system

A system of signs, symbols, sounds, gestures, or rules used in communication, e.g. a language

dct:LinguisticSystem

§ Term name: LinguisticSystem [DCTERMS]

Location

A spatial region or named place. It can be represented using a controlled vocabulary or with geographic coordinates.

dct:Location

§ Term name: Location [DCTERMS]

Media type

A media type, e.g. the format of a computer file.

dct:MediaType

§ Term name: MediaType [DCTERMS]

+Metric

Represents a standard to measure a quality dimension. An observation (instance of dqv:QualityMeasurement) assigns a value in a given unit to a Metric.

In GeoDCAT-AP, this class is used to define individuals corresponding to the different types of spatial resolution.

dqv:Metric

§ 4.2 Class: Metric [VOCAB-DQV]

Period of time

An interval of time that is named or defined by its start and end dates.

dct:PeriodOfTime

§ Term name: PeriodOfTime [DCTERMS]

Provenance Statement

A statement of any changes in ownership and custody of a resource since its creation that are significant for its authenticity, integrity, and interpretation

dct:ProvenanceStatement

§ Term name: ProvenanceStatement [DCTERMS]

Publisher type

A type of organisation that acts as a publisher

skos:Concept

§ 5.3.41 dcterms:type [VOCAB-ADMS]

+Quality Measurement

Represents the evaluation of a given resource (as a Data Service, Dataset, or Distribution) against a specific quality metric.

In GeoDCAT-AP, this class corresponds to the notion of "spatial resolution", as defined in [INSPIRE-MD-REG], [ISO-19115], and [ISO-19115-1].

dqv:QualityMeasurement

§ 4.1 Class: Quality Measurement [VOCAB-DQV]

Relationship

An association class for attaching additional information to a relationship between DCAT Resources

dcat:Relationship

§ 6.12 Class: Relationship [VOCAB-DCAT-2]

Rights statement

A statement about the intellectual property rights (IPR) held in or over a resource, a legal document giving official permission to do something with a resource, or a statement about access rights.

dct:RightsStatement

§ Term name: RightsStatement [DCTERMS]

Role

A role is the function of a resource or agent with respect to another resource, in the context of resource attribution or resource relationships.

Note it is a subclass of skos:Concept.

dcat:Role

§ 6.13 Class: Role [VOCAB-DCAT-2]

Standard

A standard or other specification to which a Catalogue, Catalogue Record, Data Service, Dataset, or Distribution conforms.

dct:Standard

§ Term name: Standard [DCTERMS]

Status

An indication of the maturity of a Distribution or the type of change of a Catalogue Record.

skos:Concept

§ 5.2.13 Status [VOCAB-ADMS]

3.4 Deprecated Classes

Class name

Usage note for the Application Profile

URI

Replaced by

Deprecated in

Media Type or Extent

A media type, e.g. the format of a computer file.

dct:MediaTypeOrExtent

dct:MediaType

[DCAT-AP-20191120]

+Service

A system that provides one or more functions [DCTERMS].

In the geospatial domain, a service is defined as the set of operations which may be performed, by invoking a computer application, on the spatial data contained in spatial data sets or on the related metadata [INSPIRE-GLOSSARY].

dctype:Service

dcat:DataService

GeoDCAT-AP 2.0.0

Note

4. Application Profile Properties per Class

A quick reference table of properties per class is included in § A. Quick Reference of Classes and Properties. The list of included properties contains all the properties in [DCAT-AP-20200608], plus a selection of properties from [VOCAB-DCAT-2] and [DCTERMS], on which GeoDCAT-AP expresses additional constraints or on which GeoDCAT-AP wants to emphasise their usage.

Examples on the use of these properties, encoded in [Turtle], are included in the relevant sections. The examples are also available in [Turtle], RDF/XML [RDF-SYNTAX-GRAMMAR], and JSON-LD [JSON-LD11] from a separate folder.

4.1 +Activity

Note
Class name Activity
Obligation Optional
URI

prov:Activity

Usage note

An activity carried out by an Agent over an entity, according to a plan, and generating another entity.

In GeoDCAT-AP, this class SHOULD be used to specify a testing activity over a resource, against a given Standard, producing as output a conformance degree.

Reference

§ (2) Class: prov:Activity [PROV-O]; § 12.2.2 Relationships between datasets and agents [VOCAB-DCAT-2]

The use of this class in GeoDCAT-AP is illustrated in § 8. Conformance Test Results.

4.1.1 Mandatory properties for Activity

Note

Property

URI

Range

Usage note

Card.

+generated

prov:generated

prov:Entity

This property refers to the Entity generated by the Activity.

1..n

+qualified association

prov:qualifiedAssociation

prov:Association

This property refers to the Plan according to which the Activity has been carried out, and possibly to the Agent who played a role in it.

1..n

+used

prov:used

prov:Entity

This property refers to the entity (e.g., a Catalogue, a Dataset, a Data Service) which was the subject of the Activity.

This property MAY be omitted in case its inverse property prov:wasUsedBy is specified.

1..n

4.1.2 Examples for Activity

Example 1 shows the use of class prov:Activity to specify the results of a testing activity assessing the conformance of a given resource against a given specification - as illustrated in § 8. Conformance Test Results.

4.2 +Address (Agent)

Note
Class name Address (Agent)
Obligation Optional
URI

locn:Address

Usage note

A postal address of the Agent.

Reference

§ Class Address [LOCN]

4.2.2 Examples for Address (Agent)

4.3 +Address (Kind)

Note
Class name Address (Kind)
Obligation Optional
URI

vcard:Address

Usage note

A postal address of the Kind.

Reference

§ Address [VCARD-RDF]

4.3.2 Examples for Address (Kind)

4.4 Agent

Class name Agent
Obligation Mandatory
URI

foaf:Agent

Usage note

An entity (e.g., an individual or an organisation) that is associated with Catalogues, Catalogue Records, Data Services, or Datasets. If the Agent is an organisation, the use of the Organization Ontology [VOCAB-ORG] is recommended. See § 7. Agent Roles for a discussion on Agent roles.

Reference

§ Class: foaf:Agent [FOAF]

[VOCAB-ORG]

4.4.1 Mandatory property for Agent

Property

URI

Range

Usage note

Card.

name

foaf:name

rdfs:Literal

This property contains a name of the Agent. This property can be repeated for different versions of the name (e.g. the name in different languages) - see § 9. Accessibility and Multilingual Aspects.

1..n

4.4.3 Optional properties for Agent

Note

Property

URI

Range

Usage note

Card.

+address

locn:address

locn:Address

This property MAY be used to specify the postal address of the Agent.

0..1

+affiliation

org:memberOf

org:Organization

This property MAY be used to specify the affiliation of the Agent.

0..1

+email

foaf:mbox

owl:Thing

This property MAY be used to provide the email address of the Agent, specified using fully qualified mailto: URI scheme [RFC6068].

0..1

+phone

foaf:phone

owl:Thing

This property MAY be used to provide the phone number of the Agent, specified using fully qualified tel: URI scheme [RFC3966].

0..1

+URL

foaf:workplaceHomepage

foaf:Document

This property MAY be used to specify the Web site of the Agent.

0..1

4.4.4 Examples for Agent

4.5 +Attribution

Note
Class name Attribution
Obligation Optional
URI

prov:Attribution

Usage note

A responsibility of an Agent for a resource.

Reference

§ (50) Class: prov:Attribution [PROV-O]; § 13.1 Relationships between datasets and agents [VOCAB-DCAT-2]

The use of this class in GeoDCAT-AP is illustrated in § 7. Agent Roles.

4.5.1 Mandatory properties for Attribution

Note

Property

URI

Range

Usage note

Card.

+agent

prov:agent

prov:Agent

This property refers to the Agent to whom the resource is attributed.

1..n

+had role

dcat:hadRole

dcat:Role

This property refers to the function of an Agent with respect to another entity or resource.

In GeoDCAT-AP, this property SHOULD take as value one of the URIs of the "Responsible party roles" code list operated by the INSPIRE Registry [INSPIRE-RPR].

1..n

4.5.2 Deprecated properties for Attribution

Property

URI

Replaced by

Deprecated in

+had role

dct:type

dcat:hadRole

GeoDCAT-AP 2.0.0

Note

4.5.3 Examples for Attribution

4.6 Catalogue

Class name Catalogue
Obligation Mandatory
URI

dcat:Catalog

Usage note

A catalogue or repository that hosts the resources (as Data Services, Datasets, or other Catalogues) being described.

Reference

§ 6.3 Class: Catalog [VOCAB-DCAT-2]

4.6.1 Mandatory properties for Catalogue

Property

URI

Range

Usage note

Card.

dataset

dcat:dataset

dcat:Dataset

This property links the Catalogue with a Dataset that is part of the Catalogue.

1..n

description

dct:description

rdfs:Literal

This property contains a free-text account of the Catalogue. This property can be repeated for parallel language versions of the description - see § 9. Accessibility and Multilingual Aspects.

1..n

publisher

dct:publisher

foaf:Agent

This property refers to an entity (organisation) responsible for making the Catalogue available.

1..1

title

dct:title

rdfs:Literal

This property contains a name given to the Catalogue. This property can be repeated for parallel language versions of the name - see § 9. Accessibility and Multilingual Aspects.

1..n

4.6.3 Optional properties for Catalogue

Property

URI

Range

Usage note

Card.

+access rights

dct:accessRights

dct:RightsStatement

This property MAY include information regarding access or restrictions based on privacy, security, or other policies.

For INSPIRE metadata, this property SHOULD be used with the URIs of the "Limitations on public access" code list operated by the INSPIRE Registry [INSPIRE-LPA].

0..1

+conforms to

dct:conformsTo

dct:Standard

This property refers to an implementing rule or other specification.

0..n

+contact point

dcat:contactPoint

vcard:Kind

This property contains contact information that can be used for sending comments about the Catalogue.

0..n

catalogue

dcat:catalog

dcat:Catalog

This property refers to a Catalogue whose contents are of interest in the context of this Catalogue.

0..n

+creation date

dct:created

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date on which the Catalogue has been first created.

0..1

creator

dct:creator

foaf:Agent

This property refers to the Agent primarily responsible for producing the Catalogue.

0..1

has part

dct:hasPart

dcat:Catalog

This property refers to a related Catalogue that is part of the described Catalogue.

0..n

+identifier

dct:identifier

rdfs:Literal

This property contains the main identifier for the Catalogue, e.g. the URI or other unique identifier.

0..n

is part of

dct:isPartOf

dcat:Catalog

This property refers to a related Catalogue in which the described Catalogue is physically or logically included.

0..1

+qualified attribution

prov:qualifiedAttribution

prov:Attribution

This property refers to a link to an Agent having some form of responsibility for the Catalogue.

0..n

record

dcat:record

dcat:CatalogRecord

This property refers to a Catalogue Record that is part of the Catalogue.

0..n

rights

dct:rights

dct:RightsStatement

This property refers to a statement that specifies rights associated with the Catalogue.

0..1

+reference system

dct:conformsTo

dct:Standard

This property SHOULD be used to specify the reference system used in the Catalogue.

Spatial reference systems SHOULD be specified by using the corresponding URIs from the “EPSG coordinate reference systems” register operated by OGC [OGC-EPSG].

0..n

+rights holder

dct:rightsHolder

foaf:Agent

This property refers to an Agent (organisation) holding rights on the Catalogue.

0..n

+temporal coverage

dct:temporal

dct:PeriodOfTime

This property refers to a temporal period that the Catalogue covers.

0..n

service

dcat:service

dcat:DataService

This property refers to a Data Service that is listed in the Catalogue.

0..n

+theme / category

dcat:theme

skos:Concept

This property refers to a Category of the Catalogue. A Catalogue may be associated with multiple Categories.

0..n

+topic category

dct:subject

skos:Concept

In GeoDCAT-AP, this property SHOULD take as value one of the URIs of the "Topic categories in accordance with EN ISO 19115" code list operated by the INSPIRE Registry [INSPIRE-TC].

0..n

+was used by

prov:wasUsedBy

prov:Activity

This property refers to an Activity that used the Catalogue.

In GeoDCAT-AP, this property MAY be used to specify a testing Activity over a Catalogue, against a given Standard, producing as output a conformance degree.

0..n

+custodian

geodcat:custodian

foaf:Agent

Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource [ISO-19115].

0..n

+distributor

geodcat:distributor

foaf:Agent

Party who distributes the resource [ISO-19115].

0..n

+originator

geodcat:originator

foaf:Agent

Party who created the resource [ISO-19115].

0..n

+principal investigator

geodcat:principalInvestigator

foaf:Agent

Key party responsible for gathering information and conducting research [ISO-19115].

0..n

+processor

geodcat:processor

foaf:Agent

Party who has processed the data in a manner such that the resource has been modified [ISO-19115].

0..n

+resource provider

geodcat:resourceProvider

foaf:Agent

Party that supplies the resource [ISO-19115].

0..n

+user

geodcat:user

foaf:Agent

Party who uses the resource [ISO-19115].

0..n

4.6.4 Deprecated properties for Catalogue

Property

URI

Replaced by

Deprecated in

+keyword / tag

dc:subject

dcat:keyword

GeoDCAT-AP 2.0.0

service

dct:hasPart

dcat:service

GeoDCAT-AP 2.0.0

+theme / category

dct:subject

dcat:theme

GeoDCAT-AP 2.0.0

Note
Note

4.7 Catalogue Record

Class name Catalogue Record
Obligation Optional
URI

dcat:CatalogRecord

Usage note

A description of a Catalogue's, Data Service's, or Dataset's entry in the Catalogue.

Reference

§ 6.5 Class: Catalog Record [VOCAB-DCAT-2]

4.7.1 Mandatory properties for Catalogue Record

Property

URI

Range

Usage note

Card.

primary topic

foaf:primaryTopic

dcat:Dataset or dcat:Dataservice or dcat:Catalog

This property links the Catalogue Record to the Dataset, Data service or Catalogue described in the record.

1..1

update / modification date

dct:modified

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the most recent date on which the Catalogue Record was changed or modified.

1..1

4.7.3 Optional properties for Catalogue Record

Property

URI

Range

Usage note

Card.

+character encoding

cnt:characterEncoding

rdfs:Literal

This property SHOULD be used to specify the character encoding of the Catalogue Record, by using as value the character set names in the IANA register [IANA-CHARSETS].

0..n

+contact point

dcat:contactPoint

vcard:Kind

This property contains contact information that can be used for sending comments about the Catalogue Record.

0..n

+creation date

dct:created

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date on which the Catalogue Record has been first created.

0..1

+creator

dct:creator

foaf:Agent

This property refers to the Agent primarily responsible for producing the Catalogue Record.

0..n

description

dct:description

rdfs:Literal

This property contains a free-text account of the Catalogue Record. This property can be repeated for parallel language versions of the description - see § 9. Accessibility and Multilingual Aspects.

0..n

+identifier

dct:identifier

rdfs:Literal

This property contains the main identifier for the Catalogue Record, e.g., the URI or other unique identifier in the context of the Catalogue.

0..n

language

dct:language

dct:LinguisticSystem

This property refers to a language used in the textual metadata describing titles, descriptions, etc. of the Catalogue Record. This property can be repeated if the metadata is provided in multiple languages - see § 9. Accessibility and Multilingual Aspects.

0..n

+publisher

dct:publisher

foaf:Agent

This property refers to an Agent (organisation) responsible for making the Catalogue Record available.

0..1

+qualified attribution

prov:qualifiedAttribution

prov:Attribution

This property refers to a link to an Agent having some form of responsibility for the Catalogue Record.

0..n

+rights holder

dct:rightsHolder

foaf:Agent

This property refers to an Agent (organisation) holding rights on the Catalogue Record.

0..n

source metadata

dct:source

dcat:CatalogRecord

This property refers to the original metadata record that was used in creating the Catalogue Record.

In GeoDCAT-AP, this MAY refer to an INSPIRE / [ISO-19115] record that was transformed into the current Geo/DCAT-AP one.

0..1

title

dct:title

rdfs:Literal

This property contains a name given to the Catalogue Record. This property can be repeated for parallel language versions of the name - see § 9. Accessibility and Multilingual Aspects.

0..n

+custodian

geodcat:custodian

foaf:Agent

Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource [ISO-19115].

0..n

+distributor

geodcat:distributor

foaf:Agent

Party who distributes the resource [ISO-19115].

0..n

+originator

geodcat:originator

foaf:Agent

Party who created the resource [ISO-19115].

0..n

+principal investigator

geodcat:principalInvestigator

foaf:Agent

Key party responsible for gathering information and conducting research [ISO-19115].

0..n

+processor

geodcat:processor

foaf:Agent

Party who has processed the data in a manner such that the resource has been modified [ISO-19115].

0..n

+resource provider

geodcat:resourceProvider

foaf:Agent

Party that supplies the resource [ISO-19115].

0..n

+user

geodcat:user

foaf:Agent

Party who uses the resource [ISO-19115].

0..n

4.7.4 Examples for Catalogue Record

4.8 Category

Class name Category
Obligation Recommended
URI

skos:Concept

Usage note

A subject of a Catalogue, Dataset, or Data Service.

Reference

§ 6.10 Class: Concept [VOCAB-DCAT-2]

4.8.1 Mandatory property for Category

Property

URI

Range

Usage note

Card.

preferred label

skos:prefLabel

rdfs:Literal

This property contains a preferred label of the Category. This property can be repeated for parallel language versions of the label - see § 9. Accessibility and Multilingual Aspects.

1..n

4.8.2 Optional property for Category

Note

Property

URI

Range

Usage note

Card.

+category scheme

skos:inScheme

skos:ConceptScheme

This property MAY be used to specify the Category Scheme to which the Category belongs.

0..1

4.8.3 Examples for Category

4.9 Category Scheme

Class name Category scheme
Obligation Recommended
URI

skos:ConceptScheme

Usage note

A concept collection (e.g. controlled vocabulary) in which the Category is defined.

Reference

§ 6.9 Class: Concept Scheme [VOCAB-DCAT-2]

4.9.1 Mandatory property for Category Scheme

Property

URI

Range

Usage note

Card.

title

dct:title

rdfs:Literal

This property contains a name of the Category Scheme. May be repeated for different versions of the name - see § 9. Accessibility and Multilingual Aspects.

1..n

4.9.2 Optional properties for Category Scheme

Note

Property

URI

Range

Usage note

Card.

+creation date

dct:created

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date on which the Category Scheme has been first created.

0..1

+release date

dct:issued

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date of formal issuance (e.g., publication) of the Category Scheme.

0..1

+update / modification date

dct:modified

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the most recent date on which the Category Scheme was changed or modified.

0..1

+version

owl:versionInfo

rdfs:Literal

This property contains a version number or other version designation of the Category Scheme.

0..1

4.9.3 Examples for Category Scheme

4.10 Checksum

Class name Checksum
Obligation Optional
URI

spdx:Checksum

Usage note

A value that allows the contents of a file to be authenticated. This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented.

Reference

§ checksum [SPDX]

4.10.1 Mandatory properties for Checksum

Property

URI

Range

Usage note

Card.

algorithm

spdx:algorithm

spdx:checksumAlgorithm_sha1

This property identifies the algorithm used to produce the subject Checksum. Currently, SHA-1 is the only supported algorithm. It is anticipated that other algorithms will be supported at a later time.

1..1

checksum value

spdx:checksumValue

rdfs:Literal typed as xsd:hexBinary

This property provides a lower case hexadecimal encoded digest value produced using a specific algorithm.

1..1

4.11 Data Service

Class name Data Service
Obligation Optional
URI

dcat:DataService

Usage note

A collection of operations that provides access to one or more datasets or data processing functions.

Reference

§ 6.8 Class: Data Service [VOCAB-DCAT-2]

4.11.1 Mandatory properties for Data Service

Property

URI

Range

Usage note

Card.

endpoint URL

dcat:endpointURL

rdfs:Resource

The root location or primary endpoint of the Service (an IRI).

1..n

title

dct:title

rdfs:Literal

This property contains a name given to the Data Service. This property can be repeated for parallel language versions of the name - see § 9. Accessibility and Multilingual Aspects.

1..n

4.11.3 Optional properties for Data Service

Property

URI

Range

Usage note

Card.

access rights

dct:accessRights

dct:RightsStatement

This property MAY include information regarding access or restrictions based on privacy, security, or other policies.

For INSPIRE metadata, this property SHOULD be used with the URIs of the "Limitations on public access" code list operated by the INSPIRE Registry [INSPIRE-LPA].

0..1

+conforms to

dct:conformsTo

dct:Standard

This property is used to indicate the general standard or specification that the Data Service endpoints implement.

0..n

+contact point

dcat:contactPoint

vcard:Kind

This property contains contact information that can be used for sending comments about the Data Service.

0..n

+creation date

dct:created

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date on which the Data Service has been first created.

0..1

+creator

dct:creator

foaf:Agent

This property refers to the Agent primarily responsible for producing the Data Service..

0..n

description

dct:description

rdfs:Literal

This property contains a free-text account of the Data Service. This property can be repeated for parallel language versions of the description - see § 9. Accessibility and Multilingual Aspects.

0..n

+identifier

dct:identifier

rdfs:Literal

This property contains the main identifier for the Data Service, e.g. the URI or other unique identifier in the context of the Catalogue.

0..n

+language

dct:language

dct:LinguisticSystem

This property refers to a language supported by the Data Service. This property can be repeated if multiple languages are supported in the Data Service - see § 9. Accessibility and Multilingual Aspects.

0..n

licence

dct:license

dct:LicenseDocument

This property contains the licence under which the Data Service is made available.

0..1

+publisher

dct:publisher

foaf:Agent

This property refers to an Agent (organisation) responsible for making the Data Service available.

0..1

+qualified attribution

prov:qualifiedAttribution

prov:Attribution

This property refers to a link to an Agent having some form of responsibility for the Data Service.

0..n

+reference system

dct:conformsTo

dct:Standard

This property SHOULD be used to specify the reference system used in the Data Service.

Spatial reference systems SHOULD be specified by using the corresponding URIs from the “EPSG coordinate reference systems” register operated by OGC [OGC-EPSG].

0..n

+release date

dct:issued

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date of formal issuance (e.g., publication) of the Data Service.

0..1

+rights holder

dct:rightsHolder

foaf:Agent

This property refers to an Agent (organisation) holding rights on the Data Service..

0..n

+service category

dct:type

skos:Concept

In GeoDCAT-AP, this property SHOULD take as value one of the URIs of the "Classification of spatial data services" code list operated by the INSPIRE Registry [INSPIRE-SDSC].

0..1

+service type

dct:type

skos:Concept

In GeoDCAT-AP, this property SHOULD take as value one of the URIs of the "Spatial data service types" code list operated by the INSPIRE Registry [INSPIRE-SDST].

0..1

+theme / category

dcat:theme

skos:Concept

This property refers to a Category of the Data Service. A Data Service may be associated with multiple Categories.

0..n

+spatial / geographic coverage

dct:spatial

dct:Location

This property refers to a geographic region that is covered by the Data Service.

0..n

+spatial resolution

dqv:hasQualityMeasurement

dqv:QualityMeasurement

Refers to the performed quality measurements.

In GeoDCAT-AP, this property is used to specify "spatial resolution", as defined in [INSPIRE-MD-REG], [ISO-19115], and [ISO-19115-1].

0..n

+spatial resolution in metres

dcat:spatialResolutionInMeters

xsd:decimal

This property refers to the minimum spatial separation resolvable in a Data Service, measured in metres.

0..n

+spatial resolution as text

rdfs:comment

rdfs:Literal

This property MAY be used to express spatial resolution as free-text, when it cannot be specified via dqv:hasQualityMeasurement and dcat:spatialResolutionInMeters.

0..n

+temporal coverage

dct:temporal

dct:PeriodOfTime

This property refers to a temporal period that the Data Service covers.

0..n

+temporal resolution

dcat:temporalResolution

rdfs:Literal typed as xsd:duration

This property refers to the minimum time period resolvable in the Data Service.

0..n

+topic category

dct:subject

skos:Concept

In GeoDCAT-AP, this property SHOULD take as value one of the URIs of the "Topic categories in accordance with EN ISO 19115" code list operated by the INSPIRE Registry [INSPIRE-TC].

0..n

+type

dct:type

skos:Concept

In GeoDCAT-AP, this property SHOULD take as value one of the URIs of the "Resource types" code list operated by the INSPIRE Registry [INSPIRE-RT] - namely the one corresponding to "Spatial data service".

0..1

+update / modification date

dct:modified

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the most recent date on which the Data Service was changed or modified.

0..1

+was used by

prov:wasUsedBy

prov:Activity

This property refers to an Activity that used the Data Service.

In GeoDCAT-AP, this property MAY be used to specify a testing Activity over a Data Service, against a given Standard, producing as output a conformance degree.

0..n

+custodian

geodcat:custodian

foaf:Agent

Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource [ISO-19115].

0..n

+distributor

geodcat:distributor

foaf:Agent

Party who distributes the resource [ISO-19115].

0..n

+originator

geodcat:originator

foaf:Agent

Party who created the resource [ISO-19115].

0..n

+principal investigator

geodcat:principalInvestigator

foaf:Agent

Key party responsible for gathering information and conducting research [ISO-19115].

0..n

+processor

geodcat:processor

foaf:Agent

Party who has processed the data in a manner such that the resource has been modified [ISO-19115].

0..n

+resource provider

geodcat:resourceProvider

foaf:Agent

Party that supplies the resource [ISO-19115].

0..n

+user

geodcat:user

foaf:Agent

Party who uses the resource [ISO-19115].

0..n

4.11.4 Deprecated properties for Data Service

Property

URI

Replaced by

Deprecated in

endpoint URL

foaf:homepage

dcat:endpointURL

GeoDCAT-AP 2.0.0

+keyword / tag

dc:subject

dcat:keyword

GeoDCAT-AP 2.0.0

serves dataset

dct:hasPart

dcat:servesDataset

GeoDCAT-AP 2.0.0

+spatial resolution

rdfs:comment

dcat:spatialResolutionInMeters

dqv:hasQualityMeasurement

GeoDCAT-AP 2.0.0

+theme / category

dct:subject

dcat:theme

GeoDCAT-AP 2.0.0

Note
Note

4.11.5 Examples for Data Service

4.12 Dataset

Class name Dataset
Obligation Mandatory
URI

dcat:Dataset

Usage note

A conceptual entity that represents the information published.

Reference

§ 6.6 Class: Dataset [VOCAB-DCAT-2]

4.12.1 Mandatory properties for Dataset

Property

URI

Range

Usage note

Card.

description

dct:description

rdfs:Literal

This property contains a free-text account of the Dataset. This property can be repeated for parallel language versions of the description - see § 9. Accessibility and Multilingual Aspects.

1..n

title

dct:title

rdfs:Literal

This property contains a name given to the Dataset. This property can be repeated for parallel language versions of the name - see § 9. Accessibility and Multilingual Aspects.

1..n

4.12.3 Optional properties for Dataset

Property

URI

Range

Usage note

Card.

access rights

dct:accessRights

dct:RightsStatement

This property refers to information that indicates whether the Dataset is open data, has access restrictions or is not public.

For INSPIRE metadata, this property SHOULD be used with the URIs of the "Limitations on public access" code list operated by the INSPIRE Registry [INSPIRE-LPA].

0..1

+creation date

dct:created

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date on which the Dataset has been first created.

0..1

creator

dct:creator

foaf:Agent

This property refers to the Agent primarily responsible for producing the Dataset.

0..1

conforms to

dct:conformsTo

dct:Standard

This property refers to an implementing rule or other specification.

0..n

documentation

foaf:page

foaf:Document

This property refers to a page or document about this Dataset.

0..n

frequency

dct:accrualPeriodicity

dct:Frequency

This property refers to the frequency at which the Dataset is updated.

0..1

has version

dct:hasVersion

dcat:Dataset

This property refers to a related Dataset that is a version, edition, or adaptation of the described Dataset.

0..n

identifier

dct:identifier

rdfs:Literal

This property contains the main identifier for the Dataset, e.g., the URI or other unique identifier in the context of the Catalogue.

0..n

is referenced by

dct:isReferencedBy

rdfs:Resource

This property is about a related resource, such as a publication, that references, cites, or otherwise points to the Dataset.

0..n

is version of

dct:isVersionOf

dcat:Dataset

This property refers to a related Dataset of which the described Dataset is a version, edition, or adaptation.

0..n

landing page

dcat:landingPage

foaf:Document

This property refers to a Web page that provides access to the Dataset, its Distributions and/or additional information. It is intended to point to a landing page at the original data provider, not to a page on a site of a third party, such as an aggregator.

0..n

language

dct:language

dct:LinguisticSystem

This property refers to a language of the Dataset. This property can be repeated if there are multiple languages in the Dataset - see § 9. Accessibility and Multilingual Aspects.

0..n

other identifier

adms:identifier

adms:Identifier

This property refers to a secondary identifier of the Dataset, such as MAST/ADS [MAST-ADS], [DataCite], [DOI], [EZID] or [W3ID].

0..n

provenance

dct:provenance

dct:ProvenanceStatement

This property contains a statement about the lineage of a Dataset.

0..n

qualified attribution

prov:qualifiedAttribution

prov:Attribution

This property refers to a link to an Agent having some form of responsibility for the Dataset.

0..n

qualified relation

dcat:qualifiedRelation

dcat:Relationship

This property provides a link to a description of a relationship with another resource.

0..n

release date

dct:issued

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date of formal issuance (e.g., publication) of the Dataset.

0..1

+reference system

dct:conformsTo

dct:Standard

This property SHOULD be used to specify the reference system used in the Dataset.

Spatial reference systems SHOULD be specified by using the corresponding URIs from the “EPSG coordinate reference systems” register operated by OGC [OGC-EPSG].

0..n

+rights holder

dct:rightsHolder

foaf:Agent

This property refers to an Agent (organisation) holding rights on the Dataset.

0..n

sample

adms:sample

dcat:Distribution

This property refers to a sample Distribution of the Dataset.

0..n

source

dct:source

dcat:Dataset

This property refers to a related Dataset from which the described Dataset is derived.

0..n

+spatial resolution

dqv:hasQualityMeasurement

dqv:QualityMeasurement

Refers to the performed quality measurements.

In GeoDCAT-AP, this property is used to specify "spatial resolution", as defined in [INSPIRE-MD-REG], [ISO-19115], and [ISO-19115-1].

0..n

spatial resolution in metres

dcat:spatialResolutionInMeters

xsd:decimal

This property refers to the minimum spatial separation resolvable in a Dataset, measured in metres.

0..n

+spatial resolution as text

rdfs:comment

rdfs:Literal

This property MAY be used to express spatial resolution as free-text, when it cannot be specified via dqv:hasQualityMeasurement and dcat:spatialResolutionInMeters.

0..n

temporal resolution

dcat:temporalResolution

rdfs:Literal typed as xsd:duration

This property refers to the minimum time period resolvable in the Dataset.

0..n

+topic category

dct:subject

skos:Concept

In GeoDCAT-AP, this property SHOULD take as value one of the URIs of the "Topic categories in accordance with EN ISO 19115" code list operated by the INSPIRE Registry [INSPIRE-TC].

0..n

type

dct:type

skos:Concept

This property refers to the type of the Dataset. A controlled vocabulary for the values has not been established in [DCAT-AP].

In GeoDCAT-AP, this property SHOULD take as value one of the URIs of the "Resource types" code list operated by the INSPIRE Registry [INSPIRE-RT]. For Datasets, the possible values are those corresponding to "Spatial data set" and "Spatial data set series".

0..1

update / modification date

dct:modified

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the most recent date on which the Dataset was changed or modified.

0..1

version

owl:versionInfo

rdfs:Literal

This property contains a version number or other version designation of the Dataset.

0..1

version notes

adms:versionNotes

rdfs:Literal

This property contains a description of the differences between this version and a previous version of the Dataset. This property can be repeated for parallel language versions of the version notes - see § 9. Accessibility and Multilingual Aspects.

0..n

was generated by

prov:wasGeneratedBy

prov:Activity

This property refers to an Activity that generated, or provides the business context for, the creation of the Dataset.

0..n

+was used by

prov:wasUsedBy

prov:Activity

This property refers to an Activity that used the Dataset.

In GeoDCAT-AP, this property MAY be used to specify a testing Activity over a Dataset, against a given Standard, producing as output a conformance degree.

0..n

+custodian

geodcat:custodian

foaf:Agent

Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource [ISO-19115].

0..n

+distributor

geodcat:distributor

foaf:Agent

Party who distributes the resource [ISO-19115].

0..n

+originator

geodcat:originator

foaf:Agent

Party who created the resource [ISO-19115].

0..n

+principal investigator

geodcat:principalInvestigator

foaf:Agent

Key party responsible for gathering information and conducting research [ISO-19115].

0..n

+processor

geodcat:processor

foaf:Agent

Party who has processed the data in a manner such that the resource has been modified [ISO-19115].

0..n

+resource provider

geodcat:resourceProvider

foaf:Agent

Party that supplies the resource [ISO-19115].

0..n

+user

geodcat:user

foaf:Agent

Party who uses the resource [ISO-19115].

0..n

4.12.4 Deprecated properties for Dataset

Property

URI

Replaced by

Deprecated in

spatial resolution

rdfs:comment

dcat:spatialResolutionInMeters

dqv:hasQualityMeasurement

GeoDCAT-AP 2.0.0

Note

4.12.5 Examples for Dataset

4.13 Distribution

Class name Distribution
Obligation Recommended
URI

dcat:Distribution

Usage note

A physical embodiment of the Dataset in a particular format.

Reference

§ 6.7 Class: Distribution [VOCAB-DCAT-2]

4.13.1 Mandatory properties for Distribution

Property

URI

Range

Usage note

Card.

access URL

dcat:accessURL

rdfs:Resource

This property contains a URL that gives access to a Distribution of the Dataset. The resource at the access URL may contain information about how to get the Distribution.

1..n

4.13.3 Optional properties for Distribution

Property

URI

Range

Usage note

Card.

+access rights

dct:accessRights

dct:RightsStatement

This property MAY include information regarding access or restrictions based on privacy, security, or other policies.

For INSPIRE metadata, this property SHOULD be used with the URIs of the "Limitations on public access" code list operated by the INSPIRE Registry [INSPIRE-LPA].

0..1

access service

dcat:accessService

dcat:DataService

This property refers to a Data Service that gives access to the Distribution of the Dataset.

0..n

byte size

dcat:byteSize

rdfs:Literal typed as xsd:decimal

This property contains the size of a Distribution in bytes.

0..1

checksum

spdx:checksum

spdx:Checksum

This property provides a mechanism that can be used to verify that the contents of a Distribution have not changed. The checksum is related to the download URL.

0..1

compression format

dcat:compressFormat

dct:MediaType

This property refers to the format of the file in which the data is contained in a compressed form, e.g., to reduce the size of the downloadable file. It SHOULD be expressed using a media type as defined in the official register of media types managed by IANA [IANA-MEDIA-TYPES].

0..1

documentation

foaf:page

foaf:Document

This property refers to a page or document about this Distribution.

0..n

download URL

dcat:downloadURL

rdfs:Resource

This property contains a URL that is a direct link to a downloadable file in a given format.

0..n

has policy

odrl:hasPolicy

odrl:Policy

This property refers to the policy expressing the rights associated with the Distribution if using the [VOCAB-ODRL] vocabulary.

0..1

language

dct:language

dct:LinguisticSystem

This property refers to a language used in the Distribution. This property can be repeated if the metadata is provided in multiple languages - see § 9. Accessibility and Multilingual Aspects.

0..n

linked schemas

dct:conformsTo

dct:Standard

This property refers to an established schema to which the described Distribution conforms.

0..n

media type

dcat:mediaType

dct:MediaType

This property refers to the media type of the Distribution as defined in the official register of media types managed by IANA [IANA-MEDIA-TYPES].

0..1

packaging format

dcat:packageFormat

dct:MediaType

This property refers to the format of the file in which one or more data files are grouped together, e.g. to enable a set of related files to be downloaded together. It SHOULD be expressed using a media type as defined in the official register of media types managed by IANA [IANA-MEDIA-TYPES].

0..1

+reference system

dct:conformsTo

dct:Standard

This property SHOULD be used to specify the reference system used in the Distribution.

Spatial reference systems SHOULD be specified by using the corresponding URIs from the “EPSG coordinate reference systems” register operated by OGC [OGC-EPSG].

0..n

release date

dct:issued

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date of formal issuance (e.g., publication) of the Distribution.

0..1

+representation technique

adms:representationTechnique

skos:Concept

This property MAY be used to provide more information about the format in which an Distribution is released. This is different from the file format as, for example, a ZIP file (file format) could contain an XML schema (representation technique).

In GeoDCAT-AP, this property SHOULD be used to express the spatial representation type (grid, vector, tin), by using a dedicated code list.

0..1

rights

dct:rights

dct:RightsStatement

This property refers to a statement that specifies rights associated with the Distribution.

0..1

+spatial resolution

dqv:hasQualityMeasurement

dqv:QualityMeasurement

Refers to the performed quality measurements.

In GeoDCAT-AP, this property is used to specify "spatial resolution", as defined in [INSPIRE-MD-REG], [ISO-19115], and [ISO-19115-1].

0..n

spatial resolution in metres

dcat:spatialResolutionInMeters

xsd:decimal

This property refers to the minimum spatial separation resolvable in a Distribution, measured in metres.

0..n

+spatial resolution as text

rdfs:comment

rdfs:Literal

This property MAY be used to express spatial resolution types that cannot be specified via dcat:spatialResolutionInMeters - i.e., spatial resolution as equivalent scale, angular distance, vertical distance.

0..n

status

adms:status

skos:Concept

This property refers to the maturity of the Distribution. It MUST take one of the values Completed, Deprecated, Under Development, Withdrawn from the ADMS status [ADMS-SKOS] vocabulary.

0..1

temporal resolution

dcat:temporalResolution

rdfs:Literal typed as xsd:duration

This property refers to the minimum time period resolvable in the Distribution.

0..n

title

dct:title

rdfs:Literal

This property contains a name given to the Distribution. This property can be repeated for parallel language versions of the description - see § 9. Accessibility and Multilingual Aspects.

0..n

update / modification date

dct:modified

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the most recent date on which the Distribution was changed or modified.

0..1

4.13.4 Deprecated properties for Distribution

Property

URI

Replaced by

Deprecated in

spatial resolution

rdfs:comment

dcat:spatialResolutionInMeters

dqv:hasQualityMeasurement

GeoDCAT-AP 2.0.0

Note

4.13.5 Examples for Distribution

4.14 Document

Note
Class name Document
Obligation Optional
URI

foaf:Document

Usage note

A textual resource intended for human consumption that contains information, e.g., a Web page about a Dataset.

Reference

§ Class: foaf:Document [FOAF]

4.14.2 Examples for Document

4.15 Identifier

Class name Identifier
Obligation Optional
URI

adms:Identifier

Usage note

An identifier in a particular context, consisting of the string that is the identifier; an optional identifier for the identifier scheme; an optional identifier for the version of the identifier scheme; an optional identifier for the agency that manages the identifier scheme

Reference

§ 5.2.6 Identifier [VOCAB-ADMS]

4.15.1 Mandatory property for Identifier

Property

URI

Range

Usage note

Card.

notation

skos:notation

rdfs:Literal typed with the URI of one of the members of the DataCite Resource Identifier Scheme [DataCite-RIS]

This property contains a string that is an identifier in the context of the identifier scheme referenced by its datatype.

0..1

4.16 Kind

Note
Class name Kind
Obligation Optional
URI

vcard:Kind

Usage note

A description following the [VCARD-RDF] specification, e.g. to provide telephone number and e-mail address for a contact point. Note that the class vcard:Kind is the parent class for the four explicit types of vCards (vcard:Individual, vcard:Organization, vcard:Location, vcard:Group).

Reference

§ Kind [VCARD-RDF]

4.16.2 Optional properties for Kind

Note

Property

URI

Range

Usage note

Card.

+address

vcard:hasAddress

vcard:Address

This property MAY be used to specify the postal address of the Kind.

0..1

+affiliation

vcard:organization-name

rdfs:Literal

This property MAY be used to specify the affiliation of the Kind. This property can be repeated for different versions of the name (e.g. the name in different languages) - see § 9. Accessibility and Multilingual Aspects.

0..1

+phone

vcard:hasTelephone

owl:Thing

This property MAY be used to provide the phone number of the Kind, specified using fully qualified tel: URI scheme [RFC3966].

0..1

4.16.3 Examples for Kind

4.17 Licence Document

Class name Licence Document
Obligation Recommended
URI

dct:LicenseDocument

Usage note

A legal document giving official permission to do something with a resource.

Reference

§ Term name: LicenseDocument [DCTERMS]

4.17.2 Optional property for Licence Document

Note

Property

URI

Range

Usage note

Card.

+licence text

rdfs:label

rdfs:Literal

This property contains the text of the Licence Document. This property can be repeated for parallel language versions of the name - see § 9. Accessibility and Multilingual Aspects.

0..n

4.17.3 Examples for Licence Document

4.18 Location

Class name Location
Obligation Optional
URI

dct:Location

Usage note

A spatial region or named place. It can be represented using a controlled vocabulary or with geographic coordinates.

Reference

§ Term name: Location [DCTERMS]

4.18.2 Optional properties for Location

Note

Property

URI

Range

Usage note

Card.

+gazetteer

skos:inScheme

skos:ConceptScheme

This property MAY be used to specify the gazetteer to which the Location belongs.

0..1

+geographic identifier

dct:identifier

rdfs:Literal

This property contains the geographic identifier for the Location, e.g., the URI or other unique identifier in the context of the relevant gazetteer.

0..n

+geographic name

skos:prefLabel

rdfs:Literal

This property contains a preferred label of the Location. This property can be repeated for parallel language versions of the label - see § 9. Accessibility and Multilingual Aspects.

1..n

geometry

locn:geometry

rdfs:Literal typed as gsp:wktLiteral or gsp:gmlLiteral

This property associates any resource with the corresponding geometry.

0..1

4.18.3 Examples for Location

4.19 Media Type

Note
Class name Media type
Obligation Optional
URI

dct:MediaType

Usage note

A media type, e.g. the format of a computer file.

Reference

§ Term name: MediaType [DCTERMS]

4.19.2 Examples for Media Type

4.20 +Metric

Note
Class name Metric
Obligation Optional
URI

dqv:Metric

Usage note

Represents a standard to measure a quality dimension. An observation (instance of dqv:QualityMeasurement) assigns a value in a given unit to a Metric.

In GeoDCAT-AP, this class is used to define individuals corresponding to the different types of spatial resolution.

Reference

§ 4.2 Class: Metric [VOCAB-DQV]

4.20.1 Instances of Metric

An abridged version of the definition of these instances is shown in Example 18.

Instance

URI

Class

Usage note

+Spatial resolution as angular distance

geodcat:spatialResolutionAsAngularDistance

dqv:Metric

Spatial resolution expressed as angular distance [ISO-19115-1], by using a decimal degree.

+Spatial resolution as distance

geodcat:spatialResolutionAsDistance

dqv:Metric

Spatial resolution expressed as distance. It corresponds to the notion of spatial resolution as "ground distance" of [ISO-19115] and "horizontal ground distance" of [ISO-19115-1].

+Spatial resolution as equivalent scale

geodcat:spatialResolutionAsScale

dqv:Metric

Spatial resolution expressed as equivalent scale [ISO-19115], [ISO-19115-1], by using a representative fraction (e.g., 1:1,000, 1:1,000,000).

+Spatial resolution as vertical distance

geodcat:spatialResolutionAsVerticalDistance

dqv:Metric

Spatial resolution expressed as vertical distance [ISO-19115-1].

In GeoDCAT-AP, this property is typically used for Catalogues, Data Services, and Datasets. However, no domain restriction is defined, and therefore this property can be used on any resource.

4.20.3 Examples for Metric

4.21 Period of Time

Class name Period of time
Obligation Optional
URI

dct:PeriodOfTime

Usage note

An interval of time that is named or defined by its start and end dates.

Reference

§ Term name: PeriodOfTime [DCTERMS]

4.21.2 Optional properties for Period of Time

Property

URI

Range

Usage note

Card.

beginning

time:hasBeginning

time:Instant

This property contains the beginning of a period or interval.

0..1

end

time:hasEnd

time:Instant

This property contains the end of a period or interval

0..1

Note

4.21.3 Deprecated properties for Period of Time

Property

URI

Replaced by

Deprecated in

start date

schema:startDate

dcat:startDate

[DCAT-AP-20191120]

end date

schema:endDate

dcat:endDate

[DCAT-AP-20191120]

Note

4.21.4 Examples for Period of Time

Example 20 is equivalent to Example 19, but it uses the [OWL-TIME] properties in § 4.21.2 Optional properties for Period of Time.

4.22 Provenance Statement

Note
Class name Provenance Statement
Obligation Optional
URI

dct:ProvenanceStatement

Usage note

A statement of any changes in ownership and custody of a resource since its creation that are significant for its authenticity, integrity, and interpretation

Reference

§ Term name: ProvenanceStatement [DCTERMS]

4.22.2 Examples for Provenance Statement

4.23 +Quality Measurement

Note
Class name Quality Measurement
Obligation Optional
URI

dqv:QualityMeasurement

Usage note

Represents the evaluation of a given resource (as a Data Service, Dataset, or Distribution) against a specific quality metric.

In GeoDCAT-AP, this class corresponds to the notion of "spatial resolution", as defined in [INSPIRE-MD-REG], [ISO-19115], and [ISO-19115-1].

Reference

§ 4.1 Class: Quality Measurement [VOCAB-DQV]

4.23.2 Examples for Quality Measurement

4.24 Relationship

Class name Relationship
Obligation Optional
URI

dcat:Relationship

Usage note

An association class for attaching additional information to a relationship between DCAT Resources

Reference

§ 6.12 Class: Relationship [VOCAB-DCAT-2]

4.24.1 Mandatory properties for Relationship

Property

URI

Range

Usage note

Card.

had role

dcat:hadRole

dcat:Role

This property refers to the function of an entity or agent with respect to another entity or resource.

1..n

relation

dct:relation

rdfs:Resource

This property refers to the resource related to the source resource.

1..n

4.25 Rights Statement

Note
Class name Rights statement
Obligation Optional
URI

dct:RightsStatement

Usage note

A statement about the intellectual property rights (IPR) held in or over a resource, a legal document giving official permission to do something with a resource, or a statement about access rights.

Reference

§ Term name: RightsStatement [DCTERMS]

4.26 Standard

Note
Class name Standard
Obligation Optional
URI

dct:Standard

Usage note

A standard or other specification to which a Catalogue, Catalogue Record, Data Service, Dataset, or Distribution conforms.

Reference

§ Term name: Standard [DCTERMS]

4.26.2 Optional properties for Standard

Note

Property

URI

Range

Usage note

Card.

+creation date

dct:created

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the date on which the Standard has been first created.

0..1

+update / modification date

dct:modified

rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the most recent date on which the Standard was changed or modified.

1..1

4.26.3 Examples for Standard

The following examples show the specification of different types of Standards.

5. Controlled Vocabularies

5.1 Requirements for controlled vocabularies

The following is a list of requirements that were identified for the controlled vocabularies to be recommended in this Application Profile.

Controlled vocabularies SHOULD:

These criteria do not intend to define a set of requirements for controlled vocabularies in general; they are only intended to be used for the selection of the controlled vocabularies that are proposed for this Application Profile.

5.2 Controlled vocabularies to be used

In the table below, a number of properties are listed with controlled vocabularies that MUST be used for the listed properties. The declaration of the following controlled vocabularies as mandatory ensures a minimum level of interoperability.

Compared with [DCAT-AP-20200608], GeoDCAT-AP makes use of additional controlled vocabularies mandated by [INSPIRE-MD-REG], and operated by the INSPIRE Registry - with the only exceptions of the coordinate reference systems register maintained by OGC [OGC-EPSG].

For two of these controlled vocabularies, namely the INSPIRE spatial data themes [INSPIRE-THEMES] and the ISO topic categories [INSPIRE-TC], the GeoDCAT-AP Working Group has defined a set of harmonised mappings to the EU Vocabularies Data Themes [EUV-THEMES], in order to facilitate the identification of the relevant theme in [EUV-THEMES] for geospatial metadata. The status of this work, along with links to a machine readable representation of the mappings, is documented on a dedicated page in Joinup [GeoDCAT-ACV].

Property URI

Used for Class

Vocabulary name

Vocabulary URI

Usage note

adms:status

Distribution

ADMS status [ADMS-SKOS] vocabulary

http://purl.org/adms/status/

The list of terms in the ADMS status vocabulary is included in the [ADMS] specification

+dcat:hadRole

Attribution

INSPIRE Responsible Party Roles [INSPIRE-RPR]

http://inspire.ec.europa.eu/metadata-codelist/ResponsiblePartyRole

GeoDCAT-AP extension.

dcat:mediaType

Distribution

IANA Media Types [IANA-MEDIA-TYPES]

http://www.iana.org/assignments/media-types

 

dcat:theme

Dataset

Dataset Theme Vocabulary [EUV-THEMES]

INSPIRE Spatial Data Themes [INSPIRE-THEMES]

http://publications.europa.eu/resource/authority/data-theme

http://inspire.ec.europa.eu/theme

The values to be used for this property are the URIs of the concepts in the vocabulary.

+dcat:theme

Catalogue

Data Service

The use of this property for Catalogues and Data Services is a GeoDCAT-AP extension.

dcat:themeTaxonomy

Catalogue

Dataset Theme Vocabulary [EUV-THEMES]

http://publications.europa.eu/resource/authority/data-theme

The value to be used for this property is the URI of the vocabulary itself, i.e. the concept scheme, not the URIs of the concepts in the vocabulary.

dcatap:availability

Distribution

Distribution availability vocabulary [DCAT-AP-DA]

http://data.europa.eu/r5r/availability/

The list of terms for the avalability levels of a dataset distribution in the DCAT-AP specification.

dct:accessRights

Data Service

Dataset

EU Vocabularies Access rights [EUV-AR]

http://publications.europa.eu/resource/authority/access-right

INSPIRE Limitations on Public Access [INSPIRE-LPA]

http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess

GeoDCAT-AP extension.

+dct:accessRights

Catalogue

Distribution

EU Vocabularies Access rights [EUV-AR]

http://publications.europa.eu/resource/authority/access-right

INSPIRE Limitations on Public Access [INSPIRE-LPA]

http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess

GeoDCAT-AP extension.

dct:accrualPeriodicity

Dataset

EU Vocabularies Frequency Named Authority List [EUV-FREQ]

http://publications.europa.eu/resource/authority/frequency

 

+dct:conformsTo

Data Service

Dataset

Distribution

OGC EPSG Coordinate Reference Systems Register [OGC-EPSG]

http://www.opengis.net/def/crs/EPSG/0/

GeoDCAT-AP extension.

Data Service

INSPIRE Protocol Values [INSPIRE-PV]

https://inspire.ec.europa.eu/metadata-codelist/ProtocolValue

dct:format

Distribution

EU Vocabularies File Type Named Authority List [EUV-FT]

http://publications.europa.eu/resource/authority/file-type

 

dct:language

Catalogue

Catalogue Record

Dataset

Distribution

EU Vocabularies Languages Named Authority List [EUV-LANG]

http://publications.europa.eu/resource/authority/language

 

dct:publisher

Catalogue

Dataset

EU Vocabularies Corporate bodies Named Authority List [EUV-CB]

http://publications.europa.eu/resource/authority/corporate-body

The Corporate bodies NAL must be used for European institutions and a small set of international organisations. In case of other types of organisations, national, regional or local vocabularies should be used.

+dct:publisher

Data Service

The use of this property for Data Services is a GeoDCAT-AP extension.

dct:spatial

Catalogue

Dataset

EU Vocabularies Continents Named Authority List [EUV-CONT], EU Vocabularies Countries Named Authority List [EUV-COUNTRIES], EU Vocabularies Places Named Authority List [EUV-PLACES], [GEONAMES]

http://publications.europa.eu/resource/authority/continent

http://publications.europa.eu/resource/authority/country

http://publications.europa.eu/resource/authority/place

http://sws.geonames.org/

The EU Vocabularies Name Authority Lists must be used for continents, countries and places that are in those lists; if a particular location is not in one of the mentioned Named Authority Lists, [GEONAMES] URIs must be used.

+dct:spatial

Data Service

The use of this property for Data Services is a GeoDCAT-AP extension.

+dct:subject

Catalogue

Data Service

Dataset

INSPIRE Topic Categories [INSPIRE-TC]

http://inspire.ec.europa.eu/metadata-codelist/TopicCategory

GeoDCAT-AP extension.

dct:type

Agent

ADMS publisher type [ADMS-SKOS] vocabulary

http://purl.org/adms/publishertype/

The list of terms in the ADMS publisher type vocabulary is included in the [ADMS] specification

dct:type

Dataset

INSPIRE Resource Types [INSPIRE-RT]

http://inspire.ec.europa.eu/metadata-codelist/ResourceType

GeoDCAT-AP extension.

No code list defined in [DCAT-AP-20200608].

+dct:type

Data Service

+dct:type

Data Service

INSPIRE Spatial Data Service Categories [INSPIRE-SDSC]

http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory

GeoDCAT-AP extension.

+dct:type

Data Service

INSPIRE Spatial Data Service Types [INSPIRE-SDST]

http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType

GeoDCAT-AP extension.

dct:type

Licence Document

ADMS licence type [ADMS-SKOS] vocabulary

http://purl.org/adms/licencetype/

The list of terms in the ADMS licence type vocabulary is included in the [ADMS] specification

+dct:type

Standard

INSPIRE Glossary [INSPIRE-GLOSSARY]

http://inspire.ec.europa.eu/glossary/SpatialReferenceSystem

http://inspire.ec.europa.eu/glossary/TemporalReferenceSystem

GeoDCAT-AP extension.

When the Standard is a spatial or temporal reference system, the relevant URIs from the [INSPIRE-GLOSSARY] SHOULD be used.

+dct:type

Test Result (linked from a prov:Activity).

INSPIRE Degree of Conformity [INSPIRE-DoC]

https://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity

GeoDCAT-AP extension.

+sdmx-attribute:unitMeasure

Quality Measurement

QUDT Units Vocabulary [QUDT-UNITS]

http://www.qudt.org/vocab/unit

GeoDCAT-AP extension.

5.3 Other controlled vocabularies

In addition to the proposed common vocabularies in § 5.2 Controlled vocabularies to be used, which are mandatory to ensure minimal interoperability, implementers are encouraged to publish and to use further region or domain-specific vocabularies that are available online. While those may not be recognised by general implementations of the Application Profile, they may serve to increase interoperability across applications in the same region or domain. Examples are the full set of concepts in EuroVoc [EUV-EUROVOC], the CERIF standard vocabularies [CERIF-VOCS], the Dewey Decimal Classification [DDC] and numerous other schemes.

For geospatial metadata, the working group has identified the following additional vocabularies:

5.4 Licence vocabularies

Concerning licence vocabularies, implementers are encouraged to use widely recognised licences such as Creative Commons licences [CC], and in particular the CC Zero Public Domain Dedication [CC0] or CC-BY Attribution 4.0 International [CC-BY], or the Open Data Commons Public Domain Dedication and License (PDDL) [PDDL]. Often there is applicable legislation or a licency policy in place which determine the set of licences to be used. They may recommend the use of an open government licence such as the UK Open Government Licence [UKOGL].

Further activities in this area are undertaken by the Open Data Institute [ODI] with the Open Data Rights Statement Vocabulary [ODRS] and by the Open Digital Rights Language (ODRL) Initiative [VOCAB-ODRL].

6. Conformance

As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The key words MAY, MUST, MUST NOT, RECOMMENDED, SHOULD, and SHOULD NOT in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

6.1 Provider requirements

In order to conform to this Application Profile, an application that provides metadata MUST:

For the properties listed in the table in § 5.2 Controlled vocabularies to be used, the associated controlled vocabularies MUST be used. Additional controlled vocabularies MAY be used.

In addition to the mandatory properties, any of the recommended and optional properties defined in § 4. Application Profile Properties per Class MAY be provided.

Recommended and optional classes may have mandatory properties, but those only apply if and when an instance of such a class is present in a description.

6.2 Receiver requirements

In order to conform to this Application Profile, an application that receives metadata MUST be able to:

As stated in § 2. Terminology used in the Application Profile, "processing" means that receivers must accept incoming data and transparently provide these data to applications and services. It does neither imply nor prescribe what applications and services finally do with the data (parse, convert, store, make searchable, display to users, etc.).

7. Agent Roles

This section is non-normative.

GeoDCAT-AP supports the 11 agent roles defined in [INSPIRE-MD-REG] and [ISO-19115] by using two different but not mutually exclusive approaches.

In the first approach, roles are mapped to specific properties. In particular, GeoDCAT-AP makes use of the relevant properties from [DCAT-AP-20200608] and [DCTERMS], which overall cover 4 of the relevant roles - namely, dcat:contactPoint, dct:creator, dct:publisher, and dct:rightsHolder (not supported in [DCAT-AP-20200608]). The remaining 7 are covered by the corresponding properties defined in the GeoDCAT-AP namespace - namely, geodcat:custodian, geodcat:distributor, geodcat:originator, geodcat:principalInvestigator, geodcat:processor, geodcat:resourceProvider, and geodcat:user.

It is important to note that, following [INSPIRE-MD-REG] and [ISO-19115], in GeoDCAT-AP all these agent roles can be specified on Catalogues, Catalogue Records, Datasets, and Data Services.

The second and more general approach is based on [PROV-O], where agent roles are specified via a “qualified attribution” (prov:qualifiedAttribution). More precisely, the relevant Agent is specified via property prov:agent, whereas the role is specified with property dcat:hadRole, which takes as value a skos:Concept describing that role - as those included in the relevant code list operated by the INSPIRE Registry [INSPIRE-RPR]. This pattern is illustrated in Example 5.

The [PROV-O]-based approach is meant to give data providers an extension mechanism to specify, in a harmonised way, any kind of role, and, possibly, to attach additional information to the role and the associated Agent. As such, it MAY be used in combination with or to complement the property-based approach, but it MUST NOT replace it. For instance, it can be used to specify roles not covered by the agent role properties used in GeoDCAT-AP, and/or to specify additional information that cannot be expressed via a property (as the period during which an Agent covered a given role).

More details on these solutions are available in § B.6.16 Responsible party and metadata point of contact - *Dataset responsible party and *Metadata point of contact.

8. Conformance Test Results

This section is non-normative.

Following [INSPIRE-MD-REG] and [ISO-19115], GeoDCAT-AP supports the specification of test results to assess the degree of conformity of a resource (i.e., a Catalogue, a Dataset, a Data Service) with a given specification (e.g., a standard, a set of implementing rules, a set of data quality or interoperability criteria).

For this purpose, GeoDCAT-AP makes use of two different but not mutually exclusive approaches. More precisely, property dct:conformsTo is used when the test result states that a resource is conformant with a given specification. The more general approach is based on [PROV-O], and it specifies conformance test results as a testing activity (prov:Activity) that generates a result (specified with property prov:generated), corresponding to one of the degrees of conformity defined in [INSPIRE-MD-REG], and available from the INSPIRE Registry [INSPIRE-DoC]. The specification against which the testing activity is carried out is specified via a “qualified association” (prov:qualifiedAssociation), linked to a “plan” (prov:hadPlan) derived from (prov:wasDerivedFrom) the specification itself.

This pattern is illustrated in Example 1.

More details on these solutions are available in § B.6.14 Conformity and data quality - *not in ISO 19115 core.

9. Accessibility and Multilingual Aspects

This section is non-normative.

Accessibility in the context of this Application Profile is limited to information about the technical format of distributions of datasets. The properties dcat:mediaType and dct:format provide information that can be used to determine what software can be deployed to process the data. The accessibility of the data within the datasets needs to be taken care of by the software that processes the data and is outside of the scope of this Application Profile.

Multilingual aspects related to this Application Profile concern all properties whose contents are expressed as strings (i.e. rdfs:Literal) with human-readable text. Wherever such properties are used, the string values are of one of two types:

Wherever values of properties are expressed with either type of string, the property can be repeated with translations in the case of free text and with parallel versions in case of named entities. For free text, e.g. in the cases of titles, descriptions and keywords, the language tag is mandatory.

Language tags to be used with rdfs:Literal are defined by [BCP47], which allows the use of the "t" extension for text transformations defined in [RFC6497] with the field "t0" [CLDR] indicating a machine translation.

A language tag will look like: "en-t-es-t0-abcd", which conveys the information that the string is in English, translated from Spanish by machine translation using a tool named "abcd".

For named entities, the language tag is optional and should only be provided if the parallel version of the name is strictly associated with a particular language. For example, the name ‘European Union’ has parallel versions in all official languages of the union, while a name like ‘W3C’ is not associated with a particular language and has no parallel versions.

For linking to different language versions of associated web pages (e.g. landing pages) or documentation, a content negotiation [CONNEG] mechanism may be used whereby different content is served based on the Accept-Languages indicated by the browser. Using such a mechanism, the link to the page or document can resolve to different language versions of the page or document.

All the occurrences of the property dct:language, which can be repeated if the metadata is provided in multiple languages, must have a URI as their object, not a literal string from the [ISO-639] code list.

How multilingual information is handled in systems, for example in indexing and user interfaces, is outside of the scope of this Application Profile.

10. Privacy and security considerations

The GeoDCAT-AP vocabulary supports the attribution of data and metadata to various participants such as resource creators, publishers and other parties or agents, and as such defines terms that may be related to personal information. In addition, it also supports the association of rights and licenses with catalogued Resources and Distributions. These rights and licenses could potentially include or reference sensitive information such as user and asset identifiers as described in [VOCAB-ODRL].

Implementations that produce, maintain, publish or consume such vocabulary terms must take steps to ensure security and privacy considerations are addressed at the application level.

11. Acknowledgements

This work was elaborated by the GeoDCAT-AP Working Group under the ISA² programme.

The ISA² Programme of the European Commission was represented by Pavlina Fragkou and Seth van Hooland. Andrea Perego and Bert van Nuffelen were the editors of the specification.

Contributors: Andreas Kuckartz, Antonio Rotundo, Danny Vandenbroucke, Fabian Kirstein, Franck Cotton, Hannes Reuter, Jakub Klímek, James Passmore, Matthias Palmér, Riccardo Albertoni, Simon Cox.

A. Quick Reference of Classes and Properties

Class Class URI Mandatory prop. Recommended prop. Optional prop.
+Activity prov:Activity

+prov:generated

+prov:qualifiedAssociation

+prov:used

+Address (Agent) locn:Address

+locn:adminUnitL1

+locn:adminUnitL2

+locn:postCode

+locn:postName

+locn:thoroughfare

+Address (Kind) vcard:Address

+vcard:country-name

+vcard:locality

+vcard:postal-code

+vcard:region

+vcard:street-address

Agent foaf:Agent

foaf:name

dct:type

+foaf:mbox

+foaf:phone

+foaf:workplaceHomepage

+locn:address

+org:memberOf

+Attribution prov:Attribution

+dcat:hadRole

+prov:agent

Catalogue dcat:Catalog

dcat:dataset

dct:description

dct:publisher

dct:title

+dcat:keyword

dcat:themeTaxonomy

dct:issued

dct:language

dct:license

dct:modified

dct:spatial

foaf:homepage

dcat:catalog

+dcat:contactPoint

dcat:record

dcat:service

+dcat:theme

+dct:accessRights

+dct:conformsTo

+dct:conformsTo

+dct:created

dct:creator

dct:hasPart

+dct:identifier

dct:isPartOf

dct:rights

+dct:rightsHolder

+dct:subject

+dct:temporal

+geodcat:custodian

+geodcat:distributor

+geodcat:originator

+geodcat:principalInvestigator

+geodcat:processor

+geodcat:resourceProvider

+geodcat:user

+prov:qualifiedAttribution

+prov:wasUsedBy

Catalogue Record dcat:CatalogRecord

dct:modified

foaf:primaryTopic

adms:status

dct:conformsTo

dct:issued

+cnt:characterEncoding

+dcat:contactPoint

+dct:created

+dct:creator

dct:description

+dct:identifier

dct:language

+dct:publisher

+dct:rightsHolder

dct:source

dct:title

+geodcat:custodian

+geodcat:distributor

+geodcat:originator

+geodcat:principalInvestigator

+geodcat:processor

+geodcat:resourceProvider

+geodcat:user

+prov:qualifiedAttribution

Category skos:Concept

skos:prefLabel

+skos:inScheme

Category scheme skos:ConceptScheme

dct:title

+dct:created

+dct:issued

+dct:modified

+owl:versionInfo

Checksum spdx:Checksum

spdx:algorithm

spdx:checksumValue

Data Service dcat:DataService

dcat:endpointURL

dct:title

dcat:endpointDescription

+dcat:keyword

dcat:servesDataset

+dcat:contactPoint

+dcat:spatialResolutionInMeters

+dcat:temporalResolution

+dcat:theme

dct:accessRights

+dct:conformsTo

+dct:conformsTo

+dct:created

+dct:creator

dct:description

+dct:identifier

+dct:issued

+dct:language

dct:license

+dct:modified

+dct:publisher

+dct:rightsHolder

+dct:spatial

+dct:subject

+dct:temporal

+dct:type

+dct:type

+dct:type

+dqv:hasQualityMeasurement

+geodcat:custodian

+geodcat:distributor

+geodcat:originator

+geodcat:principalInvestigator

+geodcat:processor

+geodcat:resourceProvider

+geodcat:user

+prov:qualifiedAttribution

+prov:wasUsedBy

+rdfs:comment

Dataset dcat:Dataset

dct:description

dct:title

dcat:contactPoint

dcat:distribution

dcat:keyword

dcat:theme

dct:publisher

dct:spatial

dct:temporal

adms:identifier

adms:sample

adms:versionNotes

dcat:landingPage

dcat:qualifiedRelation

dcat:spatialResolutionInMeters

dcat:temporalResolution

dct:accessRights

dct:accrualPeriodicity

dct:conformsTo

+dct:conformsTo

+dct:created

dct:creator

dct:hasVersion

dct:identifier

dct:isReferencedBy

dct:isVersionOf

dct:issued

dct:language

dct:modified

dct:provenance

dct:relation

+dct:rightsHolder

dct:source

+dct:subject

dct:type

+dqv:hasQualityMeasurement

foaf:page

+geodcat:custodian

+geodcat:distributor

+geodcat:originator

+geodcat:principalInvestigator

+geodcat:processor

+geodcat:resourceProvider

+geodcat:user

owl:versionInfo

prov:qualifiedAttribution

prov:wasGeneratedBy

+prov:wasUsedBy

+rdfs:comment

Distribution dcat:Distribution

dcat:accessURL

dcatap:availability

dct:description

dct:format

dct:license

+adms:representationTechnique

adms:status

dcat:accessService

dcat:byteSize

dcat:compressFormat

dcat:downloadURL

dcat:mediaType

dcat:packageFormat

dcat:spatialResolutionInMeters

dcat:temporalResolution

+dct:accessRights

dct:conformsTo

+dct:conformsTo

dct:issued

dct:language

dct:modified

dct:rights

dct:title

+dqv:hasQualityMeasurement

foaf:page

odrl:hasPolicy

+rdfs:comment

spdx:checksum

Document foaf:Document

+dct:description

+dct:title

Frequency dct:Frequency
Identifier adms:Identifier

skos:notation

Kind vcard:Kind

+vcard:fn

+vcard:hasEmail

+vcard:hasURL

+vcard:hasAddress

+vcard:hasTelephone

+vcard:organization-name

Licence Document dct:LicenseDocument

dct:type

+rdfs:label

Linguistic system dct:LinguisticSystem
Literal rdfs:Literal
Location dct:Location

dcat:bbox

dcat:centroid

+dct:identifier

locn:geometry

+skos:inScheme

+skos:prefLabel

Media type dct:MediaType

+rdfs:label

+Metric dqv:Metric

+dqv:expectedDataType

+dqv:inDimension

Period of time dct:PeriodOfTime

dcat:endDate

dcat:startDate

time:hasBeginning

time:hasEnd

Provenance Statement dct:ProvenanceStatement

+rdfs:label

Publisher type skos:Concept
+Quality Measurement dqv:QualityMeasurement

+dqv:isMeasurementOf

+dqv:value

+sdmx-attribute:unitMeasure

Relationship dcat:Relationship

dcat:hadRole

dct:relation

Resource rdfs:Resource
Rights statement dct:RightsStatement

+rdfs:label

Role dcat:Role
Standard dct:Standard

+dct:description

+dct:identifier

+dct:issued

+dct:title

+dct:type

+owl:versionInfo

+skos:inScheme

+dct:created

+dct:modified

Status skos:Concept

A.1 Classes and properties added by GeoDCAT-AP

This version of GeoDCAT-AP extends [DCAT-AP-20200608] with 6 additional classes and 69 additional properties (some of which re-used across classes). They are listed in the following table.

Class Class URI Mandatory prop. Recommended prop. Optional prop.
+Activity prov:Activity

+prov:generated

+prov:qualifiedAssociation

+prov:used

+Address (Agent) locn:Address

+locn:adminUnitL1

+locn:adminUnitL2

+locn:postCode

+locn:postName

+locn:thoroughfare

+Address (Kind) vcard:Address

+vcard:country-name

+vcard:locality

+vcard:postal-code

+vcard:region

+vcard:street-address

Agent foaf:Agent

+foaf:mbox

+foaf:phone

+foaf:workplaceHomepage

+locn:address

+org:memberOf

+Attribution prov:Attribution

+dcat:hadRole

+prov:agent

Catalogue dcat:Catalog

+dcat:keyword

+dcat:contactPoint

+dcat:theme

+dct:accessRights

+dct:conformsTo

+dct:conformsTo

+dct:created

+dct:identifier

+dct:rightsHolder

+dct:subject

+dct:temporal

+geodcat:custodian

+geodcat:distributor

+geodcat:originator

+geodcat:principalInvestigator

+geodcat:processor

+geodcat:resourceProvider

+geodcat:user

+prov:qualifiedAttribution

+prov:wasUsedBy

Catalogue Record dcat:CatalogRecord

+cnt:characterEncoding

+dcat:contactPoint

+dct:created

+dct:creator

+dct:identifier

+dct:publisher

+dct:rightsHolder

+geodcat:custodian

+geodcat:distributor

+geodcat:originator

+geodcat:principalInvestigator

+geodcat:processor

+geodcat:resourceProvider

+geodcat:user

+prov:qualifiedAttribution

Category skos:Concept

+skos:inScheme

Category scheme skos:ConceptScheme

+dct:created

+dct:issued

+dct:modified

+owl:versionInfo

Data Service dcat:DataService

+dcat:keyword

+dcat:contactPoint

+dcat:spatialResolutionInMeters

+dcat:temporalResolution

+dcat:theme

+dct:conformsTo

+dct:conformsTo

+dct:created

+dct:creator

+dct:identifier

+dct:issued

+dct:language

+dct:modified

+dct:publisher

+dct:rightsHolder

+dct:spatial

+dct:subject

+dct:temporal

+dct:type

+dct:type

+dct:type

+dqv:hasQualityMeasurement

+geodcat:custodian

+geodcat:distributor

+geodcat:originator

+geodcat:principalInvestigator

+geodcat:processor

+geodcat:resourceProvider

+geodcat:user

+prov:qualifiedAttribution

+prov:wasUsedBy

+rdfs:comment

Dataset dcat:Dataset

+dct:conformsTo

+dct:created

+dct:rightsHolder

+dct:subject

+dqv:hasQualityMeasurement

+geodcat:custodian

+geodcat:distributor

+geodcat:originator

+geodcat:principalInvestigator

+geodcat:processor

+geodcat:resourceProvider

+geodcat:user

+prov:wasUsedBy

+rdfs:comment

Distribution dcat:Distribution

+adms:representationTechnique

+dct:accessRights

+dct:conformsTo

+dqv:hasQualityMeasurement

+rdfs:comment

Document foaf:Document

+dct:description

+dct:title

Kind vcard:Kind

+vcard:fn

+vcard:hasEmail

+vcard:hasURL

+vcard:hasAddress

+vcard:hasTelephone

+vcard:organization-name

Licence Document dct:LicenseDocument

+rdfs:label

Location dct:Location

+dct:identifier

+skos:inScheme

+skos:prefLabel

Media type dct:MediaType

+rdfs:label

+Metric dqv:Metric

+dqv:expectedDataType

+dqv:inDimension

Provenance Statement dct:ProvenanceStatement

+rdfs:label

+Quality Measurement dqv:QualityMeasurement

+dqv:isMeasurementOf

+dqv:value

+sdmx-attribute:unitMeasure

Rights statement dct:RightsStatement

+rdfs:label

Standard dct:Standard

+dct:description

+dct:identifier

+dct:issued

+dct:title

+dct:type

+owl:versionInfo

+skos:inScheme

+dct:created

+dct:modified

A.2 Deprecated classes and properties

Class / Property URI Domain Replaced by Deprecated in
Media Type or Extent dct:MediaTypeOrExtent dct:MediaType [DCAT-AP-20191120]
+Service dctype:Service dcat:DataService GeoDCAT-AP 2.0.0
end date schema:endDate dct:PeriodOfTime dcat:endDate [DCAT-AP-20191120]
endpoint URL foaf:homepage dcat:DataService dcat:endpointURL GeoDCAT-AP 2.0.0
+had role dct:type +prov:Attribution dcat:hadRole GeoDCAT-AP 2.0.0
+keyword / tag dc:subject dcat:Catalog dcat:keyword GeoDCAT-AP 2.0.0
+keyword / tag dc:subject dcat:DataService dcat:keyword GeoDCAT-AP 2.0.0
serves dataset dct:hasPart dcat:DataService dcat:servesDataset GeoDCAT-AP 2.0.0
service dct:hasPart dcat:Catalog dcat:service GeoDCAT-AP 2.0.0
+spatial resolution rdfs:comment dcat:DataService dcat:spatialResolutionInMeters dqv:hasQualityMeasurement GeoDCAT-AP 2.0.0
spatial resolution rdfs:comment dcat:Dataset dcat:spatialResolutionInMeters dqv:hasQualityMeasurement GeoDCAT-AP 2.0.0
+spatial resolution rdfs:comment dcat:Distribution dcat:spatialResolutionInMeters dqv:hasQualityMeasurement GeoDCAT-AP 2.0.0
start date schema:startDate dct:PeriodOfTime dcat:startDate [DCAT-AP-20191120]
+theme / category dct:subject dcat:Catalog dcat:theme GeoDCAT-AP 2.0.0
+theme / category dct:subject dcat:DataService dcat:theme GeoDCAT-AP 2.0.0

B. INSPIRE and ISO 19115 Mappings

B.1 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].

Additionally, the following outcomes may be achieved, outside the context of this specification:

B.2 Motivation and use cases

This section is non-normative.

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, version 2.0.1 [DCAT-AP-20200608]. 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, version 2.0.1 [INSPIRE-MD-20170302]. 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) and the European Data Portal (EDP).

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] / [ISO-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 [INSPIRE-MD], 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 additional metadata elements. Furthermore, data portals are frequently complemented by a triple store, making the full set of GeoDCAT-AP metadata queryable through a SPARQL endpoint [SPARQL11-QUERY].

B.3 Methodology and summary of results

This section is non-normative.

Methodologically, the development of GeoDCAT-AP implies 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.

B.3.1 Alignment criteria and requirements

The overall objective of 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, trying, at the same time, to avoid semantic loss and to promote cross-domain re-use.

  3. Ensure backward compatibiliy with previous versions of GeoDCAT-AP.

The first two goals, having a different scope and applying to different use cases (see § B.2 Motivation and use cases), are reflected in the two mapping profiles of GeoDCAT-AP, core and extended, described in § B.4 RDF syntax bindings for INSPIRE and ISO 19115 metadata elements .

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 § B.1 Objectives, 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.

As it will be explained in § B.3.3 Alignments defined in GeoDCAT-AP, no new terms have been defined in the current version of GeoDCAT-AP.

B.3.2 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 MAY 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-SDSS-REG]. These elements are also listed in Appendix C.3 to the INSPIRE Metadata Technical Guidelines (version 2.0.1) [INSPIRE-MD-20170302].

  • The set of metadata elements recommended as common to most of the INSPIRE spatial data themes in the INSPIRE Data Specifications Technical Guidelines, and listed in the first table included in Appendix C.7 to the INSPIRE Metadata Technical Guidelines (version 2.0.1) [INSPIRE-MD-20170302]. These elements are the following ones:

    • Maintenance information.

    • Conceptual and domain consistency (Data quality – Logical consistency).

The full list of metadata elements covered by the current version of GeoDCAT-AP is available in § B.5 Overview of metadata elements covered by GeoDCAT-AP 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 Appendix C.7 to the INSPIRE Metadata Technical Guidelines (version 2.0.1) [INSPIRE-MD-20170302].

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.

B.3.3 Alignments defined in GeoDCAT-AP

The alignments defined in the current version of GeoDCAT-AP are the result of an iterative revision process of [GeoDCAT-AP-20160802], following the criteria illustrated in the previous sections and the review of the GeoDCAT-AP WG. Alignments for [ISO-19115-1] have not been defined. § B.7 Comparison between INSPIRE and ISO 19115-1:2014 contains an overview of the most important changes with respect to [ISO-19115].

The work started with the review of [DCAT-AP-20200608], [VOCAB-DCAT-2], and [INSPIRE-MD-20170302], with the purpose of identifying possible disalignments of the mappings defined in [GeoDCAT-AP], as well as possible gaps in [DCAT-AP-20200608] and [VOCAB-DCAT-2], which may require the use of different vocabularies or the definition of new classes and/or properties in the GeoDCAT-AP namespace. In all these cases, backward compatibility with [GeoDCAT-AP-20160802] has been taken into account when implementing revisions.

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:

  • Backward compatibility with [GeoDCAT-AP-20160802] is ensured: The revised mappings have been deprecated, but maintained in the mapping rules implemented in [GeoDCAT-XSLT] along with the new one, in the extended mapping profile of GeoDCAT-AP, and their support has been included in § 6. Conformance.

  • Compliance with [DCAT-AP-20200608] is ensured: The geospatial metadata elements covered by the defined mappings include all those that in [DCAT-AP-20200608] are mandatory, plus a subset of those that are recommended and optional.

  • GeoDCAT-AP offers alignments for all the metadata elements illustrated in § B.3.2 Metadata elements to be covered by GeoDCAT-AP, 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:

The details of the alignments defined in GeoDCAT-AP are illustrated in the following section.

B.4 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].

For detailed usage notes and examples of each of the metadata elements covered by GeoDCAT-AP, we refer the reader to § B.6 Detailed usage notes and examples (the relevant section is specified in the “comments” column of the mapping table).

B.4.1 Overview of bindings for GeoDCAT-AP Core

This section 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] core for which DCAT-AP provides an RDF syntax binding. Those metadata elements for which [DCAT-AP-20200608] does not provide a binding are part of the GeoDCAT-AP Extended mapping profile described in § B.4.2 Overview of bindings for GeoDCAT-AP Extended.

GeoDCAT-AP Core is meant to enable the harvesting and re-use of spatial metadata records through [DCAT-AP-20200608]-conformant applications and services, including data portals and APIs. The alignments for INSPIRE and [ISO-19115] metadata elements that are not included in GeoDCAT-AP Core are defined in GeoDCAT-AP Extended, see § B.4.2 Overview of bindings for GeoDCAT-AP Extended.

In the following table, the starred elements (*) are used to indicate the corresponding metadata element in the core profile of [ISO-19115]. For each element, it is indicated whether the element is mandatory (M), optional (O), conditional (C), or recommended (R) in either specification.

INSPIRE metadata

*ISO 19115:2003 Core Profile

DCAT-AP Property Domain Range Comments

Resource title (M)

*Dataset title (M)

dct:title (M)

-

(dcat:Catalog (M))

(dcat:Dataset (M))

(dcat:DataService (O))

rdf:PlainLiteral See § B.6.1 Resource title - *Dataset title

Resource abstract (M)

*Abstract describing the dataset (M)

dct:description (M)

-

(dcat:Catalog (M))

(dcat:Dataset (M))

(dcat:DataService (O))

rdf:PlainLiteral See § B.6.2 Resource abstract - *Abstract describing the dataset

Resource type (M)

*not in ISO 19115 core

rdf:type (M)

(see also binding for GeoDCAT-AP Extended)

-

(dcat:Catalog (M))

(dcat:Dataset (M))

(dcat:DataService (0))

rdfs:Class

(values dcat:Catalog, dcat:Dataset, dcat:DataService)

See § B.6.3 Resource type - *not in ISO 19115 core. [DCAT-AP-20200608] does not distinguish between datasets and dataset series. dcat:Catalog can be used for catalogue / discovery services, in addition to dcat:DataService.

Resource locator (C)

*On-line resource (O)

See § B.6.4 Resource locator - *On-line resource. The defined encoding depends whether the resource is a service or a dataset or data series. Also, the value of the function code (CI_OnlineFunctionCode) is to be taken into account.

For services

foaf:homepage

dcat:endpointURL

dcat:endpointDescription

-

(dcat:Catalog (M))

(dcat:DataService (O))

foaf:Document rdfs:Resource foaf:Document See § B.6.4 Resource locator - *On-line resource. Properties dcat:endpointURL and dcat:endpointDescription are used when the resource locator points to a service endpoint.

For dataset and data series (function code not provided)

dcat:landingPage (O) dcat:Dataset (M) foaf:Document See § B.6.4 Resource locator - *On-line resource.

For dataset and data series (‘download’ function code)

dcat:accessURL (M) dcat:Distribution (R) rdfs:Resource See § B.6.4 Resource locator - *On-line resource. Property dcat:accessURL is also used whenever the resource locator points to a service endpoint.

For dataset and data series (‘information’ function code)

foaf:page

-

(dcat:Dataset (M))

foaf:Document See § B.6.4 Resource locator - *On-line resource.

For dataset and data series (‘offlineAccess’ function code)

dcat:accessURL (M) dcat:Distribution (R) rdfs:Resource See § B.6.4 Resource locator - *On-line resource. Property dcat:accessURL is also used whenever the resource locator points to a service endpoint.

For dataset and data series (‘order’ function code)

dcat:accessURL (M) dcat:Distribution (R) rdfs:Resource See § B.6.4 Resource locator - *On-line resource. Property dcat:accessURL is also used whenever the resource locator points to a service endpoint.

For dataset and data series (‘search’ function code)

foaf:page

-

(dcat:Dataset)

foaf:Document See § B.6.4 Resource locator - *On-line resource.

Unique resource identifier (M)

*not in ISO 19115 core

dct:identifier (O)

-

(dcat:Dataset (M))

rdfs:Literal See § B.6.5 Unique resource identifier - *not in ISO 19115 core. In RDF, this could also be represented as the URI of the dataset.

Resource language (C)

*Dataset language (M)

dct:language (O for dcat:Dataset and R for dcat:Catalog)

-

(dcat:Dataset (M))

(dcat:Catalog (M))

dct:LinguisticSystem See § B.6.7 Resource language and metadata language - *Dataset language and Metadata language.

Keyword value (M)

*not in ISO 19115 core

dcat:keyword (R)

dcat:theme (R)

(see also binding for GeoDCAT-AP Extended)

dcat:Dataset (M) rdfs:Literal

See § B.6.8 Topic category, originating controlled vocabulary, and keyword value - *Dataset topic category. For datasets and data series, dcat:keyword is used for free keywords; dcat:theme for controlled vocabularies.

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 § 5.2 Controlled vocabularies to be used.

For services a syntax binding is provided in GeoDCAT-AP Extended only.

Geographic bounding box (M)

*Geographic location of the dataset (by four coordinates or by geographic identifier) (C)

dct:spatial (O)

-

(dcat:Catalog (M))

(dcat:Dataset (M))

dct:Location See § B.6.10 Geographic bounding box - *Geographic location of the dataset (by 4 coordinates or by geographic identifier) on the preferred format to be used in RDF for the representation of geometries.

Temporal extent (C)

*Additional extent information for the dataset (vertical and temporal) (O)

dct:temporal (O)

-

(dcat:Dataset (M))

dct:PeriodOfTime See § B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp.

Date of publication (C)

*Dataset reference date (M) – publication

dct:issued (R for dcat:Catalog and O for dcat:Dataset)

-

(dcat:Dataset (M))

(dcat:Catalog (M))

xsd:date See § B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp.

Date of last revision (C)

*Dataset reference date (M) – revision

dct:modified (R for dcat:Catalog and O for dcat:Dataset)

-

(dcat:Catalog (M))

(dcat:Dataset (M))

xsd:date See § B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp.

Spatial resolution (C)

*Spatial resolution of the dataset (O)

dcat:spatialResolutionInMeters (O)

-

(dcat:Dataset (M))

xsd:decimal See § B.6.13 Spatial resolution – Spatial resolution of the dataset. Property dcat:spatialResolutionInMeters can only be used when spatial resolution is expressed as distance in metres.

Lineage (M)

*Lineage (O)

dct:provenance (O)

-

-

(dcat:Dataset (M)

dct:ProvenanceStatement See § B.6.12 Lineage - *Lineage.

Conformity (M)

*not in ISO 19115 core

dct:conformsTo (O)

(see also binding for GeoDCAT-AP Extended)

-

(dcat:Dataset (M))

dct:Standard See § B.6.14 Conformity and data quality - *not in ISO 19115 core. dct:conformsTo can model only one of the cases supported in INSPIRE. i.e., when the degree of conformity is “conformant”.

Conformity Specification (M)

*not in ISO 19115 core

dct:title (R)

dct:issued (R)

dct:modified (O)

dct:created (O)

(see also binding for GeoDCAT-AP Extended)

rdfs:Resource

rdf:PlainLiteral

xsd:date

See § B.6.14 Conformity and data quality - *not in ISO 19115 core.

Conditions for access and use (M)

*not in ISO 19115 core

dct:license (R for dcat:Catalog and dcat:Distribution, O for dcat:DataService)

-

(dcat:Catalog (M))

(dcat:Distribution (R))

(dcat:DataService (O))

dct:LicenseDocument See § B.6.15 Conditions for access and use and limitations on public access – Use limitation and access / other constraints.

Limitations on public access (C)

*not in ISO 19115 core

dct:accessRights (O)

-

(dcat:DataService (O))

dct:RightsStatement See § B.6.15 Conditions for access and use and limitations on public access – Use limitation and access / other constraints.

Responsible party (M)

*Dataset responsible party (O)

dct:publisher (M)

dct:creator (O)

-

(dcat:Catalog (M))

dct:Agent

See § B.6.16 Responsible party and metadata point of contact - *Dataset responsible party and *Metadata point of contact. [DCAT-AP-20200608] supports only 3 of the 11 responsible party roles supported in INSPIRE. GeoDCAT-AP Extended makes use of [PROV-O] to model information concerning provenance not covered in [DCAT-AP-20200608].

dct:publisher (R)

dcat:contactPoint (R)

dct:creator (O)

-

(dcat:Dataset (M))

dct:Agent

vcard:Kind

dct:Agent

Encoding (M)

*Distribution format (O)

dct:format (R), dcat:mediaType (O) dcat:Distribution (R) dc:MediaTypeOrExtent See § B.6.25 Encoding - *Distribution format. See controlled vocabularies for encoding in § 5.2 Controlled vocabularies to be used.

Maintenance information (R)

*not in ISO 19115 core

dct:accrualPeriodicity (O)

dctype:Collection

(dcat:Dataset (M))

dct:Frequency See § B.6.27 Maintenance information - *not in ISO 19115 core.
-Metadata standard dct:conformsTo (R)

-

(dcat:CatalogRecord (O))

dct:Standard See § B.6.18 *Metadata standard name, *Metadata standard version. This element, not existing in ISO 19115, is just meant to provide the context for the specification of the metadata standard name and version.
*Metadata standard name (O) dct:title

-

(dct:Standard (O))

rdf:PlainLiteral See § B.6.18 *Metadata standard name, *Metadata standard version.
*Metadata standard version (O) owl:versionInfo

-

(dct:Standard (O))

rdfs:Literal See § B.6.18 *Metadata standard name, *Metadata standard version. This can be part of the information specified for metadata standard name.

Metadata date (M)

*Metadata date stamp (M)

dct:modified (M)

-

(dcat:CatalogRecord (O))

xsd:date See § B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp.

Metadata language (M)

*Metadata language (C)

dct:language (O)

-

(dcat:CatalogRecord (O))

dct:LinguisticSystem See § B.6.7 Resource language and metadata language - *Dataset language and Metadata language.

B.4.2 Overview of bindings for GeoDCAT-AP Extended

This section provides an overview of the RDF syntax bindings in GeoDCAT-AP Extended. This GeoDCAT-AP mapping profile covers elements defined in INSPIRE and the core profile of [ISO-19115], for which [DCAT-AP-20200608] does not provide a syntax binding. GeoDCAT-AP Extended is a superset of GeoDCAT-AP Core.

The following table contains the defined RDF syntax binding for INSPIRE metadata. In the table below, the starred elements (*) are used to indicate the corresponding metadata element in the core profile of [ISO-19115]. For each metadata element, it is indicated whether the element is mandatory (M), optional (O), conditional (C), or recommended (R) in either specification.

Please note that some metadata elements have an RDF syntax binding in both the GeoDCAT-AP Core and Extended mapping profile. These elements fall in one of these categories:

  1. Partial coverage by a [DCAT-AP-20200608] binding: This concerns conformity (only degree of conformity equal to “conformant” is supported) and responsible organisation (only responsible party roles creator, publisher, and point of contact are supported).

  2. Subsumption by a GeoDCAT-AP RDF binding: ISO metadata elements available in GeoDCAT-AP Core, but for which only a many-to-one mapping is supported in [DCAT-AP-20200608]. This concerns resource types, since the [VOCAB-DCAT-2] notion of dataset models both the ISO/INSPIRE notions of data set and data series.

In order to preserve the original semantics, the extended mapping profile of GeoDCAT-AP defines additional alignments to those included in GeoDCAT-AP Core. The two sets of alignments are not mutually exclusive, and can coexist without creating conflicts.

INSPIRE metadata

*ISO 19115:2003 Core Profile

Property Domain Range Comments

Resource type (M)

*not in ISO 19115 core

dct:type

-

(dcat:Catalog (M))

(dcat:Dataset (M))

(dcat:DataService (O))

rdfs:Class

(skos:Concept)

See § B.6.3 Resource type - *not in ISO 19115 core and the controlled vocabulary for resource type in § 5.2 Controlled vocabularies to be used. [DCAT-AP-20200608] supports the use of dct:type on dct:Dataset only.

Unique resource identifier (M)

*not in ISO 19115 core

dct:identifier

-

(dcat:Catalog (M))

(dcat:DataService (O))

rdfs:Literal See § B.6.5 Unique resource identifier - *not in ISO 19115 core. In RDF, this could also be represented as the URI of the resource.

Resource language (C)

*Dataset language (M)

dct:language

-

(dcat:DataService (O))

dct:LinguisticSystem See § B.6.7 Resource language and metadata language - *Dataset language and Metadata language.

Topic category (M)

*Dataset topic category (M)

dct:subject

-

(dcat:Dataset (M))

-

(skos:Concept)

See § B.6.8 Topic category, originating controlled vocabulary, and keyword value - *Dataset topic category and the controlled vocabulary for topic category in § 5.2 Controlled vocabularies to be used.

Spatial data service type (M)

*not in ISO 19115

dct:type

-

(dcat:DataService (O))

rdfs:Class

(skos:Concept)

See § B.6.3 Resource type - *not in ISO 19115 core. See controlled vocabulary for spatial data service type in § 5.2 Controlled vocabularies to be used.

Keyword value (M)

*not in ISO 19115 core

dcat:keyword

dcat:theme

dct:type

- (dcat:Catalog (M))

- (dcat:DataService (O))

- (rdfs:Literal)

- (rdfs:Resource)

rdfs:Class (skos:Concept)

See § B.6.8 Topic category, originating controlled vocabulary, and keyword value - *Dataset topic category.

Originating controlled vocabulary (C)

*not in ISO 19115 core

skos:inScheme skos:Concept skos:ConceptScheme See § B.6.8 Topic category, originating controlled vocabulary, and keyword value - *Dataset topic category.

Geographic bounding box (M)

*Geographic location of the dataset (by four coordinates or by geographic identifier) (C)

dct:spatial (O)

-

(dcat:DataService (O))

dct:Location See § B.6.10 Geographic bounding box - *Geographic location of the dataset (by 4 coordinates or by geographic identifier) on the preferred format to be used in RDF for the representation of geometries.

Temporal extent (C)

*Additional extent information for the dataset (vertical and temporal) (O)

dct:temporal (O)

-

(dcat:Catalog (M))

(dcat:DataService (O))

dct:PeriodOfTime See § B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp.

Date of publication (C)

*Dataset reference date (M) – publication

dct:issued

-

(dcat:DataService (O))

xsd:date See § B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp.

Date of last revision (C)

*Dataset reference date (M) – revision

dct:modified

-

(dcat:DataService (O))

xsd:date See § B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp.

Date of creation (C)

*Dataset reference date (M) - creation

dct:created

-

(dcat:Catalog (M))

(dcat:Dataset (M))

(dcat:DataService (O))

xsd:date See § B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp.

Spatial resolution (C)

*Spatial resolution of the dataset (O)

dcat:spatialResolutionInMeters

-

(dcat:DataService (O))

xsd:decimal See § B.6.13 Spatial resolution – Spatial resolution of the dataset. Property dcat:spatialResolutionInMeters can only be used when spatial resolution is expressed as distance in metres. Property dqv:hasQualityMeasurement can be used to specify any type of spatial resolution. Property rdfs:comment is used only in case spatial resolution is specified as free-text.

dqv:hasQualityMeasurement

-

(dcat:Dataset (M))

(dcat:DataService (O))

dqv:QualityMeasurement

rdfs:comment

rdfs:Literal

Conformity (M)

*not in ISO 19115 core

prov:wasUsedBy

prov:Entity

(dcat:Dataset (M))

(dcat:DataService (M))

prov:Activity See § B.6.14 Conformity and data quality - *not in ISO 19115 core.

Conformity Specification (M)

*not in ISO 19115 core

prov:wasDerivedFrom prov:Entity prov:Entity See § B.6.14 Conformity and data quality - *not in ISO 19115 core.

Conformity degree (M)

*not in ISO 19115 core

prov:generated prov:Activity prov:Entity See § B.6.14 Conformity and data quality - *not in ISO 19115 core and the controlled vocabulary for conformity degree in § 5.2 Controlled vocabularies to be used.

Topological Consistency (C)

*not in ISO 19115 core

- - - See § B.6.14 Conformity and data quality - *not in ISO 19115 core. No syntax binding is provided for data quality, other than data conformity.

Data Quality – Logical Consistency – Conceptual Consistency, Domain Consistency – (R)

*not in ISO 19115 core

- - - See § B.6.14 Conformity and data quality - *not in ISO 19115 core. No syntax binding is provided for data quality, other than conformity.

Limitations on public access (C)

*not in ISO 19115 core

dct:accessRights (O)

-

(dcat:Catalog (M))

(dcat:Distribution (R))

(dcat:DataService (O))

dct:RightsStatement See § B.6.15 Conditions for access and use and limitations on public access – Use limitation and access / other constraints.

Responsible party (M)

*Dataset responsible party (O)

dct:publisher

dct:creator

-

(dcat:CatalogRecord (O))

(dcat:DataService (O))

dct:Agent See § B.6.16 Responsible party and metadata point of contact - *Dataset responsible party and *Metadata point of contact.
dcat:contactPoint

-

(dcat:Catalog (M))

(dcat:CatalogRecord (O))

(dcat:DataService (O))

vcard:Kind

dct:rightsHolder

geodcat:custodian

geodcat:distributor

geodcat:originator

geodcat:principalInvestigator

geodcat:processor

geodcat:resourceProvider

geodcat:user

-

(dcat:Catalog (M))

(dcat:Dataset (M))

(dcat:CatalogRecord (O))

(dcat:DataService (O))

dct:Agent
prov:qualifiedAttribution

prov:Entity

(dcat:Catalog (M))

(dcat:Dataset (M))

(dcat:CatalogRecord (O))

(dcat:DataService (O))

prov:Attribution
Responsible party role (M) dcat:hadRole

-

(prov:Attribution)

dcat:Role See § B.6.16 Responsible party and metadata point of contact - *Dataset responsible party and *Metadata point of contact and controlled vocabulary for responsible party role in § 5.2 Controlled vocabularies to be used.
*Metadata file identifier (O) dct:identifier

-

(dcat:CatalogRecord (O))

rdfs:Literal See § B.6.17 *Metadata file identifier. In RDF, this could also be represented as the URI of the metadata / catalogue record.

Metadata point of contact (M)

*Metadata point of contact (M)

dcat:contactPoint

-

(dcat:CatalogRecord (O))

vcard:Kind See § B.6.16 Responsible party and metadata point of contact - *Dataset responsible party and *Metadata point of contact.
prov:qualifiedAttribution

-

(dcat:CatalogRecord (O))

prov:Attribution
*Metadata character set (C) cnt:characterEncoding

cnt:Content

(dcat:CatalogRecord (O))

rdfs:Literal See § B.6.24 Character encoding - *Dataset character set and *Metadata character set.

Coordinate Reference System (M)

*Reference System (0)

dct:conformsTo

-

(dcat:Dataset (M))

(dcat:DataService (O))

dct:Standard See § B.6.23 Coordinate reference systems and Temporal reference systems – *Reference System.

Temporal Reference System (C)

*Reference System (0)

dct:conformsTo

-

(dcat:Dataset (M))

(dcat:DataService (O))

dct:Standard See § B.6.23 Coordinate reference systems and Temporal reference systems – *Reference System.

Character Encoding (C)

*Dataset character set (C)

cnt:characterEncoding

cnt:Content

(dcat:Distribution (R))

rdfs:Literal See § B.6.24 Character encoding - *Dataset character set and *Metadata character set.

Spatial representation type – (M)

*Spatial representation type (O)

adms:representationTechnique dcat:Distribution (R) skos:Concept See § B.6.26 Spatial representation type – *Spatial representation type.

B.5 Overview of metadata elements covered by GeoDCAT-AP

The following table provides an overview of the metadata elements in the INSPIRE metadata schema and in the core profile of [ISO-19115], and the available mappings in [DCAT-AP-20200608] and GeoDCAT-AP. Columns titled with “obligation” specify whether the corresponding metadata elements are mandatory (M), conditional (C), and optional (O) (where “conditional” means “mandatory under given conditions”).

Note that the mappings covered by [DCAT-AP-20200608] correspond to those defined in GeoDCAT-AP core, whereas those covered only by GeoDCAT-AP correspond to those defined in the GeoDCAT-AP extended.

INSPIRE Obligation ISO 19115 Core Obligation DCAT-AP GeoDCAT-AP
Metadata point of contact M Metadata point of contact M Yes
Metadata date M Metadata date stamp M Yes Yes
Metadata language M Metadata language C Yes Yes
Metadata character set C Yes
Metadata file identifier O Yes
Metadata standard name O Yes
Metadata standard version O Yes
Resource title M Dataset title M Yes Yes
Temporal reference - Date of creation / publication / last revision C Dataset reference date M Partially (creation date not included) Yes
Resource abstract M Abstract describing the dataset M Yes Yes
Resource language C Dataset language M Yes Yes
Topic category M Dataset topic category M Yes
Geographic bounding box M Geographic location of the dataset (by four coordinates or by geographic identifier) C Yes Yes
Character encoding C Dataset character set C Yes
Temporal reference - Temporal extent C Additional extent information for the dataset (vertical and temporal) O Partially (temporal extent only) Partially (temporal extent only)
Lineage M Lineage O Yes Yes
Spatial representation type M Spatial representation type O Yes
Encoding M Distribution format O Yes Yes
Spatial resolution C Spatial resolution of the dataset O Yes (but only as horizontal ground distance) Yes
Responsible organisation M Dataset responsible party O Partially (only 3 of the 11 responsible party roles are supported) Yes
Resource locator C On-line resource O Yes Yes
Coordinate reference system; Temporal reference system M; C Reference system O Yes
Conformity M Yes Yes
Resource type M Yes Yes
Spatial data service type M Yes
Keyword M Partially (only for datasets and dataset series) Yes
Coupled resource C Yes Yes
Unique resource identifier M Yes Yes
Conditions for access and use M Yes Yes
Limitations on public access M Yes Yes
Maintenance information O Partially (only maintenance and update frequency) Partially (only maintenance and update frequency)
Data quality – Logical consistency – Topological consistency C Partially (only conformance results)
Data quality – Logical consistency – Conceptual consistency O Partially (only conformance results)
Data quality – Logical consistency – Domain consistency O Partially (only conformance results)

B.6 Detailed usage notes and examples

This annex contains further usage notes and examples on the mappings summarised in § B.4 RDF syntax bindings for INSPIRE and ISO 19115 metadata elements .

B.6.1 Resource title - *Dataset title

The content of the element ‘resource title’ can be represented in RDF as a plain literal, and by using property dct:title.

This binding may also include the specification of the language by using attribute @xml:lang [XML]. The language to be specified is the one indicated by element metadata language, mapped to the language identifiers defined by IETF BCP 47 [BCP47].

B.6.2 Resource abstract - *Abstract describing the dataset

The content of the elements ‘resource abstract’ can be represented in RDF as a plain literal, and by using property dct:description.

This binding may also include the specification of the language by using attribute @xml:lang [XML]. The language to be specified is the one indicated by element metadata language, mapped to the language identifiers defined by IETF BCP 47 [BCP47].

B.6.3 Resource type - *not in ISO 19115 core

Note

In [VOCAB-DCAT-2], the notion of dataset is quite broad, and may include both the INSPIRE notions of dataset and dataset series. Moreover, currently no existing vocabulary provides suitable candidates for the INSPIRE notions of dataset series – the existing ones are very generic (e.g., dctype:Collection is defined as An aggregation of resources [DCTERMS]).

Based on this, in GeoDCAT-AP both INSPIRE datasets and dataset series are specified as instances of dcat:Dataset.

Moreover, in order to maintain the INSPIRE distinction between datasets and dataset series, following the work on aligning INSPIRE Metadata and Dublin Core [INSPIRE-DC], in the extended mapping profile of GeoDCAT-AP they will be denoted by using the resource type code list operated by the INSPIRE Registry [INSPIRE-RT], and by using dct:type. More precisely, the following URIs SHOULD be used to denote, respectively, dataset and series:

As far as the INSPIRE notion of service is concerned, [VOCAB-DCAT-2] and [DCAT-AP-20200608] provide a specific class, namely, dcat:DataService, whereas class dcat:Catalog can be used to complement dcat:DataService for ‘discovery services’ in INSPIRE. Additionally, the spatial data service type can be specified by using dct:type with the corresponding code lists operated by the INSPIRE Registry [INSPIRE-SDST]. More precisely, the following URI SHOULD be used to denote services:

B.6.4 Resource locator - *On-line resource

Note

In INSPIRE, this element, quoting, defines the link(s) to the resource and/or the link to additional information about the resource. [VOCAB-DCAT-2] has a property, namely, dcat:landingPage, having exactly the same purpose.

[ISO-19115] offers however the ability to specify the “type” of resource locator by using a specific code list (CI_OnlineFunctionCode), described in the following table:

ISO 19115 – CI_OnlineFunctionCode Description
download online instructions for transferring data from one storage device or system to another
information online information about the resource
offlineAccess online instructions for requesting the resource from the provider
order online order process for obtaining the resource
search online search interface for seeking out information about the resource

Based on this, the mappings of element “resource locator” for data sets and data set series will vary depending on the function code (when available), based on the following table.

ISO 19115 – CI_OnlineFunctionCode Property Domain Range
(not provided) dcat:landingPage dcat:Dataset foaf:Document
download dcat:accessURL dcat:Distribution rdfs:Resource
Information foaf:page dcat:Dataset foaf:Document
offlineAccess dcat:accessURL dcat:Distribution rdfs:Resource
order dcat:accessURL dcat:Distribution rdfs:Resource
search foaf:page dcat:Dataset foaf:Document

However, whenever the URL points to a service endpoint, the resource locator SHOULD be always mapped to property dcat:accessURL, and complemented by additional two properties, namely, dcat:endpointURL and dcat:endpointDescription.

More precisely, if the URL is recognised as pointing to a capabilities document, the URL is mapped to property dcat:endpointDescription, whereas property dcat:endpointURL will take as value the URL without it query string component.

Properties dcat:endpointURL and dcat:endpointDescription will have as domain class dcat:DataService, linked to the dataset distribution via property dcat:accessService.

Finally, whenever it is possible to recognise the service protocol, this information will be specified by property dct:conformsTo, taking as value the URI of the relevant specification from the INSPIRE Registry's code list for protocol values [INSPIRE-PV].

As far as services are concerned, the resource locator SHOULD be mapped to properties dcat:endpointURL, dcat:endpointDescription, and dct:conformsTo, as described above.

B.6.5 Unique resource identifier - *not in ISO 19115 core

In INSPIRE, this element is meant to uniquely identify a resource (dataset, series or service), and it is mandatory for datasets and series. It is specified by (a) a mandatory character string code and by (b) an optional character string namespace.

Based on [DCAT-AP-20200608], unique resource identifiers are mapped to dct:identifier (see Example 30). The actual value is obtained by the concatenation of the values of the namespace (if specified) and of the code in the original metadata record.

If the unique resource identifier is specified with or can be encoded as an HTTP URI, it can be used as the URI of the resource (see Example 31).

B.6.6 Coupled resource - *not in ISO 19115 core

Note

This element is used to link a service to the target datasets or dataset series.

Following [VOCAB-DCAT-2] and [DCAT-AP-20200608], this relationship is specified by using property dcat:servesDataset.

Note

The target dataset or series SHOULD be preferably referred to by using its unique resource identifier, as in Example 32.

B.6.7 Resource language and metadata language - *Dataset language and Metadata language

In INSPIRE metadata, metadata and resource languages (which may be different) are specified by using the three-letter language codes defined in [ISO-639-2].

Based on [DCAT-AP-20200608], both elements are specified with property dct:language, with the URI of the relevant language available from the relevant register operated by the EU Publications Office [EUV-LANG].

Example 33 assumes that the metadata language is Dutch, and the resource language is German.

The metadata language can be also used to specify the language of textual elements of resource metadata by using the @xml:lang attribute [XML].

Since @xml:lang takes as value language identifiers defined by IETF BCP 47 [BCP47], a mapping from the actual value of the metadata language is needed.

B.6.8 Topic category, originating controlled vocabulary, and keyword value - *Dataset topic category

In INSPIRE, these two elements have specific purposes. Quoting from the INSPIRE Metadata Regulation [INSPIRE-MD-REG] (§2.1 and §3.1, respectively):

  • The topic category is a high-level classification scheme to assist in the grouping and topic-based search of available spatial data resources.

  • The keyword value is a commonly used word, formalised word or phrase used to describe the subject. While the topic category is too coarse for detailed queries, keywords help narrowing a full text search and they allow for structured keyword search.

Moreover, two types of keywords are allowed:

  • free keywords;

  • keywords taken from a controlled vocabulary.

Finally, topic categories apply only to datasets and dataset series.

B.6.8.1 Topic category and keyword in datasets and dataset series

As far as dataset metadata are concerned, in both [VOCAB-DCAT-2] and [DCAT-AP-20200608], a distinction is made only between free keywords and keywords from controlled vocabularies, associated with a URI. For the former, dcat:keyword is used, whereas for the latter dcat:theme (which is a sub-property of dct:subject). Since the INSPIRE Registry operates URI registers for topic categories and INSPIRE spatial data themes, and in order to keep the distinction existing in INSPIRE between topic categories and keywords, the mapping is as follows:

  • Topic category is mapped to dct:subject, and expressed by the corresponding URIs minted for the ISO code list in the INSPIRE Registry – reference register:

    http://inspire.ec.europa.eu/metadata-codelist/TopicCategory

  • Keywords not associated with a controlled vocabulary will be mapped to dcat:keyword;

  • INSPIRE spatial data themes are mapped to dcat:theme and expressed by the corresponding URI in the INSPIRE Registry – reference register:

    http://inspire.ec.europa.eu/theme

  • Keywords associated with other controlled vocabularies are mapped to dcat:theme.

Following [DCAT-AP-20200608] recommendations, keywords from controlled vocabularies SHOULD be preferably specified with dereferenceable HTTP URIs. In such a case, the information concerning the originating controlled vocabulary can be omitted.

When keywords cannot be specified with HTTP URIs, they SHOULD be modelled as a skos:Concept associated with a skos:ConceptScheme (modelling the originating controlled vocabulary), and annotated with the textual content and reference date(s) in the relevant INSPIRE metadata elements.

The representation of the information concerning the controlled vocabulary is illustrated in the following table.

Metadata Element Proposed mapping
Originating controlled vocabulary Title skos:ConceptScheme dct:title
Reference date creation dct:created
last revision dct:modified
publication dct:issued

For conformance with [DCAT-AP-20200608], GeoDCAT-AP records MUST also include keywords from the EU Vocabularies Data Theme Named Authority List [EUV-THEMES].

In order to ensure consistency, the relevant EU Vocabularies Data Theme keywords SHOULD be selected based on mappings with the controlled vocabularies used in INSPIRE / ISO 19115 metadata.

Note
B.6.8.2 Keyword in services
Note

As far as service metadata are concerned, keywords can classify either a service or the datasets / series operated by the service itself. For the latter, INSPIRE Metadata Regulation requires using at least one of the keywords from the ISO 19119 code list of spatial data service categories.

Both [VOCAB-DCAT-2] and [DCAT-AP-20200608] do not have any specific property for keywords classifying either a service or the datasets / series operated by a service. Moreover, dcat:theme and dcat:keyword cannot be used for services, since their domain is restricted to dcat:Dataset.

In order to keep the distinction between these two types of keywords, the adopted solution is as follows:

  • Keywords from the ISO 19119 codelists of spatial data service type and categories are mapped to dct:type, and expressed by the corresponding URI in the INSPIRE Registry – reference registers:

  • Keywords not associated with a controlled vocabulary will be mapped to dcat:keyword, and represented as un-typed literals;

  • INSPIRE spatial data themes are mapped to dcat:theme, and expressed by the corresponding URI in the INSPIRE Registry – reference register:

  • Keywords associated with other controlled vocabularies are mapped to dcat:theme. If not denoted by an HTTP URI, they SHOULD be expressed as a skos:Concept associated with a skos:ConceptScheme, and annotated with the textual content and reference date(s) in the relevant INSPIRE metadata elements.

B.6.9 Spatial data service type - *not in ISO 19115 core

See § B.6.3 Resource type - *not in ISO 19115 core on resource type.

B.6.10 Geographic bounding box - *Geographic location of the dataset (by 4 coordinates or by geographic identifier)

Note

In the core profile of [ISO-19115], spatial coverage can be specified either with a bounding box (a geometry) or a geographic identifier. INSPIRE is more restrictive, in that it requires using a bounding box

Based on that, GeoDCAT-AP specified spatial coverage as illustrated in the following sections.

B.6.10.1 Bounding box

As a general rule, when the area corresponding to the spatial coverage is denoted by a geometry, as in INSPIRE, [DCAT-AP-20200608] recommends the use of the Core Location Vocabulary [LOCN], where this is done by using property locn:geometry, having as range a geometry specified as

However, in case the geometry is a bounding box or a centroid, properties dcat:bbox and dcat:centroid, respectively, SHOULD be used instead of locn:geometry.

It is worth noting that currently there is no agreement on a preferred format to be used in RDF for the representation of geometries. In GeoDCAT-AP, geometries can be provided in any, and possibly multiple, encodings, but at least one of the following must be made available: WKT or GML. An additional requirement concerns the coordinate reference system (CRS) used, which may vary on a country or territory basis. The CRS must be specified in the GML or WKT encoding as required by GeoSPARQL [GeoSPARQL]. Geometries shall be interpreted using the axis order defined in the spatial reference system used. For example, for CRS84 the axis order is longitude / latitude, whereas for WGS84 the axis order is latitude / longitude. Summarising:

  • Geometries MAY be provided in multiple encodings, but at least one of the following MUST be made available: GML and WKT.

  • For GML and WKT, the CRS MUST be specified as defined in GeoSPARQL [GeoSPARQL].

As geometries may be provided in multiple encodings, the corresponding datatype SHOULD be always specified to ensure that the geometry literal is correctly interpreted.

For GML and WKT, the [GeoSPARQL] datatypes gsp:gmlLiteral and gsp:wktLiteral, respectively, MUST be used.

For GeoJSON [RFC7946], datatype gsp:geoJSONLiteral, defined in the current draft of the new version of GeoSPARQL [GeoSPARQL11], SHOULD be used.

For the other geometry encodings, no datatype is currently available. Therefore, their interoperability is not ensured when metadata records are shared or harvested across catalogues.

Note
B.6.10.2 Geographic identifier

[ISO-19115] core also allows specifying the geographic location using a geographic identifier. Following [DCAT-AP-20200608], for this, it is RECOMMENDED to use an HTTP URI from one of the following registers / gazetteers:

  • The Named Authority Lists operated by the Metadata Registry of the EU Publications office concerning continents [EUV-CONT], countries [EUV-COUNTRIES], and places [EUV-PLACES].

If none of the above provides the relevant geographic identifiers, Geonames [GEONAMES] SHOULD be used.

If an HTTP URI is not available, the geographic identifier MUST be expressed with skos:prefLabel, and the reference to the originating controlled vocabulary (if any) MUST be specified with skos:inScheme. The controlled vocabulary will be described by a name (dct:title) and a last modified data (dct:modified).

As far as geographic identifiers are concerned, following [DCAT-AP-20200608], GeoDCAT-AP does not prevent the use other vocabularies in addition to the recommended ones. The vocabularies identified by the GeoDCAT-AP WG are listed in § 5.2 Controlled vocabularies to be used.

B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp

Note

Temporal reference is a composite element consisting of the following possible child elements:

  • temporal extent (temporal coverage);

  • date of publication, last revision, and/or creation.

Based on [DCAT-AP-20200608], temporal extent is mapped to dct:temporal, having as range dct:PeriodOfTime. The time instant or interval is specified by using properties dcat:startDate and dcat:endDate, respectively.

By contrast, date of publication, last revision, and creation are mapped, respectively, to dct:issued, dct:modified (both core and extended GeoDCAT-AP mapping profiles), and dct:created (only for the extended mapping profile of GeoDCAT-AP).

[DCAT-AP-20200608] does not have a property equivalent to the INSPIRE metadata element metadata date. In INSPIRE, this element is defined as follows (see [INSPIRE-MD-REG], Part B, §10.2):

The date which specifies when the metadata record was created or updated.

Due to this ambiguity, the defined mapping for this element is dct:modified.

B.6.12 Lineage - *Lineage

Following [DCAT-AP-20200608], this element is mapped to property dct:provenance.

Since the range of dct:provenance is not a literal, but class dct:ProvenanceStatement, the free-text content of element “lineage” can be expressed by using rdfs:label, as illustrated in [DC-UG-PM].

B.6.13 Spatial resolution – Spatial resolution of the dataset

Note

[VOCAB-DCAT-2] and [DCAT-AP-20200608] provide property dcat:spatialResolutionInMeters, to specify spatial resolution as distance in metres. Morever, [VOCAB-DCAT-2] and [SDW-BP] recommend the use of [VOCAB-DQV] to specify other types of spatial resolution, via property dqv:hasQualityMeasurement.

Based on this, GeoDCAT-AP specifies spatial resolution as follows:

  • Property dcat:spatialResolutionInMeters is used for spatial resolution when it is expressed as distance in metres.
  • Property dqv:hasQualityMeasurement is used for all types of spatial resolution. In such a case, the type of spatial resolution is specified by using property dqv:isMeasurementOf, which takes as value the relevant instance of class dqv:Metric defined in GeoDCAT-AP for this purpose (see § 4.20.1 Instances of Metric).
  • Property rdfs:comment is used when spatial resolution is specified as free-text.

The core mapping profile of GeoDCAT-AP, following [DCAT-AP-20200608], supports only the use property dcat:spatialResolutionInMeters, and, therefore, the other types of spatial resolution are left unmapped.

B.6.14 Conformity and data quality - *not in ISO 19115 core

In [ISO-19115], conformance and quality information is encoded as a quality report containing the result of a test (an evaluation) of a given quality measure, according to an evaluation method, with either a quantitative result (a metric) or a conformance result (pass or fail) as most important outcome.

The current version of GeoDCAT-AP only defines a syntax binding for conformity and not for data quality in general, making use of property dct:conformsTo and the W3C Provenance Ontology (PROV-O) [PROV-O], as explained in the following paragraphs.

[DCAT-AP-20200608] provides a single candidate, dct:conformsTo, which however can be used to map only a conformity of degree ‘conformant’. This is suitable for the core mapping profile of GeoDCAT-AP.

Considering how conformity must be expressed in extended mapping profile of GeoDCAT-AP (see [INSPIRE-MD-REG], Part B, §7), possible candidates are the W3C Evaluation and Report Language (EARL) [EARL10] and the W3C Provenance Ontology (PROV-O) [PROV-O]. The latter candidate was chosen by the GeoDCAT-AP Working Group, since it would enable wider re-use with respect to the EARL vocabulary, which is more specific, and its use is limited.

[PROV-O] allows encoding conformity as a test activity (prov:Activity) that generated a result specified with property prov:generated, corresponding to the degree of conformity, for which the INSPIRE Registry maintains a URI set [INSPIRE-DoC]. The specification against which the conformance is asserted is specified via a qualified association (prov:qualifiedAssociation) with a test plan (a prov:Plan) in turn derived from a standard (dct:Standard, also prov:Entity). These associations are made via a property chain: prov:qualifiedAssociation, prov:hadPlan, and prov:wasDerivedFrom.

This pattern is illustrated in the following table.

Metadata element Proposed mapping
Conformity Specification (M) Title prov:wasUsedBy (range prov:Activity) prov:qualifiedAssociation (range prov:Assocation) > prov:hadPlan (range prov:Plan) > prov:wasDerivedFrom (range: prov:Entity, dct:Standard) dct:title
Reference date creation dct:created
last revision dct:modified
publication dct:issued
Degree (M) prov:generated (range prov:Entity) dct:type (range [INSPIRE-DoC])
dct:description

In order to grant interoperability with [DCAT-AP-20200608], when conformity is of degree “conformant”, the proposal is to use both [PROV-O] and dct:conformsTo for GeoDCAT-AP Extended.

B.6.15 Conditions for access and use and limitations on public access – Use limitation and access / other constraints

Note

In [DCAT-AP-20200608], licensing information is specified on (a) data catalogues (services) and on (b) the distribution(s) of a dataset, and not on the dataset itself. The principle is that different dataset distributions may be associated with different licensing terms. Moreover, [DCAT-AP-20200608] recommends the use of dct:accessRights for specifying access conditions.

Based on this, GeoDCAT-AP specifies use and access limitations by using, respectively, dct:license and dct:accessRights. These properties take as value the URI of the use / access limitations, when available. Otherwise, since the range of these properties is not a literal, but, respectively, classes dct:LicenseDocument and dct:RightsStatement, the free-text content of the corresponding ISO 19115 / INSPIRE metadata elements can be expressed by using rdfs:label, as illustrated in [DC-UG-PM].

Note

B.6.16 Responsible party and metadata point of contact - *Dataset responsible party and *Metadata point of contact

Note

[DCAT-AP-20200608] supports properties to denote the publisher, the creator, and the contact point for a dataset.

By contrast, [ISO-19115] and [INSPIRE-MD-REG] support 11 possible relationships between a resource (a dataset, a dataset series, a service) and an agent (organisation), plus one for metadata. However, for only some of them suitable candidates exist from widely used vocabularies (in particular, DCMI Metadata Terms [DCTERMS]).

In order to fill this gap, specific properties have been defined in the GeoDCAT-AP namespace to complement those available in [DCAT-AP-20200608] and [DCTERMS].

The following table lists the mappings between responsible party roles and the corresponding properties used in GeoDCAT-AP.

[ISO-19115] [INSPIRE-MD-REG] Description Proposed RDF mapping
Resource provider Part B, §6.1 Party that supplies the resource. geodcat:resourceProvider
Custodian Part B, §6.2 Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource. geodcat:custodian
Owner Part B, §6.3 Party that owns the resource. dct:rightsHolder
User Part B, §6.4 Party who uses the resource. geodcat:user
Distributor Part B, §6.5 Party who distributes the resource geodcat:distributor
Originator Part B, §6.6 Party who created the resource. geodcat:originator
Point of contact Part B, §6.7 Party who can be contacted for acquiring knowledge about or acquisition of the resource. dcat:contactPoint
Principal investigator Part B, §6.8 Key party responsible for gathering information and conducting research geodcat:principalInvestigator
Processor Part B, §6.9 Party who has processed the data in a manner such that the resource has been modified. geodcat:processor
Publisher Part B, §6.10 Party who published the resource dct:publisher
Author Part B, §6.11 Party who authored the resource. dct:creator

The extended mapping profile of GeoDCAT-AP also supports the use of the W3C PROV ontology [PROV-O] and [VOCAB-DCAT-2] to specify the relationship between the resource and the responsible organisation. The FOAF Vocabulary [FOAF] is used to specify the contact information concerning the responsible party. Finally, the responsible party role will be specified by using dcat:hadRole, and using the relevant code list values from the INSPIRE Registry – reference register [INSPIRE-RPR]:

http://inspire.ec.europa.eu/metadata-codelist/ResponsiblePartyRole

These mappings are illustrated in the following table.

Metadata element Proposed mapping
Responsible party Responsible party Organisation name prov:qualifiedAttribution (range prov:Attribution) prov:agent (range prov:Agent, foaf:Agent) foaf:name
Contact email address foaf:mbox
Responsible party role dcat:hadRole (range dcat:Role)

It is important to note that the [PROV-O]-based mappings are semantically equivalent to the property-based ones illustrated earlier in this section. Their use is therefore only accessory, and functional to possible requirements from the data provider side.

For these reasons, the GeoDCAT-AP overall approach is as follows:

  • Responsible parties and their roles MUST be represented by the corresponding properties, based on an agreed definition of 1-to-1 mappings.
  • The property-based representation MAY be complemented with the [PROV-O]-based approach.

As mentioned earlier, the latter option is supported only in the extended mapping profile of GeoDCAT-AP.

B.6.17 *Metadata file identifier

This element identifies a metadata record.

Metadata file identifiers are mapped to dct:identifier.

If the metadata file identifier is or can be encoded as an HTTP URI, it can also be used as the URI of the catalogue record (see Example 44).

B.6.18 *Metadata standard name, *Metadata standard version

Following [DCAT-AP-20200608], GeoDCAT-AP uses dct:conformsTo to specify the metadata standard, and properties dct:title and owl:versionInfo are used to specify the standard name and version, respectively.

This pattern is illustrated in the following table.

Metadata element Proposed mapping
Metadata standard Metadata standard name dct:conformsTo (range dct:Standard) dct:title
Metadata standard version owl:versionInfo

Example 45 shows a GeoDCAT-AP metadata record obtained from one conformant with [ISO-19115].

To represent the standard name and version of the source ISO record, the GeoDCAT-AP metadata record must be extended as in Example 46.

B.6.19 *Metadata characterset

See § B.6.24 Character encoding - *Dataset character set and *Metadata character set.

B.6.20 Metadata point of contact - *Metadata point of contact

See § B.6.16 Responsible party and metadata point of contact - *Dataset responsible party and *Metadata point of contact.

B.6.21 Metadata date - *Metadata date stamp

See § B.6.11 Temporal reference and metadata date –*Additional extent information for the dataset (vertical and temporal) and *Metadata date stamp.

B.6.22 Metadata language - *Metadata language

See § B.6.7 Resource language and metadata language - *Dataset language and Metadata language.

B.6.23 Coordinate reference systems and Temporal reference systems – *Reference System

In GeoDCAT-AP, these elements are mapped to property dct:conformsTo. Moreover, in order to indicate that the object of dct:conformsTo denotes a reference system, an additional statement with predicate dct:type is added, with a code list value defining the notion of (spatial / temporal) reference system, taken from the glossary operated by the INSPIRE Registry.

More precisely, the following URIs SHOULD be used to denote, respectively, spatial and temporal reference systems:

The reference system identifier SHOULD be preferably represented with an HTTP URI. In particular, spatial reference systems should be specified by using the corresponding URIs from the “EPSG coordinate reference systems” register operated by the Open Geospatial Consortium [OGC-EPSG].

In this register, the URI prefix for coordinate reference systems is the following one:

http://www.opengis.net/def/crs/EPSG/0/

followed by the number identifying the coordinate reference system in the EPSG register. For instance, the following URI

http://www.opengis.net/def/crs/EPSG/0/4258

identifies coordinate reference system EPSG 4258, corresponding to ETRS89 (European Terrestrial Reference System 1989).

Note

In case the reference system is not specified as an HTTP URI, the mapping covers also other information included in the source metadata - as the identifier (dct:identifier), name (dct:title), and version (owl:versionInfo), plus a reference to the relevant register, if available (skos:inScheme). If a reference register is available, the reference system is implicitly also a skos:Concept, and its name can be specified by using skos:prefLabel.

Note

If not represented with an HTTP URI, the reference system identifier MUST be mapped to dct:identifier, as in Example 48.

B.6.24 Character encoding - *Dataset character set and *Metadata character set

In [VOCAB-DCAT-2] and [DCAT-AP-20200608], the specification of the character encoding of a dataset and the character encoding of a metadata record is not explicitly supported.

According to [RFC4288], the character set can be part of the media type specification, but only for type “text”. By contrast, in INSPIRE the character set can be specified also for other media types.

The W3C Content vocabulary [Content-in-RDF10] provides a possibly suitable candidate, namely, property cnt:characterEncoding, taking as value the character set names in the IANA register [IANA-CHARSETS]. GeoDCAT-AP uses this property.

Character encoding in [ISO-19115] metadata is specified with a code list that can be mapped to the corresponding codes in [IANA-CHARSETS], as shown in the following table (entries with 1-to-many mappings are in italic).

ISO 19115 - MD_CharacterSetCode Description IANA
ucs2 16-bit fixed size Universal Character Set, based on ISO/IEC 10646 ISO-10646-UCS-2
ucs4 32-bit fixed size Universal Character Set, based on ISO/IEC 10646 ISO-10646-UCS-4
utf7 7-bit variable size UCS Transfer Format, based on ISO/IEC 10646 UTF-7
utf8 8-bit variable size UCS Transfer Format, based on ISO/IEC 10646 UTF-8
utf16 16-bit variable size UCS Transfer Format, based on ISO/IEC 10646 UTF-16
8859part1 ISO/IEC 8859-1, Information technology - 8-bit single byte coded graphic character sets - Part 1 : Latin alphabet No.1 ISO-8859-1
8859part2 ISO/IEC 8859-2, Information technology - 8-bit single byte coded graphic character sets - Part 2 : Latin alphabet No.2 ISO-8859-2
8859part3 ISO/IEC 8859-3, Information technology - 8-bit single byte coded graphic character sets - Part 3 : Latin alphabet No.3 ISO-8859-3
8859part4 ISO/IEC 8859-4, Information technology - 8-bit single byte coded graphic character sets - Part 4 : Latin alphabet No.4 ISO-8859-4
8859part5 ISO/IEC 8859-5, Information technology - 8-bit single byte coded graphic character sets - Part 5 : Latin/Cyrillic alphabet ISO-8859-5
8859part6 ISO/IEC 8859-6, Information technology - 8-bit single byte coded graphic character sets - Part 6 : Latin/Arabic alphabet ISO-8859-6
8859part7 ISO/IEC 8859-7, Information technology - 8-bit single byte coded graphic character sets - Part 7 : Latin/Greek alphabet ISO-8859-7
8859part8 ISO/IEC 8859-8, Information technology - 8-bit single byte coded graphic character sets - Part 8 : Latin/Hebrew alphabet ISO-8859-8
8859part9 ISO/IEC 8859-9, Information technology - 8-bit single byte coded graphic character sets - Part 9 : Latin alphabet No.5 ISO-8859-9
8859part10 ISO/IEC 8859-10, Information technology - 8-bit single byte coded graphic character sets - Part 10 : Latin alphabet No.6 ISO-8859-10
8859part11 ISO/IEC 8859-11, Information technology - 8-bit single byte coded graphic character sets - Part 11 : Latin/Thai alphabet ISO-8859-11
8859part13 ISO/IEC 8859-13, Information technology - 8-bit single byte coded graphic character sets - Part 13 : Latin alphabet No.7 ISO-8859-13
8859part14 ISO/IEC 8859-14, Information technology - 8-bit single byte coded graphic character sets - Part 14 : Latin alphabet No.8 (Celtic) ISO-8859-14
8859part15 ISO/IEC 8859-15, Information technology - 8-bit single byte coded graphic character sets - Part 15 : Latin alphabet No.9 ISO-8859-15
8859part16 ISO/IEC 8859-16, Information technology - 8-bit single byte coded graphic character sets - Part 16 : Latin alphabet No.10 ISO-8859-16
jis japanese code set used for electronic transmission JIS_Encoding
shiftJIS japanese code set used on MS-DOS machines Shift_JIS
eucJP japanese code set used on UNIX based machines EUC-JP
usAscii United States ASCII code set (ISO 646 US) US-ASCII
ebcdic IBM mainframe code set IBM037
eucKR Korean code set EUC-KR
big5 traditional Chinese code set used in Taiwan, Hong Kong of China and other areas Big5
GB2312 simplified Chinese code set GB2312

B.6.25 Encoding - *Distribution format

In both [VOCAB-DCAT-2] and [DCAT-AP-20200608], this information is specified for the distribution(s) of a dataset, and not for the dataset itself.

Two properties are available:

  • dcat:mediaType: to be used when the format corresponds to one of the media types registered by IANA [IANA-MEDIA-TYPES].

  • dct:format: to be used in all the other cases, to be used with file type register operated by the Publications Office of the EU [EUV-FT].

The same approach is used in GeoDCAT-AP for ISO 19115 / INSPIRE metadata.

B.6.26 Spatial representation type – *Spatial representation type

In [DCAT-AP-20200608], no equivalent term is provided.

In [ISO-19115], element “Spatial representation type” is meant mainly to describe the “method used to represent geographic information in the dataset”, by using a code list (see the table below).

The ADMS vocabulary [VOCAB-ADMS] includes a property, namely, adms:representationTechnique that could be used for this purpose. It is worth noting that, in the ADMS specification, adms:representationTechnique decribes a distribution, and not the dataset. Moreover, the [ISO-19115] code list of spatial representation types might be in the future available as a URI register from the INSPIRE Registry.

Based on this, GeoDCAT-AP models this information by using property adms:representationTechnique, with the spatial representation type URIs that will be operated by the INSPIRE Registry.

This mapping is supported only in the extended mapping profile of GeoDCAT-AP.

The spatial representation types defined in [ISO-19115] are listed in the following table. It is important to note that, as stated in the INSPIRE Data Specifications, the only spatial representation types in scope of INSPIRE are the following ones: “vector”, “grid”, and “tin”.

ISO 19115 - MD_SpatialRepresentionTypeCode Description In scope of INSPIRE?
vector vector data is used to represent geographic data Yes
grid grid data is used to represent geographic data Yes
textTable textual or tabular data is used to represent geographic data No
tin triangulated irregular network Yes
stereoModel three-dimensional view formed by the intersecting homologous rays of an overlapping pair of images No
video scene from a video recording No

B.6.27 Maintenance information - *not in ISO 19115 core

In [ISO-19115], element “Maintenance information” is meant mainly to describe how frequently a resource is updated.

In [DCAT-AP-20200608], the update frequency is expressed through dct:accrualPeriodicity, with the frequency codes defined in the the EU Vocabularies Frequency Named Authority List [EUV-FREQ], which can be partially mapped to the ones used in [ISO-19115], as shown in the following table.

ISO 19115 - MD_MaintenanceFrequencyCode Dublin Core Collection Description Frequency Vocabulary [CLD-FREQ] EU Vocabularies Frequency Named Authority List [EUV-FREQ]
continual continuous UPDATE_CONT / CONT
daily daily DAILY
weekly weekly WEEKLY
fortnightly biweekly BIWEEKLY
monthly monthly MONTHLY
quarterly quarterly QUARTERLY
biannually semiannual ANNUAL_2
annually annual ANNUAL
asNeeded - -
Irregular irregular IRREG
notPlanned - -
unknown - UNKNOWN
- triennial TRIENNIAL
- biennial BIENNIAL
- threeTimesAYear ANNUAL_3
- bimonthly BIMONTHLY
- semimonthly MONTHLY_2
- threeTimesAMonth MONTHLY_3
- semiweekly WEEKLY_2
- threeTimesAWeek WEEKLY_3
- - OTHER

The [ISO-19115] code list of maintenance frequency codes might be in the future available as a URI register from the INSPIRE Registry.

Based on this, maintenance frequency is modelled in GeoDCAT-AP by using dct:accrualPeriodicity with the EU Vocabularies Frequency Named Authority List [EUV-FREQ].

For the frequency codes not covered by the EU Vocabularies Frequency code list, the approach will be as follows:

  • In the core mapping profile of GeoDCAT-AP these codes will be ignored.

  • The extended mapping profile of GeoDCAT-AP will use the code list of ISO maintenance frequency codes operated by the INSPIRE Registry.

B.7 Comparison between INSPIRE and ISO 19115-1:2014

In [ISO-19115-1] the concept of ‘Core metadata’ was removed; it was translated into a normative annex (Annex F) “Discovery metadata for geographic resources”. In the Annex F metadata elements for the discovery are listed in 2 tables:

B.7.1 Spatial dataset and spatial dataset series

The table below compares the core requirements of ISO 19115:2003 (see Table 3 in 6.5 of [ISO-19115]), the requirements of INSPIRE for spatial dataset and spatial dataset series as defined in the Implementing Rules for metadata and the discovery metadata for geographic datasets and series (see Table F.1 in annex F of [ISO-19115-1]). For those last metadata elements in the last field of the table the path is indicated. For each element, in brackets the obligation/max occurrence (3rd field).

ISO 19115 Core INSPIRE Implementing Rules for Metadata ISO 19115-1:2014 Discovery metadata for datasets and series (Table F.1) ISO 19115-1:2014 Path
Dataset title (M) Part B 1.1 Resource Title Resource title (M/1) MD_Metadata.identificationInfo > MD_DataIdentification.citation > CI_Citation.title
Dataset reference date (M) Part B 5 Temporal Reference Resource reference date (O/N) MD_Metadata.idenitificationInfo > MD_DataIdentification.citation > CI_Citation.date
Dataset responsible party (O) Part B 9 Responsible organisation Resource point of contact (O/N) MD_Metadata.identificationInfo > MD_DataIdentification.pointOf-Contact > CI_Responsibility
Geographic location of the dataset (C) Part B 4.1 Geographic Bounding Box Geographic location (C/N) MD_Metadata.identificationInfo > MD_DataIdentification.extent > EX_Extent.geographicElement > EX_GeographicExtent > EX_GeographicBoundingBox -or- EX_GeographicDescription)
Dataset language (M) Part B 1.7 Resource Language Resource language (C/N) MD_Metadata.identificationInfo > MD_DataIdentification.defaultLocale > PT_Locale
Dataset character set (C) - -
Dataset topic category (M) Part B 2.1 Topic Category Resource topic category (C/N) MD_Metadata.identificationInfo > MD_DataIdentification.topicCategory > MD_TopicCategoryCode
Spatial resolution of the dataset (O) Part B 6.2 Spatial Resolution Spatial resolution (O/N)

MD_Metadata.identificationInfo > MD_Identification.spatialResolution > MD_Resolution.equivalentScale MD_Resolution.distance, MD_Resolution.vertical, or MD_Resolution.angularDistance, or MD_Resolution.levelOfDetail

Abstract describing the dataset (M) Part B 1.2 Resource abstract Resource abstract (M/1) MD_Metadata.identificationInfo > MD_DataIdentification.abstract
Distribution format (O) - -
Additional extent information for the dataset (vertical and temporal) (O) Part B 5.1 Temporal extent Extent information for the dataset (additional) (O/N) MD_Metadata.identificationInfo > MD_Identification.extent > EX_Extent > EX_TemporalExtent or EX_VerticalExtent
Spatial representation type (O) - -
Reference system (O) - -
Lineage (O) Part B 6.1 Lineage Resource lineage (O/N) MD_Metadata > resourceLineage > LI_Lineage.statement
On-line resource (O) Part B 1.4 Resource Locator Resource on-line Link (O/N) MD_Metadata.identificationInfo > MD_DataIdentification.citation > CI_Citation.onlineResource > CI_OnlineResource
Metadata file identifier (O) - Metadata reference information (O/1) MD_Metadata.metadataIdentifier
Metadata standard name (O) - -
Metadata standard version (O) - -
Metadata language (C) Part B 10.3 Metadata Language - MD_Metadata.defaultLocale > PT_Locale.language
Metadata character set (C) - -
Metadata point of contact (M) Part B 10.1 Metadata point of contact Metadata point of contact (M/N) MD_Metadata.contact > CI_Responsibility
Metadata date stamp (M) Part B 10.2 Metadata Date Metadata date stamp (M/N) MD_Metadata.dateInfo
- Part B 1.3 Resource Type Resource type (C/1) MD_Metadata.metadataScope > MD_Scope.resourceScope
Part B 1.5 Unique Resource Identifier Resource identifier (O/N) MD_Metadata.identificationInfo > MD_DataIdentification.citation > CI_Citation.identifier > MD_Identifier
Part B 3 Keyword Keywords (O/N) MD_Metadata.identificationInfo > MD_DataIdentification > descriptiveKeywords > MD_Keywords
- Part B 7 Conformity - MD_Metadata.dataQualityInfo > DQ_DataQuality.report > DQ_UsabilityElement.result > DQ_ConformanceResult
- Part B 8.1 Conditions for access and use Constraints on resource access and use (O/N) MD_Metadata.identificationInfo > MD_DataIdentification > MD_Constraints.useLimitations
- Part B 8.2 Limitations on public access Constraints on resource access and use (O/N) MD_Metadata.identificationInfo > MD_DataIdentification > MD_LegalConstraints.accessConstraint and/or MD_LegalConstraints.otherConstraint and/or MD_SecurityConstraints.classification

B.7.2 Services

The table below compares the core requirements of ISO 19115:2003 (see Table 3 in 6.5 of ISO 19115:2003), the requirements of INSPIRE for services as defined in the Implementing Rules for metadata and the discovery metadata for services (see Table F.2 in annex F of ISO 19115-1:2014). For those metadata elements in the last field of the table the path is indicated. For each element, in brackets the obligation/max occurrence (3rd field).

ISO 19115 Core INSPIRE ISO 19115-1:2014 Discovery metadata for services (Table F.2) Path ISO 19115-1:2014
Dataset title (M) Part B 1.1 Resource Title Service title (M/1) MD_Metadata.identificationInfo > SV_ServiceIdentification.citation > CI_Citation.title
Dataset reference date (M) Part B 5 Temporal Reference Reference date (O/1) MD_Metadata.identificationInfo > SV_ServiceIdentification.citation > CI_Citation.date
Dataset responsible party (O) Part B 9 Responsible organisation Responsible party (O/N) MD_Metadata.identificationInfo > SV_ServiceIdentification.pointOfContact > CI_Responsibility
Geographic location of the dataset (C) - Geographic location (M/1) MD_Metadata.identificationInfo > SV_ServiceIdentification.extent > EX_Extent.geographicElement > EX_GeographicExtent > EX_GeographicBoundingBox -or- EX_GeographicDescription
- Part B 4.1 Geographic Bounding Box -
Dataset language (M) - -
Dataset character set (C) - -
Dataset topic category (M) - Service topic category (O/N) MD_Metadata.identificationInfo > SV_ServiceIdentification.topicCategory > MD_TopicCategoryCode
Spatial resolution of the dataset (O) Part B 6.2 Spatial Resolution -
Abstract describing the dataset (M) Part B 1.2 Resource abstract Resource abstract (M/1) MD_Metadata.identificationInfo > SV_ServiceIdentification.abstract
Distribution format (O) - -
Additional extent information for the dataset (O) - -
Spatial representation type (O) - -
Reference system (O) - -
Lineage (O) - -
On-line resource (O) Part B 1.4 Resource Locator On-line Link (O/N) MD_Metadata.identificationInfo > SV_ServiceIdentification.citation > CI_Citation.onlineResource > CI_OnlineResource
Metadata file identifier (O) - Metadata reference information (O/1) MD_Metadata.metadataIdentifier
Metadata standard name (O) - -
Metadata standard version (O) - -
Metadata language (C) Part B 10.3 Metadata Language - MD_Metadata.defaultLocale > PT_Locale.language
Metadata character set (C) - -
Metadata point of contact (M) Part B 10.1 Metadata point of contact Metadata point of contact (M/N) MD_Metadata.contact > CI_Responsibility
Metadata date stamp (M) Part B 10.2 Metadata Date Metadata date stamp (M/N) MD_Metadata.dateInfo
- Part B 1.3 Resource Type Resource type (M/1) MD_Metadata.metadataScope > MD_Scope.resourceScope
- Part B 1.6 Coupled Resource Coupled Resource (C/N) MD_Metadata > SV_ServiceIdentification.coupledResource > SV_CoupledResource
- Part B 2.2 Spatial Data Service Type -
Part B 3 Keyword Keywords (O/N) MD_Metadata.identificationInfo > SV_ServiceIdentification > MD_Keywords
- Part B 7 Conformity - MD_Metadata.dataQualityInfo > DQ_DataQuality.report > DQ_UsabilityElement.result > DQ_ConformanceResult
- Part B 8.1 Conditions for access and use Constraints on access and use (O/N) MD_Metadata.identificationInfo > MD_DataIdentification > MD_Constraints.useLimitations
- Part B 8.2 Limitations on public access Constraints on access and use (O/N) MD_Metadata.identificationInfo > MD_DataIdentification > MD_LegalConstraints.accessConstraint and/or MD_LegalConstraints.otherConstraint and/or MD_SecurityConstraints.classification
- - Coupled resource type (C/1) MD_Metadata > SV_ServiceIdentification.couplingType > SV_CouplingType
- - Resource identifier (O/N) MD_Metadata.identificationInfo > SV_ServiceIdentification.citation > CI_Citation.identifier > MD_Identifier

C. Change Log

A full change-log is available on GitHub

C.1 Changes since first public working draft of 12 October 2020

C.2 Changes since GeoDCAT-AP 1.0.1 (2 August 2016)

C.3 Changes since GeoDCAT-AP 1.0.0 (23 December 2015)

C.4 Summary of changes to Application Profile classes and properties

The table below summarises the changes applied to the current release of GeoDCAT-AP, including those inherited from [DCAT-AP].

URI Type Action Description Issue Release

gsp:geoJSONLiteral

Datatype

(geometry, bounding box, centroid)

New

GeoJSON literal.

GeoDCAT-AP-4

GeoDCAT-AP 2.0.0

https://www.iana.org/assignments/media-types/application/vnd.geo+json

Datatype

(geometry, bounding box, centroid)

Deprecated

GeoJSON literal.

GeoDCAT-AP-4

GeoDCAT-AP 2.0.0

+geodcat:custodian

Optional property

(Catalogue, Catalogue Record, Data Service, Dataset)

New

Range: foaf:Agent

Custodian.

GeoDCAT-AP-32

GeoDCAT-AP 2.0.0

+geodcat:distributor

Optional property

(Catalogue, Catalogue Record, Data Service, Dataset)

New

Range: foaf:Agent

Distributor.

GeoDCAT-AP-32

GeoDCAT-AP 2.0.0

+geodcat:originator

Optional property

(Catalogue, Catalogue Record, Data Service, Dataset)

New

Range: foaf:Agent

Originator.

GeoDCAT-AP-32

GeoDCAT-AP 2.0.0

+geodcat:principalInvestigator

Optional property

(Catalogue, Catalogue Record, Data Service, Dataset)

New

Range: foaf:Agent

Principal investigator.

GeoDCAT-AP-32

GeoDCAT-AP 2.0.0

+geodcat:processor

Optional property

(Catalogue, Catalogue Record, Data Service, Dataset)

New

Range: foaf:Agent

Processor.

GeoDCAT-AP-32

GeoDCAT-AP 2.0.0

+geodcat:resourceProvider

Optional property

(Catalogue, Catalogue Record, Data Service, Dataset)

New

Range: foaf:Agent

Resource provider.

GeoDCAT-AP-32

GeoDCAT-AP 2.0.0

+geodcat:user

Optional property

(Catalogue, Catalogue Record, Data Service, Dataset)

New

Range: foaf:Agent

User.

GeoDCAT-AP-32

GeoDCAT-AP 2.0.0

+dqv:hasQualityMeasurement

Optional property

(Data Service, Dataset, Distribution)

New

Range: dqv:QualityMeasurement

Has quality measurement.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+dqv:QualityMeasurement

Optional class

New

Represents the evaluation of a given resource (as a Data Service, Dataset, or Distribution) against a specific quality metric.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+dqv:isMeasurementOf

Recommended property

(Quality Measurement)

New

Range: dqv:Metric

Is measurement of.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+sdmx-attribute:unitMeasure

Recommended property

(Quality Measurement)

New

Range: skos:Concept

Unit of measure.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+dqv:value

Recommended property

(Quality Measurement)

New

Range: rdfs:Literal

Value.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+dqv:Metric

Optional class

New

Represents a standard to measure a quality dimension.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+geodcat:spatialResolutionAsAngularDistance

Class instance

New

Instance of: dqv:Metric

Spatial resolution as angular distance.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+geodcat:spatialResolutionAsDistance

Class instance

New

Instance of: dqv:Metric

Spatial resolution as distance.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+geodcat:spatialResolutionAsScale

Class instance

New

Instance of: dqv:Metric

Spatial resolution as equivalent scale.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+geodcat:spatialResolutionAsVerticalDistance

Class instance

New

Instance of: dqv:Metric

Spatial resolution as vertical distance.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+dqv:inDimension

Recommended property

(Metric)

New

Range: dqv:Dimension

Dimension.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+dqv:expectedDataType

Recommended property

(Metric)

New

Range: rdfs:Datatype

Expected data type.

GeoDCAT-AP-15

GeoDCAT-AP 2.0.0

+dcat:keyword

Optional property

(Catalogue, Data Service)

New

Range: rdfs:Literal

Tag / keyword.

GeoDCAT-AP-8

GeoDCAT-AP 2.0.0

+dcat:theme

Optional property

(Catalogue, Data Service)

New

Range: skos:Concept

Theme / category.

GeoDCAT-AP-8

GeoDCAT-AP 2.0.0

+dcat:spatialResolutionInMeters

Optional property

(Data Service)

New

Range: xsd:decimal

This property refers to the minimum spatial separation resolvable in a Data Service, measured in metres.

GeoDCAT-AP-3

GeoDCAT-AP 2.0.0

dcat:temporalResolution

Optional property

(Data Service)

New

Range: xsd:duration

This property refers to the minimum time period resolvable in a Data Service.

GeoDCAT-AP-3

[DCAT-AP-20191120]

+dctype:Service

Optional class

Deprecated

A system that provides one or more functions.

GeoDCAT-AP-10

GeoDCAT-AP 2.0.0

+dct:hasPart

Optional property

(Data Service)

Deprecated

Range: dcat:Dataset

Serves dataset.

GeoDCAT-AP-10

GeoDCAT-AP 2.0.0

+dc:subject

Optional property

(Catalogue, Data Service)

Deprecated

Range: rdfs:Literal

Keyword / tag.

GeoDCAT-AP-8

GeoDCAT-AP 2.0.0

+foaf:homepage

Optional property

(Data Service)

Deprecated

Range: foaf:Document

Endpoint URL.

GeoDCAT-AP-10

GeoDCAT-AP 2.0.0

+dct:subject

Optional property

(Catalogue, Data Service)

Deprecated

Range: skos:Concept

Theme / category.

GeoDCAT-AP-8

GeoDCAT-AP 2.0.0

+dct:type

Optional property

Deprecated

Range: skos:Concept

Agent role.

GeoDCAT-AP-16

GeoDCAT-AP 2.0.0

+rdfs:comment

Optional property

Deprecated

Range: rdfs:Literal

Spatial resolution.

GeoDCAT-AP-3

GeoDCAT-AP 2.0.0

dct:MediaTypeorExtent

Optional class

Deprecated

A media type or extent, e.g. the format of a computer file

DCAT-AP-80

[DCAT-AP-20191120]

dct:MediaType

Optional class

New

A media type, e.g. the format of a computer file

DCAT-AP-80

[DCAT-AP-20191120]

dct:language

Property

Update

Align with [VOCAB-DCAT-2]: add to usage of controlled vocabulary for all usages

DCAT-AP-88

[DCAT-AP-20191120]

dcat:mediaType

Optional property

(Distribution)

Update

Updates

Range: dct:MediaTypeOrExtentdct:MediaType

DCAT-AP-80

[DCAT-AP-20191120]

dcat:bbox

Recommended property

(Location)

New

Range: rdfs:Literal

This property refers to the geographic bounding box of a resource.

DCAT-AP-85

[DCAT-AP-20191120]

dcat:centroid

Recommended property

(Location)

New

Range: rdfs:Literal

This property refers to the geographic centre (centroid) of a resource

DCAT-AP-85

[DCAT-AP-20191120]

time:hasEnd

Optional property

(Period Of Time)

New

Range: time:Instant

This property contains the end of a period or interval.

DCAT-AP-84

[DCAT-AP-20191120]

time:hasBeginning

Optional property

(Period Of Time)

New

Range: time:Instant

This property contains the beggining of a period or interval.

DCAT-AP-84

[DCAT-AP-20191120]

dcat:endDate

Recommended property

(Period Of Time)

New

Range: rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the end of the period

DCAT-AP-83

[DCAT-AP-20191120]

dcat:startDate

Recommended property

(Period Of Time)

New

Range: rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the start of the period.

DCAT-AP-83

[DCAT-AP-20191120]

schema:endDate

Optional property

(Period Of Time)

Deprecated

Range: rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the end of the period.

DCAT-AP-83

[DCAT-AP-20191120]

schema:startDate

Optional property

(Period Of Time)

Deprecated

Range: rdfs:Literal typed as xsd:date or xsd:dateTime

This property contains the start of the period.

DCAT-AP-83

[DCAT-AP-20191120]

dcat:Role

Optional class

New

A role is the function of a resource or agent with respect to another resource, in the context of resource attribution or resource relationships.

DCAT-AP-82

[DCAT-AP-20191120]

dct:relation

Mandatory property

(Relationship)

New

Range: rdfs:Resource

This property refers to the resource related to the source resource.

DCAT-AP-81

[DCAT-AP-20191120]

dcat:hadRole

Mandatory property

(Relationship)

New

Range: dcat:Role

This property refers to the function of an entity or agent with respect to another entity or resource.

DCAT-AP-81

[DCAT-AP-20191120]

dcat:Relationship

Optional class

New

An association class for attaching additional information to a relationship between DCAT Resources.

DCAT-AP-81

[DCAT-AP-20191120]

odrl:hasPolicy

Optional property

(Distribution)

New

Range: odrl:Policy

This property refers to the policy expressing the rights associated with the distribution if using the [VOCAB-ODRL] vocabulary.

DCAT-AP-77

[DCAT-AP-20191120]

dcat:accessService

Optional property

(Distribution)

New

Range: dcat:DataService

This property refers to a Data Service that gives access to the Distribution of the Dataset.

DCAT-AP-77

[DCAT-AP-20191120]

dcat:spatialResolutionInMeters

Optional property

(Distribution)

New

Range: xsd:decimal

This property refers to the minimum spatial separation resolvable in a Distribution, measured in metres.

DCAT-AP-78

[DCAT-AP-20191120]

dcat:temporalResolution

Optional property

(Distribution)

New

Range: xsd:duration

This property refers to the minimum time period resolvable in the Distribution.

DCAT-AP-78

[DCAT-AP-20191120]

dcat:compressFormat

(Optional property

(Distribution)

New

Range: dct:MediaType

This property refers to the format of the file in which the data is contained in a compressed form, e.g. to reduce the size of the downloadable file.

DCAT-AP-79

DCAT-AP-95

[DCAT-AP-20191120]

dcat:packageFormat

Optional property

(Distribution)

New

Range: dct:MediaType

This property refers to the format of the file in which one or more data files are grouped together, e.g. to enable a set of related files to be downloaded together.

DCAT-AP-79

DCAT-AP-95

[DCAT-AP-20191120]

dct:isReferencedBy

Optional property

(Dataset)

New

Range: rdfs:Resource

This property is about a related resource, such as a publication, that references, cites, or otherwise points to the Dataset.

DCAT-AP-75

[DCAT-AP-20191120]

dcat:qualifiedRelation

Optional property

(Dataset)

New

Range dcat:Relationship

This property provides a link to a description of a relationship with another resource.

DCAT-AP-75

[DCAT-AP-20191120]

dct:creator

Optional property

(Dataset)

New

Range:foaf:Agent

This property refers to the Agent primarily responsible for producing the Dataset.

DCAT-AP-75

[DCAT-AP-20191120]

prov:wasGeneratedBy

Optional property

(Dataset)

New

Range: prov:Activity

This property refers to an Activity that generated, or provides the business context for, the creation of the Dataset.

DCAT-AP-75

[DCAT-AP-20191120]

dcat:spatialResolutionInMeters

Optional property

(Dataset)

New

Range: xsd:decimal

This property refers to the minimum spatial separation resolvable in a Dataset, measured in metres.

DCAT-AP-76

[DCAT-AP-20191120]

dcat:temporalResolution

Optional property

(Dataset)

New

Range: xsd:duration

This property refers to the minimum time period resolvable in the Dataset.

DCAT-AP-76

[DCAT-AP-20191120]

dcat:service

Optional property

(Catalogue)

New

Range: dcat:DataService

This property refers to a Data Service that is listed in the Catalogue.

DCAT-AP-72

[DCAT-AP-20191120]

dcat:catalog

Optional property

(Catalogue)

New

Range: dcat:Catalog

This property refers to a Catalogue whose contents are of interest in the context of this Catalogue.

DCAT-AP-72

[DCAT-AP-20191120]

dcat:servesDataset

Recommended property

(Data Service)

New

Range: dcat:Dataset

This property refers to a Dataset that this Data Service can distribute.

DCAT-AP-73

[DCAT-AP-20191120]

dcat:endpointDescription

Recommended property

(Data Service)

New

Range:

This property contains a description of the Data Services available via the endpoints, including their operations, parameters etc. The property gives specific details of the actual endpoint instances, while dct:conformsTo is used to indicate the general standard or specification that the endpoints implement.

DCAT-AP-73

[DCAT-AP-20191120]

dcat:endpointURL

Mandatory property

(Data Service)

New

Range: rdfs:Resource

The root location or primary endpoint of the Data Service (an IRI).

DCAT-AP-73

[DCAT-AP-20191120]

dcat:DataService

Optional class

New

Range:

A collection of operations that provides access to one or more Datasets or data processing functions.

DCAT-AP-73

[DCAT-AP-20191120]

dcatap:availability

Recommended property (Distribution)

New

Range skos:Concept

This property indicates how long it is planned to keep the Distribution of the Dataset available. It MUST take one of the values: temporary, experimental, available, stable.

DCAT-AP-40

[DCAT-AP-20191120]

adms:status

Controlled vocabulary

(Catalog Record)

Removed

Removed:

The ADMS change type vocabulary http://purl.org/adms/changetype/

(:created, :updated, :deleted |) does not exists and has been removed from the specification.

DCAT-AP-45

[DCAT-AP-20191120]

dct:spatial

Recommended property

(Catalog)

Updated

Updates

Optional property → Recommended property

DCAT-AP-3

[DCAT-AP-20191120]

dct:spatial

Recommended property

(Dataset)

Updated

Updates

Optional property → Recommended property

DCAT-AP-9

[DCAT-AP-20191120]

dct:temporal

Recommended property

(Dataset)

Updated

Updates

Optional property → Recommended property

DCAT-AP-64

[DCAT-AP-20191120]

dct:type

Recommended property

(Licence Document)

Updated

Updates

Cardinality: 0..1 → 0..n

This property can be repeated in the case that multiple licence types apply to a Licence Document.

DCAT-AP-1

[DCAT-AP-20181108]

adms:versionNotes

Optional property (Dataset)

Updated

Updates

Cardinality: 0..1 → 0..n

This property can be repeated for parallel language versions of the version notes.

CO4

[DCAT-AP-20170224]

dct:LicenseDocument

Recommended

class

Updated

Updates

Optional class → recommended class

OB4

[DCAT-AP-20170224]

dct:source

Optional property (CatalogRecord)

New

Range: dcat:CatalogRecord

This property links to the original metadata that was used in creating metadata for the Dataset.

MO5

[DCAT-AP-20170224]

owl:versionInfo

Optionalproperty (Dataset)

Updated

Updates

URI: adms:versionowl:versionInfo

CO4

[DCAT-AP-20170224]

spdx:algorithm

Mandatory property (Checksum)

New

Range: spdx:checksumAlgorithm_sha1

Cardinality: 1..1

This property identifies the algorithm used to produce the subject Checksum. Currently, SHA-1 is the only supported algorithm. It is anticipated that other algorithms will be supported at a later time.

PR1

[DCAT-AP-20170224]

spdx:Checksum

Optional class

New

A value that allows the contents of a file to be authenticated. This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented.

PR1

[DCAT-AP-20170224]

spdx:checksum

Optional property (Dataset)

New

Range: spdx:Checksum

Cardinality: 0..1

This property provides a mechanism that can be used to verify that the contents of a Distribution have not changed.

PR1

[DCAT-AP-20170224]

spdx:checksumValue

Mandatory property (Checksum)

New

Range: rdfs:Literal typed as xsd:hexBinary

Cardinality: 1..1

This property provides a lower case hexadecimal encoded digest value produced using a specific algorithm.

PR1

[DCAT-AP-20170224]

vcard:Kind

Optional class

Updated

Updates

Class name: VCard → Kind

URI: VCard → vcard:Kind

The class Kind is the parent class for the four explicit types of vCards (Individual, Organization, Location, Group).

MO4

[DCAT-AP-20170224]

dct:source

Optional property (Dataset)

New

Range: dcat:Dataset

This property refers to a related Dataset from which the described Dataset is derived.

PR6

PR13

PR14

MO5

[DCAT-AP-20170224]

dct:accessRights

Optional property (Dataset)

New

Range: dct:RightsStatement

This property refers to information that indicates whether the Dataset is open data, has access restrictions or is not public.

PR2

PR3

[DCAT-AP-20170224]

dct:hasVersion

Optional property (Dataset)

New

Range: dcat:Dataset

This property refers to a related Dataset that is a version, edition, or adaptation of the described Dataset.

PR5

PR16

MO12

[DCAT-AP-20170224]

dct:isVersionOf

Optional property (Dataset)

New

Range: dcat:Dataset

This property refers to a related Dataset of which the described Dataset is a version, edition, or adaptation.

PR5

PR16

MO12

[DCAT-AP-20170224]

dct:relation

Optional property (Dataset)

New

Range: rdfs:Resource

This property refers to a related resource.

PR19

MO12

[DCAT-AP-20170224]

foaf:page

Optional property (Dataset)

New

Range: foaf:Document

This property refers to a page or document about this Dataset.

PR19

PR26

[DCAT-AP-20170224]

dcat:mediaType

Controlled vocabulary

Updated

Modifications:

MDR list → IANA types

PR22

VO3

[DCAT-AP-20170224]

dct:spatial

Controlled vocabulary

Updated

Modifications:

Added recommendation to use sws.geonames.org if the needed place is not listed in the MDR.

VO9

[DCAT-AP-20170224]

dct:isPartOf

Optional property (Catalogue)

New

Range: dcat:Catalog

This property refers to a related Catalogue in which the described Catalogue is physically or logically included.

Nesting

[DCAT-AP-20170224]

adms:sample

Optional property (Dataset)

New

This property is related to sample(s) of the dataset

PR21

[DCAT-AP-20170224]

foaf:page

Optional property (Distribution)

New

A page or document about this Distribution

M02

[DCAT-AP-20170224]

dct:hasPart

Optional property (Catalogue)

New

Range: dcat:Catalog

This property refers to a related Catalogue that is part of the described Catalogue.

Nesting

[DCAT-AP-20170224]

dcat:themeTaxonomy

Controlled vocabulary

Updated

Modification

Changed the recommendation to use new EU Data Theme vocabulary proposed by the Publications Office instead [EUV-THEMES] of EuroVoc [EUV-EUROVOC]. Added clarification that value is the URI of the concept scheme, not of the concepts.

VO2

[DCAT-AP-20170224]

dcat:theme

Controlled vocabulary

Updated

Modifications:

Changed the recommendation to use terms from the new EU Data Theme vocabulary proposed by the Publications Office [EUV-THEMES] instead of EuroVoc domains [EUV-EUROVOC].

URI: dct:themedcat:theme

VO2

[DCAT-AP-20170224]

dct:accrualPeriodicity

Controlled vocabulary

Updated

Modification

Changed the recommendation to use terms from the Frequency Name Authority List maintained by the Publications Office [EUV-FREQ] instead of the Dublin Core Collection Description Frequency Vocabulary [CLD-FREQ].

[DCAT-AP-20170224]

dcat:landingPage

Optional property

(Dataset)

Updated

Updates

Cardinality: 0..1 → 0..n

Issue link

[DCAT-AP-20170224]

D. References

D.1 Normative references

[ADMS]
Joinup. Asset Description Metadata Schema (ADMS). European Commission. URL: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms
[ADMS-SKOS]
Joinup. ADMS Controlled Vocabularies. European Commission. URL: https://joinup.ec.europa.eu/svn/adms/ADMS_v1.00/ADMS_SKOS_v1.00.html
[BCP47]
Tags for Identifying Languages. A. Phillips; M. Davis. IETF. September 2009. IETF Best Current Practice. URL: https://tools.ietf.org/html/bcp47
[CLD-FREQ]
Dublin Core Collection Description Frequency Vocabulary. Dublin Core Collection Description Task Group. Dublin Core Metadata Initiative. 9 March 2007. URL: http://dublincore.org/groups/collections/frequency/
[Content-in-RDF10]
Representing Content in RDF 1.0. Johannes Koch; Carlos A. Velasco; Philip Ackermann. W3C. 2 February 2017. W3C Note. URL: https://www.w3.org/TR/Content-in-RDF10/
[DC11]
Dublin Core Metadata Element Set, Version 1.1. DCMI. 14 June 2012. DCMI Recommendation. URL: http://dublincore.org/documents/dces/
[DCAT-AP]
DCAT Application Profile for data portals in Europe. Version 2.0.1. European Commission. 8 June 2020. URL: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe
[DCAT-AP-20170224]
DCAT Application Profile for data portals in Europe. Version 1.1. European Commission. 23 October 2015. URL: https://joinup.ec.europa.eu/release/dcat-ap/11
[DCAT-AP-20181108]
DCAT Application Profile for data portals in Europe. Version 1.2. European Commission. 8 November 2018. URL: https://joinup.ec.europa.eu/release/dcat-ap/12
[DCAT-AP-20191120]
DCAT Application Profile for data portals in Europe. Version 2.0.0. European Commission. 20 November 2019. URL: http://data.europa.eu/w21/f8faf044-ea69-4e98-a372-88058631ceee
[DCAT-AP-20200608]
DCAT Application Profile for data portals in Europe. Version 2.0.1. European Commission. 8 June 2020. URL: http://data.europa.eu/w21/32d70b6e-0d27-40d9-9230-017e4cd00bcc
[DCAT-AP-DA]
DCAT-AP Distribution Availability Vocabulary. European Commission. URL: http://data.europa.eu/r5r/availability/
[DCTERMS]
DCMI Metadata Terms. DCMI Usage Board. DCMI. 20 January 2020. DCMI Recommendation. URL: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/
[EUV-CB]
Named Authority List: Corporate bodies. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/corporate-body
[EUV-CONT]
Named Authority List: Continents. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/continent
[EUV-COUNTRIES]
Named Authority List: Countries. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/country
[EUV-EUROVOC]
EuroVoc. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/th-dataset/-/resource/dataset/eurovoc
[EUV-FREQ]
Named Authority List: Frequencies. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/frequency
[EUV-FT]
Named Authority List: File types. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/file-type
[EUV-LANG]
Named Authority List: Languages. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/language
[EUV-PLACES]
Named Authority List: Places. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/place
[EUV-THEMES]
Named Authority List: Data Themes. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/data-theme
[FOAF]
FOAF Vocabulary Specification 0.99 (Paddington Edition). Dan Brickley; Libby Miller. FOAF project. 14 January 2014. URL: http://xmlns.com/foaf/spec
[GeoDCAT-AP]
GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe. Version 1.0.1. European Commission. 2 August 2016. URL: https://joinup.ec.europa.eu/solution/geodcat-application-profile-data-portals-europe
[GeoDCAT-AP-20151223]
GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe. Version 1.0. European Commission. 23 December 2015. URL: https://joinup.ec.europa.eu/release/geodcat-ap/10
[GeoDCAT-AP-20160802]
GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe. Version 1.0.1. European Commission. 2 August 2016. URL: https://joinup.ec.europa.eu/release/geodcat-ap/101
[GeoDCAT-XSLT]
Reference XSLT-based implementation of GeoDCAT-AP. European Commission. URL: https://github.com/semiceu/iso-19139-to-dcat-ap/
[GEONAMES]
Geonames. URL: http://geonames.org/
[GeoSPARQL]
GeoSPARQL - A Geographic Query Language for RDF Data. Matthew Perry; John Herring. OGC. 10 September 2012. URL: http://www.opengeospatial.org/standards/geosparql
[IANA-CHARSETS]
Character sets. IANA. URL: https://www.iana.org/assignments/character-sets
[IANA-MEDIA-TYPES]
Media Types. IANA. URL: https://www.iana.org/assignments/media-types/
[INSPIRE-DoC]
INSPIRE Registry: Degrees of conformity. European Commission. URL: http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity
[INSPIRE-GLOSSARY]
INSPIRE Glossary. European Commission. URL: http://inspire.ec.europa.eu/glossary
[INSPIRE-LPA]
INSPIRE Registry: Limitations on public access. European Commission. URL: http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess
[INSPIRE-MD]
Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007. Version 2.0.1. European Commission. 2 March 2017. URL: https://inspire.ec.europa.eu/id/document/tg/metadata-iso19139
[INSPIRE-MD-20170302]
Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007. Version 2.0.1. European Commission. 2 March 2017. URL: https://inspire.ec.europa.eu/id/document/tg/metadata-iso19139/2.0.1
[INSPIRE-MD-REG]
Commission Regulation (EC) No 1205/2008 of 3 December 2008 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards metadata. OJ L 326. 4 December 2008. URL: http://data.europa.eu/eli/reg/2008/1205
[INSPIRE-PV]
INSPIRE Registry: Protocol values. European Commission. URL: https://inspire.ec.europa.eu/metadata-codelist/ProtocolValue
[INSPIRE-RPR]
INSPIRE Registry: Responsible party roles. European Commission. URL: http://inspire.ec.europa.eu/metadata-codelist/ResponsiblePartyRole
[INSPIRE-RT]
INSPIRE Registry: Resource types. European Commission. URL: http://inspire.ec.europa.eu/metadata-codelist/ResourceType
[INSPIRE-SDSC]
INSPIRE Registry: Classification of spatial data services. European Commission. URL: http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory
[INSPIRE-SDST]
INSPIRE Registry: Spatial data service types. European Commission. URL: http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType
[INSPIRE-TC]
INSPIRE Registry: Topic categories in accordance with EN ISO 19115. European Commission. URL: http://inspire.ec.europa.eu/metadata-codelist/TopicCategory
[INSPIRE-THEMES]
INSPIRE Registry: INSPIRE themes. European Commission. URL: http://inspire.ec.europa.eu/theme
[ISO-19115]
Geographic information -- Metadata. ISO/TC 211. ISO. 2003. International Standard. URL: https://www.iso.org/standard/26020.html
[ISO-19115-1]
Geographic information -- Metadata -- Part 1: Fundamentals. ISO/TC 211. ISO. 2014. International Standard. URL: https://www.iso.org/standard/53798.html
[JSON-LD11]
JSON-LD 1.1. Gregg Kellogg; Pierre-Antoine Champin; Dave Longley. W3C. 16 July 2020. W3C Recommendation. URL: https://www.w3.org/TR/json-ld11/
[LOCN]
ISA Programme Location Core Vocabulary. Andrea Perego; Michael Lutz. European Commission. 23 March 2015. Second version in w3.org/ns space. URL: http://www.w3.org/ns/locn
[OGC-EPSG]
EPSG CRS Register. OGC. URL: http://www.opengis.net/def/crs/EPSG/
[OWL-REF]
OWL Web Ontology Language Reference. Mike Dean; Guus Schreiber. W3C. 10 February 2004. W3C Recommendation. URL: https://www.w3.org/TR/owl-ref/
[OWL-TIME]
Time Ontology in OWL. Simon Cox; Chris Little. W3C. 26 March 2020. W3C Candidate Recommendation. URL: https://www.w3.org/TR/owl-time/
[PROV-O]
PROV-O: The PROV Ontology. Timothy Lebo; Satya Sahoo; Deborah McGuinness. W3C. 30 April 2013. W3C Recommendation. URL: https://www.w3.org/TR/prov-o/
[QUDT-UNITS]
QUDT Units Vocabulary. QUDT.org. URL: http://www.qudt.org/vocab/unit
[RDF-SCHEMA]
RDF Schema 1.1. Dan Brickley; Ramanathan Guha. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/rdf-schema/
[RDF-SYNTAX-GRAMMAR]
RDF 1.1 XML Syntax. Fabien Gandon; Guus Schreiber. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/rdf-syntax-grammar/
[RDF11-CONCEPTS]
RDF 1.1 Concepts and Abstract Syntax. Richard Cyganiak; David Wood; Markus Lanthaler. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/rdf11-concepts/
[RFC2119]
Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119
[RFC3966]
The tel URI for Telephone Numbers. H. Schulzrinne. IETF. December 2004. Proposed Standard. URL: https://tools.ietf.org/html/rfc3966
[RFC6068]
The 'mailto' URI Scheme. M. Duerst; L. Masinter; J. Zawinski. IETF. October 2010. Proposed Standard. URL: https://tools.ietf.org/html/rfc6068
[RFC8174]
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words. B. Leiba. IETF. May 2017. Best Current Practice. URL: https://tools.ietf.org/html/rfc8174
[SKOS-REFERENCE]
SKOS Simple Knowledge Organization System Reference. Alistair Miles; Sean Bechhofer. W3C. 18 August 2009. W3C Recommendation. URL: https://www.w3.org/TR/skos-reference/
[SPDX]
SPDX 2.2. SPDX. URL: http://spdx.org/rdf/terms#
[Turtle]
RDF 1.1 Turtle. Eric Prud'hommeaux; Gavin Carothers. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/turtle/
[VCARD-RDF]
vCard Ontology - for describing People and Organizations. Renato Iannella; James McKinney. W3C. 22 May 2014. W3C Note. URL: https://www.w3.org/TR/vcard-rdf/
[VOCAB-ADMS]
Asset Description Metadata Schema (ADMS). Phil Archer; Gofran Shukair. W3C. 1 August 2013. W3C Note. URL: https://www.w3.org/TR/vocab-adms/
[VOCAB-DATA-CUBE]
The RDF Data Cube Vocabulary. Richard Cyganiak; Dave Reynolds. W3C. 16 January 2014. W3C Recommendation. URL: https://www.w3.org/TR/vocab-data-cube/
[VOCAB-DCAT-2]
Data Catalog Vocabulary (DCAT) - Version 2. Riccardo Albertoni; David Browning; Simon Cox; Alejandra Gonzalez Beltran; Andrea Perego; Peter Winstanley. W3C. 4 February 2020. W3C Recommendation. URL: https://www.w3.org/TR/vocab-dcat-2/
[VOCAB-DQV]
Data on the Web Best Practices: Data Quality Vocabulary. Riccardo Albertoni; Antoine Isaac. W3C. 15 December 2016. W3C Note. URL: https://www.w3.org/TR/vocab-dqv/
[VOCAB-ODRL]
ODRL Vocabulary & Expression 2.2. Renato Iannella; Michael Steidl; Stuart Myles; Víctor Rodríguez-Doncel. W3C. 15 February 2018. W3C Recommendation. URL: https://www.w3.org/TR/odrl-vocab/
[VOCAB-ORG]
The Organization Ontology. Dave Reynolds. W3C. 16 January 2014. W3C Recommendation. URL: https://www.w3.org/TR/vocab-org/
[XML]
Extensible Markup Language (XML) 1.0 (Fifth Edition). Tim Bray; Jean Paoli; Michael Sperberg-McQueen; Eve Maler; François Yergeau et al. W3C. 26 November 2008. W3C Recommendation. URL: https://www.w3.org/TR/xml/
[XMLSCHEMA11-2]
W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes. David Peterson; Sandy Gao; Ashok Malhotra; Michael Sperberg-McQueen; Henry Thompson; Paul V. Biron et al. W3C. 5 April 2012. W3C Recommendation. URL: https://www.w3.org/TR/xmlschema11-2/

D.2 Informative references

[CC]
About The Licenses. Creative Commons. URL: http://creativecommons.org/licenses/
[CC-BY]
CC-BY 4.0 Attribution 4.0 International. Creative Commons. URL: https://creativecommons.org/licenses/by/4.0/
[CC0]
CC0 1.0 Universal (CC0 1.0) Public Domain Dedication. Creative Commons. URL: http://creativecommons.org/publicdomain/zero/1.0/
[CERIF-VOCS]
CERIF standard vocabularies. URL: http://www.eurocris.org/Uploads/Web%20pages/CERIF-1.5/CERIF1.5_Semantics.xhtml
[CLDR]
CLDR - Unicode Common Locale Data Repository. BCP47, transform_mt.xml. UNICODE Consortium. URL: http://unicode.org/cldr/trac/browser/trunk/common/bcp47/transform_mt.xml
[CONNEG]
Apache Web Server: content negotiation. Apache Foundation. URL: http://httpd.apache.org/docs/current/content-negotiation.html
[CSW]
Catalogue Services 3.0 - General Model. Douglas Nebert; Uwe Voges; Lorenzo Bigagli. OGC. 10 June 2016. URL: http://www.opengeospatial.org/standards/cat
[DataCite]
DataCite Metadata Schema. DataCite Metadata Working Group. DataCite e.V. 16 August 2019. URL: https://schema.datacite.org/
[DataCite-RIS]
DataCite Resource Identifier Scheme. URL: http://purl.org/spar/datacite/ResourceIdentifierScheme
[DataStrategy]
COMMUNICATION FROM THE COMMISSION TO THE EUROPEAN PARLIAMENT, THE COUNCIL, THE EUROPEAN ECONOMIC AND SOCIAL COMMITTEE AND THE COMMITTEE OF THE REGIONS A European strategy for data. COM/2020/66 final. 19 February 2020. URL: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52020DC0066
[DC-UG-PM]
Dublin Core™ User Guide: Publishing Metadata. Stefanie Rühle; Tom Baker; Pete Johnston. Dublin Core Metadata Initiative. URL: https://www.dublincore.org/resources/userguide/publishing_metadata/
[DCAT-AP-CRMP]
Joinup. Change and Release Management Policy for DCAT-AP. European Commission. URL: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/document/change-and-release-management-policy-dcat-ap
[DCAT-AP-EG]
Joinup. DCAT-AP Implementation Guidelines: How to extend DCAT-AP?. European Commission. URL: https://joinup.ec.europa.eu/release/dcat-ap-how-extend-dcat-ap
[DDC]
Dewey Summaries as Linked Data. OCLC. URL: http://www.oclc.org/dewey/webservices.en.html
[DOI]
Digital Object Identifier. DOI. URL: http://www.doi.org/
[DWBP]
Data on the Web Best Practices. Bernadette Farias Loscio; Caroline Burle; Newton Calegari. W3C. 31 January 2017. W3C Recommendation. URL: https://www.w3.org/TR/dwbp/
[DXWG]
Dataset Exchange Working Group (DXWG). W3C. URL: https://www.w3.org/2017/dxwg/
[EARL10]
Evaluation and Report Language (EARL) 1.0 Schema. Shadi Abou-Zahra. W3C. 2 February 2017. W3C Note. URL: https://www.w3.org/TR/EARL10-Schema/
[EPSG-RDF]
Proof of concept for the RDF representation of the OGC EPSG register of coordinate reference systems. European Commission. URL: https://github.com/semiceu/epsg-to-rdf/
[EUV-AR]
Named Authority List: Access rights. Publications Office of the European Union. URL: https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/access-right
[EZID]
EZID. URL: http://n2t.net/ezid
[GeoDCAT-ACV]
Joinup. GeoDCAT-AP: Alignment of controlled vocabularies. European Commission. URL: https://joinup.ec.europa.eu/node/148245/
[GEOHASH]
Geohash. Wikipedia. URL: http://en.wikipedia.org/wiki/Geohash
[GEOHASH-36]
Geohash-36. Wikipedia. URL: http://en.wikipedia.org/wiki/Geohash-36
[GeoSPARQL11]
OGC GeoSPARQL 1.1. OGC. 16 December 2020. Draft. URL: https://github.com/opengeospatial/ogc-geosparql/1.1
[GETTY]
Introduction to Controlled Vocabularies: Terminology for Art, Architecture, and Other Cultural Works. Patricia Harpring. The Getty Research Institute. 2010. URL: https://www.getty.edu/research/publications/electronic_publications/intro_controlled_vocab/
[GLD]
Government Linked Data (GLD) Working Group. W3C. URL: https://www.w3.org/2011/gld/
[GML]
Geography Markup Language (GML) Encoding Standard. Open Geospatial Consortium Inc. URL: http://www.opengeospatial.org/standards/gml
[INSPIRE-CAU]
INSPIRE Registry: Conditions applying to access and use. European Commission. URL: http://inspire.ec.europa.eu/metadata-codelist/ConditionsApplyingToAccessAndUse
[INSPIRE-DC]
State of progress in the development of guidelines to express elements of the INSPIRE metadata implementing rules using ISO 15836 (Dublin core). European Commission. 6 May 2008. URL: https://inspire.ec.europa.eu/reports/ImplementingRules/metadata/MD_IR_and_DC_state%20of%20progress.pdf
[INSPIRE-DIR]
DIRECTIVE 2007/2/EC OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 14 March 2007 establishing an Infrastructure for Spatial Information in the European Community (INSPIRE). OJ L 108. 25 April 2007. URL: http://data.europa.eu/eli/dir/2007/2/oj
[INSPIRE-SDSS-REG]
Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services. OJ L 323. 8 December 2010. URL: http://data.europa.eu/eli/reg/2010/1089
[ISA2]
Interoperability solutions for public administrations, businesses and citizens (ISA²). European Commission. URL: https://ec.europa.eu/isa2/
[ISO-19119]
Geographic information -- Services. ISO/TC 211. ISO. 2016. International Standard. URL: https://www.iso.org/standard/59221.html
[ISO-19125-1]
Geographic information -- Simple feature access -- Part 1: Common architecture. ISO/TC 211. ISO. 2004. International Standard. URL: https://www.iso.org/standard/40114.html
[ISO-19139]
Geographic information -- Metadata -- XML schema implementation. ISO/TC 211. ISO. 2007. Technical Specification. URL: https://www.iso.org/standard/32557.html
[ISO-639]
Code for the representation of names of languages. ISO/TC 37/SC 2. ISO. 1988. International Standard. URL: https://www.iso.org/standard/4766.html
[ISO-639-2]
Codes for the representation of names of languages -- Part 2: Alpha-3 code. ISO/TC 37/SC 2. ISO. 1998. International Standard. URL: https://www.iso.org/standard/4767.html
[KML]
OGC KML 2.3. David Burggraf. OGC. 4 August 2015. URL: http://www.opengeospatial.org/standards/kml
[LOCN-MAPPING]
LOCN mappings to vCard and Schema.org. Andrea Perego. European Commission, Joint Research Centre (JRC). 2019. Working Draft. URL: https://semiceu.github.io/locn-mapping/
[MAST-ADS]
Referencing Data Sets in Astronomical Literature. Mikulski Archive for Space Telescopes (MAST). URL: http://archive.stsci.edu/pub_dsn.html
[ODI]
ODI. URL: http://www.theodi.org/
[ODRS]
Open Data Rights Statement Vocabulary. Leigh Dodds. ODI. 29 July 2013. URL: http://schema.theodi.org/odrs
[OPENDATA-DIR]
Directive (EU) 2019/1024 of the European Parliament and of the Council of 20 June 2019 on open data and the re-use of public sector information. OJ L 172. 20 June 2019. URL: http://data.europa.eu/eli/dir/2019/1024/oj
[PDDL]
Public Domain Dedication and License (PDDL). Open Data Commons. URL: http://opendatacommons.org/licenses/pddl/
[RFC4288]
Media Type Specifications and Registration Procedures. N. Freed; J. Klensin. IETF. December 2005. Best Current Practice. URL: https://tools.ietf.org/html/rfc4288
[RFC5870]
A Uniform Resource Identifier for Geographic Locations ('geo' URI). A. Mayrhofer; C. Spanring. IETF. June 2010. Proposed Standard. URL: https://tools.ietf.org/html/rfc5870
[RFC6497]
BCP 47 Extension T - Transformed Content. M. Davis; A. Phillips; Y. Umaoka; C. Falk. IETF. February 2012. Informational. URL: https://tools.ietf.org/html/rfc6497
[RFC7946]
The GeoJSON Format. H. Butler; M. Daly; A. Doyle; S. Gillies; S. Hagen; T. Schaub. IETF. August 2016. Proposed Standard. URL: https://tools.ietf.org/html/rfc7946
[SCHEMA-ORG]
Schema.org. URL: http://schema.org/
[SDW-BP]
Spatial Data on the Web Best Practices. Jeremy Tandy; Linda van den Brink; Payam Barnaghi. W3C. 28 September 2017. W3C Note. URL: https://www.w3.org/TR/sdw-bp/
[SEMIC]
Interoperability solutions for public administrations, businesses and citizens (ISA²). Improving semantic interoperability in European eGovernment systems. European Commission. URL: https://ec.europa.eu/isa2/actions/improving-semantic-interoperability-european-egovernment-systems_en
[SPARQL11-QUERY]
SPARQL 1.1 Query Language. Steven Harris; Andy Seaborne. W3C. 21 March 2013. W3C Recommendation. URL: https://www.w3.org/TR/sparql11-query/
[UKOGL]
Open Government Licence for public sector information. The National Archives. URL: http://www.nationalarchives.gov.uk/doc/open-government-licence/version/2/
[Vickery]
Review of recent studies on PSI reuse and related market developments. Graham Vickery. URL: http://ec.europa.eu/information_society/policy/psi/docs/pdfs/report/final_version_study_psi.docx
[VOCAB-DCAT-20140116]
Data Catalog Vocabulary (DCAT). Fadi Maali; John Erickson. W3C. 16 January 2014. W3C Recommendation. URL: https://www.w3.org/TR/2014/REC-vocab-dcat-20140116/
[W3C-BASIC-GEO]
Basic Geo (WGS84 lat/long) Vocabulary. Dan Brickley. W3C Semantic Web Interest Group. 1 February 2006. URL: https://www.w3.org/2003/01/geo/
[W3ID]
Permanent Identifiers for the Web. W3C Permanent Identifier Community Group. URL: https://w3id.org/