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

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

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: <http://xmlns.com/foaf/0.1/> .
@prefix locn: <http://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: <http://www.w3.org/ns/dcat#> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix vcard: <http://www.w3.org/2006/vcard/ns#> .
@prefix xsd: <http://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 <http://data.europa.eu/930/> ;
    dct:identifier "af4c4fd6-0485-45c8-b6bc-8a8ed12aa3eb"^^xsd:string ;
    dct:language <http://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 Record 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.

Checksum

Definition: A value that allows the contents of a file to be authenticated.
Reference in DCAT-AP: Link
Usage Note: This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented.
Properties: For this entity the following properties are defined: algorithm , checksum value .

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

Data Service

Definition: A collection of operations that provides access to one or more datasets or data processing functions.
Reference in DCAT-AP: Link
Subclass of
: Catalogued Resource
Properties: For this entity the following properties are defined: access rights , applicable legislation , conforms to , contact point , creation date , creator , custodian , description , distributor , endpoint description , endpoint URL , format , geographical coverage , identifier , keyword , landing page , language , licence , modification date , orginator , principal investigator , processor , publisher , qualified attribution , reference system , release date , resource provider , rights , rights holder , serves dataset , service category , service protocol , service type , spatial resolution , spatial resolution as text , spatial resolution in metres , temporal coverage , temporal resolution , theme , title , topic category , type , 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 Data Service.		P
conforms to	Standard	0..*	An established (technical) standard to which the Data Service conforms.	The standards referred here SHOULD describe the Data Service and not the data it serves. The latter is provided by the dataset with which this Data Service is connected. For instance the data service adheres to the OGC WFS API standard, while the associated dataset adheres to the INSPIRE Address data model.	A
contact point	Kind	0..*	Contact information that can be used for sending comments about the Data Service.		A
creation date	Temporal Literal	0..1	The date on which the Data Service has been first created.		P
creator	Agent	0..*	An Agent primarily responsible for producing the Data Service.		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
description	Literal	0..*	A free-text account of the Data Service.	This property can be repeated for parallel language versions of the description.	A
distributor	Agent	0..*	Party who distributes the resource [[ISO-19115]].		P
endpoint description	Resource	0..*	A description of the services available via the end-points, including their operations, parameters etc.	The property gives specific details of the actual endpoint instances, while the property application profile (dct:conformsTo) is used to indicate the general standard or specification that the endpoints implement.	A
endpoint URL	Resource	1..*	The root location or primary endpoint of the service (an IRI).		A
format	Media Type or Extent	0..*	The structure that can be returned by querying the endpointURL.		P
geographical coverage	Location	0..*	A geographic region that is covered by the Data Service.	If the Data Service provides access to multiple Datasets, then this will be the union of the spatial coverages of these Datasets.	P
identifier	Literal	0..*	The main identifier for the Data Service, e.g. the URI or other unique identifier in the context of the Catalogue.		E
keyword	Literal	0..*	A keyword or tag describing the Data Service.		A
landing page	Document	0..*	A web page that provides access to the Data Service and/or additional information.	It is intended to point to a landing page at the original data service provider, not to a page on a site of a third party, such as an aggregator.	A
language	Linguistic system	0..*	The language of the structure that can be returned by querying the endpointURL.	This property can be repeated if multiple languages are supported in the Data Service - see § 11. Accessibility and Multilingual Aspects.	E
licence	Licence Document	0..1	A licence under which the Data service is made available.		A
modification date	Temporal Literal	0..1	The most recent date on which the Data Service was changed or modified.		A
orginator	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	0..1	An entity (organisation) responsible for making the Data Service available.		A
qualified attribution	Attribution	0..*	Link to an Agent having some form of responsibility for the Data Service.		A
reference system	Concept	0..*	The reference system used in the Data Service.	Spatial reference systems SHOULD be specified by using the corresponding URIs from the "EPSG coordinate reference systems" register operated by OGC [[OGC-EPSG]].	P
release date	Temporal Literal	0..1	The date of formal issuance (e.g., publication) of the Data Service.		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 Data Service.		A
rights holder	Agent	0..*	An Agent (organisation) holding rights on the Catalogue.		P
serves dataset	Dataset	0..*	This property refers to a collection of data that this data service can distribute.		A
service category	Concept	0..1	Service category in accordance with INSPIRE Spatial Data Service Categories [[INSPIRE-SDSC]].	The URIs of the "Classification of spatial data services" code list operated by the INSPIRE Registry [[INSPIRE-SDSC]].	P
service protocol	Concept	0..1	Protocol value in accordance with INSPIRE Protocol Values [[INSPIRE-PV]].		P
service type	Concept	0..1	Service type in accordance with INSPIRE Spatial Data Service Types [[INSPIRE-SDST]].	One of the URIs of the "Spatial Data Service Types" code list operated by the INSPIRE Registry [[INSPIRE-SDST]].	P
spatial resolution	Quality Measurement	0..*	Spatial resolution, as defined in [[INSPIRE-MD-REG]], [[ISO-19115]], and [[ISO-19115-1]].	Represents the capabilities of the data service, i.e. in which spatial resolutions it can serve the data.	P
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. Represents the capabilities of the data service, i.e. in which spatial resolutions it can serve the data.	P
spatial resolution in metres	xsd:decimal	0..*	The minimum spatial separation resolvable in a Data Service, measured in metres.	Represents the capabilities of the data service, i.e. in which spatial resolutions it can serve the data.	P
temporal coverage	Period of time	0..*	A temporal period that the Data Service covers.		P
temporal resolution	xsd:duration	0..*	The minimum time period resolvable in the Data Service.		E
theme	Concept	0..*	A category of the Data Service.	A Data Service may be associated with multiple themes.	A
title	Literal	1..*	A name given to the Data Service.	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]].	One of the URIs of the "Topic categories in accordance with EN ISO 19115" code list operated by the INSPIRE Registry [[INSPIRE-TC]].	P
type	Concept	0..1	Resource type in accordance with INSPIRE Resource Types [[INSPIRE-RT]].	URIs of the "Resource types" code list operated by the INSPIRE Registry [[INSPIRE-RT]] - namely the one corresponding to "Spatial data service".	P
user	Agent	0..*	Party who uses the resource [[ISO-19115]].		P
was used by	Activity	0..*	To an Activity that used the Data Service.	In GeoDCAT-AP, this property MAY be used to specify a testing Activity over a Data Service, against a given Standard, producing as output a conformance degree.	P

@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix geodcatap: <http://data.europa.eu/930/> .
@prefix gsp: <http://www.opengis.net/ont/geosparql#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix vcard: <http://www.w3.org/2006/vcard/ns#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

@prefix record: <https://some.catalogue/record/> .
@prefix resource: <https://some.catalogue/resource/> .

