Carview!

CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 server: GitHub.com content-type: text/html; charset=utf-8 last-modified: Mon, 06 Oct 2025 14:50:50 GMT access-control-allow-origin: * etag: W/"68e3d74a-15e260" expires: Thu, 09 Oct 2025 16:00:58 GMT cache-control: max-age=600 content-encoding: gzip x-proxy-cache: MISS x-github-request-id: 272B:2B2B65:C9D2E:ED250:68E7D9E1 accept-ranges: bytes age: 0 date: Thu, 09 Oct 2025 15:50:58 GMT via: 1.1 varnish x-served-by: cache-bom-vanm7210095-BOM x-cache: MISS x-cache-hits: 0 x-timer: S1760025058.926840,VS0,VE330 vary: Accept-Encoding x-fastly-request-id: 770e9997793c18f0e646d701f85b68b42b8518e0 content-length: 145891 GeoDCAT-AP 3.0.0

Abstract

GeoDCAT-AP is an extension of the DCAT application profile for data portals in Europe ([[[DCAT-AP-3]]]) 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]], those defined in the framework of the INSPIRE Directive [[INSPIRE-DIR]] of the European Union and those defined in the Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007 [[INSPIRE-MD]].

Introduction

This document contains version 3.0.0 of the specification for GeoDCAT-AP, an extension of the DCAT application profile for data portals in Europe [[DCAT-AP-3]] 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]], its XML metadata encoding standard, ISO/TS 19139:2007 [[ISO-19139]], 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 producers and maintainers of geospatial metadata the possibility to achieve more by providing the means of an additional implementation through harmonised RDF syntax bindings used in the Open Data community. 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-3]]-conformant data portals. A conversion to an RDF representation allows additional metadata elements to be displayed on general-purposed open 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.

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 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 describing 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 2.0.0 [[GeoDCAT-AP-20201223]], with the purpose of aligning it with DCAT-AP version 3.x.x [[DCAT-AP-3]] and with version 2.2.0 of the INSPIRE Metadata Technical Guidelines for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007 [[INSPIRE-MD]].

This work has been carried out in the context of the European Commission’s Interoperable Europe initiative [[INTEROPERABLE-EUROPE]].

Scope of the Application Profile

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-3]] and [[INSPIRE-MD]].

As [[[DCAT-AP-3]]], the Application Profile specified in this document is based on the specification of the Data Catalog Vocabulary (DCAT). DCAT is originally developed under the responsibility of the Government Linked Data Working Group [[GLD]] at W3C, and was 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.

