Copyright © 2015-2019 European Union. This document is licensed under the ISA Open Metadata Licence v1.1.

This document contains the specification for GeoDCAT-AP, an extension of the DCAT application profile for data portals in Europe (DCAT-AP) for describing geospatial datasets, dataset series, and services.

Its basic use case is to make spatial datasets, dataset series, and services searchable on general data portals, thereby making geospatial information better searchable across borders and sectors. This can be achieved by the exchange of descriptions of data sets among data portals. For this purpose, GeoDCAT-AP provides an RDF syntax binding for the union of metadata elements of the core profile of ISO 19115:2003 and those defined in the framework of the INSPIRE Directive of the European Union.

Disclaimer

This specification was prepared for the ISA Programme by: PwC EU Services.

The views expressed in this specification are purely those of the authors and may not, in any circumstances, be interpreted as stating an official position of the European Commission.

The European Commission does not guarantee the accuracy of the information included in this study, nor does it accept any responsibility for any use thereof.

Reference herein to any specific products, specifications, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favouring by the European Commission.

All care has been taken by the author to ensure that s/he has obtained, where necessary, permission to use any parts of manuscripts including illustrations, maps, and graphs, on which intellectual property rights already exist from the titular holder(s) of such rights or from her/his or their legal representative.

Change history

This version of GeoDCAT-AP 1.0 has been amended with respect to the original one with editorial changes.

None of such changes affect the actual content of the original specification (GeoDCAT-AP v1.0), or the mapping rules defined thereby.

Changes since GeoDCAT-AP v1.0.1

Changes since GeoDCAT-AP v1.0

Abbreviations used in this document

ARE3NA Reusable INSPIRE Reference Platform
CRS Coordinate Reference System
CSW Catalog Services for the Web
DCAT Data Catalog Vocabulary
DCAT-AP DCAT Application Profile for Data Portals in Europe
DCMI Dublin Core Metadata Initiative
EARL Evaluation and Report Language
EU European Union
EuroVoc Multilingual Thesaurus of the European Union
GEMET GEneral Multilingual Environmental Thesaurus
GML Geography Markup Language
GeoDCAT-AP Geographical extension of [[DCAT-AP]]
IANA Internet Assigned Numbers Authority
INSPIRE Infrastructure for Spatial Information in the European Community
ISO International Standardisation Organisation
JRC European Commission - Joint Research Centre
MDR Metadata Registry
NAL Named Authority Lists
OGC Open Geospatial Consortium
RDF Resource Description Framework
RFC Request for Comments
SPARQL SPARQL Protocol and RDF Query Language
URI Uniform Resource Identifier
W3C World Wide Web Consortium
WG Working Group
WKT Well Known Text
XML eXtensible Markup Language
XSLT eXtensible Stylesheet Language Transformations

Introduction

This document contains the specification for GeoDCAT-AP, an extension of the DCAT application profile for data portals in Europe (DCAT-AP) [[DCAT-AP]] for describing geospatial datasets, dataset series, and services.

Its basic use case is to make spatial datasets, dataset series, and services searchable on general data portals, thereby making geospatial information better searchable across borders and sectors. This can be achieved by the exchange of descriptions of data sets among data portals. For this purpose, GeoDCAT-AP provides an RDF syntax binding for the union of metadata elements of the core profile of ISO 19115:2003 [[ISO-19115]] and those defined in the framework of the INSPIRE Directive [[INSPIRE-DIR]].

The GeoDCAT-AP specification does not replace the INSPIRE Metadata Regulation [[?INSPIRE-MD-REG]] nor the INSPIRE Metadata technical guidelines [[INSPIRE-MD-20131029]] based on ISO 19115 and ISO 19119. Its purpose is to give owners of geospatial metadata the possibility to achieve more by providing the means of an additional implementation through harmonised RDF syntax bindings. Conversion rules to RDF syntax would allow Member States to maintain their collections of INSPIRE-relevant datasets following the INSPIRE Metadata technical guidelines based on ISO 19115 and ISO 19119 [[ISO-19119]], while at the same time publishing these collections on [[DCAT-AP]]-conformant data portals. A conversion to RDF syntax allows additional metadata elements to be displayed on general-purposed data portals, provided that such data portals are capable of displaying additional metadata elements. Additionally, data portals may be capable of providing machine-to-machine interfaces where additional metadata could be provided.

Objectives

The objective of this work is to define an RDF syntax that can be used for the exchange of descriptions of spatial datasets, dataset series, and services among data portals. The RDF syntax should extend the DCAT Application Profile for data portals in Europe [[DCAT-AP]].

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

Structure of this document

This document consists of the following sections:

This specification is accompanied by a set of annexes, providing additional reference and support material. More precisely:

Motivation and use cases

The basic use case that GeoDCAT-AP intends to enable is a cross-domain data portal search for datasets, as documented in the DCAT-AP specification [[DCAT-AP]]. GeoDCAT-AP will make it easier to share descriptions of spatial datasets between spatial data portals and general data portals, and thus help increase public and cross-sector access to such high value datasets. The datasets could include:

Datasets on the INSPIRE Geoportal

The INSPIRE Geoportal aggregates metadata for over 100k datasets across Europe. It provides the means to search for spatial data sets and spatial data services, and subject to access restrictions, to view spatial data sets from the EU Member States within the framework of the INSPIRE Directive. The metadata stored on this portal is structured according to the INSPIRE Metadata Technical Guidelines [[INSPIRE-MD-20131029]]. In order to maximise visibility and re-use, spatial datasets could also be listed on general-purpose Open Data Portals, such as the European Union Open Data Portal (EU ODP) and the European Data Portal (EDP) .