resource:eea_v_4326_250_k_wise-eionet-monitoring-sites_service a dcat:DataService ;
  geodcatap:custodian <http://publications.europa.eu/resource/authority/corporate-body/EEA> ;
  geodcatap:processor [ a foaf:Organization ;
      foaf:mbox <mailto:wisesoe.helpdesk@eionet.europa.eu> ;
      foaf:name "Tracasa"@en ] ;
  dct:accessRights <http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/noLimitations> ;
  dct:conformsTo <http://www.opengeospatial.org/standards/wms>,
    <http://www.opengis.net/def/crs/EPSG/0/102100>,
    <http://www.opengis.net/def/crs/EPSG/0/3857>,
    <http://www.opengis.net/def/crs/EPSG/0/4326>,
    <http://www.opengis.net/def/crs/OGC/1.3/CRS84> ;
  dct:description """
    The service contains information on European surface water and groundwater 
    monitoring sites reported to the European Environment Agency between 
    2001-11-29 and 2020-01-17. The information was reported to the European 
    Environment Agency under the State of Environment reporting obligations. 
    ...
  """@en ;
  dct:identifier "eea_v_4326_250_k_wise-eionet-monitoring-sites_service" ;
  dct:issued "2018-09-15"^^xsd:date ;
  dct:license <http://publications.europa.eu/resource/authority/licence/CC_BY_4_0> ;
  dct:rights [ a dct:LicenseDocument ;
      dcterms:description "No limitations in the use of this web service."@en ] ;
  dct:spatial [ a dct:Location ;
      dcat:bbox "<gml:Envelope srsName=\"http://www.opengis.net/def/crs/OGC/1.3/CRS84\"><gml:lowerCorner>-62.9951 -21.378367</gml:lowerCorner><gml:upperCorner>55.813367 70.620781</gml:upperCorner></gml:Envelope>"^^gsp:gmlLiteral,
        "POLYGON((-62.9951 70.620781,55.813367 70.620781,55.813367 -21.378367,-62.9951 -21.378367,-62.9951 70.620781))"^^gsp:wktLiteral ] ;
  dct:title "EIONET monitoring sites - Web Service"@en ;
  geodcatap:resourceType <http://inspire.ec.europa.eu/metadata-codelist/ResourceType/service>,
    <http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/view> ;
  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:info@eea.europa.eu> ;
      vcard:hasURL <http://www.eea.europa.eu> ] ;
  dcat:endpointDescription <https://water.discomap.eea.europa.eu/arcgis/rest/services/WISE_SoE/EIONET_MonitoringSite_WM/MapServer>,
    <https://water.discomap.eea.europa.eu/arcgis/services/WISE_SoE/EIONET_MonitoringSite_WM/MapServer/WMSServer?request=GetCapabilities&service=WMS> ;
  dcat:endpointURL <https://water.discomap.eea.europa.eu/arcgis/rest/services/WISE_SoE/EIONET_MonitoringSite_WM/MapServer>,
    <https://water.discomap.eea.europa.eu/arcgis/services/WISE_SoE/EIONET_MonitoringSite_WM/MapServer/WMSServer> ;
  dcat:keyword "Groundwater body"@en,
    "Monitoring Site"@en,
    "Surface water body"@en,
    "Water Information System for Europe"@en ;
  dcat:servesDataset resource:eea_v_4326_250_k_wise-eionet_p_2001-2020_v01_r04 ;
  dcat:theme <http://inspire.ec.europa.eu/theme/ef>,
    <http://www.eionet.europa.eu/gemet/concept/12301>,
    <http://www.eionet.europa.eu/gemet/concept/3780>,
    <http://www.eionet.europa.eu/gemet/concept/5352>,
    <http://www.eionet.europa.eu/gemet/concept/8229> ;
  prov:wasUsedBy [ a prov:Activity ;
      prov:generated [ a prov:Entity ;
          dct:description "See the referenced specification"@en ;
          dct:type <http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/notEvaluated> ] ;
      prov:qualifiedAssociation [ a prov:Association ;
          prov:hadPlan [ a prov:Plan ;
              prov:wasDerivedFrom <http://inspire.ec.europa.eu/id/citation/ir/reg-976-2009> ] ] ] .

Dataset

Definition: A conceptual entity that represents the information published.
Reference in DCAT-AP: Link
Usage Note: If a Dataset is used as part of a Dataset Series, the properties listed below can be used additionally, or slightly differently to those listed for the Dataset outside of a Dataset Series. For this usage, consult the usage guidelines of DCAT-AP.
Subclass of
: Catalogued Resource
Properties: For this entity the following properties are defined: access rights , applicable legislation , conforms to , contact point , creation date , creator , custodian , dataset distribution , description , distributor , documentation , frequency , geographical coverage , has version , identifier , in series , is referenced by , keyword , landing page , language , modification date , originator , other identifier , principal investigator , processor , provenance , publisher , qualified attribution , qualified relation , reference system , related resource , release date , resource provider , resource type , rights , rights holder , sample , source , spatial resolution , spatial resolution as text , spatial resolution in metres , temporal coverage , temporal resolution , theme , title , topic category , user , version , version notes , was generated by , was used by .

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

@prefix adms: <http://www.w3.org/ns/adms#> .
@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dct: <http://purl.org/dc/terms/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix geodcatap: <http://data.europa.eu/930/> .
@prefix gsp: <http://www.opengis.net/ont/geosparql#> .
@prefix locn: <http://www.w3.org/ns/locn#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix record: <https://some.catalogue/record/> .
@prefix resource: <https://some.catalogue/resource/> .
@prefix vcard: <http://www.w3.org/2006/vcard/ns#> .
@prefix xml: <http://www.w3.org/XML/1998/namespace> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

resource:eea_r_3035_10_m_noise-contours-end2017_i_2016_v01_r00 a dcat:Dataset ;
  geodcatap:custodian <http://publications.europa.eu/resource/authority/corporate-body/EEA> ;
  dct:accrualPeriodicity <http://publications.europa.eu/resource/authority/frequency/IRREG> ;
  dct:conformsTo <http://www.opengis.net/def/crs/EPSG/0/3035> ;
  dct:created "2019-10-31"^^xsd:date ;
  dct:description """
    The data set includes the rasterized noise contours which have been 
    reported by countries under the terms of the Environmental Noise 
    Directive (END) by the 33 EEA member countries (EEA-33) excluding 
    Turkey for the third round of noise mapping in 2017. The data set 
    includes submissions from the countries until 01/01/2019. 
    ...
  """@en ;
  dct:identifier "eea_r_3035_10_m_noise-contours-end2017_i_2016_v01_r00" ;
  dct:language <http://publications.europa.eu/resource/authority/language/ENG> ;
  dct:provenance [ a dct:ProvenanceStatement ;
      dct:description "The raster data sets have been created out of the Noise Spatial Database, which in turn contains all versions delivered by the relevant countries (EU and EFTA) to Reportnet (CDR). The data from Reportnet is automatically incorporated into the database, with the exception of those data sets which require a manual review (due to problems with naming conventions or Coordinate Reference System). The data set covers any submission by the countries until 01/01/2019."@en ] ;
  dct:spatial [ a dct:Location ;
      dcat:bbox "<gml:Envelope srsName=\"http://www.opengis.net/def/crs/OGC/1.3/CRS84\"><gml:lowerCorner>-31.285 27.642</gml:lowerCorner><gml:upperCorner>34.099 70.075</gml:upperCorner></gml:Envelope>"^^gsp:gmlLiteral,
        "POLYGON((-31.285 70.075,34.099 70.075,34.099 27.642,-31.285 27.642,-31.285 70.075))"^^gsp:wktLiteral ] ;
  dct:subject <http://inspire.ec.europa.eu/metadata-codelist/TopicCategory/environment>,
    <http://inspire.ec.europa.eu/metadata-codelist/TopicCategory/health>,
    <http://inspire.ec.europa.eu/metadata-codelist/TopicCategory/transportation> ;
  dct:temporal [ a dct:PeriodOfTime ;
      dcat:endDate "2016-12-31"^^xsd:date ;
      dcat:startDate "2016-01-01"^^xsd:date ] ;
  dct:title "Noise contours data reported under Environmental Noise Directive (END) 2017 (raster 10m) - version 2019, Oct. 2019"@en ;
  geodcatap:resourceType <http://inspire.ec.europa.eu/metadata-codelist/ResourceType/dataset> ;
  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:info@eea.europa.eu> ;
      vcard:hasURL <http://www.eea.europa.eu> ] ;
  dcat:distribution [ a dcat:Distribution ;
      dct:accessRights <http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/INSPIRE_Directive_Article13_1e> ;
      dct:description "NoiseContours_air_lnight"@en ;
      dct:format <http://publications.europa.eu/resource/authority/file-type/TIFF> ;
      dct:license <http://publications.europa.eu/resource/authority/licence/CC_BY_4_0> ;
      dct:rights [ a dct:LicenseDocument ;
          dct:description "The full noise contour maps data set is in principle only available for EEA internal use. A public version of the data set may in the future be available, excluding those data sets for which there is any limitation or restriction in their use (beyond acknowledgement)."@en ] ;
      adms:representationTechnique <http://inspire.ec.europa.eu/metadata-codelist/SpatialRepresentationType/grid> ;
      dcat:accessService [ a dcat:DataService ;
          dct:conformsTo <http://www.opengeospatial.org/standards/wms> ;
          dcat:endpointDescription <https://noise.discomap.eea.europa.eu/arcgis/services/noiseStoryMap/NoiseContours_air_lnight/ImageServer/WMSServer?request=GetCapabilities&service=WMS> ;
          dcat:endpointURL <https://noise.discomap.eea.europa.eu/arcgis/services/noiseStoryMap/NoiseContours_air_lnight/ImageServer/WMSServer> ] ;
      dcat:accessURL <https://noise.discomap.eea.europa.eu/arcgis/services/noiseStoryMap/NoiseContours_air_lnight/ImageServer/WMSServer?request=GetCapabilities&service=WMS> ] ;
  dcat:keyword "Environmental Noise Directive"@en,
    "Noise map"@en,
    "agglomerations"@en,
    "noise contour"@en,
    "noise source"@en ;
  dcat:spatialResolutionInMeters 10.0 ;
  dcat:theme <http://inspire.ec.europa.eu/theme/hh>,
    <http://publications.europa.eu/resource/authority/data-theme/HEAL>,
    <http://www.eionet.europa.eu/gemet/concept/2884> ;
  prov:wasUsedBy [ a prov:Activity ;
      prov:generated [ a prov:Entity ;
          dct:description "See the referenced specification"@en ;
          dct:type <http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/notEvaluated> ] ;
      prov:qualifiedAssociation [ a prov:Association ;
          prov:hadPlan [ a prov:Plan ;
              prov:wasDerivedFrom <http://data.europa.eu/eli/reg/2010/1089> ] ] ] ;
  foaf:isPrimaryTopicOf record:e7807ecb-a8e6-4a33-baa2-d119eec9ce24 ;
  foaf:page <https://noise.eea.europa.eu/> .

Dataset Series

Definition: A collection of datasets that are published separately,but share some characteristics that group them.
Reference in DCAT-AP: Link
Usage Note: It is recommended to avoid Dataset Series without a dataset in the collection. Therefore at least one Dataset should refer to a Dataset Series using the property in series (dcat:inSeries).
Subclass of
: Dataset
Properties: For this entity the following properties are defined: access rights , applicable legislation , conforms to , contact point , creation date , creator , custodian , dataset series distribution , description , distributor , documentation , frequency , geographical coverage , has version , identifier , in series , is referenced by , keyword , landing page , language , modification date , originator , other identifier , principal investigator , processor , publisher , qualified attribution , qualified relation , reference system , related resource , release date , resource provider , resource type , rights , rights holder , sample , source , spatial resolution , spatial resolution as text , spatial resolution in metres , temporal coverage , theme , title , topic category , user , version , version notes , was generated by , was used by .

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

Distribution

Definition: A physical embodiment of the Dataset in a particular format.
Reference in DCAT-AP: Link
Properties: For this entity the following properties are defined: access rights , access service , access URL , applicable legislation , availability , byte size , character encoding , checksum , compression format , description , documentation , download URL , format , has policy , language , licence , linked schemas , media type , modification date , packaging format , reference system , release date , representation technique , rights , spatial resolution , spatial resolution as text , spatial resolution in metres , status , temporal resolution , title .

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

@prefix adms: <http://www.w3.org/ns/adms#> .
@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dct: <http://purl.org/dc/terms/> .

[] a dcat:Distribution ;
  dct:accessRights <http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/INSPIRE_Directive_Article13_1e> ;
  dct:description "NoiseContours_air_lnight"@en ;
  dct:format <http://publications.europa.eu/resource/authority/file-type/TIFF> ;
  dct:license <http://publications.europa.eu/resource/authority/licence/CC_BY_4_0> ;
  dct:rights [ a dct:LicenseDocument ;
      dct:description "The full noise contour maps data set is in principle only available for EEA internal use. A public version of the data set may in the future be available, excluding those data sets for which there is any limitation or restriction in their use (beyond acknowledgement)."@en ] ;
  adms:representationTechnique <http://inspire.ec.europa.eu/metadata-codelist/SpatialRepresentationType/grid> ;
  dcat:accessService [ a dcat:DataService ;
      dct:conformsTo <http://www.opengeospatial.org/standards/wms> ;
      dcat:endpointDescription <https://noise.discomap.eea.europa.eu/arcgis/services/noiseStoryMap/NoiseContours_air_lnight/ImageServer/WMSServer?request=GetCapabilities&service=WMS> ;
      dcat:endpointURL <https://noise.discomap.eea.europa.eu/arcgis/services/noiseStoryMap/NoiseContours_air_lnight/ImageServer/WMSServer> ] ;
  dcat:accessURL <https://noise.discomap.eea.europa.eu/arcgis/services/noiseStoryMap/NoiseContours_air_lnight/ImageServer/WMSServer?request=GetCapabilities&service=WMS> .

Kind

Definition: A description following the vCard specification,e.g. to provide telephone number and e-mail address for a contact point.
Reference in DCAT-AP: Link
Usage Note: Note that the class Kind is the parent class for the four explicit types of vCard (Individual, Organization, Location, Group).
Properties: For this entity the following properties are defined: address , affiliation , email , name , phone , URL .

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

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix vcard: <http://www.w3.org/2006/vcard/ns#> .
@prefix xml: <http://www.w3.org/XML/1998/namespace> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

[] 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> ;
  vcard:hasTelephone <tel:+451234567890> .

Licence Document

Definition: A legal document giving official permission to do something with a resource.
Reference in DCAT-AP: Link
Properties: For this entity the following properties are defined: type .

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

Location

Definition: A spatial region or named place.
Reference in DCAT-AP: Link
Usage Note: It can be represented using a controlled vocabulary or with geographic coordinates. In the latter case, the use of the Core Location Vocabulary is recommended, following the approach described in the GeoDCAT-AP specification.
Properties: For this entity the following properties are defined: bbox , centroid , gazetteer , geograhic identifier , geograhic name , geometry .

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

@prefix dct: <http://purl.org/dc/terms/> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

[] a dct:Location,
    skos:Concept ;
  dct:identifier "202" ;
  skos:inScheme [ a skos:ConceptScheme ;
      dct:issued "2018-11-16T00:01:27+01:00"^^xsd:dateTime ;
      dct:title "UNSD - Methodology - Standard country or area codes for statistical use (M49)"@en ] ;
  skos:prefLabel "Sub-Saharan Africa"@en .

  @prefix dcat: <http://www.w3.org/ns/dcat#> .
  @prefix dct: <http://purl.org/dc/terms/> .
  @prefix gsp: <http://www.opengis.net/ont/geosparql#> .
  
  [] a dct:Location ;
    dcat:bbox "<gml:Envelope srsName=\"http://www.opengis.net/def/crs/OGC/1.3/CRS84\"><gml:lowerCorner>-62.9951 -21.378367</gml:lowerCorner><gml:upperCorner>55.813367 70.620781</gml:upperCorner></gml:Envelope>"^^gsp:gmlLiteral,
      "POLYGON((-62.9951 70.620781,55.813367 70.620781,55.813367 -21.378367,-62.9951 -21.378367,-62.9951 70.620781))"^^gsp:wktLiteral .

Relationship

Definition: An association class for attaching additional information to a relationship between DCAT Resources.
Reference in DCAT-AP: Link
Properties: For this entity the following properties are defined: had role , relation .

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 area	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
city	Literal	0..1	A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.	P
country	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
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]]	http://inspire.ec.europa.eu/metadata-codelist/SpatialRepresentationType	GeoDCAT-AP extension.	AT-LEAST
`adms:status`	Distribution	Distribution Status Vocabulary [[EUV-DISTS]]	http://publications.europa.eu/resource/authority/distribution-status	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
`dcat:hadRole`	Attribution	INSPIRE Responsible Party Roles [[INSPIRE-RPR]]	http://inspire.ec.europa.eu/metadata-codelist/ResponsiblePartyRole	GeoDCAT-AP extension.	AT-LEAST
`dcat:mediaType`	Distribution	IANA Media Types [[IANA-MEDIA-TYPES]]	http://www.iana.org/assignments/media-types	Inherited from DCAT [[vocab-dcat-3]]	MUST
`dcat:compressFormat`	Distribution	IANA Media Types [[IANA-MEDIA-TYPES]]	http://www.iana.org/assignments/media-types	Inherited from DCAT [[vocab-dcat-3]]	MUST
`dcat:packageFormat`	Distribution	IANA Media Types [[IANA-MEDIA-TYPES]]	http://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]]	http://publications.europa.eu/resource/authority/data-theme	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
INSPIRE Spatial Data Themes [[INSPIRE-THEMES]]	http://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]]	http://publications.europa.eu/resource/authority/access-right	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
INSPIRE Limitations on Public Access [[?INSPIRE-LPA]]	http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess	GeoDCAT-AP extension.	MAY
`dct:accrualPeriodicity`	Dataset Dataset Series	EU Vocabularies Frequency Named Authority List [[EUV-FREQ]]	http://publications.europa.eu/resource/authority/frequency	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
INSPIRE Maintenance Frequency [[INSPIRE-MF]]	http://inspire.ec.europa.eu/metadata-codelist/MaintenanceFrequency	GeoDCAT-AP extension.	MAY
`dct:format`	Distribution	EU Vocabularies File Type Named Authority List [[EUV-FT]]	http://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]]	http://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]]	http://publications.europa.eu/resource/authority/corporate-body	The Corporate bodies NAL MUST be used for European institutions and a small set of international organisations. In case of other types of organisations, national, regional or local vocabularies should be used.	MAY
`geodcatap:referenceSystem`	Data Service Dataset Dataset Series Distribution	OGC EPSG Coordinate Reference Systems Register [[OGC-EPSG]]	http://www.opengis.net/def/crs/EPSG/0/	Defined by GeoDCAT-AP	MUST
`geodcatap:resourceType`	Dataset Dataset Series Data Service	INSPIRE Resource Types [[INSPIRE-RT]]	http://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]]	http://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]]	http://publications.europa.eu/resource/authority/country
EU Vocabularies Places Named Authority List [[EUV-PLACES]]	http://publications.europa.eu/resource/authority/place
[[GEONAMES]]	http://sws.geonames.org/
`geodcatap:serviceCategory`	Data Service	INSPIRE Spatial Data Service Categories [[INSPIRE-SDSC]]	http://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]]	http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType	GeoDCAT-AP extension.	MUST
`geodcatap:topicCategory`	Catalogue Data Service Dataset Dataset Series	INSPIRE Topic Categories [[INSPIRE-TC]]	http://inspire.ec.europa.eu/metadata-codelist/TopicCategory	GeoDCAT-AP extension.	MUST
`dct:type`	Agent	ADMS publisher type [[ADMS-SKOS]] vocabulary	http://purl.org/adms/publishertype/	Inherited from DCAT-AP [[DCAT-AP-3]]	MUST
`dct:type`	Licence Document	ADMS licence type [[ADMS-SKOS]] vocabulary	http://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]]	http://www.qudt.org/vocab/unit	GeoDCAT-AP extension.	AT-LEAST

INSPIRE and ISO 19115 Mappings

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

To provide an RDF syntax binding for the union of the elements in the INSPIRE metadata schema [[INSPIRE-MD-REG]], [[INSPIRE-MD]] and the core profile of ISO 19115:2003 [[ISO-19115]]. The guiding design principle is to make the resulting RDF syntax as simple as possible; thereby maximally using existing RDF vocabularies – such as the Dublin Core [[DCTERMS]] and [[DCAT-AP-3]] –, and as much as possible avoiding minting new terms. The defined syntax binding must enable the conversion of metadata records from ISO 19115 / INSPIRE to a harmonised RDF representation. The ability to convert metadata records from RDF to ISO 19115 / INSPIRE is not a requirement.
To update the reference XSLT implementation [[GeoDCAT-XSLT]] of the mappings defined in the GeoDCAT-AP specification.
To take into account and refer to alignment of relevant controlled vocabularies (e.g., the alignments between GEMET, INSPIRE themes, EuroVoc carried out by the Publications Office of the EU [[EUV-EUROVOC]]).

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

To define new controlled vocabularies or define mappings between controlled vocabularies.
To define an RDF syntax binding for the elements in ISO 19115-1:2014 [[?ISO-19115-1]].

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

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

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

Supported tooling

To support the transformation from INSPIRE metadata to GeoDCAT-AP compliant metadata an XSLT tool was developed. This tool has been updated to transform data to be compliant with GeoDCAT-AP 3.0.0. The GeoDCAT-AP XSLT can be found on the dev branch of the GitHub repository. The XSLT can be run directly on the output of a CSW or on single metadata records, by using any of the programming languages supporting XSLT conversion. Additionally, a proof-of-concept API has been developed to facilitate the testing of the XSLT on single metadata records or on top of a CSW endpoint.

Methodology and summary of results

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

Definition of alignment criteria and requirements.
Identification of the metadata elements to be covered by GeoDCAT-AP.
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 overall objective of GeoDCAT-AP is twofold:

Provide a [[DCAT-AP-3]]-conformant representation of geospatial metadata.
Provide an as much as possible comprehensive RDF-based representation of geospatial metadata, based on widely used vocabularies, trying, at the same time, to avoid semantic loss and to promote cross-domain re-use.
Ensure backward compatibiliy with previous versions of GeoDCAT-AP.

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

Note that point (1) implies that:

GeoDCAT-AP must include, at least, all the mandatory [[DCAT-AP-3]] elements.
Vocabularies different from [[DCAT-AP-3]] can be used only for those geospatial metadata elements not supported in [[DCAT-AP-3]].

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.

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 MAY be excluded.

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

All the metadata elements in the core profile of [[ISO-19115]].
All the metadata elements defined in INSPIRE, with the exclusion of those not common to all the INSPIRE spatial data themes.

More precisely, the supported INSPIRE metadata elements include:

The set of metadata elements defined in the INSPIRE Metadata Regulation [[?INSPIRE-MD-REG]].
The set of metadata elements defined in the INSPIRE Data and Services Regulation (Article 13: “Metadata required for Interoperability”) [[INSPIRE-SDSS-REG]]. These elements are also listed in Appendix C.3 to the INSPIRE Metadata Technical Guidelines (version 2.2.0) [[INSPIRE-MD]].
The set of metadata elements recommended as common to most of the INSPIRE spatial data themes in the INSPIRE Data Specifications Technical Guidelines, and listed in the first table included in Appendix C.7 to the INSPIRE Metadata Technical Guidelines (version 2.2.0) [[INSPIRE-MD]]. These elements are the following ones:
- Maintenance information.
- Conceptual and domain consistency (Data quality – Logical consistency).

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

The metadata elements not supported in the current version of GeoDCAT-AP are those recommended only for specific INSPIRE spatial data themes in the INSPIRE Data Specifications Technical Guidelines, and listed in Appendix C.7 to the INSPIRE Metadata Technical Guidelines (version 2.2.0) [[INSPIRE-MD]].

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

The priority was to support all those elements relevant to any dataset.
These elements are all optional.

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

Alignments defined in GeoDCAT-AP

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

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

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

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

Backward compatibility with [[GeoDCAT-AP-20201223]] is ensured: The revised mappings have been deprecated, but maintained in the mapping rules implemented in [[GeoDCAT-XSLT]] along with the new one, in the extended mapping profile of GeoDCAT-AP, and their support has been included in .
Compliance with [[DCAT-AP-3]] is ensured: The geospatial metadata elements covered by the defined mappings include all those that in [[DCAT-AP-3]] are mandatory, plus a subset of those that are recommended and optional.
GeoDCAT-AP offers alignments for all the metadata elements illustrated in , by using existing vocabularies, and without defining new terms.

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

Partial mappings: For some metadata elements, only a partial mapping is available. This concerns data quality and maintenance information, for which only the mandatory components have been mapped (for more details, see and , respectively). This decision was taken because existing vocabularies did not offer the ability to represent all the components of these metadata elements.

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

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

Overview of bindings for GeoDCAT-AP Core

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

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

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

INSPIRE metadata *ISO 19115:2003 Core Profile	DCAT-AP Property	Domain	Range	Comments
Resource title (M) *Dataset title (M)	`dct:title` (M)	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`rdfs:Literal`	See
Resource abstract (M) *Abstract describing the dataset (M)	`dct:description` (M)	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`rdfs:Literal`	See
Resource type (M) *not in ISO 19115 core	`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)				See . The defined encoding depends whether the resource is a service or a dataset or data series. Also, the value of the function code (`CI_OnlineFunctionCode`) is to be taken into account.
For services	`foaf:homepage` `dcat:endpointURL` `dcat:endpointDescription`	`dcat:Catalog` `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 data series (function code not provided)	`dcat:landingPage` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`foaf:Document`	See .
For dataset and data 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 data series (‘information’ function code)	`foaf:page`	`dcat:Dataset` `dcat:DatasetSeries`	`foaf:Document`	See .
For dataset and data 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 data 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 data series (‘search’ function code)	`foaf:page`	`dcat:Dataset` `dcat:DatasetSeries`	`foaf:Document`	See .
Unique resource identifier (M) *not in ISO 19115 core	`dct:identifier` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`rdfs:Literal`	See . In RDF, this could also be represented as the URI of the dataseti or of the dataset series.
Resource language (C) *Dataset language (M)	`dct:language` (O for `dcat:Dataset` and `dcat:DatasetSeries`, R for `dcat:Catalog`)	`dcat:Dataset` `dcat:DatasetSeries` `dcat:Catalog`	`dct:LinguisticSystem`	See .
Keyword value (M) *not in ISO 19115 core	`dcat:keyword` (R) `dcat:theme` (R) (see also binding for GeoDCAT-AP Extended)	`dcat:Dataset`	`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:Catalog` `dcat:Dataset` `dcat:DatasetSeries`	`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` `dcat:DatasetSeries`	`dct:PeriodOfTime`	See .
Date of publication (C) *Dataset reference date (M) – publication	`dct:issued` (R for `dcat:Catalog` and O for `dcat:Dataset` and `dcat:DatasetSeries`)	`dcat:Dataset` `dcat:DatasetSeries` `dcat:Catalog`	`Temporal Literal`	See .
Date of last revision (C) *Dataset reference date (M) – revision	`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 of the dataset (O)	`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)	`dct:provenance` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`dct:ProvenanceStatement`	See .
Conformity (M) *not in ISO 19115 core	`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) *not in ISO 19115 core	`dct:title` (R) `dct:issued` (R) `dct:modified` (O) `dct:created` (O) (see also binding for GeoDCAT-AP Extended)	`rdfs:Resource`	`Temporal Literal`	See .
Conditions for access and use (M) *not in ISO 19115 core	`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) *not in ISO 19115 core	`dct:accessRights` (O)	`dcat:DataService`	`dct:RightsStatement`	See .
Responsible party (M) *Dataset responsible party (O)	`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]].
Responsible party (M) *Dataset responsible party (O)	`dct:publisher` (R) `dcat:contactPoint` (R) `dct:creator` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`foaf:Agent` `vcard:Kind` `foaf:Agent`
Encoding (M) *Distribution format (O)	`dct:format` (R), `dcat:mediaType` (O)	`dcat:Distribution`	`dct:MediaTypeOrExtent`	See . See controlled vocabularies for encoding in .
Maintenance information (R) *not in ISO 19115 core	`dct:accrualPeriodicity` (O)	`dcat:Dataset` `dcat:DatasetSeries`	`dct:Frequency`	See .
*Metadata standard	`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.
*Metadata standard name (O)	`dct:title`	`dct:Standard`	`rdfs:Literal`	See .
*Metadata standard version (O)	`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)	`dct:modified` (M)	`dcat:CatalogRecord`	`Temporal Literal`	See .
Metadata language (M) *Metadata language (C)	`dct:language` (O)	`dcat:CatalogRecord`	`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 mapping profile covers elements defined in INSPIRE and the core profile of [[ISO-19115]], for which [[DCAT-AP-3]] does not provide a syntax binding. GeoDCAT-AP Extended is a superset of GeoDCAT-AP Core.

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

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

Partial coverage by a [[DCAT-AP-3]] binding: This concerns conformity (only degree of conformity equal to “conformant” is supported) and responsible organisation (only responsible party roles creator, publisher, and point of contact are supported).
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-3]].

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

INSPIRE metadata *ISO 19115:2003 Core Profile	Property	Domain	Range	Comments
Resource type (M) *not in ISO 19115 core	`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) *not in ISO 19115 core	`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)	`dct:language`	`dcat:DatasetSeries` `dcat:DataService`	`dct:LinguisticSystem`	See .
Topic category (M) *Dataset topic category (M)	`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) *not in ISO 19115	`geodcatap:serviceType`	`dcat:DataService`	`skos:Concept`	See . See controlled vocabulary for spatial data service type in .
Keyword value (M) *not in ISO 19115 core	`dcat:keyword` `dcat:theme` `geodcatap:serviceCategory`	`dcat:Catalog` `dcat:DatasetSeries` `dcat:DataService`	`rdfs:Literal` `skos:Concept`	See .
Originating controlled vocabulary (C) *not in ISO 19115 core	`skos:inScheme`	`skos:Concept`	`skos:ConceptScheme`	See .
Geographic bounding box (M) *Geographic location of the dataset (by four coordinates or by geographic identifier) (C)	`dct:spatial` (O)	`dcat:DataService`	`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:Catalog` `dcat:DataService`	`dct:PeriodOfTime`	See .
Date of publication (C) *Dataset reference date (M) – publication	`dct:issued`	`dcat:DataService`	Temporal Literal	See .
Date of last revision (C) *Dataset reference date (M) – revision	`dct:modified`	`dcat:DataService`	Temporal Literal	See .
Date of creation (C) *Dataset reference date (M) - creation	`dct:created`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	Temporal Literal	See .
Spatial resolution (C) *Spatial resolution of the dataset (O)	`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`	`dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`rdfs:Literal`
Conformity (M) *not in ISO 19115 core	`prov:wasUsedBy`	`prov:Entity` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService`	`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.
Limitations on public access (C) *not in ISO 19115 core	`dct:accessRights` (O), `dct:rights` (O)	`dcat:Catalog` `dcat:Distribution` `dcat:DataService`	`dct:RightsStatement`	See .
Responsible party (M) *Dataset responsible party (O)	`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)	`dcat:hadRole`	`prov:Attribution`	`dcat:Role`	See and controlled vocabulary for responsible party role in .
*Metadata file identifier (O)	`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)	`dcat:contactPoint`	`dcat:CatalogRecord`	`vcard:Kind`	See .
	`prov:qualifiedAttribution`	`dcat:CatalogRecord`	`prov:Attribution`	See .
*Metadata character set (C)	-	-	-	Metadata in GeoDCAT-AP are always in UTF-8. See .
Coordinate Reference System (M) *Reference System (0)	`geodcatap:referenceSystem`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService` `dcat:Distribution`	`skos:Concept`	See .
Temporal Reference System (C) *Reference System (0)	`geodcatap:referenceSystem`	`dcat:Catalog` `dcat:Dataset` `dcat:DatasetSeries` `dcat:DataService` `dcat:Distribution`	`skos:Concept`	See .
Character Encoding (C) *Dataset character set (C)	`cnt:characterEncoding`	`dcat:Distribution`	`rdfs:Literal`	See .
Spatial representation type – (M) *Spatial representation type (O)	`adms:representationTechnique`	`dcat:Distribution`	`skos:Concept`	See .

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-3]] 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-3]] correspond to those defined in GeoDCAT-AP core, whereas those covered only by GeoDCAT-AP correspond to those defined in the GeoDCAT-AP extended.

INSPIRE	Obligation	ISO 19115 Core	Obligation	DCAT-AP	GeoDCAT-AP
Metadata point of contact	M	Metadata point of contact	M		Yes
Metadata date	M	Metadata date stamp	M	Yes	Yes
Metadata language	M	Metadata language	C	Yes	Yes
		Metadata character set	C		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)

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 metadata in GeoDCAT-AP:

[] dct:title "Forest / Non-Forest Map 2006"@en.

Resource metadata in ISO 19139:

<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:citation>
        <gmd:CI_Citation>
          <gmd:title>
            <gco:CharacterString>
              Forest / Non-Forest Map 2006
            </gco:CharacterString>
          </gmd:title>
        </gmd:CI_Citation>
      </gmd:citation>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

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.

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>

Resource type - *not in ISO 19115 core

[[VOCAB-DCAT-3]] and [[DCAT-AP-3]] provide specific classes that can be used to represent the INSPIRE notions of dataset, dataset series, and service, namely, dcat:Dataset, dcat:DatasetSeries, and dcat:DataService.

In order to explicitly indicate the correspondence with the relevant INSPIRE resource types, following the work on aligning INSPIRE Metadata and Dublin Core [[?INSPIRE-DC]], in the extended mapping profile of GeoDCAT-AP they will be denoted by using the resource type code list operated by the INSPIRE Registry [[INSPIRE-RT]], and by using geodcatap:resourceType. More precisely, the following URIs SHOULD be used to denote, respectively, dataset, series, and services:

Additionally, the spatial data service type can be specified by using geodcatap:serviceType with the corresponding code lists operated by the INSPIRE Registry [[INSPIRE-SDST]].

Resource metadata in GeoDCAT-AP:

# Resource type for datasets
[] a dcat:Dataset;
  geodcatap:resourceType <http://inspire.ec.europa.eu/metadata-codelist/ResourceType/dataset> .

## Resource type for series
[] a dcat:DatasetSeries;
  geodcatap:resourceType <http://inspire.ec.europa.eu/metadata-codelist/ResourceType/series> .

## Resource type for services (here, a view service)
[] a dcat:DataService;
  geodcatap:resourceType <http://inspire.ec.europa.eu/metadata-codelist/ResourceType/service> .
  geodcatap:serviceType <http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/view> .

Resource metadata in ISO 19139:

<!-- MD_ScopeCode for a dataset in ISO 19139 -->
<gmd:MD_Metadata>
  ...
  <gmd:hierarchyLevel>
    <gmd:MD_ScopeCode
      codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_ScopeCode"
      codeListValue="dataset">
      dataset
    </gmd:MD_ScopeCode>
  </gmd:hierarchyLevel>
  ...
</gmd:MD_Metadata>

<!-- MD_ScopeCode for a data series in ISO 19139 -->
<gmd:MD_Metadata>
  ...
  <gmd:hierarchyLevel>
    <gmd:MD_ScopeCode
      codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_ScopeCode"
      codeListValue="series">
      series
    </gmd:MD_ScopeCode>
  </gmd:hierarchyLevel>
  ...
</gmd:MD_Metadata>

<!-- MD_ScopeCode for a service in ISO 19139 -->
<gmd:MD_Metadata>
  ...
  <gmd:hierarchyLevel>
    <gmd:MD_ScopeCode
      codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_ScopeCode"
      codeListValue="service">
      service
    </gmd:MD_ScopeCode>
  </gmd:hierarchyLevel>
  ...
  <srv:SV_ServiceIdentification>
    ...
    <srv:serviceType>
      <gco:LocalName>view</gco:LocalName>
    </srv:serviceType>
    ...
  </srv:SV_ServiceIdentification>
  ...
</gmd:MD_Metadata>

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. [[VOCAB-DCAT-3]] has a property, namely, dcat:landingPage, having exactly the same purpose.

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

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

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

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

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

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

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

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

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

Resource metadata in GeoDCAT-AP:

## Resource locator for datasets and series
[] a dcat:Dataset;
  foaf:page <http://forest.jrc.ec.europa.eu/forestmap-download> .

## Resource locator for services
[] a dcat:DataService;
  dcat:endpointDescription <http://geohub.jrc.ec.europa.eu/efas_cc?service=WMS&request=GetCapabilities> ;
  dcat:endpointURL <http://geohub.jrc.ec.europa.eu/efas_cc> ; 
  dcat:accessURL <http://geohub.jrc.ec.europa.eu/efas_cc> ; 
  geodcatap:serviceProtocol <http://www.opengeospatial.org/standards/wms> ; 
.

Resource metadata in ISO 19139 for datasets:

<gmd:MD_Metadata>
  ...
  <gmd:transferOptions>
    <gmd:MD_DigitalTransferOptions>
      <gmd:onLine>
        <gmd:CI_OnlineResource>
          <gmd:linkage>
            <gmd:URL>http://forest.jrc.ec.europa.eu/forestmap-download</gmd:URL>
          </gmd:linkage>
          <gmd:name>
            <gco:CharacterString> … </gco:CharacterString>
          </gmd:name>
          <gmd:description>
            <gco:CharacterString> … </gco:CharacterString>
          </gmd:description>
          <gmd:function>
            <CI_OnLineFunctionCode
              codeListValue="information"
              codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode"
              xmlns="http://www.isotc211.org/2005/gmd"/>
          </gmd:function>
        </gmd:CI_OnlineResource>
      </gmd:onLine>
    </gmd:MD_DigitalTransferOptions>
  </gmd:transferOptions>
  ...
</gmd:MD_Metadata>

Resource locator in ISO 19139 for services:

<gmd:MD_Metadata>
  ...
  <gmd:distributionInfo>
    <gmd:MD_Distribution>
      ...
      <gmd:transferOptions>
        <gmd:MD_DigitalTransferOptions>
          <gmd:onLine>
            <gmd:CI_OnlineResource>
              ...
              <gmd:linkage>
                <gmd:URL>http://geohub.jrc.ec.europa.eu/efas_cc?service=WMS&request=GetCapabilities</gmd:URL>
              </gmd:linkage>
              <gmd:protocol>
                <gco:CharacterString>OGC:WMS</gco:CharacterString>
              </gmd:protocol>
              <gmd:function>
                <CI_OnLineFunctionCode
                  codeListValue="information"
                  codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_OnLineFunctionCode"
                  xmlns="http://www.isotc211.org/2005/gmd"/>
              </gmd:function>
              ...
            </gmd:CI_OnlineResource>
          </gmd:onLine>
        </gmd:MD_DigitalTransferOptions>
      </gmd:transferOptions>
    </gmd:MD_Distribution>
  </gmd:distributionInfo>
  ...
</gmd:MD_Metadata>

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-3]], unique resource identifiers are mapped to dct:identifier (see ). 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.

Resource metadata in GeoDCAT-AP:

[] dct:identifier "1234567890"^^xsd:string .

Resource metadata in ISO 19139

<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      ...
      <gmd:identifier>
        <gmd:MD_Identifier>
          <gmd:code>
            <gco:CharacterString>1234567890</gco:CharacterString>
          </gmd:code>
        </gmd:MD_Identifier>
      </gmd:identifier>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

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

Resource metadata in GeoDCAT-AP

<https://some.catalogue/resource/1234567890>
  dct:identifier "https://some.catalogue/resource/1234567890"^^xsd:anyURI .

Resource metadata in ISO 19139

<!-- Unique resource identifier specified only with code -->
<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      ...
      <gmd:identifier>
        <gmd:MD_Identifier>
          <gmd:code>
            <gco:CharacterString>
              https://some.catalogue/resource/1234567890
            </gco:CharacterString>
          </gmd:code>
        </gmd:MD_Identifier>
      </gmd:identifier>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

<!-- Unique resource identifier specified with code and namespace -->
<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      ...
      <gmd:identifier>
        <gmd:RS_Identifier>
          <gmd:code>
            <gco:CharacterString>
              1234567890
            </gco:CharacterString>
          </gmd:code>
          <gmd:codeSpace>
            <gco:CharacterString>
              https://some.catalogue/resource/
            </gco:CharacterString>
          </gmd:codeSpace>
        </gmd:RS_Identifier>
      </gmd:identifier>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

Coupled resource - *not in ISO 19115 core

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

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

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

Resource metadata in GeoDCAT-AP

[] a dcat:DataService ;
  dct:type <http://inspire.ec.europa.eu/metadata-codelist/ResourceType/service> ,
    <http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/view> ;
  dcat:servesDataset [ a dcat:Dataset ;
    dct:identifier "1234567890"^^xsd:string
  ] .

Resource metadata in ISO 19139

<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <srv:SV_ServiceIdentification>
    ...
    <srv:operatesOn>
    <!-- Coupled resource identification (either embedded or by reference) -->
    </srv:operatesOn>
    </srv:SV_ServiceIdentification>
    ...
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

<!-- Coupled resource metadata (data identification section) -->
<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      ...
      <gmd:identifier>
        <gmd:MD_Identifier>
          <gmd:code>
            <gco:CharacterString>1234567890</gco:CharacterString>
          </gmd:code>
        </gmd:MD_Identifier>
      </gmd:identifier>
    </gmd:MD_DataIdentification>
    ...
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

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-3]], both elements are specified with property dct:language, with the URI of the relevant language available from the relevant register operated by the EU Publications Office [[EUV-LANG]].

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

Resource metadata in GeoDCAT-AP

# Metadata on metadata
[] a dcat:CatalogRecord ;
  dct:language
  <http://publications.europa.eu/resource/authority/language/NLD> ;
  foaf:primaryTopic [ 
    # Resource metadata
    dct:language
      <http://publications.europa.eu/resource/authority/language/DEU> .
  ] .

Resource metadata in ISO 19139

<gmd:MD_Metadata>
  ...
<!-- Metadata on metadata: metadata language -->
  <gmd:language>
    <gmd:LanguageCode
      codeList="http://www.loc.gov/standards/iso639-2/"
      codeListValue="dut"/>
  </gmd:language>
  ...
<!-- Resource language -->
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
    ...
      <gmd:language>
        <gmd:LanguageCode
          codeList="http://www.loc.gov/standards/iso639-2/"
          codeListValue="ger"/>
      </gmd:language>
    ...
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

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):

The topic category is a high-level classification scheme to assist in the grouping and topic-based search of available spatial data resources.
The keyword value is a commonly used word, formalised word or phrase used to describe the subject. While the topic category is too coarse for detailed queries, keywords help narrowing a full text search and they allow for structured keyword search.

Moreover, two types of keywords are allowed:

free keywords;
keywords taken from a controlled vocabulary.

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

Topic category and keyword in datasets and dataset series

As far as dataset metadata are concerned, in both [[VOCAB-DCAT-3]] and [[DCAT-AP-3]], 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 geodcatap:topicCategory, 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-3]] 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 typed as a skos:Concept associated with a skos:ConceptScheme (used to type the originating controlled vocabulary), and annotated with the textual content and reference date(s) in the relevant INSPIRE metadata elements.

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

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

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

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

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.

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

Keywords from the ISO 19119 codelist of spatial data service types mapped to geodcatap:serviceType, and expressed by the corresponding URI in the INSPIRE Registry – reference register http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType;
Keywords from the ISO 19119 codelist of spatial data service categories are mapped to geodcatap:serviceCategory, and expressed by the corresponding URI in the INSPIRE Registry – reference register http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory;
Keywords not associated with a controlled vocabulary will be mapped to dcat:keyword, and represented as un-typed literals;
INSPIRE spatial data themes are mapped to dcat:theme, and expressed by the corresponding URI in the INSPIRE Registry – reference register http://inspire.ec.europa.eu/theme
Keywords associated with other controlled vocabularies are mapped to dcat:theme. If not denoted by an HTTP URI, they SHOULD be expressed as a skos:Concept associated with a skos:ConceptScheme, and annotated with the textual content and reference date(s) in the relevant INSPIRE metadata elements.

Resource metadata in GeoDCAT-AP:

## Datasets and series
[] a dcat:Dataset ;
### Free keywords
  dcat:keyword "CHM"@en, "RDSI"@en ;
### Keywords from controlled vocabularies
  dcat:theme
### Data themes Name Authority List (Environment)
    <http://publications.europa.eu/resource/authority/data-theme/ENVI> ,
### INSPIRE theme URI (land coverage)
    <http://inspire.ec.europa.eu/theme/lc> ,
### Other controlled vocabulary
    [ a skos:Concept ;
      skos:prefLabel "coniferous forest"@en ;
      skos:inScheme [ a skos:ConceptScheme ;
        dct:title "GEMET - Concepts, version 2.4"@en ;
        dct:issued "2010-01-13"^^xsd:date ] ] ;
### Topic categories
  geodcatap:topicCategory <http://inspire.ec.europa.eu/metadata-codelist/TopicCategory/geoscientificInformation> .

## Services
[] a dcat:DataService ;
### Free keywords
  dcat:keyword "hydrography"@en ;
### Keyword from ISO 19119 codelist of spatial data service categories
  geodcatap:serviceCategory <http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory/humanGeographicViewer> ;
### Keywords from controlled vocabularies
  dcat:theme <http://inspire.ec.europa.eu/theme/hy> ,
    [ a skos:Concept ;
    skos:prefLabel "Floods"@en ;
    skos:inScheme [ a skos:ConceptScheme ;
      dct:title "GEOSS - Societal Benefit Areas, version 1.0"@en ;
      dct:issued "2010-08-25"^^xsd:date ] ] .

Resource metadata in ISO 19139:

<!-- Datasets and series -->
<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
<!-- free keywords -->
      <gmd:descriptiveKeywords>
        <gmd:keyword>
          <gco:CharacterString>CHM</gco:CharacterString>
        </gmd:keyword>
        <gmd:keyword>
          <gco:CharacterString>RDSI</gco:CharacterString>
        </gmd:keyword>
      </gmd:descriptiveKeywords>
<!-- Keywords from controlled vocabularies -->
      <gmd:descriptiveKeywords>
        <gmd:keyword>
          <gco:CharacterString>coniferous forest</gco:CharacterString>
        </gmd:keyword>
        <gmd:thesaurusName>
          <gmd:CI_Citation>
            <gmd:title>
              <gco:CharacterString>GEMET - Concepts, version 2.4</gco:CharacterString>
            </gmd:title>
            <gmd:date>
              <gmd:CI_Date>
                <gmd:date>
                  <gco:Date>2010-01-13</gco:Date>
                </gmd:date>
                <gmd:dateType>
                  <gmd:CI_DateTypeCode
                    codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode"
                    codeListValue="publication">
                      publication
                    </gmd:CI_DateTypeCode>
                </gmd:dateType>
              </gmd:CI_Date>
            </gmd:date>
          </gmd:CI_Citation>
        </gmd:thesaurusName>
      </gmd:descriptiveKeywords>

<!-- Topic category -->
      <gmd:topicCategory>
        <gmd:MD_TopicCategoryCode>
          http://inspire.ec.europa.eu/metadata-codelist/TopicCategory/geoscientificInformation
        </gmd:MD_TopicCategoryCode>
      </gmd:topicCategory>
      ...
    </gmd:MD_DataIdentification>
  ...
  </gmd:identificationInfo>
</gmd:MD_Metadata>

<!-- Keywords for services -->
<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <srv:SV_ServiceIdentification>
<!-- free keywords -->
      <gmd:descriptiveKeywords>
        <gmd:keyword>
          <gco:CharacterString>hydrography</gco:CharacterString>
        </gmd:keyword>
      </gmd:descriptiveKeywords>
<!-- Keyword from ISO 19119 codelist of spatial data service categories -->
      <gmd:descriptiveKeywords>
        <gmd:keyword>
          <gco:CharacterString>humanGeographicViewer</gco:CharacterString>
        </gmd:keyword>
        <gmd:thesaurusName>
          <gmd:CI_Citation>
            <gmd:title>
              <gco:CharacterString>ISO 19119 codelist of spatial data service categories</gco:CharacterString>
            </gmd:title>
            <gmd:date>
              <gmd:CI_Date>
                <gmd:date>
                <gco:Date>2007-06-01</gco:Date>
                </gmd:date>
                <gmd:dateType>
                  <gmd:CI_DateTypeCode
                    codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode"
                    codeListValue="publication">
                    publication
                  </gmd:CI_DateTypeCode>
                </gmd:dateType>
              </gmd:CI_Date>
            </gmd:date>
          </gmd:CI_Citation>
        </gmd:thesaurusName>
      </gmd:descriptiveKeywords>
<!-- Keywords from controlled vocabularies -->
      <gmd:descriptiveKeywords>
        <gmd:keyword>
          <gco:CharacterString>Floods</gco:CharacterString>
        </gmd:keyword>
        <gmd:thesaurusName>
          <gmd:CI_Citation>
          <gmd:title>
            <gco:CharacterString>GEOSS - Societal Benefit Areas, version 1.0</gco:CharacterString>
          </gmd:title>
          <gmd:date>
            <gmd:CI_Date>
              <gmd:date>
                <gco:Date>2010-08-25</gco:Date>
              </gmd:date>
              <gmd:dateType>
                <gmd:CI_DateTypeCode
                  codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode"
                  codeListValue="publication">
                  publication
                </gmd:CI_DateTypeCode>
              </gmd:dateType>
            </gmd:CI_Date>
          </gmd:date>
          </gmd:CI_Citation>
        </gmd:thesaurusName>
      </gmd:descriptiveKeywords>
    ...
    </srv:SV_ServiceIdentification>
  ...
  </gmd:identificationInfo>
</gmd:MD_Metadata>

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 using a bounding box

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

Bounding box

As a general rule, when the area corresponding to the spatial coverage is denoted by a geometry, as in INSPIRE, [[DCAT-AP-3]] 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 [[?RFC7946]]; or
a semantic representation - using vocabularies like W3C Lat/long [[?W3C-BASIC-GEO]] or schema.org [[?SCHEMA-ORG]].

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

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

Geometries MAY be provided in multiple encodings, but at least one of the following MUST be made available: GML and WKT.
For GML and WKT, the CRS MUST be specified as defined in GeoSPARQL [[GeoSPARQL11]].

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

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

For GeoJSON [[?RFC7946]], datatype gsp:geoJSONLiteral, defined in GeoSPARQL, version 1.1 [[?GeoSPARQL11]], SHOULD be used.

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

Resource metadata in GeoDCAT-AP using a geographic bounding box. This example uses multiple encodings, namely, the recommended ones (GML and WKT), plus GeoJSON.

[] dct:spatial [ a dct:Location ;
  dcat:bbox """
      POLYGON((-10.58 70.09,34.59 70.09,34.59 34.56,-10.58 34.56,-10.58 70.09))
    """^^gsp:wktLiteral ;
  dcat:bbox """
      <gml:Envelope srsName="http://www.opengis.net/def/crs/OGC/1.3/CRS84">
        <gml:lowerCorner>34.56 -10.58</gml:lowerCorner>
        <gml:upperCorner>70.09 34.59</gml:upperCorner>
      </gml:Envelope>
    """^^gsp:gmlLiteral ; 
  dcat:bbox """
      {
        "type":"Polygon",
        "coordinates":[[
          [-10.58,70.09],[34.59,70.09],[34.59,34.56],
          [-10.58,34.56],[-10.58,70.09]
        ]]
      }
    """^^gsp:geoJSONLiteral ] ;
.

Resource metadata in ISO 19139 using a geographic bounding box:

<gmd:MD_Metadata>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:extent>
        <gmd:EX_Extent>
          <gmd:geographicElement>
            <gmd:EX_GeographicBoundingBox>
              <gmd:extentTypeCode>
                <gco:Boolean>true</gco:Boolean>
              </gmd:extentTypeCode>
              <gmd:westBoundLongitude>
                <gco:Decimal>-9.227701</gco:Decimal>
              </gmd:westBoundLongitude>
              <gmd:eastBoundLongitude>
                <gco:Decimal>2.687637</gco:Decimal>
              </gmd:eastBoundLongitude>
              <gmd:southBoundLatitude>
                <gco:Decimal>49.83726</gco:Decimal>
              </gmd:southBoundLatitude>
              <gmd:northBoundLatitude>
                <gco:Decimal>60.850441</gco:Decimal>
              </gmd:northBoundLatitude>
            </gmd:EX_GeographicBoundingBox>
          </gmd:geographicElement>
        </gmd:EX_Extent>
      </gmd:extent>
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

Geographic identifier

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

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

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

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

As far as geographic identifiers are concerned, following [[DCAT-AP-3]], 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 .

Resource metadata in GeoDCAT-AP using a geographic identifier

# If a URI is used for the geographic identifier (recommended)
[]
  dct:spatial <http://publications.europa.eu/resource/authority/country/NLD> .

# If no URI is used for the geographic identifier
[]
  dct:spatial [ a dct:Location , skos:Concept ;
    skos:preflabel "Netherlands"@en;
    skos:prefLabel "Nederland"@nl;
    skos:inScheme [ skos:ConceptScheme ;
      dct:title "Countries Authority Table"@en;
      dct:modified "2009-01-01"^^xsd:date
    ]
  ] .

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:

temporal extent (temporal coverage);
date of publication, last revision, and/or creation.

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

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

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

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

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

Resource metadata in GeoDCAT-AP

## Creation, publication and last revision dates
# Metadata on metadata
[] a dcat:CatalogRecord ;
  ## Metadata date
  dct:modified "2012-08-13"^^xsd:date ;
  foaf:primaryTopic [
     dct:created "2010-03-01"^^xsd:date ;
     dct:issued "2010-10-05"^^xsd:date ;
     dct:modified "2011-09-01"^^xsd:date ;
  ## Temporal extent
     dct:temporal [ a dct:PeriodOfTime ;
       dcat:endDate "2006-12-31"^^xsd:date ;
       dcat:startDate "2006-01-01"^^xsd:date ] ].

Resource metadata in ISO 19139:

<gmd:MD_Metadata>
  ...
  <!-- metadata date -->
  <gmd:dateStamp>
    <gco:Date>2012-08-13</gco:Date>
  </gmd:dateStamp>
  ...
  <!-- temporal extent -->
  <gmd:extent>
    <gmd:EX_Extent>
      <gmd:temporalElement>
        <gmd:EX_TemporalExtent>
          <gmd:extent>
            <gml:TimePeriod gml:id="w5633aaa">
              <gml:beginPosition>2006-01-01</gml:beginPosition>
              <gml:endPosition>2006-12-31</gml:endPosition>
            </gml:TimePeriod>
          </gmd:extent>
        </gmd:EX_TemporalExtent>
      </gmd:temporalElement>
    </gmd:EX_Extent>
  </gmd:extent>
  ...
  <!-- Publication date (creation and last modification dates encoded similarly) -->
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      <gmd:citation>
        <gmd:CI_Citation>
          ...
          <gmd:date>
            <gmd:CI_Date>
              <gmd:date>
                <gco:Date>2010-03-01</gco:Date>
              </gmd:date>
              <gmd:dateType>
                <gmd:CI_DateTypeCode
                  codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode"
                  codeListValue="publication">
                    publication
                </gmd:CI_DateTypeCode>
              </gmd:dateType>
            </gmd:CI_Date>
          </gmd:date>
          ...
        </gmd:CI_Citation>
      </gmd:citation>
      ...
    </gmd:MD_DataIdentification>
  ...
  </gmd:identificationInfo>
</gmd:MD_Metadata>

Lineage - *Lineage

Following [[DCAT-AP-3]], 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 dct:description.

Resource metadata in GeoDCAT-AP:

[] a dcat:Dataset ;
  dct:provenance [ a dct:ProvenanceStatement ;
    dct:description "Forest Map 2006 is derived from the IMAGE2006 (SPOT/LISS scenes)
      and CORINE2006 landcover dataset. In addition, MODIS composites are used for
      the Forest type classification."@en ] .

Resource metadata in ISO 19139:

<gmd:MD_Metadata>
  ...
  <gmd:dataQualityInfo>
    <gmd:DQ_DataQuality>
      <gmd:lineage>
        <gmd:LI_Lineage>
          <gmd:statement>
          <gco:CharacterString>
            Forest Map 2006 is derived from the IMAGE2006 (SPOT/LISS scenes) and
            CORINE2006 landcover dataset. In addition, MODIS composites are used
            for the Forest type classification.
          </gco:CharacterString>
          </gmd:statement>
        </gmd:LI_Lineage>
      </gmd:lineage>
    </gmd:DQ_DataQuality>
  </gmd:dataQualityInfo>
  ...
</gmd:MD_Metadata>

Spatial resolution – Spatial resolution of the dataset

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

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

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

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

Resource metadata in GeoDCAT-AP:

# Spatial resolution as distance in metres
[] a dcat:Dataset ;
  dcat:spatialResolutionInMeters "5000"^^xsd:decimal .
# Spatial resolution as equivalent scale
[] a dcat:Dataset ;
  dqv:hasQualityMeasurement [ a dqv:QualityMeasurement ;
    dqv:isMeasurementOf geodcatap:spatialResolutionAsScale ;
    dqv:value "0.0001"^^xsd:decimal 
  ] .

Resource metadata in ISO 19139

<gmd:MD_Resolution>
  <gmd:equivalentScale>
    <gmd:MD_RepresentativeFraction>
      <gmd:denominator>
        <gco:Integer>10000</gco:Integer>
      </gmd:denominator>
    </gmd:MD_RepresentativeFraction>
  </gmd:equivalentScale>
</gmd:MD_Resolution>

Conformity and data quality - *not in ISO 19115 core

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

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

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

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

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

This pattern is illustrated in the following table.

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

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

Resource metadata in GeoDCAT-AP:

prov:wasUsedBy [
  a prov:Activity;
# Conformity degree
  prov:generated [ a prov:Entity ;
    dct:type <http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/conformant> ;
    dct:description "See the referenced specification"@en
    prov:qualifiedAssociation [ a prov:Association ;
      prov:hadPlan [ a prov:Plan;
        prov:wasDerivedFrom [
# Specification
          a prov:Entity , dct:Standard ;
          dct:title "COMMISSION REGULATION (EC) No 976/2009 of 19 October 2009
          implementing Directive 2007/2/EC of the European Parliament and of the Council
          as regards the Network Services"@en
          dct:issued "2009-10-20"^^xsd:date
      ]
    ];
  ];
] .

Resource metadata in ISO 19139:

<gmd:result>
  <gmd:DQ_ConformanceResult>
    <gmd:specification>
      <gmd:CI_Citation>
        <gmd:title>
          <gco:CharacterString>COMMISSION REGULATION (EC) No 976/2009 of 19 October 2009 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards the Network Services</gco:CharacterString>
        </gmd:title>
        <gmd:date>
          <gmd:CI_Date>
            <gmd:date>
              <gco:Date>2009-10-20</gco:Date>
            </gmd:date>
            <gmd:dateType>
              <gmd:CI_DateTypeCode
                codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_DateTypeCode"
                codeListValue="publication">
                  publication
              </gmd:CI_DateTypeCode>
            </gmd:dateType>
          </gmd:CI_Date>
        </gmd:date>
      </gmd:CI_Citation>
    </gmd:specification>
    <gmd:explanation>
      <gco:CharacterString> </gco:CharacterString>
    </gmd:explanation>
    <gmd:pass><gco:Boolean>true</gco:Boolean></gmd:pass>
  </gmd:DQ_ConformanceResult>
</gmd:result>

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

In [[DCAT-AP-3]], 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-3]] recommends the use of dct:accessRights for specifying access conditions. Both licenses and access rights should be indicated by their corresponding URIs.

Based on this, GeoDCAT-AP specifies use and access limitations by using, respectively, dct:license and dct:accessRights whenever the value is available as a URI. Otherwise, since the range of these properties is not a literal, but, respectively, classes dct:LicenseDocument and dct:RightsStatement, the free-text content of the corresponding ISO 19115 / INSPIRE metadata elements can be expressed using dct:description on the dct:RightsStatement instance, connected using the dct:rights property.

Resource metadata in GeoDCAT-AP (using URIs for use and access limitations):

[] dcat:distribution [ a dcat:Distribution ;
  dct:license <https://creativecommons.org/licenses/by/4.0/> ;
  dct:accessRights <https://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/noLimitations> ;
] .

Resource metadata in GeoDCAT-AP, free-text version:

[] dcat:distribution [ a dcat:Distribution ;
  dct:rights [ a dct:RightsStatement ;
    dct:description """
        The dataset contains parts which are restricted 
        by the data providers and not to be made public. 
        For further information and specification regarding 
        the use limitations and constraints please consult 
        the file WISE_WFD_ReferenceSpatialDataSets_2020-04-02.pdf 
        which is provided together with the data.    
      """@en ] ;
  dct:rights [ a dct:RightsStatement ;
    dct:description """
        public access limited according to Article 13(1)(b) 
	of the INSPIRE Directive
      """@en ] ] .

Resource metadata in ISO 19139 (using URIs for use and access limitations):

<gmd:MD_Metadata>
  ...
  <gmd:MD_LegalConstraints>
    <gmd:useConstraints>
      <gmd:MD_RestrictionCode
        codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_RestrictionCode"
        codeListValue="otherRestrictions"/>
    </gmd:useConstraints>
    <gmd:otherConstraints>
      <gmx:Anchor xlink:href="https://creativecommons.org/licenses/by/4.0/">
        CC-BY 4.0
      </gmx:Anchor>
    </gmd:otherConstraints>
  </gmd:MD_LegalConstraints>
  ...
  <gmd:MD_LegalConstraints>
    <gmd:accessConstraints>
      <gmd:MD_RestrictionCode
        codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_RestrictionCode"
        codeListValue="otherRestrictions"/>
    </gmd:accessConstraints>
    <gmd:otherConstraints>
      <gmx:Anchor xlink:href="https://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess/noLimitations">
        no limitations to public access
      </gmx:Anchor>
    </gmd:otherConstraints>
  </gmd:MD_LegalConstraints>
  ...
</gmd:MD_Metadata>

Resource metadata in ISO 19139:

<gmd:MD_Metadata>
  ...
  <gmd:MD_LegalConstraints>
    <gmd:useConstraints>
      <gmd:MD_RestrictionCode
        codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_RestrictionCode"
        codeListValue="otherRestrictions"/>
    </gmd:useConstraints>
    <gmd:otherConstraints>
      <gco:CharacterString>
        The dataset contains parts which are restricted 
        by the data providers and not to be made public. 
        For further information and specification regarding 
        the use limitations and constraints please consult 
        the file WISE_WFD_ReferenceSpatialDataSets_2020-04-02.pdf 
        which is provided together with the data.    
      </gco:CharacterString>
    </gmd:otherConstraints>
  </gmd:MD_LegalConstraints>
  ...
  <gmd:MD_LegalConstraints>
    <gmd:accessConstraints>
      <gmd:MD_RestrictionCode
        codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_RestrictionCode"
        codeListValue="otherRestrictions"/>
    </gmd:accessConstraints>
    <gmd:otherConstraints>
      <gco:CharacterString>
        public access limited according to Article 13(1)(b) 
	of the INSPIRE Directive
      </gco:CharacterString>
    </gmd:otherConstraints>
  </gmd:MD_LegalConstraints>
  ...
</gmd:MD_Metadata>

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

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

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

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

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

[[ISO-19115]]	[[INSPIRE-MD-REG]]	Description	Proposed RDF mapping
Resource provider	Part B, §6.1	Party that supplies the resource.	`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`

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

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

These mappings are illustrated in the following table.

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

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

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

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

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

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

Resource metadata in GeoDCAT-AP:

# Metadata on metadata in GeoDCAT-AP
[] dcat:contactPoint [ a vcard:Organization ;
      vcard:hasEmail <mailto:bag@kadaster.nl> ;
      vcard:organization-name "Kadaster"@nl ] ;
   prov:qualifiedAttribution [ a prov:Attribution ;
      dcat:hadRole <http://inspire.ec.europa.eu/metadata-codelist/ResponsiblePartyRole/pointOfContact> ;
      prov:agent [ a prov:Agent , foaf:Organization ;
        foaf:mbox <mailto:bag@kadaster.nl> ;
        foaf:workplaceHomepage <http://www.kadaster.nl/bag> ;
        foaf:name "Kadaster"@nl ] ] ;
   foaf:primaryTopic [ 
      dcat:contactPoint [ a vcard:Organization ;
      vcard:hasEmail <mailto:bag@kadaster.nl> ;
      vcard:organization-name "Kadaster"@nl ] ;
      geodcatap:custodian [ a prov:Agent , foaf:Organization ;
        foaf:mbox <mailto:bag@kadaster.nl> ;
        foaf:name "Kadaster"@nl ] ;
      prov:qualifiedAttribution
        [ a prov:Attribution ;
          dcat:hadRole <http://inspire.ec.europa.eu/metadata-codelist/ResponsiblePartyRole/custodian> ;
          prov:agent [ a prov:Agent , foaf:Organization ;
            foaf:mbox <mailto:bag@kadaster.nl> ;
            foaf:name "Kadaster"@nl ] ] ] .

Resource metadata in ISO 19139:

<gmd:MD_Metadata>
  ...
  <gmd:pointOfContact>
    <gmd:CI_ResponsibleParty>
      <gmd:organisationName>
        <gco:CharacterString>Kadaster</gco:CharacterString>
      </gmd:organisationName>
      <gmd:contactInfo>
        <gmd:CI_Contact>
          <gmd:address>
            <gmd:CI_Address>
              <gmd:electronicMailAddress>
                <gco:CharacterString>bag@kadaster.nl</gco:CharacterString>
              </gmd:electronicMailAddress>
            </gmd:CI_Address>
          </gmd:address>
          <gmd:onlineResource>
            <gmd:CI_OnlineResource>
              <gmd:linkage>
                <gmd:URL>http://www.kadaster.nl/bag</gmd:URL>
              </gmd:linkage>
            </gmd:CI_OnlineResource>
          </gmd:onlineResource>
        </gmd:CI_Contact>
      </gmd:contactInfo>
      <gmd:role>
      <gmd:CI_RoleCode
        codeListValue="custodian"
        codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_RoleCode"/>
      </gmd:role>
    </gmd:CI_ResponsibleParty>
  </gmd:pointOfContact>
  ...

</gmd:MD_Metadata>
<!-- Metadata on metadata in ISO 19139 -->
<gmd:MD_Metadata>
  ...
  <gmd:contact>
    <gmd:CI_ResponsibleParty>
      <gmd:organisationName>
        <gco:CharacterString>Kadaster</gco:CharacterString>
      </gmd:organisationName>
      <gmd:contactInfo>
        ...
      </gmd:contactInfo>
      <gmd:role>
        <gmd:CI_RoleCode
          codeListValue="pointofContact"
          codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#CI_RoleCode"/>
      </gmd:role>
    </gmd:CI_ResponsibleParty>
  </gmd:contact>
  ...
</gmd:MD_Metadata>

*Metadata file identifier

This element identifies a metadata record.

Metadata file identifiers are mapped to dct:identifier.

Metadata on metadata in GeoDCAT-AP:

[] a dcat:CatalogRecord ;
  dct:identifier "947e5a55-e548-11e1-9105-0017085a97ab"^^xsd:string .

Resource metadata in ISO 19139:

<gmd:MD_Metadata>
<!-- Metadata on metadata -->
  ...
  <gmd:fileIdentifier>
    <gco:CharacterString>
      947e5a55-e548-11e1-9105-0017085a97ab
    </gco:CharacterString>
  </gmd:fileIdentifier>
  ...
</gmd:MD_Metadata>

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

Metadata on metadata in GeoDCAT-AP:

<https://some.catalogue/record/947e5a55-e548-11e1-9105-0017085a97ab>
  a dcat:CatalogRecord ;
  dct:identifier
    "https://some.catalogue/record/947e5a55-e548-11e1-9105-0017085a97ab"^^xsd:anyURI .

Metadata standard name, Metadata standard version

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

This pattern is illustrated in the following table.

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

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

Metadata on metadata in GeoDCAT-AP:

[] a dcat:CatalogRecord ;
  dct:conformsTo <https://joinup.ec.europa.eu/release/geodcat-ap/10> ;
.

<https://joinup.ec.europa.eu/release/geodcat-ap/10>
# Standard name and version of the GeoDCAT-AP record
  a dct:Standard ;
  dct:title "GeoDCAT-AP"@en ;
  owl:versionInfo "1.0" ;
.

Resource metadata in ISO 19139 for datasets:

<gmd:MD_Metadata>
  ...
  <gmd:metadataStandardName>
    <gco:CharacterString>ISO 19115</gco:CharacterString>
  </gmd:metadataStandardName>
  <gmd:metadataStandardVersion>
    <gco:CharacterString>Nederlands metadata profiel op ISO 19115 voor geografie 1.3</gco:CharacterString>
  </gmd:metadataStandardVersion>
</gmd:MD_Metadata>

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

Metadata on metadata in GeoDCAT-AP:

[] a dcat:CatalogRecord ;
  dct:conformsTo <https://joinup.ec.europa.eu/release/geodcat-ap/10> ;
  dct:source [ a dcat:CatalogRecord ; 
# Standard name and version of the source ISO 19115 record
    dct:conformsTo [ a dct:Standard ;
      dct:title "ISO 19115"@en ;
      owl:versionInfo "Nederlands metadata profiel op ISO 19115 voor geografie 1.3".
    ] ] ;
.

<https://joinup.ec.europa.eu/release/geodcat-ap/10>
# Standard name and version of the GeoDCAT-AP record
  dct:title "GeoDCAT-AP"@en ;
  owl:versionInfo "1.0" ;
.

Resource metadata in ISO 19139 for datasets:

<gmd:MD_Metadata>
  ...
  <gmd:metadataStandardName>
    <gco:CharacterString>ISO 19115</gco:CharacterString>
  </gmd:metadataStandardName>
  <gmd:metadataStandardVersion>
    <gco:CharacterString>Nederlands metadata profiel op ISO 19115 voor geografie 1.3</gco:CharacterString>
  </gmd:metadataStandardVersion>
</gmd:MD_Metadata>

*Metadata characterset

Since in RDF serializations always use UTF-8, the metadata characterset is not reflected in the GeoDCAT-AP.

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 GeoDCAT-AP, these elements are mapped to property geodcatap:referenceSystem. Moreover, in order to indicate which type of a reference system the object of geodcatap:referenceSystem denotes, 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 [[INSPIRE-GLOSSARY]].

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

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

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

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

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

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

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

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

Resource metadata in GeoDCAT-AP:

[] a dcat:Dataset ;
  geodcatap:referenceSystem <http://www.opengis.net/def/crs/EPSG/0/4258> .

<http://www.opengis.net/def/crs/EPSG/0/4258>
  a dct:Standard ;
  dct:type <http://inspire.ec.europa.eu/glossary/SpatialReferenceSystem> .

Resource metadata in ISO 19139:

<gmd:referenceSystemInfo>
  <gmd:MD_ReferenceSystem>
    <gmd:referenceSystemIdentifier>
      <gmd:RS_Identifier>
        <gmd:code>
          <gco:CharacterString>
            http://www.opengis.net/def/crs/EPSG/0/4258
          </gco:CharacterString>
        </gmd:code>
        ...
      </gmd:RS_Identifier>
    </gmd:referenceSystemIdentifier>
  </gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>

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

Resource metadata in GeoDCAT-AP:

[] a dcat:Dataset ;
  geodcatap:referenceSystem [ a dct:Standard ;
    dct:identifer "EPSG:4258"^^xsd:string ;
    dct:type <http://inspire.ec.europa.eu/glossary/SpatialReferenceSystem> .
  ] .

Resource metadata in ISO 19139:

<gmd:referenceSystemInfo>
  <gmd:MD_ReferenceSystem>
    <gmd:referenceSystemIdentifier>
      <gmd:RS_Identifier>
        <gmd:code>
          <gco:CharacterString>EPSG:4258</gco:CharacterString>
        </gmd:code>
        ...
      </gmd:RS_Identifier>
    </gmd:referenceSystemIdentifier>
  </gmd:MD_ReferenceSystem>
</gmd:referenceSystemInfo>

Character encoding - Dataset character set and Metadata character set

In [[VOCAB-DCAT-3]] and [[DCAT-AP-3]], the specification of the character encoding of a dataset and the character encoding of a metadata record is not explicitly supported. Moreover, since GeoDCAT-AP is an RDF-based specification, the metadata represented using GeoDCAT-AP are always in the UTF-8 encoding.

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

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

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

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

Resource metadata in GeoDCAT-AP:

[] a dcat:Dataset ;
  dcat:distribution [ a dcat:Distribution ;
    cnt:characterEncoding "UTF-8"^^xsd:string ] .

Resource metadata in ISO 19139:

<gmd:MD_Metadata>
<!-- Resource metadata: dataset character set -->
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification>
      ...
      <gmd:characterSet>
        <gmd:MD_CharacterSetCode
          codeListValue="utf8"
          codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_CharacterSetCode"/>
      </gmd:characterSet>
      ...
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

Encoding - *Distribution format

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

Two properties are available:

dcat:mediaType: to be used when the format corresponds to one of the media types registered by IANA [[IANA-MEDIA-TYPES]].
dct:format: to be used in all the other cases, to be used with file type register operated by the Publications Office of the EU [[EUV-FT]].

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

Resource metadata in GeoDCAT-AP:

[] a dcat:Dataset ;
  dcat:distribution [ a dcat:Distribution ;
    dct:format <http://publications.europa.eu/resource/authority/file-type/TIFF> ] .

Resource metadata in ISO 19139:

<gmd:MD_Metadata>
  ...
  <gmd:distributionInfo>
    <gmd:MD_Distribution>
      <gmd:distributionFormat>
        <gmd:MD_Format>
          <gmd:name>
            <gco:CharacterString>GeoTIFF</gco:CharacterString>
          </gmd:name>
          <gmd:version>
            <gco:CharacterString>1.0</gco:CharacterString>
          </gmd:version>
        </gmd:MD_Format>
      </gmd:distributionFormat>
      ...
    </gmd:MD_Distribution>
  </gmd:distributionInfo>
  ...
</gmd:MD_Metadata>

Spatial representation type – *Spatial representation type

In [[DCAT-AP-3]], 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 is available as a URI register from the INSPIRE Registry [[INSPIRE-SRT]].

Based on this, GeoDCAT-AP specifies this information by using property adms:representationTechnique, with the spatial representation type URIs operated by the INSPIRE Registry [[INSPIRE-SRT]].

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

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

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

Resource metadata in GeoDCAT-AP:

[] a dcat:Dataset ;
  dcat:distribution [ a dcat:Distribution
    adms:representionTechnique <http://inspire.ec.europa.eu/metadata-codelist/SpatialRepresentationType/vector>
] .

Resource metadata in ISO 19139:

<gmd:spatialRepresentationType>
  <gmd:MD_SpatialRepresentationTypeCode
    codeListValue="vector"
    codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/gmxCodelists.xml#MD_SpatialRepresentationTypeCode">vector</gmd:MD_SpatialRepresentationTypeCode>
</gmd:spatialRepresentationType>

Maintenance information - *not in ISO 19115 core

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

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

ISO 19115 - MD_MaintenanceFrequencyCode	Dublin Core Collection Description Frequency Vocabulary [[?CLD-FREQ]]	EU Vocabularies Frequency Named Authority List [[EUV-FREQ]]
continual	continuous	UPDATE_CONT / CONT
daily	daily	DAILY
weekly	weekly	WEEKLY
fortnightly	biweekly	BIWEEKLY
monthly	monthly	MONTHLY
quarterly	quarterly	QUARTERLY
biannually	semiannual	ANNUAL_2
annually	annual	ANNUAL
asNeeded	-	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

The [[ISO-19115]] code list of maintenance frequency codes is available as a URI register from the INSPIRE Registry [[INSPIRE-MF]].

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

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

In the core mapping profile of GeoDCAT-AP these codes will be ignored.
The extended mapping profile of GeoDCAT-AP will use the code list of ISO maintenance frequency codes operated by the INSPIRE Registry [[INSPIRE-MF]].

Resource metadata in GeoDCAT-AP:

[] a dcat:Dataset ;
  dct:accrualPeriodicity <http://publications.europa.eu/resource/authority/frequency/DAILY> .

Resource metadata in ISO 19139:

<gmd:MD_MaintenanceInformation>
  <gmd:maintenanceAndUpdateFrequency gco:nilReason="missing">
    <gmd:MD_MaintenanceFrequencyCode
      codeList="http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/codelist/ML_gmxCodelists.xml#MD_MaintenanceFrequencyCode"
      codeListValue="daily">daily</gmd:MD_MaintenanceFrequencyCode>
  </gmd:maintenanceAndUpdateFrequency>
</gmd:MD_MaintenanceInformation>

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:

the metadata elements to be used for discovery of geographic datasets and series are identified in F.1;
the metadata elements to be used for discovery of service resources are identified in F.2.

Spatial dataset and spatial dataset series

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

ISO 19115 Core	INSPIRE Implementing Rules for Metadata	ISO 19115-1:2014 Discovery metadata for datasets and series (Table F.1)	ISO 19115-1:2014 Path
Dataset title (M)	Part B 1.1 Resource Title	Resource title (M/1)	`MD_Metadata.identificationInfo` > `MD_DataIdentification.citation` > `CI_Citation.title`
Dataset reference date (M)	Part B 5 Temporal Reference	Resource reference date (O/N)	`MD_Metadata.idenitificationInfo` > `MD_DataIdentification.citation` > `CI_Citation.date`
Dataset responsible party (O)	Part B 9 Responsible organisation	Resource point of contact (O/N)	`MD_Metadata.identificationInfo` > `MD_DataIdentification.pointOf-Contact` > `CI_Responsibility`
Geographic location of the dataset (C)	Part B 4.1 Geographic Bounding Box	Geographic location (C/N)	`MD_Metadata.identificationInfo` > `MD_DataIdentification.extent` > `EX_Extent.geographicElement` > `EX_GeographicExtent` > `EX_GeographicBoundingBox` -or- `EX_GeographicDescription`)
Dataset language (M)	Part B 1.7 Resource Language	Resource language (C/N)	`MD_Metadata.identificationInfo` > `MD_DataIdentification.defaultLocale` > `PT_Locale`
Dataset character set (C)	-	-
Dataset topic category (M)	Part B 2.1 Topic Category	Resource topic category (C/N)	`MD_Metadata.identificationInfo` > `MD_DataIdentification.topicCategory` > `MD_TopicCategoryCode`
Spatial resolution of the dataset (O)	Part B 6.2 Spatial Resolution	Spatial resolution (O/N)	`MD_Metadata.identificationInfo` > `MD_Identification.spatialResolution` > `MD_Resolution.equivalentScale` `MD_Resolution.distance`, `MD_Resolution.vertical`, or `MD_Resolution.angularDistance`, or `MD_Resolution.levelOfDetail`
Abstract describing the dataset (M)	Part B 1.2 Resource abstract	Resource abstract (M/1)	`MD_Metadata.identificationInfo` > `MD_DataIdentification.abstract`
Distribution format (O)	-	-
Additional extent information for the dataset (vertical and temporal) (O)	Part B 5.1 Temporal extent	Extent information for the dataset (additional) (O/N)	`MD_Metadata.identificationInfo` > `MD_Identification.extent` > `EX_Extent` > `EX_TemporalExtent` or `EX_VerticalExtent`
Spatial representation type (O)	-	-
Reference system (O)	-	-
Lineage (O)	Part B 6.1 Lineage	Resource lineage (O/N)	`MD_Metadata` > `resourceLineage` > `LI_Lineage.statement`
On-line resource (O)	Part B 1.4 Resource Locator	Resource on-line Link (O/N)	`MD_Metadata.identificationInfo` > `MD_DataIdentification.citation` > `CI_Citation.onlineResource` > `CI_OnlineResource`
Metadata file identifier (O)	-	Metadata reference information (O/1)	`MD_Metadata.metadataIdentifier`
Metadata standard name (O)	-	-
Metadata standard version (O)	-	-
Metadata language (C)	Part B 10.3 Metadata Language	-	`MD_Metadata.defaultLocale` > `PT_Locale.language`
Metadata character set (C)	-	-
Metadata point of contact (M)	Part B 10.1 Metadata point of contact	Metadata point of contact (M/N)	`MD_Metadata.contact` > `CI_Responsibility`
Metadata date stamp (M)	Part B 10.2 Metadata Date	Metadata date stamp (M/N)	`MD_Metadata.dateInfo`
-	Part B 1.3 Resource Type	Resource type (C/1)	`MD_Metadata.metadataScope` > `MD_Scope.resourceScope`
	Part B 1.5 Unique Resource Identifier	Resource identifier (O/N)	`MD_Metadata.identificationInfo` > `MD_DataIdentification.citation` > `CI_Citation.identifier` > `MD_Identifier`
	Part B 3 Keyword	Keywords (O/N)	`MD_Metadata.identificationInfo` > `MD_DataIdentification` > `descriptiveKeywords` > `MD_Keywords`
-	Part B 7 Conformity	-	`MD_Metadata.dataQualityInfo` > `DQ_DataQuality.report` > `DQ_UsabilityElement.result` > `DQ_ConformanceResult`
-	Part B 8.1 Conditions for access and use	Constraints on resource access and use (O/N)	`MD_Metadata.identificationInfo` > `MD_DataIdentification` > `MD_Constraints.useLimitations`
-	Part B 8.2 Limitations on public access	Constraints on resource access and use (O/N)	`MD_Metadata.identificationInfo` > `MD_DataIdentification` > `MD_LegalConstraints.accessConstraint` and/or `MD_LegalConstraints.otherConstraint` and/or `MD_SecurityConstraints.classification`

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 (3^rd field).

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

Quick Reference of Classes and Properties

This section provides a condensed tabular overview of the mentioned classes and properties in this specification. The properties are grouped under headings mandatory, recommended, optional and deprecated. These terms have the following meaning.

Mandatory property: a receiver MUST be able to process the information for that property; a sender MUST provide the information for that property.
Recommended property: a receiver MUST be able to process the information for that property; a sender SHOULD provide the information for that property if it is available.
Optional property: a receiver MUST be able to process the information for that property; a sender MAY provide the information for that property but is not obliged to do so.
Deprecated property: a receiver SHOULD be able to process information about instances of that property; a sender SHOULD NOT provide the information about instances of that property.

Class	Class IRI	Property Type	Property	Property IRI
Activity	http://www.w3.org/ns/prov#Activity	Optional	generated	http://www.w3.org/ns/prov#generated
Activity	http://www.w3.org/ns/prov#Activity	Optional	qualified association	http://www.w3.org/ns/prov#qualifiedAssociation
Activity	http://www.w3.org/ns/prov#Activity	Optional	used	http://www.w3.org/ns/prov#used
Address (Core Location)	http://www.w3.org/ns/locn#Address	Optional	administrative area	http://www.w3.org/ns/locn#adminUnitL2
Address (Core Location)	http://www.w3.org/ns/locn#Address	Optional	city	http://www.w3.org/ns/locn#postName
Address (Core Location)	http://www.w3.org/ns/locn#Address	Optional	country	http://www.w3.org/ns/locn#adminUnitL2
Address (Core Location)	http://www.w3.org/ns/locn#Address	Optional	post code	http://www.w3.org/ns/locn#postCode
Address (Core Location)	http://www.w3.org/ns/locn#Address	Optional	street address	http://www.w3.org/ns/locn#thoroughfare
Address (vCard)	http://www.w3.org/2006/vcard/ns#Address	Optional	administrative area	http://www.w3.org/2006/vcard/ns#region
Address (vCard)	http://www.w3.org/2006/vcard/ns#Address	Optional	city	http://www.w3.org/2006/vcard/ns#locality
Address (vCard)	http://www.w3.org/2006/vcard/ns#Address	Optional	country	http://www.w3.org/2006/vcard/ns#country-name
Address (vCard)	http://www.w3.org/2006/vcard/ns#Address	Optional	postal code	http://www.w3.org/2006/vcard/ns#postal-code
Address (vCard)	http://www.w3.org/2006/vcard/ns#Address	Optional	street address	http://www.w3.org/2006/vcard/ns#street-address
Agent	http://xmlns.com/foaf/0.1/Agent	Mandatory	name	http://xmlns.com/foaf/0.1/name
Agent	http://xmlns.com/foaf/0.1/Agent	Recommended	type	http://purl.org/dc/terms/type
Agent	http://xmlns.com/foaf/0.1/Agent	Optional	address	http://www.w3.org/ns/locn#address
Agent	http://xmlns.com/foaf/0.1/Agent	Optional	affiliation	http://www.w3.org/ns/org#memberOf
Agent	http://xmlns.com/foaf/0.1/Agent	Optional	email	http://xmlns.com/foaf/0.1/mbox
Agent	http://xmlns.com/foaf/0.1/Agent	Optional	phone	http://xmlns.com/foaf/0.1/phone
Agent	http://xmlns.com/foaf/0.1/Agent	Optional	URL	http://xmlns.com/foaf/0.1/workplaceHomepage
Association	http://www.w3.org/ns/prov#Association
Attribution	http://www.w3.org/ns/prov#Attribution	Optional	agent	http://www.w3.org/ns/prov#agent
Attribution	http://www.w3.org/ns/prov#Attribution	Optional	had role	http://www.w3.org/ns/dcat#hadRole
Catalogue	http://www.w3.org/ns/dcat#Catalog	Mandatory	description	http://purl.org/dc/terms/description
Catalogue	http://www.w3.org/ns/dcat#Catalog	Mandatory	publisher	http://purl.org/dc/terms/publisher
Catalogue	http://www.w3.org/ns/dcat#Catalog	Mandatory	title	http://purl.org/dc/terms/title
Catalogue	http://www.w3.org/ns/dcat#Catalog	Recommended	dataset	http://www.w3.org/ns/dcat#dataset
Catalogue	http://www.w3.org/ns/dcat#Catalog	Recommended	geographical coverage	http://purl.org/dc/terms/spatial
Catalogue	http://www.w3.org/ns/dcat#Catalog	Recommended	homepage	http://xmlns.com/foaf/0.1/homepage
Catalogue	http://www.w3.org/ns/dcat#Catalog	Recommended	language	http://purl.org/dc/terms/language
Catalogue	http://www.w3.org/ns/dcat#Catalog	Recommended	licence	http://purl.org/dc/terms/license
Catalogue	http://www.w3.org/ns/dcat#Catalog	Recommended	modification date	http://purl.org/dc/terms/modified
Catalogue	http://www.w3.org/ns/dcat#Catalog	Recommended	release date	http://purl.org/dc/terms/issued
Catalogue	http://www.w3.org/ns/dcat#Catalog	Recommended	service	http://www.w3.org/ns/dcat#service
Catalogue	http://www.w3.org/ns/dcat#Catalog	Recommended	themes	http://www.w3.org/ns/dcat#themeTaxonomy
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	access rights	http://purl.org/dc/terms/accessRights
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	applicable legislation	http://data.europa.eu/r5r/applicableLegislation
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	catalogue	http://www.w3.org/ns/dcat#catalog
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	conforms to	http://purl.org/dc/terms/conformsTo
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	contact point	http://www.w3.org/ns/dcat#contactPoint
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	creation date	http://purl.org/dc/terms/created
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	creator	http://purl.org/dc/terms/creator
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	custodian	http://data.europa.eu/930/custodian
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	distributor	http://data.europa.eu/930/distributor
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	has part	http://purl.org/dc/terms/hasPart
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	identifier	http://purl.org/dc/terms/identifier
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	keyword	http://www.w3.org/ns/dcat#keyword
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	originator	http://data.europa.eu/930/originator
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	principal investigator	http://data.europa.eu/930/principalInvestigator
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	processor	http://data.europa.eu/930/processor
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	qualified attribution	http://www.w3.org/ns/prov#qualifiedAttribution
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	record	http://www.w3.org/ns/dcat#record
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	reference system	http://data.europa.eu/930/referenceSystem
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	resource provider	http://data.europa.eu/930/resourceProvider
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	rights	http://purl.org/dc/terms/rights
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	rights holder	http://purl.org/dc/terms/rightsHolder
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	temporal coverage	http://purl.org/dc/terms/temporal
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	theme	http://www.w3.org/ns/dcat#theme
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	topic category	http://data.europa.eu/930/topicCategory
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	user	http://data.europa.eu/930/user
Catalogue	http://www.w3.org/ns/dcat#Catalog	Optional	was used by	http://www.w3.org/ns/prov#wasUsedBy
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Mandatory	modification date	http://purl.org/dc/terms/modified
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Mandatory	primary topic	http://xmlns.com/foaf/0.1/primaryTopic
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Recommended	application profile	http://purl.org/dc/terms/conformsTo
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Recommended	change type	http://www.w3.org/ns/adms#status
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Recommended	listing date	http://purl.org/dc/terms/issued
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	contact point	http://www.w3.org/ns/dcat#contactPoint
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	creation date	http://purl.org/dc/terms/created
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	creator	http://purl.org/dc/terms/creator
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	custodian	http://data.europa.eu/930/custodian
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	description	http://purl.org/dc/terms/description
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	distributor	http://data.europa.eu/930/distributor
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	identifier	http://purl.org/dc/terms/identifier
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	language	http://purl.org/dc/terms/language
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	originator	http://data.europa.eu/930/originator
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	principal investigator	http://data.europa.eu/930/principalInvestigator
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	processor	http://data.europa.eu/930/processor
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	publisher	http://purl.org/dc/terms/publisher
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	qualified attribution	http://www.w3.org/ns/prov#qualifiedAttribution
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	resource provider	http://data.europa.eu/930/resourceProvider
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	rights holder	http://purl.org/dc/terms/rightsHolder
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	source metadata	http://purl.org/dc/terms/source
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	title	http://purl.org/dc/terms/title
Catalogue Record	http://www.w3.org/ns/dcat#CatalogRecord	Optional	user	http://data.europa.eu/930/user
Catalogued Resource	http://www.w3.org/ns/dcat#Resource
Checksum	http://spdx.org/rdf/terms#Checksum	Mandatory	algorithm	http://spdx.org/rdf/terms#algorithm
Checksum	http://spdx.org/rdf/terms#Checksum	Mandatory	checksum value	http://spdx.org/rdf/terms#checksumValue
Checksum Algorithm	http://spdx.org/rdf/terms#ChecksumAlgorithm
Concept	http://www.w3.org/2004/02/skos/core#Concept	Mandatory	preferred label	http://www.w3.org/2004/02/skos/core#prefLabel
Concept	http://www.w3.org/2004/02/skos/core#Concept	Optional	category scheme	http://www.w3.org/2004/02/skos/core#inScheme
Concept Scheme	http://www.w3.org/2004/02/skos/core#ConceptScheme	Mandatory	title	http://purl.org/dc/terms/title
Data Service	http://www.w3.org/ns/dcat#DataService	Mandatory	endpoint URL	http://www.w3.org/ns/dcat#endpointURL
Data Service	http://www.w3.org/ns/dcat#DataService	Mandatory	title	http://purl.org/dc/terms/title
Data Service	http://www.w3.org/ns/dcat#DataService	Recommended	conforms to	http://purl.org/dc/terms/conformsTo
Data Service	http://www.w3.org/ns/dcat#DataService	Recommended	contact point	http://www.w3.org/ns/dcat#contactPoint
Data Service	http://www.w3.org/ns/dcat#DataService	Recommended	endpoint description	http://www.w3.org/ns/dcat#endpointDescription
Data Service	http://www.w3.org/ns/dcat#DataService	Recommended	keyword	http://www.w3.org/ns/dcat#keyword
Data Service	http://www.w3.org/ns/dcat#DataService	Recommended	publisher	http://purl.org/dc/terms/publisher
Data Service	http://www.w3.org/ns/dcat#DataService	Recommended	serves dataset	http://www.w3.org/ns/dcat#servesDataset
Data Service	http://www.w3.org/ns/dcat#DataService	Recommended	theme	http://www.w3.org/ns/dcat#theme
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	access rights	http://purl.org/dc/terms/accessRights
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	applicable legislation	http://data.europa.eu/r5r/applicableLegislation
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	creation date	http://purl.org/dc/terms/created
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	creator	http://purl.org/dc/terms/creator
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	custodian	http://data.europa.eu/930/custodian
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	description	http://purl.org/dc/terms/description
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	distributor	http://data.europa.eu/930/distributor
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	format	http://purl.org/dc/terms/format
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	geographical coverage	http://purl.org/dc/terms/spatial
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	identifier	http://purl.org/dc/terms/identifier
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	landing page	http://www.w3.org/ns/dcat#landingPage
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	language	http://purl.org/dc/terms/language
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	licence	http://purl.org/dc/terms/license
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	modification date	http://purl.org/dc/terms/modified
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	orginator	http://data.europa.eu/930/originator
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	principal investigator	http://data.europa.eu/930/principalInvestigator
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	processor	http://data.europa.eu/930/processor
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	qualified attribution	http://www.w3.org/ns/prov#qualifiedAttribution
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	reference system	http://data.europa.eu/930/referenceSystem
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	release date	http://purl.org/dc/terms/issued
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	resource provider	http://data.europa.eu/930/resourceProvider
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	rights	http://purl.org/dc/terms/rights
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	rights holder	http://purl.org/dc/terms/rightsHolder
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	service category	http://data.europa.eu/930/serviceCategory
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	service protocol	http://data.europa.eu/930/serviceProtocol
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	service type	http://data.europa.eu/930/serviceType
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	spatial resolution	http://www.w3.org/ns/dqv#hasQualityMeasurement
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	spatial resolution as text	http://data.europa.eu/930/spatialResolutionAsText
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	spatial resolution in metres	https://www.w3.org/ns/dcat#spatialResolutionInMeters
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	temporal coverage	http://purl.org/dc/terms/temporal
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	temporal resolution	http://www.w3.org/ns/dcat#temporalResolution
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	topic category	http://data.europa.eu/930/topicCategory
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	type	http://data.europa.eu/930/resourceType
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	user	http://data.europa.eu/930/user
Data Service	http://www.w3.org/ns/dcat#DataService	Optional	was used by	http://www.w3.org/ns/prov#wasUsedBy
Dataset	http://www.w3.org/ns/dcat#Dataset	Mandatory	description	http://purl.org/dc/terms/description
Dataset	http://www.w3.org/ns/dcat#Dataset	Mandatory	title	http://purl.org/dc/terms/title
Dataset	http://www.w3.org/ns/dcat#Dataset	Recommended	contact point	http://www.w3.org/ns/dcat#contactPoint
Dataset	http://www.w3.org/ns/dcat#Dataset	Recommended	dataset distribution	http://www.w3.org/ns/dcat#distribution
Dataset	http://www.w3.org/ns/dcat#Dataset	Recommended	geographical coverage	http://purl.org/dc/terms/spatial
Dataset	http://www.w3.org/ns/dcat#Dataset	Recommended	keyword	http://www.w3.org/ns/dcat#keyword
Dataset	http://www.w3.org/ns/dcat#Dataset	Recommended	publisher	http://purl.org/dc/terms/publisher
Dataset	http://www.w3.org/ns/dcat#Dataset	Recommended	temporal coverage	http://purl.org/dc/terms/temporal
Dataset	http://www.w3.org/ns/dcat#Dataset	Recommended	theme	http://www.w3.org/ns/dcat#theme
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	access rights	http://purl.org/dc/terms/accessRights
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	applicable legislation	http://data.europa.eu/r5r/applicableLegislation
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	conforms to	http://purl.org/dc/terms/conformsTo
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	creation date	http://purl.org/dc/terms/created
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	creator	http://purl.org/dc/terms/creator
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	custodian	http://data.europa.eu/930/custodian
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	distributor	http://data.europa.eu/930/distributor
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	documentation	http://xmlns.com/foaf/0.1/page
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	frequency	http://purl.org/dc/terms/accrualPeriodicity
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	has version	http://www.w3.org/ns/dcat#hasVersion
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	identifier	http://purl.org/dc/terms/identifier
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	in series	http://www.w3.org/ns/dcat#inSeries
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	is referenced by	http://purl.org/dc/terms/isReferencedBy
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	landing page	http://www.w3.org/ns/dcat#landingPage
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	language	http://purl.org/dc/terms/language
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	modification date	http://purl.org/dc/terms/modified
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	originator	http://data.europa.eu/930/originator
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	other identifier	http://www.w3.org/ns/adms#identifier
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	principal investigator	http://data.europa.eu/930/principalInvestigator
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	processor	http://data.europa.eu/930/processor
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	provenance	http://purl.org/dc/terms/provenance
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	qualified attribution	http://www.w3.org/ns/prov#qualifiedAttribution
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	qualified relation	http://www.w3.org/ns/dcat#qualifiedRelation
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	reference system	http://data.europa.eu/930/referenceSystem
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	related resource	http://purl.org/dc/terms/relation
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	release date	http://purl.org/dc/terms/issued
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	resource provider	http://data.europa.eu/930/resourceProvider
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	resource type	http://data.europa.eu/930/resourceType
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	rights	http://purl.org/dc/terms/rights
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	rights holder	http://purl.org/dc/terms/rightsHolder
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	sample	http://www.w3.org/ns/adms#sample
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	source	http://purl.org/dc/terms/source
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	spatial resolution	http://www.w3.org/ns/dqv#hasQualityMeasurement
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	spatial resolution as text	http://data.europa.eu/930/spatialResolutionAsText
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	spatial resolution in metres	http://www.w3.org/ns/dcat#spatialResolutionInMeters
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	temporal resolution	http://www.w3.org/ns/dcat#temporalResolution
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	topic category	http://data.europa.eu/930/topicCategory
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	user	http://data.europa.eu/930/user
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	version	http://www.w3.org/ns/dcat#version
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	version notes	http://www.w3.org/ns/adms#versionNotes
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	was generated by	http://www.w3.org/ns/prov#wasGeneratedBy
Dataset	http://www.w3.org/ns/dcat#Dataset	Optional	was used by	http://www.w3.org/ns/prov#wasUsedBy
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Mandatory	title	http://purl.org/dc/terms/title
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Recommended	contact point	http://www.w3.org/ns/dcat#contactPoint
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Recommended	geographical coverage	http://purl.org/dc/terms/spatial
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Recommended	keyword	http://www.w3.org/ns/dcat#keyword
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Recommended	publisher	http://purl.org/dc/terms/publisher
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Recommended	temporal coverage	http://purl.org/dc/terms/temporal
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Recommended	theme	http://www.w3.org/ns/dcat#theme
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	access rights	http://purl.org/dc/terms/accessRights
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	applicable legislation	http://data.europa.eu/r5r/applicableLegislation
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	conforms to	http://purl.org/dc/terms/conformsTo
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	creation date	http://purl.org/dc/terms/created
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	creator	http://purl.org/dc/terms/creator
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	custodian	http://data.europa.eu/930/custodian
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	dataset series distribution	http://www.w3.org/ns/dcat#distribution
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	description	http://purl.org/dc/terms/description
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	distributor	http://data.europa.eu/930/distributor
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	documentation	http://xmlns.com/foaf/0.1/page
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	frequency	http://purl.org/dc/terms/accrualPeriodicity
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	has version	http://www.w3.org/ns/dcat#hasVersion
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	identifier	http://purl.org/dc/terms/identifier
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	in series	http://www.w3.org/ns/dcat#inSeries
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	is referenced by	http://purl.org/dc/terms/isReferencedBy
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	landing page	http://www.w3.org/ns/dcat#landingPage
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	language	http://purl.org/dc/terms/language
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	modification date	http://purl.org/dc/terms/modified
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	originator	http://data.europa.eu/930/originator
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	other identifier	http://www.w3.org/ns/adms#identifier
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	principal investigator	http://data.europa.eu/930/principalInvestigator
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	processor	http://data.europa.eu/930/processor
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	qualified attribution	http://www.w3.org/ns/prov#qualifiedAttribution
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	qualified relation	http://www.w3.org/ns/dcat#qualifiedRelation
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	reference system	http://data.europa.eu/930/referenceSystem
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	related resource	http://purl.org/dc/terms/relation
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	release date	http://purl.org/dc/terms/issued
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	resource provider	http://data.europa.eu/930/resourceProvider
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	resource type	http://data.europa.eu/930/resourceType
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	rights	http://purl.org/dc/terms/rights
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	rights holder	http://purl.org/dc/terms/rightsHolder
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	sample	http://www.w3.org/ns/adms#sample
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	source	http://purl.org/dc/terms/source
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	spatial resolution	http://www.w3.org/ns/dqv#hasQualityMeasurement
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	spatial resolution as text	http://data.europa.eu/930/spatialResolutionAsText
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	spatial resolution in metres	http://www.w3.org/ns/dcat#spatialResolutionInMeters
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	topic category	http://data.europa.eu/930/topicCategory
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	user	http://data.europa.eu/930/user
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	version	http://www.w3.org/ns/dcat#version
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	version notes	http://www.w3.org/ns/adms#versionNotes
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	was generated by	http://www.w3.org/ns/prov#wasGeneratedBy
Dataset Series	http://www.w3.org/ns/dcat#DatasetSeries	Optional	was used by	http://www.w3.org/ns/prov#wasUsedBy
Datatype	http://www.w3.org/2000/01/rdf-schema#Datatype
Dimension	http://www.w3.org/ns/dqv#Dimension
Distribution	http://www.w3.org/ns/dcat#Distribution	Mandatory	access URL	http://www.w3.org/ns/dcat#accessURL
Distribution	http://www.w3.org/ns/dcat#Distribution	Recommended	description	http://purl.org/dc/terms/description
Distribution	http://www.w3.org/ns/dcat#Distribution	Recommended	format	http://purl.org/dc/terms/format
Distribution	http://www.w3.org/ns/dcat#Distribution	Recommended	licence	http://purl.org/dc/terms/license
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	access rights	http://purl.org/dc/terms/accessRights
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	access service	http://www.w3.org/ns/dcat#accessService
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	applicable legislation	http://data.europa.eu/r5r/applicableLegislation
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	availability	http://data.europa.eu/r5r/availability
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	byte size	http://www.w3.org/ns/dcat#byteSize
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	character encoding	http://www.w3.org/2011/content#characterEncoding
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	checksum	http://spdx.org/rdf/terms#checksum
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	compression format	http://www.w3.org/ns/dcat#compressFormat
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	documentation	http://xmlns.com/foaf/0.1/page
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	download URL	http://www.w3.org/ns/dcat#downloadURL
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	has policy	http://www.w3.org/ns/odrl/2/hasPolicy
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	language	http://purl.org/dc/terms/language
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	linked schemas	http://purl.org/dc/terms/conformsTo
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	media type	http://www.w3.org/ns/dcat#mediaType
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	modification date	http://purl.org/dc/terms/modified
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	packaging format	http://www.w3.org/ns/dcat#packageFormat
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	reference system	http://data.europa.eu/930/referenceSystem
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	release date	http://purl.org/dc/terms/issued
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	representation technique	http://www.w3.org/ns/adms#representationTechnique
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	rights	http://purl.org/dc/terms/rights
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	spatial resolution	http://www.w3.org/ns/dqv#hasQualityMeasurement
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	spatial resolution as text	http://data.europa.eu/930/spatialResolutionAsText
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	spatial resolution in metres	http://www.w3.org/ns/dcat#spatialResolutionInMeters
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	status	http://www.w3.org/ns/adms#status
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	temporal resolution	http://www.w3.org/ns/dcat#temporalResolution
Distribution	http://www.w3.org/ns/dcat#Distribution	Optional	title	http://purl.org/dc/terms/title
Document	http://xmlns.com/foaf/0.1/Document	Optional	description	http://purl.org/dc/terms/description
Document	http://xmlns.com/foaf/0.1/Document	Optional	title	http://purl.org/dc/terms/title
Email (vCard)	http://www.w3.org/2006/vcard/ns#Email
Entity	http://www.w3.org/ns/prov#Entity
Frequency	http://purl.org/dc/terms/Frequency
Geometry	http://www.w3.org/ns/locn#Geometry
Identifier	http://www.w3.org/ns/adms#Identifier	Mandatory	notation	http://www.w3.org/2004/02/skos/core#notation
Kind	http://www.w3.org/2006/vcard/ns#Kind	Optional	address	http://www.w3.org/2006/vcard/ns#hasAddress
Kind	http://www.w3.org/2006/vcard/ns#Kind	Optional	affiliation	http://www.w3.org/2006/vcard/ns#organization-name
Kind	http://www.w3.org/2006/vcard/ns#Kind	Optional	email	http://www.w3.org/2006/vcard/ns#hasEmail
Kind	http://www.w3.org/2006/vcard/ns#Kind	Optional	name	http://www.w3.org/2006/vcard/ns#fn
Kind	http://www.w3.org/2006/vcard/ns#Kind	Optional	phone	http://www.w3.org/2006/vcard/ns#hasTelephone
Kind	http://www.w3.org/2006/vcard/ns#Kind	Optional	URL	http://www.w3.org/2006/vcard/ns#hasURL
Legal Resource	http://data.europa.eu/eli/ontology#LegalResource
Licence Document	http://purl.org/dc/terms/LicenseDocument	Recommended	type	http://purl.org/dc/terms/type
Linguistic system	http://purl.org/dc/terms/LinguisticSystem
Literal	http://www.w3.org/2000/01/rdf-schema#Literal
Location	http://purl.org/dc/terms/Location	Recommended	bbox	http://www.w3.org/ns/dcat#bbox
Location	http://purl.org/dc/terms/Location	Recommended	centroid	http://www.w3.org/ns/dcat#centroid
Location	http://purl.org/dc/terms/Location	Optional	gazetteer	http://www.w3.org/2004/02/skos/core#inScheme
Location	http://purl.org/dc/terms/Location	Optional	geograhic identifier	http://purl.org/dc/terms/identifier
Location	http://purl.org/dc/terms/Location	Optional	geograhic name	http://www.w3.org/2004/02/skos/core#prefLabel
Location	http://purl.org/dc/terms/Location	Optional	geometry	http://www.w3.org/ns/locn#geometry
Metric	http://www.w3.org/ns/dqv#Metric	Optional	dimension	http://www.w3.org/ns/dqv#inDimension
Metric	http://www.w3.org/ns/dqv#Metric	Optional	expected data type	http://www.w3.org/ns/dqv#expectedDataType
Organisation	http://www.w3.org/ns/org#Organization
Period of time	http://purl.org/dc/terms/PeriodOfTime	Recommended	end date	http://www.w3.org/ns/dcat#endDate
Period of time	http://purl.org/dc/terms/PeriodOfTime	Recommended	start date	http://www.w3.org/ns/dcat#startDate
Period of time	http://purl.org/dc/terms/PeriodOfTime	Optional	beginning	http://www.w3.org/2006/time#hasBeginning
Period of time	http://purl.org/dc/terms/PeriodOfTime	Optional	end	http://www.w3.org/2006/time#hasEnd
Policy	http://www.w3.org/ns/odrl/2/Policy
Provenance Statement	http://purl.org/dc/terms/ProvenanceStatement	Optional	provenance statement text	http://purl.org/dc/terms/description
Quality Measurement	http://www.w3.org/ns/dqv#QualityMeasurement	Optional	is measurement of	http://www.w3.org/ns/dqv#isMeasurementOf
Quality Measurement	http://www.w3.org/ns/dqv#QualityMeasurement	Optional	unit of measure	http://purl.org/linked-data/sdmx/2009/attribute#unitMeasure
Quality Measurement	http://www.w3.org/ns/dqv#QualityMeasurement	Optional	value	http://www.w3.org/ns/dqv#value
Relationship	http://www.w3.org/ns/dcat#Relationship	Mandatory	had role	http://www.w3.org/ns/dcat#hadRole
Relationship	http://www.w3.org/ns/dcat#Relationship	Mandatory	relation	http://purl.org/dc/terms/relation
Resource	http://www.w3.org/2000/01/rdf-schema#Resource
Rights statement	http://purl.org/dc/terms/RightsStatement	Optional	rights statement text	http://purl.org/dc/terms/description
Role	http://www.w3.org/ns/dcat#Role
Standard	http://purl.org/dc/terms/Standard	Optional	creation date	http://purl.org/dc/terms/created
Standard	http://purl.org/dc/terms/Standard	Optional	description	http://purl.org/dc/terms/description
Standard	http://purl.org/dc/terms/Standard	Optional	identifier	http://purl.org/dc/terms/identifier
Standard	http://purl.org/dc/terms/Standard	Optional	reference register	http://www.w3.org/2004/02/skos/core#ínScheme
Standard	http://purl.org/dc/terms/Standard	Optional	release date	http://purl.org/dc/terms/issued
Standard	http://purl.org/dc/terms/Standard	Optional	title	http://purl.org/dc/terms/title
Standard	http://purl.org/dc/terms/Standard	Optional	type	http://purl.org/dc/terms/type
Standard	http://purl.org/dc/terms/Standard	Optional	update / modification date	http://purl.org/dc/terms/modified
Standard	http://purl.org/dc/terms/Standard	Optional	version	http://www.w3.org/2002/07/owl#versionInfo

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