The objective of this work is to produce an extension of [[DCAT-AP-3]] based on numerous requests for change coming from real-world implementations of the specification listed on the GitHub issues section since the previous release [[GeoDCAT-AP-20201223]]. For that purpose the [[DCAT-AP-3]] specification is extended with improved definitions, usage notes and usage constraints such as cardinalities for properties and the usage of controlled vocabularies. Additional classes and properties are re-used or introduced 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 section [[[#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.

As mentioned in the context, the prime objective of the Application Profile is to enhance data findability and promote reusability. To achieve this goal, datasets should be coherently documented. To enable this, the Application Profile considers several essential aspects, including among others:

Understanding the data or service structure, and how to get access to the data
Information on scope or purpose of the data
Legal information
Knowledge on data publishers, and any other agents involved
Knowledge of data availability and change policies

These are addressed with the aim to facilitate effective data reuse, allowing users to locate, understand and utilise the available data resources more efficiently.

DCAT-AP Context

Around 2010, on behalf of the European Commission the access to public sector information was studied. These studies showed that businesses and citizens faced many difficulties in finding and reusing public sector information. The studies indicated that the availability of the information in a machine-readable format as well as a thin layer of commonly agreed metadata could facilitate data cross-reference and interoperability and therefore considerably enhance its value for reuse. Therefore, to overcome these hurdles, the European Commission invested in policies [[PSI]], data interoperability [[SEMIC]] and infrastructure [[DEU]].

Interoperable Europe, within its mission to stimulate the data interoperability in Europe, manages this specification on the metadata agreements for sharing dataset descriptions between data portals. The governance is taken care by the SEMIC action within Interoperable Europe. Initially, the scope of the specification was the exchange between Open Data Portals in Europe. Although this is still at the core of the specification, DCAT-AP is not limited to publicly accessible Open Data, but can be applied to any kind of datasets. In the past decade, DCAT-AP has grown from a single specification to a whole ecosystem of related and interconnected specifications.

Revision history

The first GeoDCAT-AP specification was released in December 2015. The subsequent release 1.0.1 improved the specification. These specifications are aligned with the core profile of ISO 19115:2003 [[ISO-19115]] and those defined in the framework of the INSPIRE Directive [[INSPIRE-DIR]]. Five years later in December 2020 the second version of GeoDCAT-AP was released. W3C DCAT 2 restructured DCAT by introducing the notions of a generic Catalogued Resource of which Datasets and Data Services are special cases. As a consequence both DCAT-AP and GeoDCAT-AP required a major revision ensuring alignment between the different specifications. In 2023, the adoption of W3C DCAT 3 [[vocab-dcat-3]] triggered a new alignment for DCAT-AP, and consequently for GeoDCAT-AP. W3C DCAT 3 extends the profile with the Dataset Series notion. This document is the combination of this alignment and addressing issues raised by the community.

Notes on alignment with DCAT 3

Being an extension of [[DCAT-AP-3]], GeoDCAT-AP inherits the changes that were introduced in [[[DCAT-AP-3]]] due to the aligment with [[[vocab-dcat-3]]]. The introduction of Dataset Series in DCAT is an additive operation from semantical, data modeling perspective. Therefore the impact on existing GeoDCAT-AP 2.x, exchanges is limited. Nevertheless, publishers may face substantial impact on the existing catalogues as the new terminology for Dataset Series may require to revisit the publisher's metadata guidelines. For instance, if the publisher had chosen to document a Dataset Series as a Dataset with multiple Distributions, then the alignment with Dataset Series as expressed in this specification will require a substantial effort. This impact goes beyond the specification and is dependent on the usage of the shared information. In the context of GeoDCAT-AP and in line with the conformance expectations and [[DCAT-AP-3]], the term Dataset Series will be solely used for resources that are explicitly identified by the class Dataset Series. The situation, as mentioned, where a Dataset has multiple Distributions, will be considered as a Dataset with multiple Distributions and not as a Dataset Series. This way, receivers of GeoDCAT-AP metadata can rely on the classes to process the metadata.

The sole data model impact DCAT 3 creates, is by deprecating the use of some URIs and introducing new URIs in the DCAT namespace for the use case of Dataset versioning. As these properties are optional and since there is an equivalence between the deprecated and the new ones, catalogue owners can easily realign.

GeoDCAT-AP 3 is the result of an alignment with DCAT 3, DCAT-AP 3 and improvements to harmonise the interoperability between DCAT-AP and GeoDCAT-AP. These changes are listed in detail in the Changelog. To support the review, the changes are also highlighted on the diagram below.

Meeting minutes

The following webinars have been held for the creation of this release

Webinar 20 February 2024 (Meeting Minutes, recording, slides)
Webinar 12 March 2024 (Meeting Minutes, recording, slides)
Webinar 23 April 2024 (Meeting Minutes, recording, slides)
Webinar 14 May 2024 (Meeting Minutes, recording, slides)

Status

This application profile has the status Candidate Recommendation published at 2024-10-04.

Information about the process and the decisions involved in the creation of this specification are consultable at the Changelog.

License

Conformance Statement

Provider requirements

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

Provide a description of the Catalogue, including at least the mandatory properties specified for the class Catalogue.
Provide information for the mandatory properties for Catalogue Records, if descriptions of Catalogue Records are provided – please note that the provision of descriptions of Catalogue Records is optional.
Provide descriptions of Datasets in the Catalogue, including at least the mandatory properties for the class Dataset.
Provide descriptions of Distributions, if any, of Datasets in the Catalogue, including at least the mandatory properties for the class Distribution.
Provide descriptions of Data Services, if any, of Datasets in the Catalogue, including at least the mandatory properties for the class Data Service.
Provide descriptions of all organisations involved in the descriptions of Catalogue and Datasets, including at least the mandatory properties for the class Agent.
Apply the publication requirements for the controlled vocabularies as mentioned in section [[[#controlled-vocs]]].

For the properties listed in the table in section [[[#controlled-vocs]]], 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 section [[[#quick-reference]]] MAY be provided.

Receiver requirements

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

Process information for all classes and properties specified in section [[[#quick-reference]]].

Process information for all controlled vocabularies specified in section [[[#controlled-vocs]]].

"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.).

Terminology

An Application Profile is a specification that reuses terms from one or more base standards, 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.

A Dataset is a collection of data, published or curated by a single source, and available for access or download in one or more formats. A Data Portal is a Web-based system that contains a data catalogue with descriptions of datasets and provides services enabling discovery and reuse of the datasets.

Used prefixes

Prefix	Namespace IRI
`adms`	`https://www.w3.org/ns/adms#`
`dcat`	`https://www.w3.org/ns/dcat#`
`dcatap`	`https://data.europa.eu/r5r/`
`dct`	`https://purl.org/dc/terms/`
`dctype`	`https://purl.org/dc/dcmitype/`
`foaf`	`https://xmlns.com/foaf/0.1/`
`locn`	`https://www.w3.org/ns/locn#`
`odrl`	`https://www.w3.org/ns/odrl/2/`
`owl`	`https://www.w3.org/2002/07/owl#`
`prov`	`https://www.w3.org/ns/prov#`
`rdf`	`https://www.w3.org/1999/02/22-rdf-syntax-ns#`
`rdfs`	`https://www.w3.org/2000/01/rdf-schema#`
`skos`	`https://www.w3.org/2004/02/skos/core#`
`spdx`	`https://spdx.org/rdf/terms#`
`time`	`https://www.w3.org/2006/time#`
`vcard`	`https://www.w3.org/2006/vcard/ns#`
`xsd`	`https://www.w3.org/2001/XMLSchema#`
`org`	`https://www.w3.org/ns/org#`
`content`	`https://www.w3.org/2011/content#`
`dqv`	`https://www.w3.org/ns/dqv#`
`sdmx-attribute`	`https://purl.org/linked-data/sdmx/2009/attribute#`
`geodcatap`	`https://data.europa.eu/930/`

Overview

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

additional classes and properties;

additional recommendations on the use of classes and properties;

additional controlled vocabularies (documented in 9. Controlled Vocabularies to be used, along with the ones used in [[DCAT-AP-3]]).

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 A. 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-20201223]], but rather it updates some of the corresponding mappings based on the new classes and properties included in [[DCAT-AP-3]], following the release of version 2 of the W3C Data Catalog (DCAT) Vocabulary [[vocab-dcat-3]], and aligns them with version 2.2.0 of the INSPIRE Metadata Technical Guidelines [[INSPIRE-MD]].

Application profile diagram

An overview of GeoDCAT-AP is shown by the UML diagram below. The UML diagram illustrates the specification described in this document. For readability purposes, the representation has been condensed as follows:

The figure contains the key classes with some important supporting classes. Other object properties (relationships) are listed as properties on the UML class with their target range.
The class dcat:Resource has been included to ease to see the connection with W3C DCAT. GeoDCAT-AP treats it as an abstract notion.

The cardinalities and qualifications are included in the figure. This specification distinguishes between main entities, i.e. classes in the core of the application profile, supporting entities, i.e. classes used for representation of less crucial aspects of the application profile, and datatypes used for typing literal values.

UML diagram overview of the GeoDCAT-AP 3.0.0 Application profile

Main Entities

The main entities are those that form the core of the Application Profile. The properties and their associated constraints that apply in the context of this profile are listed in a tabular form. Each row corresponds to one property. In addition to the constraints also cross-references are provided to DCAT. To save space, the following abbreviations are used to indicate in short the difference with DCAT:

A: reused as-is defined and expressed in DCAT-AP, or if it has been reused as-is from DCAT in case the property was not explicitly mentioned in DCAT-AP
E: reused with additional usage notes or additional restrictions compared to DCAT-AP (or DCAT)
P: GeoDCAT-AP profile specific extension where DCAT-AP had no requirements earlier on specified

This reuse qualification assessement is w.r.t. a specific version of DCAT. Therefore it may vary over time when new versions of DCAT-AP are created.

Agent

Definition: Any entity carrying out actions with respect to the entities Catalogue and the Catalogued Resources.
Reference in DCAT-AP: Link
Usage Note: If the Agent is an organisation, the use of the Organization Ontology [[ORG]] is recommended. For the purpose of this application profile, Agent from the FOAF Vocabulary [[FOAF]] is used as a unifying class, also representing Agent from Dublin Core [[DC-TERMS]] and Agent from the W3C Provenance Ontology (PROV-O) [[PROV-O]].
Properties: For this entity the following properties are defined: address , affiliation , email , name , phone , type , URL .

Property	Range	Card	Definition	Usage	Reuse
address	Address (Core Location)	0..1	The postal address of the Agent.		P
affiliation	Organisation	0..1	The affiliation of the Agent.		P
email	Resource	0..1	The email address of the Agent, specified using fully qualified mailto: URI scheme [[RFC6068]].		P
name	Literal	1..*	A name of the agent.	This property can be repeated for different versions of the name (e.g. the name in different languages).	A
phone	Resource	0..1	The phone number of the Agent, specified using fully qualified tel: URI scheme [[RFC3966]].		P
type	Concept	0..1	The nature of the agent.		A
URL	Document	0..1	The Web site of the Agent.		P

@prefix foaf: <https://xmlns.com/foaf/0.1/> .
@prefix locn: <https://www.w3.org/ns/locn#> .
[] a foaf:Organization ;
  locn:address [ a locn:Address ;
      locn:adminUnitL1 "Denmark" ;
      locn:adminUnitL2 "K" ;
      locn:postCode "1050" ;
      locn:postName "Copenhagen" ;
      locn:thoroughfare "Kongens Nytorv 6" ] ;
  foaf:mbox <mailto:sdi@eea.europa.eu> ;
  foaf:name "European Environment Agency"@en ;
  foaf:phone <tel:+451234567890> .

Catalogue

Definition: A catalogue or repository that hosts the Datasets, Data Services or Dataset Series being described.
Reference in DCAT-AP: Link
Properties: For this entity the following properties are defined: access rights , applicable legislation , catalogue , conforms to , contact point , creation date , creator , custodian , dataset , description , distributor , geographical coverage , has part , homepage , identifier , keyword , language , licence , modification date , originator , principal investigator , processor , publisher , qualified attribution , record , reference system , release date , resource provider , rights , rights holder , service , temporal coverage , theme , themes , title , topic category , user , was used by .

Property	Range	Card	Definition	Usage	Reuse
access rights	Rights statement	0..1	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]].	E
applicable legislation	Legal Resource	0..*	The legislation that mandates the creation or management of the Catalog.		A
catalogue	Catalogue	0..*	A catalogue whose contents are of interest in the context of this catalogue.		A
conforms to	Standard	0..*	An established standard to which the described Catalogue conforms.		A
contact point	Kind	0..*	Contact information that can be used for sending comments about the Catalogue.		A
creation date	Temporal Literal	0..1	The date on which the Catalogue has been first created.		P
creator	Agent	0..1	An entity responsible for the creation of the Catalogue.		A
custodian	Agent	0..*	Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource [[ISO-19115]].		P
dataset	Dataset	0..*	A Dataset that is part of the Catalogue.		A
description	Literal	1..*	A free-text account of the Catalogue.	This property can be repeated for parallel language versions of the description.	A
distributor	Agent	0..*	Party who distributes the resource [[ISO-19115]].		P
geographical coverage	Location	0..*	A geographical area covered by the Catalogue.	This property refers to a geographic region that is covered by the Catalogue. When multiple values are used for spatial coverage, this may be interpreted as a spatial union, or as alternative representations of spatial coverage that might fit, with no explicit spatial relation.	A
has part	Catalogue	0..*	A related Catalogue that is part of the described Catalogue.		A
homepage	Document	0..1	A web page that acts as the main page for the Catalogue.		A
identifier	Literal	0..*	The main identifier for the Catalogue, e.g. the URI or other unique identifier.		A
keyword	Literal	0..*	A keyword or tag describing the Catalogue.		A
language	Linguistic system	0..*	A language used in the textual metadata describing titles, descriptions, etc. of the Datasets, Data Services and Dataset Series in the Catalogue.	This property can be repeated if the metadata is provided in multiple languages.	A
licence	Licence Document	0..1	A licence under which the Catalogue can be used or reused.		A
modification date	Temporal Literal	0..1	The most recent date on which the Catalogue was modified.		A
originator	Agent	0..*	Party who created the resource [[ISO-19115]].		P
principal investigator	Agent	0..*	Key party responsible for gathering information and conducting research [[ISO-19115]].		P
processor	Agent	0..*	Party who has processed the data in a manner such that the resource has been modified [[ISO-19115]].		P
publisher	Agent	1	An entity (organisation) responsible for making the Catalogue available.		A
qualified attribution	Attribution	0..*	A link to an Agent having some form of responsibility for the Catalogue.		A
record	Catalogue Record	0..*	A Catalogue Record that is part of the Catalogue.		A
reference system	Standard	0..*	The reference system used in accordance with OGC EPSG Coordinate Reference Systems Register [[OGC-EPSG]].		P
release date	Temporal Literal	0..1	The date of formal issuance (e.g., publication) of the Catalogue.		A
resource provider	Agent	0..*	Party that supplies the resource [[ISO-19115]].		P
rights	Rights statement	0..*	A statement that specifies rights associated with the Catalogue.		A
rights holder	Agent	0..*	An Agent (organisation) holding rights on the Catalogued Resource.		P
service	Data Service	0..*	A site or end-point (Data Service) that is listed in the Catalogue.		A
temporal coverage	Period of time	0..*	A temporal period that the Catalogue covers.		A
theme	Concept	0..*	A main category of the Catalogue. A Catalogue can have multiple categories.	A Catalogue may be associated with multiple Categories.	A
themes	Concept Scheme	0..*	A knowledge organization system used to classify the Resources that are in the Catalogue.	This property refers to a knowledge organization system used to classify the Catalogue's Datasets. It must have at least the value NAL:data-theme as this is the manatory controlled vocabulary for dcat:theme.	A
title	Literal	1..*	A name given to the Catalogue.	This property can be repeated for parallel language versions of the name.	A
topic category	Concept	0..*	Topic category in accordance with EN ISO 19115.	The URIs of the "Topic categories in accordance with EN ISO 19115" code list operated by the INSPIRE Registry [[INSPIRE-TC]].	P
user	Agent	0..*	Party who uses the resource [[ISO-19115]].		P
was used by	Activity	0..*	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.	P

Catalogue Record

Definition: A description of a Catalogued Resource's entry in the Catalogue.
Reference in DCAT-AP: Link
Properties: For this entity the following properties are defined: application profile , change type , contact point , creation date , creator , custodian , description , distributor , identifier , language , listing date , modification date , originator , primary topic , principal investigator , processor , publisher , qualified attribution , resource provider , rights holder , source metadata , title , user .

Property	Range	Card	Definition	Usage	Reuse
application profile	Standard	0..*	An Application Profile that the Catalogued Resource's metadata conforms to.		A
change type	Concept	0..1	The status of the catalogue record in the context of editorial flow of the dataset and data service descriptions.		A
contact point	Kind	0..*	Contact information that can be used for sending comments about the Catalogue Record.		A
creation date	Temporal Literal	0..1	The date on which the Catalogue Record has been first created.		P
creator	Agent	0..*	The Agent primarily responsible for producing the Catalogue Record.		P
custodian	Agent	0..*	Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource [[ISO-19115]].		P
description	Literal	0..*	A free-text account of the record. This property can be repeated for parallel language versions of the description.		A
distributor	Agent	0..*	Party who distributes the resource [[ISO-19115]].		P
identifier	Literal	0..*	The main identifier for the Catalogue Record, e.g., the URI or other unique identifier in the context of the Catalogue.		P
language	Linguistic system	0..*	A language used in the textual metadata describing titles, descriptions, etc. of the Catalogued Resource.	This property can be repeated if the metadata is provided in multiple languages.	A
listing date	Temporal Literal	0..1	The date on which the description of the Resource was included in the Catalogue.		A
modification date	Temporal Literal	1	The most recent date on which the Catalogue entry was changed or modified.		A
originator	Agent	0..*	Party who created the resource [[ISO-19115]].		P
primary topic	Catalogued Resource	1	A link to the Dataset, Data service or Catalog described in the record.	A catalogue record will refer to one entity in a catalogue. This can be either a Dataset or a Data Service. To ensure an unambigous reading of the cardinality the range is set to Catalogued Resource. However it is not the intend with this range to require the explicit use of the class Catalogued Record. As abstract class, an subclass should be used.	A
principal investigator	Agent	0..*	Key party responsible for gathering information and conducting research [[ISO-19115]].		P
processor	Agent	0..*	Party who has processed the data in a manner such that the resource has been modified [[ISO-19115]].		P
publisher	Agent	0..1	An entity (organisation) responsible for making the Data Service available.		P
qualified attribution	Attribution	0..*	Link to an Agent having some form of responsibility for the Catalogue Record.		P
resource provider	Agent	0..*	Party that supplies the resource [[ISO-19115]].		P
rights holder	Agent	0..*	An Agent (organisation) holding rights on the Catalogue.		P
source metadata	Catalogue Record	0..1	The original metadata that was used in creating metadata for the Dataset.	This MAY refer to an INSPIRE / [[ISO-19115]] record that was transformed into the current GeoDCAT-AP one.	A
title	Literal	0..*	A name given to the Catalogue Record.	This property can be repeated for parallel language versions of the name.	A
user	Agent	0..*	Party who uses the resource [[ISO-19115]].		P

@prefix dcat: <https://www.w3.org/ns/dcat#> .
@prefix dct: <https://purl.org/dc/terms/> .
@prefix foaf: <https://xmlns.com/foaf/0.1/> .
@prefix vcard: <https://www.w3.org/2006/vcard/ns#> .
@prefix xsd: <https://www.w3.org/2001/XMLSchema#> .
@prefix record: <https://some.catalogue/record/> .
@prefix resource: <https://some.catalogue/resource/> .
record:af4c4fd6-0485-45c8-b6bc-8a8ed12aa3eb a dcat:CatalogRecord ;
    dct:conformsTo <https://data.europa.eu/930/> ;
    dct:identifier "af4c4fd6-0485-45c8-b6bc-8a8ed12aa3eb"^^xsd:string ;
    dct:language <https://publications.europa.eu/resource/authority/language/ENG> ;
    dct:modified "2020-03-25"^^xsd:date ;
    dcat:contactPoint [ a vcard:Organization ;
        vcard:fn "European Environment Agency"@en ;
        vcard:hasAddress [ a vcard:Address ;
            vcard:country-name "Denmark" ;
            vcard:locality "Copenhagen" ;
            vcard:postal-code "1050" ;
            vcard:region "K" ;
            vcard:street-address "Kongens Nytorv 6" ] ;
        vcard:hasEmail <mailto:sdi@eea.europa.eu> ] ;
    foaf:primaryTopic resource:eea_v_4326_1_mio_EU27-2020-basemap_i_2020_v01_r00 .

Catalogued Resource

Definition: Resource published or curated by a single agent.
Reference in DCAT-AP: Link
Usage Note: This class Catalogued Resource is an abstract class for DCAT-AP. Therefore only subclasses should be used in a data exchange.
Properties: This specification does not impose any additional requirements to properties for this entity.

Property	Range	Card	Definition	Usage	Reuse
algorithm	Checksum Algorithm	1	The algorithm used to produce the subject Checksum.		A
checksum value	xsd:hexBinary	1	A lower case hexadecimal encoded digest value produced using a specific algorithm.		A

Property	Range	Card	Definition	Usage	Reuse
access rights	Rights statement	0..1	Information that indicates whether the Dataset is publicly accessible, 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]].	E
applicable legislation	Legal Resource	0..*	The legislation that mandates the creation or management of the Dataset.		A
conforms to	Standard	0..*	An implementing rule or other specification.		A
contact point	Kind	0..*	Contact information that can be used for sending comments about the Dataset.		A
creation date	Temporal Literal	0..1	The date on which the Dataset has been first created.		P
creator	Agent	0..*	The Agent primarily responsible for producing the Dataset.		A
custodian	Agent	0..*	Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource [[ISO-19115]].		P
dataset distribution	Distribution	0..*	An available Distribution for the Dataset.		A
description	Literal	1..*	A free-text account of the Dataset.	This property can be repeated for parallel language versions of the description.	A
distributor	Agent	0..*	Party who distributes the resource [[ISO-19115]].		P
documentation	Document	0..*	A page or document about this Dataset.		A
frequency	Frequency	0..1	The frequency at which the Dataset is updated.		A
geographical coverage	Location	0..*	A geographic region that is covered by the Dataset.	This property refers to a geographic region that is covered by the Dataset. When multiple values are used for spatial coverage, this may be interpreted as a spatial union, or as alternative representations of spatial coverage that might fit, with no explicit spatial relation.	A
has version	Dataset	0..*	A related Dataset that is a version, edition, or adaptation of the described Dataset.		A
identifier	Literal	0..*	The main identifier for the Dataset, e.g. the URI or other unique identifier in the context of the Catalogue.		A
in series	Dataset Series	0..*	A dataset series of which the dataset is part.		A
is referenced by	Resource	0..*	A related resource, such as a publication, that references, cites, or otherwise points to the Dataset.		A
keyword	Literal	0..*	A keyword or tag describing the Dataset.		A
landing page	Document	0..*	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.	A
language	Linguistic system	0..*	A language of the Dataset.	This property can be repeated if there are multiple languages in the Dataset.	A
modification date	Temporal Literal	0..1	The most recent date on which the Dataset was changed or modified.		A
originator	Agent	0..*	Party who created the resource [[ISO-19115]].		P
other identifier	Identifier	0..*	A secondary identifier of the Dataset	Examples are MAST/ADS [[MASTADS]], DOI [[DOI]], EZID [[EZID]] or W3ID [[W3ID]].	A
principal investigator	Agent	0..*	Key party responsible for gathering information and conducting research [[ISO-19115]].		P
processor	Agent	0..*	Party who has processed the data in a manner such that the resource has been modified [[ISO-19115]].		P
provenance	Provenance Statement	0..*	A statement about the lineage of a Dataset.		A
publisher	Agent	0..1	An entity (organisation) responsible for making the Dataset available.		A
qualified attribution	Attribution	0..*	An Agent having some form of responsibility for the resource.		A
qualified relation	Relationship	0..*	A description of a relationship with another resource.		A
reference system	Concept	0..*	The reference system used in accordance with OGC EPSG Coordinate Reference Systems Register [[OGC-EPSG]].		P
related resource	Resource	0..*	A related resource.		A
release date	Temporal Literal	0..1	The date of formal issuance (e.g., publication) of the Dataset.		A
resource provider	Agent	0..*	Party that supplies the resource [[ISO-19115]].		P
resource type	Concept	0..1	Resource type in accordance with INSPIRE Resource Types [[INSPIRE-RT]].		E
rights	Rights statement	0..*	A statement that specifies rights associated with the Dataset.		A
rights holder	Agent	0..*	An Agent (organisation) holding rights on the Dataset.		P
sample	Distribution	0..*	A sample distribution of the dataset.		A
source	Dataset	0..*	A related Dataset from which the described Dataset is derived.		A
spatial resolution	Quality Measurement	0..*	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]]. Describes the spatial resolution of the original data in the dataset, i.e. regardless of how it is distributed using distributions.	E
spatial resolution as text	Literal	0..*	Textual description of spatial resolution.	Spatial resolution as free-text, when it cannot be specified via dqv:hasQualityMeasurement and dcat:spatialResolutionInMeters. Describes the spatial resolution of the original data in the dataset, i.e. regardless of how it is distributed using distributions.	P
spatial resolution in metres	xsd:decimal	0..*	The minimum spatial separation resolvable in a Dataset, measured in meters.	Describes the spatial resolution of the original data in the dataset, i.e. regardless of how it is distributed using distributions.	A
temporal coverage	Period of time	0..*	A temporal period that the Dataset covers.		A
temporal resolution	xsd:duration	0..*	The minimum time period resolvable in the Dataset.		A
theme	Concept	0..*	A category of the Dataset.	A Dataset may be associated with multiple themes.	A
title	Literal	1..*	A name given to the Dataset.	This property can be repeated for parallel language versions of the name.	A
topic category	Concept	0..*	Topic category in accordance with ISO-19115 [[INSPIRE-TC]].		P
user	Agent	0..*	Party who uses the resource [[ISO-19115]].		P
version	Literal	0..*	The version indicator (name or identifier) of a resource.		A
version notes	Literal	0..*	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.	A
was generated by	Activity	0..*	An activity that generated, or provides the business context for, the creation of the Dataset.		A
was used by	Activity	0..*	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.	P

Property	Range	Card	Definition	Usage	Reuse
access rights	Rights statement	0..1	Information that indicates whether the Dataset Series is publicly accessible, 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]].	E
applicable legislation	Legal Resource	0..*	The legislation that mandates the creation or management of the Dataset Series.		A
conforms to	Standard	0..*	An implementing rule or other specification.		E
contact point	Kind	0..*	Contact information that can be used for sending comments about the Dataset Series.		A
creation date	Temporal Literal	0..1	The date on which the Dataset Series has been first created.		P
creator	Agent	0..*	An entity responsible for producing the Dataset Series.		E
custodian	Agent	0..*	Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource [[ISO-19115]].		P
dataset series distribution	Distribution	0..*	An available Distribution for the Dataset Series.		E
description	Literal	1..*	A free-text account of the Dataset Series.	This property can be repeated for parallel language versions. It is recommended to provide an indication about the dimensions the Dataset Series evolves.	A
distributor	Agent	0..*	Party who distributes the resource [[ISO-19115]].		P
documentation	Document	0..*	A page or document about this Dataset Series.		E
frequency	Frequency	0..1	The frequency at which the Dataset Series is updated.	The frequency of a dataset series is not equal to the frequency of the dataset in the collection.	A
geographical coverage	Location	0..*	A geographic region that is covered by the Dataset Series.	When spatial coverage is a dimension in the dataset series then the spatial coverage of each dataset in the collection should be part of the spatial coverage. In that case, an open ended value is recommended, e.g. EU or a broad bounding box covering the expected values.	A
has version	Dataset	0..*	A related Dataset that is a version, edition, or adaptation of the described Dataset Series.		E
identifier	Literal	0..*	The main identifier for the Dataset Series, e.g. the URI or other unique identifier in the context of the Catalogue.		E
in series	Dataset Series	0..*	A dataset series of which the dataset series is part.		E
is referenced by	Resource	0..*	A related resource, such as a publication, that references, cites, or otherwise points to the Dataset Series.		E
keyword	Literal	0..*	A keyword or tag describing the Dataset.		E
landing page	Document	0..*	A web page that provides access to the Dataset Series, its Distributions and/or additional information.		E
language	Linguistic system	0..*	A language of the Dataset Series.		E
modification date	Temporal Literal	0..1	The most recent date on which the Dataset Series was changed or modified.	This is not equal to the most recent modified dataset in the collection of the dataset series.	A
originator	Agent	0..*	Party who created the resource [[ISO-19115]].		P
other identifier	Identifier	0..*	A secondary identifier of the Dataset Series.	Examples are MAST/ADS [[MASTADS]], DOI [[DOI]], EZID [[EZID]] or W3ID [[W3ID]].	E
principal investigator	Agent	0..*	Key party responsible for gathering information and conducting research [[ISO-19115]].		P
processor	Agent	0..*	Party who has processed the data in a manner such that the resource has been modified [[ISO-19115]].		P
publisher	Agent	0..1	An entity (organisation) responsible for ensuring the coherency of the Dataset Series	The publisher of the dataset series may not be the publisher of all datasets. E.g. a digital archive could take over the publishing of older datasets in the series.	A
qualified attribution	Attribution	0..*	An Agent having some form of responsibility for the resource.		E
qualified relation	Relationship	0..*	A description of a relationship with another resource.		E
reference system	Concept	0..*	The reference system used in accordance with OGC EPSG Coordinate Reference Systems Register [[OGC-EPSG]].	Spatial reference systems SHOULD be specified by using the corresponding URIs from the "EPSG coordinate reference systems" register operated by OGC [[OGC-EPSG]].	P
related resource	Catalogued Resource	0..*	A related resource.		E
release date	Temporal Literal	0..1	The date of formal issuance (e.g., publication) of the Dataset Series.	The moment when the dataset series was established as a managed resource. This is not equal to the release date of the oldest dataset in the collection of the dataset series.	A
resource provider	Agent	0..*	Party that supplies the resource [[ISO-19115]].		P
resource type	Concept	0..1	Resource type in accordance with INSPIRE Resource Types [[INSPIRE-RT]].		P
rights	Rights statement	0..*	A statement that specifies rights associated with the Dataset Series.		A
rights holder	Agent	0..*	An Agent (organisation) holding rights on the Dataset Series.		P
sample	Distribution	0..*	A sample distribution of the Dataset Series.		E
source	Dataset	0..*	A related Dataset from which the described Dataset Series is derived.		E
spatial resolution	Quality Measurement	0..*	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]].	E
spatial resolution as text	Literal	0..*	Textual description of spatial resolution.	Spatial resolution as free-text, when it cannot be specified via dqv:hasQualityMeasurement and dcat:spatialResolutionInMeters.	P
spatial resolution in metres	xsd:decimal	0..*	The minimum spatial separation resolvable in a Dataset, measured in meters.		A
temporal coverage	Period of time	0..*	A temporal period that the Dataset Series covers.	When temporal coverage is a dimension in the dataset series then the temporal coverage of each dataset in the collection should be part of the temporal coverage. In that case, an open ended value is recommended, e.g. after 2012.	A
theme	Concept	0..*	A category of the Dataset Series.		E
title	Literal	1..*	A name given to the Dataset Series.	This property can be repeated for parallel language versions of the name.	A
topic category	Concept	0..*	Topic category in accordance with ISO-19115 [[INSPIRE-TC]].		P
user	Agent	0..*	Party who uses the resource [[ISO-19115]].		P
version	Literal	0..*	The version indicator (name or identifier) of a resource.		E
version notes	Literal	0..*	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.	E
was generated by	Activity	0..*	An activity that generated, or provides the business context for, the creation of the Dataset Series.		E
was used by	Activity	0..*	An Activity that used the Dataset Series.	In GeoDCAT-AP, this property MAY be used to specify a testing Activity over a Dataset Series, against a given Standard, producing as output a conformance degree.	P

Property	Range	Card	Definition	Usage	Reuse
access rights	Rights statement	0..1	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]].	P
access service	Data Service	0..*	A data service that gives access to the distribution of the dataset.		A
access URL	Resource	1..*	A URL that gives access to a Distribution of the Dataset or Dataset Series.	The resource at the access URL may contain information about how to get the Dataset or Dataset Series.	A
applicable legislation	Legal Resource	0..*	The legislation that mandates the creation or management of the Distribution.		A
availability	Concept	0..1	An indication how long it is planned to keep the Distribution of the Dataset available.		A
byte size	xsd:nonNegativeInteger	0..1	The size of a Distribution in bytes.		A
character encoding	Literal	0..*	A character encoding used in the downloadable file or output of the data service represented by the Distribution.	It SHOULD be expressed using a character set name defined in the IANA register [[IANA-CHARSETS]].	P
checksum	Checksum	0..1	A mechanism that can be used to verify that the contents of a distribution have not changed.	The checksum is related to the downloadURL.	A
compression format	Media Type	0..1	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]].	A
description	Literal	0..*	A free-text account of the Distribution.	This property can be repeated for parallel language versions of the description.	A
documentation	Document	0..*	A page or document about this Distribution.		A
download URL	Resource	0..*	A URL that is a direct link to a downloadable file in a given format.		A
format	Media Type or Extent	0..1	The file format of the Distribution.		A
has policy	Policy	0..1	The policy expressing the rights associated with the Distribution if using the [[ODRL]] vocabulary.		A
language	Linguistic system	0..*	A language used in the Distribution.	This property can be repeated if the metadata is provided in multiple languages.	A
licence	Licence Document	0..1	A licence under which the Distribution is made available.		A
linked schemas	Standard	0..*	An established schema to which the described Distribution conforms.		A
media type	Media Type	0..1	The media type of the Distribution as defined in the official register of media types managed by IANA.	It SHOULD be expressed using a media type as defined in the official register of media types managed by IANA [[IANA-MEDIA-TYPES]].	A
modification date	Temporal Literal	0..1	The most recent date on which the Distribution was changed or modified.		A
packaging format	Media Type	0..1	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]].	A
reference system	Standard	0..*	The reference system used in the Distribution.	The reference system used in accordance with OGC EPSG Coordinate Reference Systems Register [[OGC-EPSG]].	P
release date	Temporal Literal	0..1	The date of formal issuance (e.g., publication) of the Distribution.		A
representation technique	Concept	0..1	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 the URIs of the corresponding code list operated by the INSPIRE Registry [[INSPIRE-SRT]].	P
rights	Rights statement	0..*	A statement that specifies rights associated with the Distribution.		A
spatial resolution	Quality Measurement	0..1	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]].	E
spatial resolution as text	Literal	0..1	Textual description of spatial resolution of a Distribution.	Spatial resolution types that cannot be specified via dcat:spatialResolutionInMeters - i.e., spatial resolution as equivalent scale, angular distance, vertical distance.	P
spatial resolution in metres	xsd:decimal	0..1	The minimum spatial separation resolvable in a dataset distribution, measured in meters.		A
status	Concept	0..1	The status of the Distribution in the context of maturity lifecycle.	It MUST take one of the values Completed, Deprecated, Under Development, Withdrawn.	A
temporal resolution	xsd:duration	0..*	The minimum time period resolvable in the dataset distribution.		A
title	Literal	0..*	A name given to the Distribution.	This property can be repeated for parallel language versions of the description.	A