Datasets on national SDIs

GeoDCAT-AP would facilitate the integration of SDIs operated by EU Member States with any data catalogue able to consume [[DCAT-AP]]-compliant metadata.

General geospatial datasets

The geospatial community shares a common background and makes consistent use of consolidated standards and technologies. In particular, as far as metadata are concerned, it is widespread to use standards like ISO 19115 / 19139, for the representation and encoding of metadata, and OGC’s [[?CSW]] (Catalog Service for the Web) for accessing and querying metadata records. These standards are also those currently recommended in INSPIRE.

An additional RDF syntax for INSPIRE and ISO 19115 metadata elements is beneficial, especially when other data portals support the [[DCAT-AP]] metadata elements only.

Conversion rules to RDF syntax would allow Member States to maintain their collections of INSPIRE-relevant datasets following the INSPIRE Metadata Technical Guidelines based on ISO 19115 and ISO 19119, while at the same time publishing these collections on [[DCAT-AP]]-conformant data portals. A conversion to RDF syntax – using for example the GeoDCAT-AP XSLT script [[GEODCAT-XSLT]] - allows additional metadata elements to be displayed on general-purposed data portals, provided that such data portals are capable of displaying additional metadata elements. Furthermore, data portals frequently are complemented by a triple store, making that the full set of GeoDCAT-AP metadata can be queried through a SPARQL endpoint.

Methodology and summary of results

Methodologically, the development of GeoDCAT-AP implied three main interrelated tasks:

  1. Definition of alignment criteria and requirements.

  2. Identification of the metadata elements to be covered by GeoDCAT-AP.

  3. Definition of alignments for the metadata elements to be covered by GeoDCAT-AP.

These tasks and their results are described in the following sections.

Alignment criteria and requirements

The objective of the GeoDCAT-AP is twofold:

  1. Provide a [[DCAT-AP]]-conformant representation of geospatial metadata.

  2. Provide an as much as possible comprehensive RDF-based representation of geospatial metadata, based on widely used vocabularies (as [[DCAT-AP]]), trying, at the same time, to avoid semantic loss and to promote cross-domain re-use.

These two goals, having a different scope and applying to different use cases (see ), are reflected in the two profiles of GeoDCAT-AP, core and extended, described in .

Note that point (1) implies that:

Another key criterion was to base as much as possible the defined alignments on existing practices, in particular those contributed by the GeoDCAT-AP WG. The objective was to build upon experiences having already addressed issues in scope of GeoDCAT-AP, and to avoid a negative impact on existing implementations.

Finally, as already mentioned in , whenever no suitable candidates were available in existing vocabularies to represent geospatial metadata elements, the possibility of defining new terms was not excluded. However, this option needed to be carefully assessed, and discarded whenever it might have led to a specification that was conflicting with standards under preparation. For example, this was the case of the work carried out by the W3C Data on the Web Best Practices Working Group and the joint W3C/OGC Spatial Data on the Web Working Group.

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

Metadata elements to be covered by GeoDCAT-AP

The general criterion used for this task was that GeoDCAT-AP would ideally cover all the metadata elements of the core profile of ISO 19115 and those defined in INSPIRE, with the requirement that only optional elements might be excluded.

Based on this, the current version of GeoDCAT-AP covers the following set of metadata elements:

More precisely, the supported INSPIRE metadata elements include:

The full list of metadata elements covered by the current version of GeoDCAT-AP is available in to this document.

The metadata elements not supported in the current version of GeoDCAT-AP are those recommended only for specific INSPIRE spatial data themes in the INSPIRE Data Specifications Technical Guidelines, and listed in the second, third and fourth table included in Appendix B.2 to the INSPIRE Metadata Technical Guidelines (version 1.3) [[INSPIRE-MD-20131029]].

These elements have been excluded in the current version of GeoDCAT-AP for the following reasons:

Support to these metadata elements might be provided in future versions of GeoDCAT-AP.

Alignments defined in GeoDCAT-AP

The alignments defined in the current version of GeoDCAT-AP are the result of an iterative revision process, following the criteria illustrated in the previous sections and the review of the GeoDCAT-AP WG.

The work started with the review of the suite of specifications concerning the INSPIRE profile of [[DCAT-AP]] (INSPIRE+DCAT-AP) [[INSPIRE-DCAT]], and of the preliminary proposals concerning the metadata elements not covered by INSPIRE+DCAT-AP.

In two specific cases, feedback has been asked to relevant standardisation bodies, in order to validate the proposal made in GeoDCAT-AP. In particular, this concerned feedback provided by the W3C Provenance Working Group on the use of the W3C PROV ontology to model responsible party roles and conformance results (data quality).

Finally, the GeoDCAT-AP WG has worked in close coordination with the DCAT-AP WG, in order to ensure mutual compliance of the proposed solutions.

The results of this work, reflected in the current version of GeoDCAT-AP, can be summarised as follows:

The majority of the alignments defined in GeoDCAT-AP provide a complete representation of the corresponding geospatial metadata elements, but some metadata elements have open issues:

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

RDF syntax bindings for INSPIRE and ISO 19115 metadata elements

The following sections provide the list of the bindings defined in GeoDCAT-AP for the RDF representation of INSPIRE metadata and the core profile of ISO 19115:2003.

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