Property	Range	Card	Definition	Usage	Reuse
address	Address (vCard)	0..1	The postal address of the Kind.		P
affiliation	Literal	0..1	The affiliation of the Kind.	His property can be repeated for different versions of the name (e.g. the name in different languages) - see § 11. Accessibility and Multilingual Aspects.	P
email	Email (vCard)	0..1	An email address of the Kind.	It MUST be specified using fully qualified mailto: URI scheme [[RFC6068]].	P
name	Literal	0..1	A name of the Kind.	This property can be repeated for different versions of the name (e.g., the name in different languages	P
phone	Resource	0..1	The phone number of the Kind.	It MUST be specified using fully qualified tel: URI scheme [[RFC3966]].	P
URL	Resource	0..1	A Web site of the Kind.		P

Property	Range	Card	Definition	Usage	Reuse
type	Concept	0..*	A type of licence, e.g. indicating 'public domain' or 'royalties required'.		P

Property	Range	Card	Definition	Usage	Reuse
bbox	Literal	0..1	The geographic bounding box of a resource.		A
centroid	Literal	0..1	The geographic center (centroid) of a resource.		A
gazetteer	Concept Scheme	0..1	The gazetteer to which the Location belongs.		P
geograhic identifier	Literal	0..*	The geographic identifier for the Location, e.g., the URI or other unique identifier in the context of the relevant gazetteer.		P
geograhic name	Literal	0..*	A preferred label of the Location.	This property can be repeated for parallel language versions of the label - see § 11. Accessibility and Multilingual Aspects.	P
geometry	Geometry	0..1	The corresponding geometry for a resource.		A

Property	Range	Card	Definition	Usage	Reuse
had role	Role	1..*	A function of an entity or agent with respect to another entity or resource.		A
relation	Resource	1..*	A resource related to the source resource.		A

Property	Range	Card	Definition	Usage	Reuse
generated	Entity	0..*	The Entity generated by the Activity.		P
qualified association	Association	0..*	Association to the Plan according to which the Activity has been carried out, and possibly to the Agent who played a role in it.		P
used	Entity	0..*	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.	P

Property	Range	Card	Definition	Reuse
administrative unit level 1	Literal	0..1	The name of the uppermost level of the address, almost always a country.	P
administrative unit level 2	Literal	0..1	The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities.	P
post code	Literal	0..1	The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.	P
post name	Literal	0..1	A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.	P
street address	Literal	0..1	The name of a passage or way through from one location to another.	P

Property	Range	Card	Definition	Usage	Reuse
administrative area	Literal	0..1	The administrative area of an Address.	Depending on the country, this corresponds to a province, a county, a region, or a state.	P
city	Literal	0..1	The city of an Address.		P
country	Literal	0..1	The country of an Address.		P
postal code	Literal	0..1	The postal code of an Address.		P
street address	Literal	0..1	The street name and civic number of an Address.		P

Property	Range	Card	Definition	Usage	Reuse
agent	Agent	0..*	The Agent to whom the resource is attributed.		P
had role	Role	0..*	A function of an entity or 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]].	P

Property	Range	Card	Definition	Usage	Reuse
category scheme	Concept Scheme	0..1	Relates a resource (for example a concept) to a concept scheme in which it is included.		P
preferred label	Literal	1..*	A preferred label of the concept.	This property can be repeated for parallel language versions of the label.	P

Property	Range	Card	Definition	Usage	Reuse
title	Literal	1..*	A name of the concept scheme.	May be repeated for different versions of the name	P

Property	Range	Card	Definition	Usage	Reuse
description	Literal	0..*	A free-text account of the Document.		P
title	Literal	0..*	A name of the document.		P

Property	Range	Card	Definition	Usage	Reuse
notation	Literal	1	A string that is an identifier in the context of the identifier scheme referenced by its datatype.		A

Property	Range	Card	Definition	Usage	Reuse
dimension	Dimension	0..1	The dimensions a quality metric, certificate and annotation allow a measurement of.	In GeoDCAT-AP, this property is used in the definition of the instances of dqv:Metric corresponding to the different types of spatial resolution (see Instances of Metric). When used for this purpose, it MUST always take as value `dqv:precision`.	P
expected data type	Datatype	0..1	Represents the expected data type for the metric's observed value (e.g., xsd:boolean, xsd:double etc...)		P

Property	Range	Card	Definition	Reuse
beginning	Time instant	0..1	The beginning of a period or interval.	A
end	Time instant	0..1	The end of a period or interval.	A
end date	Temporal Literal	0..1	The end of the period.	A
start date	Temporal Literal	0..1	The start of the period.	A