Used namespaces

Table 1 lists the RDF namespaces (and prefixes) used in the remainder of this document.

Table 1: Namespace prefixes
Prefix Namespace RDF Vocabulary
adms http://www.w3.org/ns/adms# Asset Description Metadata Schema [[!VOCAB-ADMS]]
cnt http://www.w3.org/2011/content# Representing Content in RDF 1.0 [[!Content-in-RDF10]]
dc http://purl.org/dc/elements/1.1/ Dublin Core Metadata Element Set, Version 1.1 [[!DC11]]
dcat http://www.w3.org/ns/dcat# Data Catalog Vocabulary [[!VOCAB-DCAT]]
dct http://purl.org/dc/terms/ DCMI Metadata Terms [[!DCTERMS]]
dctype http://purl.org/dc/dcmitype/ DCMI Type Vocabulary [[!DCTERMS]]
foaf http://xmlns.com/foaf/0.1/ FOAF Vocabulary [[!FOAF]]
gsp http://www.opengis.net/ont/geosparql# OGC GeoSPARQL [[!GeoSPARQL]]
locn http://www.w3.org/ns/locn# ISA Programme Core Location Vocabulary [[!LOCN]]
owl http://www.w3.org/2002/07/owl# OWL Web Ontology Language [[!OWL-REF]]
prov http://www.w3.org/ns/prov# PROV-O: The PROV Ontology [[!PROV-O]]
rdf http://www.w3.org/1999/02/22-rdf-syntax-ns# Resource Description Framework (RDF): Concepts and Abstract Syntax [[!RDF-CONCEPTS]]
rdfs http://www.w3.org/2000/01/rdf-schema# RDF Vocabulary Description Language 1.0: RDF Schema [[!RDF-SCHEMA-20040210]]
schema http://schema.org/ schema.org [[SCHEMA-ORG]]
skos http://www.w3.org/2004/02/skos/core# SKOS Simple Knowledge Organization System - Reference [[!SKOS-REFERENCE]]
vcard http://www.w3.org/2006/vcard/ns# vCard Ontology [[!VCARD-RDF]]
xsd http://www.w3.org/2001/XMLSchema# XML Schema Part 2: Datatypes Second Edition [[!XMLSCHEMA-2]]

Overview of bindings for GeoDCAT-AP Core

Table 2 provides an overview of GeoDCAT-AP Core. This includes bindings for metadata elements of the INSPIRE metadata and metadata elements in the core profile of ISO 19115:2003 core for which DCAT-AP provides an RDF syntax binding. Those metadata elements for which [[!DCAT-AP]] does not provide a binding are part of the GeoDCAT-AP Extended profile described in .

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

In addition to this, GeoDCAT-AP Core does not provide alignments from metadata records concerning services, with the only exception of catalogue or discovery services, which are the only ones supported in [[DCAT-AP]].

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

Table 2: Element bindings for GeoDCAT-AP Core

INSPIRE metadata

*ISO 19115:2003 Core Profile

 DCAT-AP Property Domain Range Comments

Resource title (M)

*Dataset title (M)

 dct:title (M)

-

(dcat:Dataset (M), dcat:Catalog (M))

 rdf:PlainLiteral See

Resource abstract (M)

*Abstract describing the dataset (M)

 dct:description (M)

-

(dcat:Dataset (M), dcat:Catalog (M))

 rdf:PlainLiteral See

Resource type (M)

*not in ISO 19115 core

rdf:type (M)

(see also binding for GeoDCAT-AP Extended)

-

(dcat:Dataset (M), dcat:Catalog (M))

rdfs:Class (values dcat:Dataset, dcat:Catalog)

 See . [[DCAT-AP]] does not distinguish between datasets and dataset series. dcat:Catalog can be used for catalogue / discovery services.

Resource locator (C)

*On-line resource (O)

 See . The proposed encoding depends whether the resource is a service or a dataset or data series. Also, the value of the function code (CI_OnlineFunctionCode) must be taken into account.

For services

 foaf:homepage

-

(dcat:Catalog (M))

 foaf:Document See .

For dataset and data series (function code not provided)

 dcat:landingPage (O) dcat:Dataset (M) foaf:Document See .

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

 dcat:accessURL (M) dcat:Distribution (R) rdfs:Resource See .

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

 foaf:page (not in [[DCAT-AP]]!)

-

(dcat:Dataset (M))

 foaf:Document See .

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

 dcat:accessURL (M) dcat:Distribution (R) rdfs:Resource See .

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

 dcat:accessURL (M) dcat:Distribution (R) rdfs:Resource See .

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

 foaf:page

-

(dcat:Dataset)

 foaf:Document See .

Unique resource identifier (M)

*not in ISO 19115 core

 dct:identifier (O)

-

(dcat:Dataset (M))

 rdfs:Literal See . In RDF, this could also be represented as the URI of the dataset.

Resource language (C)

*Dataset language (M)

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

-

(dcat:Dataset (M), dcat:Catalog (M))

 dct:LinguisticSystem See .

Spatial data service type (M)

*not in ISO 19115 core

 rdf:type -

rdfs:Class (values

dcat:Catalog)

 See . [[DCAT-AP]] supports only one type of services - i.e., data catalogues.

Keyword value (M)

*not in ISO 19115 core

dcat:keyword (R)

dcat:theme (R)

(see also binding for GeoDCAT-AP Extended)

 dcat:Dataset (M) rdfs:Literal