Property	Range	Card	Definition	Usage	Reuse
provenance statement text	Literal	0..*	The text of the Provenance Statement	This property can be repeated for parallel language versions of the text.	P

Property	Range	Card	Definition	Usage	Reuse
is measurement of	Metric	0..1	The Metric being observed.	In GeoDCAT-AP, this property is used to specify the type of spatial resolution being described, by taking as object one of the instances of dqv:Metric documented in Instances of Metric.	P
unit of measure	Concept	0..1	The unit in which the data values are measured.	In GeoDCAT-AP, this property is used to specify, when relevant, the unit of measure of the spatial resolution being described, by taking as object the relevant term from the QUDT Units Vocabulary [[QUDT-UNITS]].	P
value	Literal	0..1	Value computed by the relevant Metric.	In GeoDCAT-AP, this property is used to specify the value of the spatial resolution being described via a typed literal. The datatype MUST correspond to the one specified via property `dqv:expectedDataType` in the definition of the corresponding instance of `dqv:Metric`.	P

Property	Range	Card	Definition	Usage	Reuse
rights statement text	Literal	0..*	The text of the Rights Statement.	This property can be repeated for parallel language versions of the text.	P

Property	Range	Card	Definition	Usage	Reuse
creation date	Temporal Literal	0..1	The date on which the Standard has been first created.		P
description	Literal	0..*	A free-text account of the Standard.	This property can be repeated for parallel language versions of the description.	P
identifier	Literal	0..*	The main identifier for the Standard, e.g. the URI or other unique identifier in the context of the Catalogue, or of a reference register (e.g., the ISO, OGC, W3C catalogues of their standards, the OGC "EPSG coordinate reference systems" register [[OGC-EPSG]]).		P
reference register	Concept Scheme	0..1	The reference register to which the Standard belongs.		P
release date	Temporal Literal	0..1	The date of formal issuance (e.g., publication) of the Standard.		P
title	Literal	0..*	Name given to the Standard.	This property can be repeated for parallel language versions of the name.	P
type	Concept	0..1	The type of the Standard.	In GeoDCAT-AP, when the Standard is a spatial or temporal reference system, the relevant URIs from the INSPIRE glossary SHOULD be used [[INSPIRE-GLOSSARY]].	P
update / modification date	Temporal Literal	0..1	The most recent date on which the Standard was changed or modified.		P
version	Literal	0..1	A version number or other version designation of the Standard.		P

	Class	Definition
	Media Type	A file format or physical medium.
	Media Type or Extent	A media type or extent.
	Temporal Literal	rdfs:Literal encoded using the relevant [[ISO8601]] Date and Time compliant string and typed using the appropriate XML Schema datatype (xsd:gYear, xsd:gYearMonth, xsd:date, or xsd:dateTime).
	Time instant	A temporal entity with zero extent or duration.
	xsd:decimal	Decimal represents a subset of the real numbers, which can be represented by decimal numerals. The ·value space· of decimal is the set of numbers that can be obtained by multiplying an integer by a non-positive power of ten, i.e., expressible as i × 10^-n where i and n are integers and n >= 0.
	xsd:duration	Duration represents a duration of time. The ·value space· of duration is a six-dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second components defined in § 5.5.3.2 of [[ISO8601]], respectively.
	xsd:hexBinary	Hex-encoded binary data. The ·value space· of hexBinary is the set of finite-length sequences of binary octets.
	xsd:nonNegativeInteger	Number derived from integer by setting the value of minInclusive to be 0.

Property URI	Used for Class	Vocabulary name	Vocabulary URI	Usage note	Expected Usage
`adms:representationTechnique`	Distribution	INSPIRE Spatial Representation Type [[INSPIRE-SRT]]	https://inspire.ec.europa.eu/metadata-codelist/SpatialRepresentationType	GeoDCAT-AP extension.	AT-LEAST
`adms:status`	Distribution	Distribution Status Vocabulary [[EUV-DISTS]]	https://publications.europa.eu/resource/authority/distribution-status	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
`dcat:hadRole`	Attribution	INSPIRE Responsible Party Roles [[INSPIRE-RPR]]	https://inspire.ec.europa.eu/metadata-codelist/ResponsiblePartyRole	GeoDCAT-AP extension.	AT-LEAST
`dcat:mediaType`	Distribution	IANA Media Types [[IANA-MEDIA-TYPES]]	https://www.iana.org/assignments/media-types	Inherited from DCAT [[vocab-dcat-3]]	MUST
`dcat:compressFormat`	Distribution	IANA Media Types [[IANA-MEDIA-TYPES]]	https://www.iana.org/assignments/media-types	Inherited from DCAT [[vocab-dcat-3]]	MUST
`dcat:packageFormat`	Distribution	IANA Media Types [[IANA-MEDIA-TYPES]]	https://www.iana.org/assignments/media-types	Inherited from DCAT [[vocab-dcat-3]]	MUST
`dcat:theme`	Dataset Catalogue Data Service Dataset Series	Dataset Theme Vocabulary [[EUV-THEMES]]	https://publications.europa.eu/resource/authority/data-theme	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
INSPIRE Spatial Data Themes [[INSPIRE-THEMES]]	https://inspire.ec.europa.eu/theme	Mapping INSPIRE to GeoDCAT-AP	MAY
`dcatap:availability`	Distribution	EU Vocabularies Planned availability [[?EUV-PAV]]	Distribution availability vocabulary	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
`dct:accessRights`	Catalogue Dataset Dataset Series Data Service Distribution	EU Vocabularies Access rights [[?EUV-AR]]	https://publications.europa.eu/resource/authority/access-right	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
INSPIRE Limitations on Public Access [[?INSPIRE-LPA]]	https://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess	GeoDCAT-AP extension.	MAY
`dct:accrualPeriodicity`	Dataset Dataset Series	EU Vocabularies Frequency Named Authority List [[EUV-FREQ]]	https://publications.europa.eu/resource/authority/frequency	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
INSPIRE Maintenance Frequency [[INSPIRE-MF]]	https://inspire.ec.europa.eu/metadata-codelist/MaintenanceFrequency	GeoDCAT-AP extension.	MAY
`dct:format`	Distribution	EU Vocabularies File Type Named Authority List [[EUV-FT]]	https://publications.europa.eu/resource/authority/file-type	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
`dct:language`	Catalogue Catalogue Record Dataset Dataset Series Data Service Distribution	EU Vocabularies Languages Named Authority List [[EUV-LANG]]	https://publications.europa.eu/resource/authority/language	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
`dct:publisher`	Catalogue Dataset Dataset Series Data Service	EU Vocabularies Corporate bodies Named Authority List [[EUV-CB]]	https://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.	MAY
`geodcatap:referenceSystem`	Data Service Dataset Dataset Series Distribution	OGC EPSG Coordinate Reference Systems Register [[OGC-EPSG]]	https://www.opengis.net/def/crs/EPSG/0/	Defined by GeoDCAT-AP	MUST
`geodcatap:resourceType`	Dataset Dataset Series Data Service	INSPIRE Resource Types [[INSPIRE-RT]]	https://inspire.ec.europa.eu/metadata-codelist/ResourceType	Defined by GeoDCAT-AP	MUST
`dct:spatial`	Catalogue Dataset Dataset Series Data Service	EU Vocabularies Continents Named Authority List [[EUV-CONT]]	https://publications.europa.eu/resource/authority/continent	Inherited from DCAT-AP [[DCAT-AP-3]] 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.	MAY
EU Vocabularies Countries Named Authority List [[EUV-COUNTRIES]]	https://publications.europa.eu/resource/authority/country
EU Vocabularies Places Named Authority List [[EUV-PLACES]]	https://publications.europa.eu/resource/authority/place
[[GEONAMES]]	https://sws.geonames.org/
`geodcatap:serviceCategory`	Data Service	INSPIRE Spatial Data Service Categories [[INSPIRE-SDSC]]	https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory	GeoDCAT-AP extension.	MUST
`geodcatap:serviceProtocol`	Data Service	INSPIRE Protocol Values [[INSPIRE-PV]]	https://inspire.ec.europa.eu/metadata-codelist/ProtocolValue	GeoDCAT-AP extension.	MUST
`geodcatap:serviceType`	Data Service	INSPIRE Spatial Data Service Types [[INSPIRE-SDST]]	https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType	GeoDCAT-AP extension.	MUST
`geodcatap:topicCategory`	Catalogue Data Service Dataset Dataset Series	INSPIRE Topic Categories [[INSPIRE-TC]]	https://inspire.ec.europa.eu/metadata-codelist/TopicCategory	GeoDCAT-AP extension.	MUST
`dct:type`	Agent	ADMS publisher type [[ADMS-SKOS]] vocabulary	https://purl.org/adms/publishertype/	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
`dct:type`	Licence Document	ADMS licence type [[ADMS-SKOS]] vocabulary	https://purl.org/adms/licencetype/	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
`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.	AT-LEAST
`sdmx-attribute:unitMeasure`	Quality Measurement	QUDT Units Vocabulary [[QUDT-UNITS]]	https://www.qudt.org/vocab/unit	GeoDCAT-AP extension.	AT-LEAST

INSPIRE metadata * ISO 19115:2003 Core ISO 19115 path	Required in INSPIRE	DCAT-AP Property	Domain	Range	Comments
Resource title (M) * Resource title (M) `./identificationInfo/citation/title`	Datasets Dataset series Services	`dct:title` (M)	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`rdfs:Literal`	See
Resource abstract (M) * Abstract describing the resource (M) `./identificationInfo/abstract`	Datasets Dataset series Services	`dct:description` (M)	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`rdfs:Literal`	See
Resource type (M) * Hierarchy Level (C) (not in ISO 19115 core) `./hierarchyLevel`	Datasets Dataset series Services	`rdf:type` (M) (see also binding for GeoDCAT-AP Extended)	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`rdfs:Class` (values `dcat:Catalog`, `dcat:Dataset`, `dcat:DatasetSeries`, `dcat:DataService`)	See . `dcat:Catalog` can be used for catalogue / discovery services, in addition to `dcat:DataService`.
Resource locator (C) * On-line resource (O) `./distributionInfo/transferOptions/onLine/linkage`	Datasets Dataset series Services				See . The defined encoding depends whether the resource is a service or a dataset or dataset 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` `dcat:DataService`	`foaf:Document` `rdfs:Resource` `foaf:Document`	See . Properties `dcat:endpointURL` and `dcat:endpointDescription` are used when the resource locator points to a service endpoint.
For dataset and dataset series (function code not provided)		`dcat:landingPage` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`foaf:Document`	See .
For dataset and dataset series (‘download’ function code)		`dcat:accessURL` (M)	`dcat:Distribution`	`rdfs:Resource`	See . Property `dcat:accessURL` is also used whenever the resource locator points to a service endpoint.
For dataset and dataset series (‘information’ function code)		`foaf:page`	`dcat:Dataset` `dcat:DatasetSeries`	`foaf:Document`	See .
For dataset and dataset series (‘offlineAccess’ function code)		`dcat:accessURL` (M)	`dcat:Distribution`	`rdfs:Resource`	See . Property `dcat:accessURL` is also used whenever the resource locator points to a service endpoint.
For dataset and dataset series (‘order’ function code)		`dcat:accessURL` (M)	`dcat:Distribution`	`rdfs:Resource`	See . Property `dcat:accessURL` is also used whenever the resource locator points to a service endpoint.
For dataset and dataset series (‘search’ function code)		`foaf:page`	`dcat:Dataset` `dcat:DatasetSeries`	`foaf:Document`	See .
Unique resource identifier (M) * Dataset identifier (O) (not in ISO 19115 core) `./identificationInfo/citation/identifier`	Datasets Dataset series	`dct:identifier` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`rdfs:Literal`	See . In RDF, this could also be represented as the URI of the dataset or of the dataset series.
Coupled resource (O) * Operates On (O) (not in ISO 19115 core) `./identificationInfo/operatesOn`	Services	`dcat:servesDataset` (O)	`dcat:DataService`	`dcat:Dataset` `dcat:DatasetSeries`	See .
Resource language (C) * Dataset language (M) `./identificationInfo/language`	Datasets Dataset series	`dct:language` (O for `dcat:Dataset` and `dcat:DatasetSeries`, R for `dcat:Catalog`)	`dcat:Dataset` `dcat:DatasetSeries` `dcat:Catalog`	`dct:LinguisticSystem`	See .
Keyword (M) * Keyword (O) (not in ISO 19115 core) `./identificationInfo/descriptiveKeywords/keyword` `./identificationInfo/descriptiveKeywords/Type`	Datasets Dataset series Services	`dcat:keyword` (R) `dcat:theme` (R) (see also binding for GeoDCAT-AP Extended)	`dcat:Dataset`	`rdfs:Literal`	See . For datasets and dataset 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 . For services a syntax binding is provided in GeoDCAT-AP Extended only.
Geographic bounding box (M) * Geographic location of the resource (C) `./identificationInfo/extent/geographicElement/westBoundLongitude` `./identificationInfo/extent/geographicElement/eastBoundLongitude` `./identificationInfo/extent/geographicElement/southBoundLatitude` `./identificationInfo/extent/geographicElement/northBoundLatitude` `./identificationInfo/extent/geographicElement/geographicIdentifier`	Datasets Dataset series Services	`dct:spatial` (O)	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries`	`dct:Location`	See on the preferred format to be used in RDF for the representation of geometries.
Temporal reference (C) * Temporal extent (O) `./identificationInfo/extent/temporalElement/extent`	Datasets Dataset series Services	`dct:temporal` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`dct:PeriodOfTime`	See .
Temporal reference - Date of publication (C) * Dataset reference date (M) – publication `./identificationInfo/citation/date (date type = 'publication')`	Datasets Dataset series Services	`dct:issued` (R for `dcat:Catalog` and O for `dcat:Dataset` and `dcat:DatasetSeries`)	`dcat:Dataset` `dcat:DatasetSeries` `dcat:Catalog`	`Temporal Literal`	See .
Temporal reference - Date of last revision (C) * Dataset reference date (M) – revision `./identificationInfo/citation/date (date type = 'revision')`	Datasets Dataset series Services	`dct:modified` (R for `dcat:Catalog` and O for `dcat:Dataset` and `dcat:DatasetSeries`)	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries`	`Temporal Literal`	See .
Spatial resolution (C) * Spatial resolution (O) `./identificationInfo/spatialResolution/equivalentScale/denominator` `./identificationInfo/spatialResolution/distance`	Datasets Dataset series Services	`dcat:spatialResolutionInMeters` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`xsd:decimal`	See . Property `dcat:spatialResolutionInMeters` can only be used when spatial resolution is expressed as distance in metres.
Lineage (M) * Lineage (O) `./dataQualityInfo/lineage/statement`	Datasets Dataset series	`dct:provenance` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`dct:ProvenanceStatement`	See .
Conformity (M) * Report result (O) (not in ISO 19115 core) `./dataQualityInfo/report/result (applied to DQ_DomainConsistency)`	Datasets Dataset series Services	`dct:conformsTo` (O) (see also binding for GeoDCAT-AP Extended)	`dcat:Dataset` `dcat:DatasetSeries`	`dct:Standard`	See . `dct:conformsTo` can be used to specify only one of the cases supported in INSPIRE. i.e., when the degree of conformity is “conformant”.
Conformity Specification (M) * Report result - Specification (O) (not in ISO 19115 core) `./dataQualityInfo/report/result/specification (applied to DQ_DomainConsistency)`	Datasets Dataset series Services	`dct:title` (R) `dct:issued` (R) `dct:modified` (O) `dct:created` (O) (see also binding for GeoDCAT-AP Extended)	`rdfs:Resource`	`Temporal Literal`	See .
Conditions for access and use (M) * Restrictions on the access and use of the resource (O) (not in ISO 19115 core) either: `./identificationInfo/resourceConstraints/accessConstraints (gmd:MD_RestrictionCode = 'otherRestrictions')` Or: `./identificationInfo/resourceConstraints/useConstraints (gmd:MD_RestrictionCode = 'otherRestrictions')` And: `./identificationInfo/resourceConstraints/otherConstraints`	Datasets Dataset series Services	`dct:license` (R for `dcat:Catalog` and `dcat:Distribution`, O for `dcat:DataService`), `dct:rights` (O)	`dcat:Catalog` `dcat:Distribution` `dcat:DataService`	`dct:LicenseDocument`	See .
Limitations on public access (C) * Restrictions on the access and use of the resource (O) (not in ISO 19115 core) `./identificationInfo/resourceConstraints/accessConstraints (gmd:MD_RestrictionCode = 'otherRestrictions')` And: `./identificationInfo/resourceConstraints/otherConstraints` (with `gmx:Anchor` pointing to one values from the LimitationsOnPublicAccess INSPIRE code list)	Datasets Dataset series Services	`dct:accessRights` (O)	`dcat:DataService`	`dct:RightsStatement`	See .
Responsible party (M) * Responsible party (O) `./identificationInfo/pointOfContact`	Datasets Dataset series Services	`dct:publisher` (M) `dct:creator` (O)	`dcat:Catalog`	`foaf:Agent`	See . [[DCAT-AP-3]] supports only 3 of the 11 responsible party roles supported in INSPIRE. GeoDCAT-AP Extended makes use of [[PROV-O]] to specify information concerning provenance not covered in [[DCAT-AP-3]].
`dct:publisher` (R) `dcat:contactPoint` (R) `dct:creator` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`foaf:Agent` `vcard:Kind` `foaf:Agent`
Encoding (M) * Distribution format (O) `./identificationInfo/distributionFormat/name`	Datasets Dataset series	`dct:format` (R), `dcat:mediaType` (O)	`dcat:Distribution`	`dct:MediaTypeOrExtent`	See . See controlled vocabularies for encoding in .
Maintenance information (R) * Maintenance and update frequency (not in ISO 19115 core) `./identificationInfo/resourceMaintenance/maintenanceAndUpdateFrequency`		`dct:accrualPeriodicity` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`dct:Frequency`	See .
- not in [[INSPIRE-MD-REG]] - * Metadata standard implicit element		`dct:conformsTo` (R)	`dcat:CatalogRecord`	`dct:Standard`	See . This element, not existing in ISO 19115, is just meant to provide the context for the specification of the metadata standard name and version.
- not in [[INSPIRE-MD-REG]] - * Metadata standard name (O) `./metadataStandardName`		`dct:title`	`dct:Standard`	`rdfs:Literal`	See .
- not in [[INSPIRE-MD-REG]] - * Metadata standard version (O) `./metadataStandardVersion`		`owl:versionInfo`	`dct:Standard`	`rdfs:Literal`	See . This can be part of the information specified for metadata standard name.
Metadata date (M) * Metadata date stamp (M) `./dateStamp`	Datasets Dataset series Services	`dct:modified` (M)	`dcat:CatalogRecord`	`Temporal Literal`	See .
Metadata language (M) * Metadata language (C) `./language`	Datasets Dataset series Services	`dct:language` (O)	`dcat:CatalogRecord`	`dct:LinguisticSystem`	See .