See . For datasets and data series, dcat:keyword is used for free keywords; dcat:theme for controlled vocabularies.

Keywords whose controlled vocabulary is the one of the INSPIRE spatial data themes are mapped to dcat:theme, and expressed by the corresponding URI in the INSPIRE Registry. See controlled vocabulary for theme in .

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

Geographic bounding box (M)

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

 dct:spatial (O)

-

(dcat:Dataset (M), dcat:Catalog (M))

 dct:Location See on the preferred format to be used in RDF for the representation of geometries.

Temporal extent (C)

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

 dct:temporal (O)

-

(dcat:Dataset (M))

 dct:PeriodOfTime See .

Date of publication (C)

*Dataset reference date (M) – publication

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

-

(dcat:Dataset (M), dcat:Catalog (M))

 xsd:date See .

Date of last revision (C)

*Dataset reference date (M) – revision

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

-

(dcat:Dataset (M), dcat:Catalog (M))

 xsd:date See .

Lineage (M)

*Lineage (O)

 dct:provenance

-

-

(dcat:Dataset (M), dcat:Catalog (M))

 dct:ProvenanceStatement See .

Conformity (M)

*not in ISO 19115 core

dct:conformsTo (O)

(see also binding for GeoDCAT-AP Extended)

-

(dcat:Dataset

(M))

 dct:Standard See . dct:conformsTo can model only one of the cases supported in INSPIRE. i.e., when the degree of conformity is “conformant”.

Conformity Specification (M)

*not in ISO 19115 core

dct:title

dct:issued, dct:modified, dct:created

(see also binding for GeoDCAT-AP Extended)

 rdfs:Resource

rdf:PlainLiteral

xsd:date

 See .

Conditions for access and use (M)

*not in ISO 19115 core

 dct:license (O)

-

(dcat:Distribution (R))

 dct:LicenseDocument See .

Limitations on public access (C)

*not in ISO 19115 core

 dct:accessRights (O)

-

(dcat:Distribution (R))

 dct:RightsStatement See .

Responsible party (M)

*Dataset responsible party (O)

 dct:publisher (R), dcat:contactPoint (R)

-

(dcat:Dataset (M))

dct:Agent

vcard:Kind

 See . [[DCAT-AP]] supports only 2 of the 11 responsible party roles supported in INSPIRE. GeoDCAT-AP Extended suggests the use of the W3C PROV ontology to model information concerning provenance not covered in [[DCAT-AP]].

Encoding (M)

*Distribution format (O)

 dct:format (R), dcat:mediaType (O) dcat:Distribution (R) dc:MediaTypeOrExtent See . See controlled vocabularies for encoding in .

Maintenance information (R)

*not in ISO 19115 core

 dct:accrualPeriodicity (O)

dctype:Collection

(dcat:Dataset) (M)

 dct:Frequency See .
-Metadata standard dct:conformsTo (R)

-

(dcat:CatalogRecord (O))

 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.
*Metadata standard name (O) dct:title

-

(dct:Standard (O))

 rdf:PlainLiteral See .
*Metadata standard version (O) owl:versionInfo

-

(dct:Standard (O))

 rdfs:Literal See . This can be part of the information specified for metadata standard name.

Metadata date (M)

*Metadata date stamp (M)

 dct:modified (M)

-

(dcat:CatalogRecord (O))

 xsd:date See .

Metadata language (M)

*Metadata language (C)

 dct:language (O)

-

(dcat:CatalogRecord (O))

 dct:LinguisticSystem See .

Overview of bindings for GeoDCAT-AP Extended

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

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

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

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

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

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

Table 3: Element bindings for GeoDCAT-AP Extended

INSPIRE metadata

*ISO 19115:2003 Core Profile

 Property Domain Range Comments

Resource type (M)

*not in ISO 19115

 dct:type

-

(dcat:Dataset (M), dcat:Catalog (M))

rdfs:Class

(skos:Concept)

 See and the controlled vocabulary for resource type in . [[DCAT-AP]] supports the use of dct:type on dct:Dataset only.

Topic category (M)

*Dataset topic category (M)

 dct:subject

-

(dcat:Dataset (M))

-

(skos:Concept)

 See and the controlled vocabulary for topic category in .

Spatial data service type (M)

*not in ISO 19115

 dct:type

-

(dcat:Dataset (M), dcat:Catalog (M), dctype:Service)

rdfs:Class

(skos:Concept)

 See . See controlled vocabulary for spatial data service type in .

Keyword value (M)

*not in ISO 19115 core

dc:subject

dct:subject

dct:type

 - (dcat:Catalog (M))

- (rdfs:Literal)

- (rdfs:Resource)

rdfs:Class (skos:Concept)

 See .

Originating controlled vocabulary (C)

*not in ISO 19115 core

 skos:inScheme skos:Concept skos:ConceptScheme See .

Date of creation (C)

*Dataset reference date (M) - creation

 dct:created

-

(dcat:Dataset (M), dcat:Catalog (M))

 xsd:date See .

Spatial resolution (C)

*Spatial resolution of the dataset (O)

 rdfs:comment - rdfs:Literal See . Spatial resolution is encoded in a human-readable form only.

Conformity (M)

*not in ISO 19115 core

 prov:wasUsedBy

prov:Entity

(dcat:DataSet (M))

 prov:Activity See .

Conformity Specification (M)

*not in ISO 19115 core

 prov:wasDerivedFrom prov:Entity prov:Entity See .

Conformity degree (M)