INSPIRE metadata * ISO 19115:2003 Core Profile ISO 19115 path	Required in INSPIRE	Property	Domain	Range	Comments
Resource type (M) * Hierarchy Level (C) (not in ISO 19115 core) `./hierarchyLevel`	Datasets Dataset series Services	`geodcatap:resourceType`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`skos:Concept`	See and the controlled vocabulary for resource type in . [[DCAT-AP-3]] supports the use of `dct:type` on `dct:Dataset` only.
Unique resource identifier (M) * Dataset identifier (O) (not in ISO 19115 core) `./identificationInfo/citation/identifier`	Datasets Dataset series	`dct:identifier`	`dcat:Catalog` `dcat:DatasetSeries` `dcat:DataService`	`rdfs:Literal`	See . In RDF, this could also be represented as the URI of the resource.
Resource language (C) * Dataset language (M)	Datasets Dataset series	`dct:language`	`dcat:DatasetSeries` `dcat:DataService`	`dct:LinguisticSystem`	See .
Topic category (M) * Dataset topic category (M) `./identificationInfo/topicCategory`	Datasets Dataset series	`geodcatap:topicCategory`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`skos:Concept`	See and the controlled vocabulary for topic category in .
Spatial data service type (M) * Service type (not in ISO 19115 core)	Services	`geodcatap:serviceType`	`dcat:DataService`	`skos:Concept`	See . See controlled vocabulary for spatial data service type in .
Keyword (M) * Keyword (O) (not in ISO 19115 core) `./identificationInfo/descriptiveKeywords/keyword` `./identificationInfo/descriptiveKeywords/Type`	Datasets Dataset series Services	`dcat:keyword` `dcat:theme` `geodcatap:serviceCategory`	`dcat:Catalog` `dcat:DatasetSeries` `dcat:DataService`	`rdfs:Literal` `skos:Concept`	See .
Originating controlled vocabulary (C) * Thesaurus name (not in ISO 19115 core) `./identificationInfo/descriptiveKeywords/thesaurusName`	Datasets Dataset series Services	`skos:inScheme`	`skos:Concept`	`skos:ConceptScheme`	See .
Geographic bounding box (M) * Geographic location of the resource (C) `./identificationInfo/extent/geographicElement/westBoundLongitude` `./identificationInfo/extent/geographicElement/eastBoundLongitude` `./identificationInfo/extent/geographicElement/southBoundLatitude` `./identificationInfo/extent/geographicElement/northBoundLatitude` `./identificationInfo/extent/geographicElement/geographicIdentifier`	Datasets Dataset series Services	`dct:spatial` (O)	`dcat:DataService`	`dct:Location`	See on the preferred format to be used in RDF for the representation of geometries.
Temporal reference (C) * Temporal extent (O) `./identificationInfo/extent/temporalElement/extent`	Datasets Dataset series Services	`dct:temporal` (O)	`dcat:Catalog` `dcat:DataService`	`dct:PeriodOfTime`	See .
Temporal reference - Date of publication (C) * Dataset reference date (M) – publication `./identificationInfo/citation/date (date type = 'publication')`	Datasets Dataset series Services	`dct:issued`	`dcat:DataService`	Temporal Literal	See .
Temporal reference - Date of last revision (C) * Dataset reference date (M) – revision `./identificationInfo/citation/date (date type = 'revision')`	Datasets Dataset series Services	`dct:modified`	`dcat:DataService`	Temporal Literal	See .
Temporal reference - Date of creation (C) * Resource reference date (M) - creation `./identificationInfo/citation/date (date type = 'creation')`	Datasets Dataset series Services	`dct:created`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	Temporal Literal	See .
Spatial resolution (C) * Spatial resolution (O) `./identificationInfo/spatialResolution/equivalentScale/denominator` `./identificationInfo/spatialResolution/distance`	Datasets Dataset series Services	`dcat:spatialResolutionInMeters`	`dcat:DatasetSeries` `dcat:DataService`	`xsd:decimal`	See . 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 `geodcatap:spatialResolutionAsText` is used only in case spatial resolution is specified as free-text.
`dqv:hasQualityMeasurement`	`dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`dqv:QualityMeasurement`
`geodcatap:spatialResolutionAsText`	`rdfs:Literal`
Conformity (M) * Report result (O) (not in ISO 19115 core) `./dataQualityInfo/report/result (applied to DQ_DomainConsistency)`	Datasets Dataset series Services	`prov:wasUsedBy`	`prov:Entity` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`prov:Activity`	See .
Conformity Specification (M) * Report result - Specification (O) (not in ISO 19115 core) `./dataQualityInfo/report/result/specification (applied to DQ_DomainConsistency)`	Datasets Dataset series Services	`prov:wasDerivedFrom`	`prov:Entity`	`prov:Entity`	See .
Conformity degree (M) * Conformance Indication (M) (not in ISO 19115 core) `./dataQualityInfo/report/result/pass(applied to DQ_DomainConsistency)`	Datasets Dataset series Services	`prov:generated`	`prov:Activity`	`prov:Entity`	See and the controlled vocabulary for conformity degree in .
Topological Consistency (C) * Topological consistency (O) (not in ISO 19115 core) `./dataQualityInfo/report (applied to DQ_TopologicalConsistency)`	Datasets Dataset series	-	-	-	See . No syntax binding is provided for data quality, other than data conformity.
Data Quality – Logical Consistency – Conceptual Consistency, Domain Consistency – (R) * Domain consistency (O) (not in ISO 19115 core) `./dataQualityInfo/report (applied to DQ_DomainConsistency)`	Datasets Dataset series Services	-	-	-	See . No syntax binding is provided for data quality, other than conformity.
Limitations on public access (C) * Restrictions on the access and use of the resource (O) (not in ISO 19115 core) `./identificationInfo/resourceConstraints/accessConstraints (gmd:MD_RestrictionCode = 'otherRestrictions')`	Datasets Dataset series Services	`dct:accessRights` (O), `dct:rights` (O)	`dcat:Catalog` `dcat:Distribution` `dcat:DataService`	`dct:RightsStatement`	See .
Responsible party (M) * Responsible party (O) `./identificationInfo/pointOfContact`	Datasets Dataset series Services	`dct:publisher` `dct:creator`	`dcat:CatalogRecord` `dcat:DataService`	`foaf:Agent`	See .
`dcat:contactPoint`	`dcat:Catalog` `dcat:CatalogRecord` `dcat:DataService`	`vcard:Kind`
`dct:rightsHolder` `geodcatap:custodian` `geodcatap:distributor` `geodcatap:originator` `geodcatap:principalInvestigator` `geodcatap:processor` `geodcatap:resourceProvider` `geodcatap:user`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:CatalogRecord` `dcat:DataService`	`foaf:Agent`
`prov:qualifiedAttribution`	`prov:Entity` `dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:CatalogRecord` `dcat:DataService`	`prov:Attribution`
Responsible party role (M) * Responsible party role `./identificationInfo/pointOfContact/role`	Datasets Dataset series Services	`dcat:hadRole`	`prov:Attribution`	`dcat:Role`	See and controlled vocabulary for responsible party role in .
- not in [[INSPIRE-MD-REG]] - * Metadata file identifier (O) `./fileIdentifier`		`dct:identifier`	`dcat:CatalogRecord`	`rdfs:Literal`	See . 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) `./contact`	Datasets Dataset series Services	`dcat:contactPoint`	`dcat:CatalogRecord`	`vcard:Kind`	See .
`prov:qualifiedAttribution`	`dcat:CatalogRecord`	`prov:Attribution`
- not in [[INSPIRE-MD-REG]] - * Metadata character set (C) `./characterSet`		-	-	-	Metadata in GeoDCAT-AP are always in UTF-8. See .
Coordinate Reference System (M) * Reference System (O) (spatial component) `./referenceSystemInfo`	Datasets Dataset series Services	`geodcatap:referenceSystem`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService` `dcat:Distribution`	`skos:Concept`	See .
Temporal Reference System (C) * Reference System (O) (temporal component) `./referenceSystemInfo`	Datasets Dataset series	`geodcatap:referenceSystem`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService` `dcat:Distribution`	`skos:Concept`	See .
Character Encoding (C) * Dataset character set (C) `./identificationInfo/characterSet`	Datasets Dataset series	`cnt:characterEncoding`	`dcat:Distribution`	`rdfs:Literal`	See .
Spatial representation type – (M) * Spatial representation type (O) `./identificationInfo/spatialRepresentationType`	Datasets Dataset series	`adms:representationTechnique`	`dcat:Distribution`	`skos:Concept`	See .

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