*not in ISO 19115 core

 prov:generated prov:Activity prov:Entity See and the controlled vocabulary for conformity degree in .

Topological Consistency (C)

*not in ISO 19115 core

 - - - See . No syntax binding is provided for data quality, other than data conformity.

Data Quality – Logical Consistency –

Conceptual Consistency, Domain Consistency – (R)

*not in ISO 19115 core

 - - - See . No syntax binding is provided for data quality, other than conformity.

Responsible party (M)

*Dataset responsible party (O)

 dct:creator

-

(dcat:Dataset (M))

 dct:Agent See .
prov:qualifiedAttribution

prov:Entity

(dcat:Dataset (M))

 prov:Attribution
Responsible party role (M) dct:type

-

(prov:Attribution)

 rdfs:Class See and controlled vocabulary for responsible party role in .
*Metadata file identifier (O) dct:identifier

-

(dcat:CatalogRecord (O))

 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)

 prov:qualifiedAttribution

-

(dcat:CatalogRecord (O))

 prov:Attribution See .
dcat:contactPoint

-

(dcat:CatalogRecord (O))

 vcard:Kind See .
*Metadata character set (C) cnt:characterEncoding

cnt:Content

(dcat:CatalogRecord (O))

 rdfs:Literal See .

Coordinate Reference System (M)

*Reference System (0)

 dct:conformsTo

-

(dcat:Dataset

(M))

 dct:Standard See .

Temporal Reference System (C)

*Reference System (0)

 dct:conformsTo

-

(dcat:Dataset

(M))

 dct:Standard See .

Character Encoding (C)

*Dataset character set (C)

 cnt:characterEncoding

cnt:Content

(dcat:Distribution (R))

 rdfs:Literal See .

Spatial representation type – (M)

*Spatial representation type (O)

 adms:representationTechnique dcat:Distribution (R) skos:Concept See .

Controlled vocabularies

This section lists the controlled vocabularies that SHOULD be used according to the GeoDCAT-AP Core Profile and the GeoDCAT-AP Extended Profile.

Table 4: Controlled vocabularies to be used

Element(s) in INSPIRE Metadata Regulation

*ISO 19115:2003 Core Profile

 Property Controlled Vocabulary Comment

Resource language

Metadata language

(ISO 639-2)

 dct:language

Language Named Authority List [[!MDR-LANG]] operated by the Metadata Registry of the Publications Office of the EU

http://publications.europa.eu/resource/authority/language
Resource type dct:type

Register operated by the INSPIRE Registry for resource types defined in ISO 19115 [[!INSPIRE-RT]]

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

 GeoDCAT-AP Extended profile only.
Spatial data service type dct:type

Register operated by the INSPIRE Registry for service types [[!INSPIRE-SDST]]

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

 GeoDCAT-AP Extended profile only.
Topic category dct:subject

Register operated by the INSPIRE Registry for topic categories defined in ISO 19115 [[!INSPIRE-TC]]

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

 GeoDCAT-AP Extended profile only.
Keyword denoting one of the INSPIRE spatial data themes dcat:theme

INSPIRE spatial data theme register operated by the INSPIRE Registry [[!INSPIRE-THEMES]]

http://inspire.ec.europa.eu/theme
MDR Data Themes dcat:theme

Data Theme Named Authority List [[!MDR-THEMES]] operated by the Metadata Registry of the Publications Office of the EU

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

 Required for compliance with [[DCAT-AP]]. See for more details.
Keyword denoting one of the spatial data service categories dct:type

Register operated by the INSPIRE Registry for spatial data service categories defined in ISO 19119 [[!INSPIRE-SDSC]]

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

 GeoDCAT-AP Extended profile only.
Conformity degree dct:type

Register operated by the INSPIRE Registry for degrees of conformity [[!INSPIRE-DoC]]

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

 GeoDCAT-AP Extended profile only.
Responsible party role dct:type

Register operated by the INSPIRE Registry for responsible party roles [[!INSPIRE-RPR]]

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

 GeoDCAT-AP Extended profile only.
Encoding dct:format

File type Named Authority List [[!MDR-FT]] operated by the Metadata Registry of the Publications Office of the EU

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

For formats not (yet) included into [[!MDR-FT]], the media type register for datasets in INSPIRE download services is to be used [[!INSPIRE-MT]].

http://inspire.ec.europa.eu/media-types

 GeoDCAT-AP Extended profile only
Character encoding - *Character sets cnt:characterEncoding

Register of Character Sets operated by IANA [[!CHARSETS]].

http://www.iana.org/assignments/character-sets/

See mapping table in .

GeoDCAT-AP Extended profile only.
Coordinate reference system dct:conformsTo

Register of coordinate reference systems included in the European Petroleum Survey Group (EPSG) Geodetic Parameter Dataset [[!OGC-EPSG]].

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

http://www.epsg-registry.org/

 GeoDCAT-AP Extended profile only.
Spatial representation types adms:representationTechnique The ISO 19115 code list of spatial representation types might be in the future available as a URI register from the INSPIRE Registry.

See mapping table in .

GeoDCAT-AP Extended profile only.
Maintenance frequency dct:accrualPeriodicity

MDR Frequency Named Authority List [[!MDR-FREQ]].

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

 See mapping table in .
For the frequency codes not covered by the MDR Frequency code list, GeoDCAT-AP will use the code list of ISO maintenance frequency codes operated by the INSPIRE Registry. GeoDCAT-AP Extended profile only
Geographic identifier dct:spatial

The continents, countries and places Named Authority Lists operated by the Metadata Registry of the Publications Office of the EU [[!MDR-CONT]], [[!MDR-COUNTRIES]], [[!MDR-PLACES]].

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

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

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

The geonames URI sets [[?GEONAMES]].

http://www.geonames.org/

 The MDR 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 SHOULD be used.

Other controlled vocabularies can be used in addition to those mentioned above. For example, the working group has identified the following vocabularies:

Acknowledgements

This work was elaborated by a Working Group under the ISA programme. The Working Group was chaired by Andrea Perego from the Joint Research Centre of the European Commission. The ISA Programme of the European Commission was represented by Vassilios Peristeras and Athanasios Karalopoulos. Andrea Perego and Stijn Goedertier were the editors of the specification.

A special acknowledgement is due to Antonio Rotundo, from Agenzia per l’Italia Digitale, who contributed a study comparing INSPIRE and ISO 19115-1:2014, included in annex to this specification.

The following table lists all the people who contributed to the development and revision of this specification, either as members of the GeoDCAT-AP Working Group or as external reviewers.

Name Organisation Data portal / project Country
Adrià Mercader OKFN CKAN UK
Aleš Veršič Ministry of Public Administration geoportal.gov.si SI
Alessio Dragoni SCIAMlab dati.minambiente.it IT
Ana Fernández de Soria PwC EU Services SEMIC project EU
Anastasia Dimou iMinds / Ghent University BE
Anders Friis­-Christensen European Commission - Joint Research Centre JRC Data Catalogue EU
Andrea Perego European Commission - Joint Research Centre JRC Data Catalogue, INSPIRE Geoportal EU
Angelos Tzotsos IMIS Athena Research Centre data.gov.gr and geodata.gov.gr EL
Anja Loddenkemper Landesamt für Geoinformation und Landesvermessung Niedersachsen (LGLN) Spatial Data Infrastructure Lower Saxony DE
Antoine Isaac Vrije Universiteit Europeana NL
Antonio Rotundo Agenzia per l’Italia Digitale Repertorio Nazionale dei Dati Territoriali (RNDT): www.rndt.gov.it IT
Armin Retterath

Zentrale Stelle Geodateninfrastruktur

Rheinland-Pfalz

 geoportal.rlp.de DE
Athanasios Karalopoulos European Commission ISA Programme EU
Bert Van Nuffelen Tenforce Open Data Support project EU
Chrysi Tsinaraki European Commission - Joint Research Centre JRC Data Catalogue EU
David Read Data.gov.uk data.gov.uk UK
Deirdre Lee Derilinx data.gov.ie IE
Eliane Roos Institut géographique national (IGN) geoportail.gouv.fr FR
Franks Knibbe Geodan NL
Georges Charlot GIS team of Brussels Regional Informatics Centre (BRIC) BE
Geraldine Nolf AGIV geopunt.be BE
Hannes Reuter GISCO Team at Eurostat EU
Hans Overbeek Kennis- en Exploitatiecentrum Officiële Overheidspublicaties (KOOP) data.overheid.nl NL
Ine de Visser Geonovum nationaalgeoregister.nl NL
James Passmore British Geological Survey UK
Jan Hjelmager Danish Geodata Agency DK
Jon Blower University of Reading MELODIES EU project UK
Jorgen Van den Langenbergh PwC EU Services SEMIC project EU
Kostas Patroumpas IMIS - Athena Research Center EL
Lorena Hernandez Quiroz European Commission - Joint Research Centre INSPIRE Geoportal EU
Lorenzino Vaccari European Commission - Joint Research Centre JRC Data Catalogue EU
Maik Riechert University of Reading MELODIES EU project UK
Makx Dekkers AMI Consult SEMIC project NL
Martin Seiler National Spatial Data Infrastructure www.geoportal.de DE
Matthias Palmér MetaSolutions AB SE
Michael Lutz European Commission - Joint Research Centre INSPIRE Geoportal EU
Michael Östling MetaGIS SE
Paul Smits European Commission - Joint Research Centre INSPIRE Geoportal EU
Paul van Genuchten GEOCAT GeoNetwork NL
Pedro Gonçalves Terradue IT
Piergiorgio Cipriano Sinergis IT
Pierluigi Cara Italian Civil Protection – Open data Group IT
Pieter Colpaert iMinds / Ghent University / Open Knowledge Belgium BE
Simon Cox CSIRO AU
Simon Dutkowski Fraunhofer FOKUS www.govdata.de, European Data Portal DE
Stephan Kafka Help Service Remote Sensing, Ltd. Czech national INSPIRE Geoportal CZ
Stijn Goedertier PwC EU Services SEMIC project EU
Susanne Wigard European Commission EU
Trevor Alcorn Marine Institute data.marine.ie IE
Udo Einspanier Con Terra European Data Portal DE
Willem Van Gemert Publications Office of the EU Metadata Registry EU
Wouter Schaubroeck Hewlett-Packard BE

Overview of metadata elements covered by GeoDCAT-AP

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

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