Resource metadata in GeoDCAT-AP:

[] dct:description "Pan-European Forest / Non Forest Map with target year 2006,
  Data Source: Landsat ETM+ and Corine Land Cover 2006, Classes: for-est, non-forest,
  clouds/snow, no data; Method: automatic classification performed with an in-house
  algorithm; spatial resolution: 25m. In addition, the forest map 2006 is extended to
  FTYPE2006 to include forest types (broadleaf, coniferous forest) that are mapped
  using MODIS composites."@en .

Resource metadata in ISO 19139:

<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:abstract>
        <gco:CharacterString>
          Pan-European Forest / Non Forest Map with target year 2006, Data Source:
          Landsat ETM+ and Corine Land Cover 2006, Classes: for-est, non-forest,
          clouds/snow, no data; Method: automatic classification performed with an
          in-house algorithm; spatial resolution: 25m. In addition, the forest map
          2006 is extended to FTYPE2006 to include forest types (broadleaf, coniferous
          forest) that are mapped using MODIS composites.
        </gco:CharacterString>
      </gmd:abstract>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

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		Always UTF-8
		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)

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]])
	Degree (M)				`prov:generated` (range `prov:Entity`)	`dct:description`

[[ISO-19115]]	[[INSPIRE-MD-REG]]	Description	Proposed RDF mapping
Resource provider	Part B, §6.1	Party that supplies the resource.	`geodcatap:resourceProvider`
Custodian	Part B, §6.2	Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource.	`geodcatap:custodian`
Owner	Part B, §6.3	Party that owns the resource.	`dct:rightsHolder`
User	Part B, §6.4	Party who uses the resource.	`geodcatap:user`
Distributor	Part B, §6.5	Party who distributes the resource	`geodcatap:distributor`
Originator	Part B, §6.6	Party who created the resource.	`geodcatap: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	`geodcatap:principalInvestigator`
Processor	Part B, §6.9	Party who has processed the data in a manner such that the resource has been modified.	`geodcatap: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`

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

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

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

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`

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

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

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

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	-	AS_NEEDED
Irregular	irregular	IRREG
notPlanned	-	NOT_PLANNED
unknown	-	UNKNOWN
-	triennial	TRIENNIAL
-	biennial	BIENNIAL
-	threeTimesAYear	ANNUAL_3
-	bimonthly	BIMONTHLY
-	semimonthly	MONTHLY_2
-	threeTimesAMonth	MONTHLY_3
-	semiweekly	WEEKLY_2
-	threeTimesAWeek	WEEKLY_3
-	-	OTHER

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`

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`

Abstract

Introduction

Context

Scope of the Application Profile

DCAT-AP Context

Revision history

Notes on alignment with DCAT 3

Meeting minutes

Status

License

Conformance Statement

Provider requirements

Receiver requirements

Terminology

Used prefixes

Overview

Application profile diagram

Main Entities

Supportive Entities

Datatypes

Controlled Vocabularies

Requirements for controlled vocabularies

Expected usage of controlled vocabularies

Controlled vocabularies to be used

Other controlled vocabularies

Agent Roles

Accessibility and Multilingual Aspects

High Value Datasets

Legal information

Privacy and security considerations

Conformance Test Results

Validation of GeoDCAT-AP

INSPIRE and ISO 19115 Mappings

Objectives

Motivation and use cases

Supported tooling

Methodology and summary of results

Alignment criteria and requirements

Metadata elements to be covered by GeoDCAT-AP

Alignments defined in GeoDCAT-AP

RDF syntax bindings for INSPIRE and ISO 19115 metadata elements

Overview of bindings for GeoDCAT-AP Core

Overview of bindings for GeoDCAT-AP Extended

Overview of metadata elements covered by GeoDCAT-AP

Detailed usage notes and examples

Resource title - *Dataset title

Resource abstract - *Abstract describing the dataset

Resource type - *not in ISO 19115 core

Resource locator - *On-line resource

Unique resource identifier - *not in ISO 19115 core

Coupled resource - *not in ISO 19115 core

Resource language and metadata language - *Dataset language and Metadata language

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

Topic category and keyword in datasets and dataset series

Keyword in services

Spatial data service type - *not in ISO 19115 core

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

Bounding box

Geographic identifier

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

Lineage - *Lineage

Spatial resolution – Spatial resolution of the dataset

Conformity and data quality - *not in ISO 19115 core

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

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

*Metadata file identifier

*Metadata standard name, *Metadata standard version

*Metadata characterset

Metadata point of contact - *Metadata point of contact

Metadata date - *Metadata date stamp

Metadata language - *Metadata language

Coordinate reference systems and Temporal reference systems – *Reference System

Character encoding - *Dataset character set and *Metadata character set

Encoding - *Distribution format

Spatial representation type – *Spatial representation type

Maintenance information - *not in ISO 19115 core

Comparison between INSPIRE and ISO 19115-1:2014

Spatial dataset and spatial dataset series

Services

Quick Reference of Classes and Properties

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

Responsible party and metadata point of contact - Dataset responsible party and Metadata point of contact

Metadata standard name, Metadata standard version

Character encoding - Dataset character set and Metadata character set