Table 5: Overview of covered metadata elements
INSPIRE Obligation ISO 19115 Core Obligation DCAT-AP GeoDCAT-AP
Metadata point of contact M Metadata point of contact M Yes
Metadata date M Metadata date stamp M Yes Yes
Metadata language M Metadata language C Yes Yes
Metadata character set C Yes
Metadata file identifier O Yes
Metadata standard name O Yes
Metadata standard version O Yes
Resource title M Dataset title M Yes Yes
Temporal reference - Date of creation / publication / last revision C Dataset reference date M Partially (creation date not included) Yes
Resource abstract M Abstract describing the dataset M Yes Yes
Resource language C Dataset language M Yes Yes
Topic category M Dataset topic category M Yes
Geographic bounding box M Geographic location of the dataset (by four coordinates or by geographic identifier) C Yes Yes
Character encoding C Dataset character set C Yes
Temporal reference - Temporal extent C Additional extent information for the dataset (vertical and temporal) O Partially (temporal extent only) Partially (temporal extent only)
Lineage M Lineage O Yes Yes
Spatial representation type M Spatial representation type O Yes
Encoding M Distribution format O Yes Yes
Spatial resolution C Spatial resolution of the dataset O Yes (but as free text)
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 Partially (only datasets, series and discovery / catalogue services) Yes
Spatial data service type M Yes
Keyword M Partially (only for datasets and dataset series) Yes
Coupled resource C 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)

Detailed usage notes and examples

This annex contains further usage notes and examples on the mappings summarised in .

Resource title - *Dataset title

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

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

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 type - *not in ISO 19115 core

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

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

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

As far as the INSPIRE notion of service is concerned, [[VOCAB-DCAT]] and [[DCAT-AP]] provide a single class, namely, dcat:Catalog, which only matches the notion of ‘discovery service’ in INSPIRE. Other services will be of type dctype:Service. Additionally, the spatial data service type can be specified by using dct:type with the corresponding code lists operated by the INSPIRE Registry. More precisely, the following URI SHOULD be used to denote services:

For the reason explained above, the core profile of GeoDCAT-AP includes only the mappings for catalogue services (i.e., dcat:Catalog), whereas the mappings of other types of services are supported only in the extended profile of GeoDCAT-AP.

Resource locator - *On-line resource

In INSPIRE, this element, quoting, “defines the link(s) to the resource and/or the link to additional information about the resource”.

For datasets, [[VOCAB-DCAT]] has a property, namely, dcat:landingPage, having exactly the same purpose. By contrast, the only property available in [[VOCAB-DCAT]] for linking a service to an online resource is foaf:homepage.

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

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

Based on this, the mappings of element “resource locator” are the following:

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

Unique resource identifier - *not in ISO 19115 core

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

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

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

Coupled resource - *not in ISO 19115 core

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

This relationship is modelled by using dct:hasPart. This mapping is supported only in the extended profile of GeoDCAT-AP.

The target dataset or series SHOULD be preferably referred to by using its unique resource identifier (as in the following example).

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

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

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

The following example assumes that the metadata language is Dutch, and the resource language is German.

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

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

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

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

Moreover, two types of keywords are allowed:

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

Topic category and keyword in datasets and dataset series

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

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

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

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

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

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

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

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

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

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

Table 6: Mappings for metadata element ‘originating controlled vocabulary’
Metadata Element Proposed mapping
Originating controlled vocabulary Title skos:ConceptScheme dct:title
Reference date creation dct:created
last revision dct:modified
publication dct:issued

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

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

At the date of publication of this specification [2015-12-23], work is under-way to define a set of harmonised mappings between the relevant vocabularies. The status of this work, and links to a machine readable representation of the mappings, is documented on the dedicated page on Joinup, available at:

https://joinup.ec.europa.eu/node/148245/

Keyword in services

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

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

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

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

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

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

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

Spatial data service type - *not in ISO 19115 core

See on resource type.

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

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

Based on that, GeoDCAT-AP models spatial coverage as follows:

Bounding box

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

  • a URI - e.g., by using the geo URI scheme (IET RFC-5870) [[?RFC5870]], or a geohash URI [[?GEOHASH]], [[?GEOHASH-36]];

  • a syntax encoding scheme - e.g., geohashes [[?GEOHASH]], [[?GEOHASH-36]], WKT [[?ISO-19125-1]], GML [[?GML]], KML [[?KML]], GeoJSON [[?GEOJSON]]; or

  • a semantic representation - using vocabularies like W3C Lat/long [[?W3C-BASIC-GEO]] or schema.org [[?SCHEMA-ORG]].

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

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

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

Geographic identifier

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

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

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

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

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

The following example shows how to specify the spatial coverage.

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

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

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

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

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

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

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

Lineage - *Lineage

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

Since the range of dct:provenance is not a literal, but class dct:ProvenanceStatement, the free-text content of element “lineage” can be expressed by using rdfs:label, as illustrated in the DCMI user guide on publishing metadata [[?DCWIKI]].

Spatial resolution – Spatial resolution of the dataset

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

There are currently no candidates in existing vocabularies to represent such metadata elements.

Based on this, GeoDCAT-AP defines a provisional mapping, representing spatial resolution in a human-readable form only, using property rdfs:comment.

Conformity and data quality - *not in ISO 19115 core

The GeoDCAT-AP specification only provides a syntax binding for conformity and not for data quality in general.

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

For encoding conformance, GeoDCAT-AP proposes to use dct:conformsTo and the W3C Provenance Ontology (PROV-O) [[PROV-O]] as explained in the following paragraphs. For encoding other aspects of data quality, GeoDCAT-AP does not provide a syntax binding as there is a risk that the (future) work of other standards bodies on data quality may make the proposed syntax binding for GeoDCAT-AP outdated. For example, the W3C Data on the Web Best Practices WG is working on a Data Quality Vocabulary (DQV) [[?VOCAB-DQV]]. To limit the impact, it was decided to only provide a partial mapping for Data Quality / Conformance.

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

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

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

Table 7: Mappings for metadata element ‘conformity’
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

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

The PROV-O-based approach might be revised in the future – but still supported for backward interoperability –, if future standard vocabularies will be able to address GeoDCAT-AP requirement.

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

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

Based on this, GeoDCAT-AP models use and access limitations by using, respectively, dct:license and dct:accessRights.

Since the range of these properties is not a literal, but, respectively, classes dct:LicenseDocument and dct:RightsStatement, the free-text content of the corresponding ISO 19115 / INSPIRE metadata elements can be expressed by using rdfs:label, as illustrated in [[?DCWIKI]].

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

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

By contrast, ISO 19115 and the INSPIRE Metadata Regulation supports 11 possible relationships between a resource (a dataset, a dataset series, a service) and an agent (organisation), plus one for metadata. For some of them, suitable candidates exist from widely used vocabularies (in particular, DCMI Metadata Terms [[DCTERMS]]). However, for some of them no suitable candidate is available in the existing vocabularies (in particular, for roles “user” and “processor”).

In the extended profile of GeoDCAT-AP, the W3C PROV ontology [[PROV-O]] is used to specify the relationship between the resource and the responsible organisation. The W3C vCard ontology [[VCARD-RDF]] will then be used to specify the contact information concerning the responsible party. Finally, the responsible party role will be specified by using dct:type, and using the relevant code list values from the INSPIRE Registry – reference register:

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

These mappings are illustrated in the following table.

Table 8: Mappings for metadata element ‘responsible party’
Metadata element Proposed mapping
Responsible party Responsible party Organisation name prov:Attribution vcard:Kind vcard:organization-name
Contact email address vcard:hasEmail
Responsible party role dct:type

This option has the advantage of preserving the semantics in the original metadata, and of preventing information loss. However, it does not rely on RDF properties used in [[DCAT-AP]].

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

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

The following table lists the GeoDCAT-AP mappings for responsible party roles, taking into account only widely used vocabularies.

Table 9: Responsible party roles
ISO 19115:2003 INSPIRE Metadata Regulation Description

Proposed RDF mapping

(where not available prov:qualifiedAttribution can be used)
Resource provider Part B §6.1 Party that supplies the resource. N/A
Custodian Part B §6.2 Party that accepts accountability and responsibility for the data and ensures appropriate care and maintenance of the resource. N/A
Owner Part B §6.3 Party that owns the resource. dct:rightsHolder
User Part B §6.4 Party who uses the resource. N/A
Distributor Part B §6.5 Party who distributes the resource N/A
Originator Part B §6.6 Party who created the resource. N/A
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 N/A
Processor Part B §6.9 Party who has processed the data in a manner such that the resource has been modified. N/A
Publisher Part B §6.10 Party who published the resource dct:publisher
Author Part B §6.11 Party who authored the resource. dct:creator

In the following example, the same organisation is both the data custodian and the metadata point of contact.

*Metadata file identifier

This element identifies a metadata record.

Metadata file identifiers are mapped to dct:identifier.

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

*Metadata standard name, *Metadata standard version

Following [[DCAT-AP]], GeoDCAT-AP uses dct:conformsTo to encode information about the metadata standard name and metadata standard version.

The metadata on metadata is encoded as a dcat:CatalogRecord.

Table 10: Metadata standard name and metadata standard version
Metadata element Proposed mapping
Metadata standard Metadata standard name dct:conformsTo dct:title
Metadata standard version owl:versionInfo

The following example shows a GeoDCAT-AP metadata record obtained from one conformant with ISO 19115.

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

*Metadata characterset

See .

Metadata point of contact - *Metadata point of contact

See .

Metadata date - *Metadata date stamp

See .

Metadata language - *Metadata language

See .

Coordinate reference systems and Temporal reference systems – *Reference System

In [[DCAT-AP]], no equivalent term is provided. This is also the case for the NeoGeo [[?NEOGEO]], GeoSPARQL [[?GeoSPARQL]], and the Core Location Vocabulary [[?LOCN]].

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Encoding - *Distribution format

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

Two properties are available:

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

In both cases, [[DCAT-AP]] recommends the use of the URI file type register [[MDR-FT]], operated by the Metadata Registry of the Publications Office of the EU, to specify formats/media types. However, this register does not include many of the formats/media types typically used for INSPIRE data – as, e.g., GML, shapefiles and raster files – which are available through the INSPIRE media type register [[INSPIRE-MT]].

The proposal is then to use the file type register of the Publications Office, if it includes the relevant format/media type, and the INSPIRE Media Types register otherwise.

Spatial representation type – *Spatial representation type

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

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

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

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

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

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

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

Maintenance information - *not in ISO 19115 core

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

[[VOCAB-DCAT]] and [[DCAT-AP]], the update frequency is expressed through dct:accrualPeriodicity, with the frequency codes defined in the Dublin Core Collection Description Frequency Vocabulary [[?CLD-FREQ]], which can be partially mapped to the ones used in ISO 19115, as shown in the following table (the missing alignments are in bold). A similar mapping was added for the MDR Frequency Named Authority List [[MDR-FREQ]].

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

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

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

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

Comparison between INSPIRE and ISO 19115-1:2014

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

Spatial dataset and spatial dataset series

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

Table 11: Metadata elements used for discovery of geographic datasets and series
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

Services

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

Table 12: Metadata elements used for discovery of service resources
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