- This application profile has the status Candidate Recommendation published at 2024-09-30. + This application profile has the status Candidate Recommendation published at 2024-10-03.
Information about the process and the decisions involved in the creation of this specification are consultable at the Changelog. @@ -23042,7 +23042,7 @@
In the following table, the starred elements (*) are used to indicate the corresponding metadata element in the core 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) |
-
-
-
|
-rdfs:Literal |
-See | -||||
|
- Resource abstract (M) -*Abstract describing the dataset (M) - |
-dct:description (M) |
-
-
-
|
-rdfs:Literal |
-See | -||||
|
- Resource type (M) -*not in ISO 19115 core - |
-
-
(see also binding for GeoDCAT-AP Extended) - |
-
+
+ |
+ |
+ INSPIRE metadata +*ISO 19115:2003 Core +ISO 19115 path +Required in INSPIRE |
+ DCAT-AP Property |
+ Domain |
+ Range |
+ Comments |
+ |
|
+ Resource title (M) +* Resource title (M) +
+ |
+
+ Datasets +Dataset series +Services + |
+
+ dct:title (M) |
+
+
+
+
+
+ |
+
+ rdfs:Literal
+ |
+ See + | +|||
|
+ Resource abstract (M) +* Abstract describing the resource (M) +
+ |
+
+ Datasets +Dataset series +Services + |
+
+ dct:description (M) |
+
-
|
-
-
(values |
-See . dcat:Catalog can be used for catalogue / discovery services, in addition to dcat:DataService. |
-
+ rdfs:Literal
+ |
+ See + | + + +|
|
+ Resource type (M) +* Hierarchy Level (C) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+ (see also binding for GeoDCAT-AP Extended) + |
+
+
+
+
+
+ |
+
+
+ (values |
+ See .
+ dcat:Catalog can be used for catalogue / discovery services, in addition to dcat:DataService.
+ |
+ |||
|
+ Resource locator (C) +*On-line resource (O) +
|
+
+ Datasets +Dataset series +Services + |
+ + | + | See . The defined encoding depends whether the resource is a service or a dataset or dataset series. Also, the value of the function code (CI_OnlineFunctionCode) is to be taken into account. |
+ ||||
+ ++ |
+ + |
+
+
+
+ |
+
+
+
+ |
+
+ foaf:Document
+ rdfs:Resource
+ foaf:Document
+ |
+ See . Properties dcat:endpointURL and dcat:endpointDescription are used when the resource locator points to a service endpoint. |
+ |||
+ ++ |
+ + |
+ dcat:landingPage (O) |
+
+
+
+ |
+
+ foaf:Document
+ |
+ See . + | +|||
+ ++ |
+ + |
+ dcat:accessURL (M) |
+
+ dcat:Distribution
+ |
+
+ rdfs:Resource
+ |
+ See . Property dcat:accessURL is also used whenever the resource locator points to a service endpoint. |
+ |||
+ ++ |
+ + |
+ foaf:page
+ |
+
+
+
+ |
+
+ foaf:Document
+ |
+ See . + | +|||
+ ++ |
+ + |
+ dcat:accessURL (M) |
+
+ dcat:Distribution
+ |
+
+ rdfs:Resource
+ |
+ See . Property dcat:accessURL is also used whenever the resource locator points to a service endpoint. |
+ |||
+ ++ |
+ + |
+ dcat:accessURL (M) |
+
+ dcat:Distribution
+ |
+
+ rdfs:Resource
+ |
+ See . Property dcat:accessURL is also used whenever the resource locator points to a service endpoint. |
+ |||
+ ++ |
+ + |
+ foaf:page
+ |
+
+
+
+ |
+
+ foaf:Document
+ |
+ See . + | +|||
|
+ Unique resource identifier (M) +* Dataset identifier (O) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series + |
+
+ dct:identifier (O) |
+
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . In RDF, this could also be represented as the URI of the dataset or of the dataset series. | +|||
|
+ Coupled resource (O) +* Operates On (O) (not in ISO 19115 core) +
|
+
+ Services + |
+
+ dcat:servesDataset (O) |
+
+
+ |
+
+
+
+ |
+ See . + | +|||
|
+ Resource language (C) +*Dataset language (M) +
|
+
+ Datasets +Dataset series + |
+
+ dct:language (O for dcat:Dataset and dcat:DatasetSeries, R for dcat:Catalog)
+ |
+
+
+
+
+ |
+
+ dct:LinguisticSystem
+ |
+ See . + | +|||
--- |
-
-
|
-+ | ||||||
|
+ Keyword (M) +* Keyword (O) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+
+ (see also binding for GeoDCAT-AP Extended) + |
+
+
+ |
+
+ rdfs:Literal
+ |
+
+ See . For datasets and dataset series, Keywords whose controlled vocabulary is the one of the INSPIRE spatial data themes are mapped to For services a syntax binding is provided in GeoDCAT-AP Extended only. + |
+ |||
|
+ Geographic bounding box (M) +* Geographic location of the resource (C) +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:spatial (O) |
+
+
+
+
+ |
+
+ dct:Location
+ |
+ See on the preferred format to be used in RDF for the representation of geometries. | +|||
|
+ Temporal reference (C) +* Temporal extent (O) +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:temporal (O) |
+
+
+
+ |
+
+ dct:PeriodOfTime
+ |
+ See . + | +|||
|
+ Temporal reference - Date of publication (C) +*Dataset reference date (M) – publication +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:issued (R for dcat:Catalog and O for dcat:Dataset and dcat:DatasetSeries)
+ |
+
+
+
+
+ |
+
+
+ Temporal Literal
+
+ |
+ See . + | +|||
|
+ Temporal reference - Date of last revision (C) +*Dataset reference date (M) – revision +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:modified (R for dcat:Catalog and O for dcat:Dataset and dcat:DatasetSeries)
+ |
+
+
+
+
+ |
+
+
+ Temporal Literal
+
+ |
+ See . + | +|||
|
+ Spatial resolution (C) +*Spatial resolution (O) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+ |
+
+
+
+ |
+
+ xsd:decimal
+ |
+ See . Property dcat:spatialResolutionInMeters can only be used when spatial resolution is expressed as distance in metres. |
+ |||
|
+ Lineage (M) +*Lineage (O) +
|
+
+ Datasets +Dataset series + |
+
+ dct:provenance (O) |
+
+
+
+ |
+
+ dct:ProvenanceStatement
+ |
+ See . + | +|||
|
+ Conformity (M) +* Report result (O) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+ (see also binding for GeoDCAT-AP Extended) + |
+
+
+
+ |
+
+ dct:Standard
+ |
+ See . dct:conformsTo can be used to specify only one of the cases supported in INSPIRE. i.e., when the degree of conformity is “conformant”. |
+ |||
|
+ Conformity Specification (M) +* Report result - Specification (O) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+
+
+
+ (see also binding for GeoDCAT-AP Extended) + |
+
+ rdfs:Resource
+ |
+
+
+ Temporal Literal
+
+ |
+ See . + | +|||
|
+ Conditions for access and use (M) +* Restrictions on the access and use of the resource (O) (not in ISO 19115 core) + |
+
+ Datasets +Dataset series +Services + |
+
+ dct:license (R for dcat:Catalog and dcat:Distribution, O for dcat:DataService), dct:rights (O) |
+
+
+
+
+ |
+
+
+ dct:LicenseDocument
+ |
+ See . + | +|||
|
+ Limitations on public access (C) +* Restrictions on the access and use of the resource (O) (not in ISO 19115 core) +
And: |
+
+ Datasets +Dataset series +Services + |
+
+ dct:accessRights (O) |
+
+
+ |
+
+ dct:RightsStatement
+ |
+ See . + | +|||
|
+ Responsible party (M) +* Responsible party (O) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+
+ |
+
+
+ |
+
+
+ |
+ 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]]. | +|||
|
+
+
+
+ |
+
+
+
+ |
+
+
+
+
+ |
+ ||||||
|
+ Encoding (M) +*Distribution format (O) +
|
+
+ Datasets +Dataset series + |
+
+ dct:format (R), dcat:mediaType (O) |
+
+ dcat:Distribution
+ |
+
+ dct:MediaTypeOrExtent
+ |
+ See . See controlled vocabularies for encoding in . + | +|||
|
+ Maintenance information (R) +* Maintenance and update frequency (not in ISO 19115 core) +
|
+ + | +
+ dct:accrualPeriodicity (O) |
+
+
+
+ |
+
+ dct:Frequency
+ |
+ See . + | +|||
|
+ - not in [[INSPIRE-MD-REG]] - +* Metadata standard +implicit element + |
+ + | +
+ dct:conformsTo (R) |
+
+
+ |
+
+ dct:Standard
+ |
+ See . This element, not existing in ISO 19115, is just meant to provide the context for the specification of the metadata standard name and version. | +|||
|
+ - not in [[INSPIRE-MD-REG]] - +* Metadata standard name (O) +
|
+ + |
+ dct:title
+ |
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . + | +|||
|
+ - not in [[INSPIRE-MD-REG]] - +* Metadata standard version (O) +
|
+ + |
+ owl:versionInfo
+ |
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . This can be part of the information specified for metadata standard name. | +|||
|
+ Metadata date (M) +*Metadata date stamp (M) +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:modified (M) |
+
+
+ |
+
+
+ Temporal Literal
+
+ |
+ See . + | +|||
|
+ Metadata language (M) +*Metadata language (C) +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:language (O) |
+
+
+ |
+
+ dct:LinguisticSystem
+ |
+ See . + | +
-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--For dataset and data series (‘download’ function code)
-
dcat:accessURL (M)dcat:Distributionrdfs:Resourcedcat:accessURL is also used whenever the resource locator points to a service endpoint.--For dataset and data series (‘information’ function code)
-
foaf:pagedcat:Dataset
dcat:DatasetSeries
foaf:DocumentThis 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 of [[ISO-19115]], for which [[DCAT-AP-3]] does not provide a fully suitable syntax binding. GeoDCAT-AP Extended therefore complements GeoDCAT-AP Core with a more complete representation beyond [[DCAT-AP-3]].
---For dataset and data series (‘offlineAccess’ function code)
-
dcat:accessURL (M)dcat:Distributionrdfs:Resourcedcat:accessURL is also used whenever the resource locator points to a service endpoint.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 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.
---For dataset and data series (‘order’ function code)
-
dcat:accessURL (M)dcat:Distributionrdfs:Resourcedcat:accessURL is also used whenever the resource locator points to a service endpoint.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 the following two categories:
---For dataset and data series (‘search’ function code)
-
foaf:pagedcat:Dataset
dcat:DatasetSeries
foaf:DocumentPartial 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]].
Unique resource identifier (M)
-*not in ISO 19115 core
-dct:identifier (O)dcat:Dataset
dcat:DatasetSeries
rdfs:LiteralCoupled resource (O)
-*not in ISO 19115 core
-dcat:servesDataset (O)dcat:DataService
dcat:Dataset
dcat:DatasetSeries
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:LinguisticSystemKeyword value (M)
-*not in ISO 19115 core
-dcat:keyword (R)
dcat:theme (R)
(see also binding for GeoDCAT-AP Extended)
dcat:Dataset
rdfs:LiteralSee . 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:LocationTemporal extent (C)
-*Additional extent information for the dataset (vertical and temporal) (O)
-dct:temporal (O)dcat:Dataset
dcat:DatasetSeries
dct:PeriodOfTimeDate 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 LiteralDate 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 LiteralSpatial resolution (C)
-*Spatial resolution of the dataset (O)
-dcat:spatialResolutionInMeters (O)
dcat:Dataset
dcat:DatasetSeries
xsd:decimaldcat: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:ProvenanceStatementConformity (M)
-*not in ISO 19115 core
-dct:conformsTo (O)
(see also binding for GeoDCAT-AP Extended)
dcat:Dataset
dcat:DatasetSeries
dct:Standarddct: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:ResourceTemporal LiteralConditions 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:LicenseDocumentLimitations on public access (C)
-*not in ISO 19115 core
-dct:accessRights (O)dcat:DataService
dct:RightsStatementResponsible party (M)
-*Dataset responsible party (O)
-dct:publisher (M)
dct:creator (O)
dcat:Catalog
foaf:Agent
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:Distributiondct:MediaTypeOrExtentMaintenance information (R)
-*not in ISO 19115 core
-dct:accrualPeriodicity (O)dcat:Dataset
dcat:DatasetSeries
dct:Frequencydct:conformsTo (R)dcat:CatalogRecord
dct:Standarddct:titledct:Standard
rdfs:Literalowl:versionInfodct:Standard
rdfs:LiteralMetadata date (M)
-*Metadata date stamp (M)
-dct:modified (M)dcat:CatalogRecord
Temporal LiteralMetadata language (M)
-*Metadata language (C)
-dct:language (O)dcat:CatalogRecord
dct:LinguisticSystemThis 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 of [[ISO-19115]], for which [[DCAT-AP-3]] does not provide a fully suitable syntax binding. GeoDCAT-AP Extended therefore complements GeoDCAT-AP Core with a more complete representation beyond [[DCAT-AP-3]].
- -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 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 the following two 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.
+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 |
-
-
|
-
|
-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 |
-
-
|
-rdfs:Literal |
-See . In RDF, this could also be represented as the URI of the resource. | -
|
- Resource language (C) -*Dataset language (M) - |
-dct:language |
-
-
|
-dct:LinguisticSystem |
-See . | -
|
- Topic category (M) -*Dataset topic category (M) - |
-geodcatap:topicCategory |
-
-
|
-
-
|
-See and the controlled vocabulary for topic category in . | -
|
- Spatial data service type (M) -*not in ISO 19115 core - |
-geodcatap:serviceType |
-
-
|
-
|
-See . See controlled vocabulary for spatial data service type in . | -
|
- Keyword value (M) -*not in ISO 19115 core - |
-
-
|
-
-
|
-
-
|
-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) |
-
-
|
-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) |
-
-
|
-dct:PeriodOfTime |
-See . | -
|
- Date of publication (C) -*Dataset reference date (M) – publication - |
-dct:issued |
-
-
|
-Temporal Literal | -See . | -
|
- Date of last revision (C) -*Dataset reference date (M) – revision - |
-dct:modified |
-
-
|
-Temporal Literal | -See . | -
|
- Date of creation (C) -*Dataset reference date (M) - creation - |
-dct:created |
-
-
|
-Temporal Literal | -See . | -
|
- Spatial resolution (C) -*Spatial resolution of the dataset (O) - |
-
-
|
-
-
|
-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:QualityMeasurement |
-||
|
-
|
-rdfs:Literal |
-|||
|
- Conformity (M) -*not in ISO 19115 core - |
-prov:wasUsedBy |
-
-
|
-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) |
-
-
|
-dct:RightsStatement |
-See . | -
|
- Responsible party (M) -*Dataset responsible party (O) - |
-
-
|
-
-
|
-foaf:Agent |
-See . | -
dcat:contactPoint |
-
-
|
-vcard:Kind |
-||
|
-
|
-
-
|
-foaf:Agent |
-||
prov:qualifiedAttribution |
-
-
|
-prov:Attribution |
-||
| Responsible party role (M) | -dcat:hadRole |
-
-
|
-dcat:Role |
-See and controlled vocabulary for responsible party role in . | -
| *Metadata file identifier (O) | -dct:identifier |
-
-
|
-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 |
-
-
|
-vcard:Kind |
-See . | -
prov:qualifiedAttribution |
-
-
|
-prov:Attribution |
-||
| *Metadata character set (C) | -- |
-- |
-- |
-Metadata in GeoDCAT-AP are always in UTF-8. See . | -
Coordinate Reference System (M) -*Reference System (0) |
-geodcatap:referenceSystem |
-
-
|
-skos:Concept |
-See . | -
Temporal Reference System (C) -*Reference System (0) |
-geodcatap:referenceSystem |
-
-
|
-skos:Concept |
-See . | -
Character Encoding (C) -*Dataset character set (C) |
-cnt:characterEncoding |
-
|
-rdfs:Literal |
-See . | -
Spatial representation type – (M) -*Spatial representation type (O) |
-adms:representationTechnique |
-dcat:Distribution |
-skos:Concept |
-See . | -
|
+ INSPIRE metadata +*ISO 19115:2003 Core Profile + |
+ Property | +Domain | +Range | +Comments | +
|
+ Resource type (M) +*not in ISO 19115 core + |
+
+ geodcatap:resourceType
+ |
+
+
+
+
+
+ |
+
+
+ |
+ 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
+ |
+
+
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . In RDF, this could also be represented as the URI of the resource. | +
|
+ Resource language (C) +*Dataset language (M) + |
+
+ dct:language
+ |
+
+
+
+ |
+
+ dct:LinguisticSystem
+ |
+ See . + | +
|
+ Topic category (M) +*Dataset topic category (M) + |
+
+ geodcatap:topicCategory
+ |
+
+
+
+
+
+ |
+
+
+ |
+ See and the controlled vocabulary for topic category in . + | +
|
+ Spatial data service type (M) +*not in ISO 19115 core + |
+
+ geodcatap:serviceType
+ |
+
+
+ |
+
+
+ |
+ See . See controlled vocabulary for spatial data service type in . + | +
|
+ Keyword value (M) +*not in ISO 19115 core + |
+
+
+
+
+ |
+
+
+
+
+ |
+
+
+
+ |
+ 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) |
+
+
+ |
+
+ 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) |
+
+
+
+ |
+
+ dct:PeriodOfTime
+ |
+ See . + | +
|
+ Date of publication (C) +*Dataset reference date (M) – publication + |
+
+ dct:issued
+ |
+
+
+ |
+ + Temporal Literal + | +See . + | +
|
+ Date of last revision (C) +*Dataset reference date (M) – revision + |
+
+ dct:modified
+ |
+
+
+ |
+ + Temporal Literal + | +See . + | +
|
+ Date of creation (C) +*Dataset reference date (M) - creation + |
+
+ dct:created
+ |
+
+
+
+
+
+ |
+ + Temporal Literal + | +See . + | +
|
+ Spatial resolution (C) +*Spatial resolution of the dataset (O) + |
+
+
+ |
+
+
+
+ |
+
+ 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:QualityMeasurement
+ |
+ ||
|
+
+ |
+
+ rdfs:Literal
+ |
+ |||
|
+ Conformity (M) +*not in ISO 19115 core + |
+
+ prov:wasUsedBy
+ |
+
+
+
+
+
+ |
+
+ 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) |
+
+
+
+
+ |
+
+ dct:RightsStatement
+ |
+ See . + | +
|
+ Responsible party (M) +*Dataset responsible party (O) + |
+
+
+
+ |
+
+
+
+ |
+
+ foaf:Agent
+ |
+ See . + | +
+ dcat:contactPoint
+ |
+
+
+
+
+ |
+
+ vcard:Kind
+ |
+ ||
|
+
+
+
+
+
+
+
+
+ |
+
+
+
+
+
+
+ |
+
+ foaf:Agent
+ |
+ ||
+ prov:qualifiedAttribution
+ |
+
+
+
+
+
+
+
+ |
+
+ prov:Attribution
+ |
+ ||
| Responsible party role (M) | +
+ dcat:hadRole
+ |
+
+
+ |
+
+ dcat:Role
+ |
+ See and controlled vocabulary for responsible party role in . + | +
| *Metadata file identifier (O) | +
+ dct:identifier
+ |
+
+
+ |
+
+ 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
+ |
+
+
+ |
+
+ vcard:Kind
+ |
+ See . + | +
+ prov:qualifiedAttribution
+ |
+
+
+ |
+
+ prov:Attribution
+ |
+ ||
| *Metadata character set (C) | +
+ - + |
+
+ - + |
+
+ - + |
+ Metadata in GeoDCAT-AP are always in UTF-8. See . + | +
|
+ Coordinate Reference System (M) +*Reference System (0) + |
+
+ geodcatap:referenceSystem
+ |
+
+
+
+
+
+
+ |
+
+ skos:Concept
+ |
+ See . + | +
|
+ Temporal Reference System (C) +*Reference System (0) + |
+
+ geodcatap:referenceSystem
+ |
+
+
+
+
+
+
+ |
+
+ skos:Concept
+ |
+ See . + | +
|
+ Character Encoding (C) +*Dataset character set (C) + |
+
+ cnt:characterEncoding
+ |
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . + | +
|
+ Spatial representation type – (M) +*Spatial representation type (O) + |
+
+ adms:representationTechnique
+ |
+
+ dcat:Distribution
+ |
+
+ skos:Concept
+ |
+ See . + | +
The following table provides an overview of the metadata elements in the INSPIRE metadata schema and in the core 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.
+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 | -
|---|---|---|---|---|---|
| INSPIRE | +Obligation | +ISO 19115 Core | +Obligation | +DCAT-AP | +GeoDCAT-AP | +
| Metadata point of contact | -M | -Metadata point of contact | -M | -- | Yes | -
| Metadata date | -M | -Metadata date stamp | -M | -Yes | -Yes | -
| Metadata language | -M | -Metadata language | -C | -Yes | -Yes | -
| - | - | Metadata character set | -C | -- - | Always UTF-8 | -
| - | - | Metadata file identifier | -O | -- | Yes | -
| - | - | Metadata standard name | -O | -- | Yes | -
| - | - | Metadata standard version | -O | -- | Yes | -
| Resource title | -M | -Dataset title | -M | -Yes | -Yes | -
| Temporal reference - Date of creation / publication / last revision | -C | -Dataset reference date | -M | -Partially (creation date not included) | -Yes | -
| Resource abstract | -M | -Abstract describing the dataset | -M | -Yes | -Yes | -
| Resource language | -C | -Dataset language | -M | -Yes | -Yes | -
| Topic category | -M | -Dataset topic category | -M | -- | Yes | -
| Geographic bounding box | -M | -Geographic location of the dataset (by four coordinates or by geographic identifier) | -C | -Yes | -Yes | -
| Character encoding | -C | -Dataset character set | -C | -- | Yes | -
| Temporal reference - Temporal extent | -C | -Additional extent information for the dataset (vertical and temporal) | -O | -Partially (temporal extent only) | -Partially (temporal extent only) | -
| Lineage | -M | -Lineage | -O | -Yes | -Yes | -
| Spatial representation type | -M | -Spatial representation type | -O | -- | Yes | -
| Encoding | -M | -Distribution format | -O | -Yes | -Yes | -
| Spatial resolution | -C | -Spatial resolution of the dataset | -O | -Yes (but only as horizontal ground distance) | -Yes | -
| Responsible organisation | -M | -Dataset responsible party | -O | -Partially (only 3 of the 11 responsible party roles are supported) | -Yes | -
| Resource locator | -C | -On-line resource | -O | -Yes | -Yes | -
| Coordinate reference system; Temporal reference system | -M; C | -Reference system | -O | -- | Yes | -
| Conformity | -M | -- | - | Yes | -Yes | -
| Resource type | -M | -- | - | Yes | -Yes | -
| Spatial data service type | -M | -- | - | - | Yes | -
| Keyword | -M | -- | - | Partially (only for datasets and dataset series) | -Yes | -
| Coupled resource | -C | -- | - | Yes | -Yes | -
| Unique resource identifier | -M | -- | - | Yes | -Yes | -
| Conditions for access and use | -M | -- | - | Yes | -Yes | -
| Limitations on public access | -M | -- | - | Yes | -Yes | -
| Maintenance information | -O | -- | - | Partially (only maintenance and update frequency) | -Partially (only maintenance and update frequency) | -
| Data quality – Logical consistency – Topological consistency | -C | -- | - | - | Partially (only conformance results) | -
| Data quality – Logical consistency – Conceptual consistency | -O | -- | - | - | Partially (only conformance results) | -
| Data quality – Logical consistency – Domain consistency | -O | -- | - | - | Partially (only conformance results) | -
| Metadata 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) | +
| ISO 19115 – CI_OnlineFunctionCode | +ISO 19115 – CI_OnlineFunctionCode | Description |
|---|
| ISO 19115 – CI_OnlineFunctionCode | +ISO 19115 – CI_OnlineFunctionCode | Property | Domain | Range | @@ -26622,10 +27405,10 @@
|---|
| ISO 19115 - MD_CharacterSetCode | +ISO 19115 - MD_CharacterSetCode | Description | IANA | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ISO 19115 Core | +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 | +ISO 19115-1:2014 Discovery metadata for datasets and series (Table F.1) | +ISO 19115-1:2014 Path |
| ISO 19115 Core | +ISO 19115 Core | INSPIRE | -ISO 19115-1:2014 Discovery metadata for services (Table F.2) | -Path ISO 19115-1:2014 | +ISO 19115-1:2014 Discovery metadata for services (Table F.2) | +Path ISO 19115-1:2014 |
|---|
|
- INSPIRE metadata -*ISO 19115:2003 Core Profile - |
-DCAT-AP Property | -Domain | -Range | -Comments | -||||
|---|---|---|---|---|---|---|---|---|
|
- Resource title (M) -*Dataset title (M) - |
-dct:title (M) |
-
-
-
|
-rdfs:Literal |
-See | -||||
|
- Resource abstract (M) -*Abstract describing the dataset (M) - |
-dct:description (M) |
-
-
-
|
-rdfs:Literal |
-See | -||||
|
- Resource type (M) -*not in ISO 19115 core - |
-
-
(see also binding for GeoDCAT-AP Extended) - |
-
+
+ |
+ |
+ INSPIRE metadata +*ISO 19115:2003 Core +ISO 19115 path +Required in INSPIRE |
+ DCAT-AP Property |
+ Domain |
+ Range |
+ Comments |
+ |
|
+ Resource title (M) +* Resource title (M) +
+ |
+
+ Datasets +Dataset series +Services + |
+
+ dct:title (M) |
+
+
+
+
+
+ |
+
+ rdfs:Literal
+ |
+ See + | +|||
|
+ Resource abstract (M) +* Abstract describing the resource (M) +
+ |
+
+ Datasets +Dataset series +Services + |
+
+ dct:description (M) |
+
-
|
-
-
(values |
-See . dcat:Catalog can be used for catalogue / discovery services, in addition to dcat:DataService. |
-
+ rdfs:Literal
+ |
+ See + | + + +|
|
+ Resource type (M) +* Hierarchy Level (C) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+ (see also binding for GeoDCAT-AP Extended) + |
+
+
+
+
+
+ |
+
+
+ (values |
+ See .
+ dcat:Catalog can be used for catalogue / discovery services, in addition to dcat:DataService.
+ |
+ |||
|
+ Resource locator (C) +*On-line resource (O) +
|
+
+ Datasets +Dataset series +Services + |
+ + | + | See . The defined encoding depends whether the resource is a service or a dataset or dataset series. Also, the value of the function code (CI_OnlineFunctionCode) is to be taken into account. |
+ ||||
+ ++ |
+ + |
+
+
+
+ |
+
+
+
+ |
+
+ foaf:Document
+ rdfs:Resource
+ foaf:Document
+ |
+ See . Properties dcat:endpointURL and dcat:endpointDescription are used when the resource locator points to a service endpoint. |
+ |||
+ ++ |
+ + |
+ dcat:landingPage (O) |
+
+
+
+ |
+
+ foaf:Document
+ |
+ See . + | +|||
+ ++ |
+ + |
+ dcat:accessURL (M) |
+
+ dcat:Distribution
+ |
+
+ rdfs:Resource
+ |
+ See . Property dcat:accessURL is also used whenever the resource locator points to a service endpoint. |
+ |||
+ ++ |
+ + |
+ foaf:page
+ |
+
+
+
+ |
+
+ foaf:Document
+ |
+ See . + | +|||
+ ++ |
+ + |
+ dcat:accessURL (M) |
+
+ dcat:Distribution
+ |
+
+ rdfs:Resource
+ |
+ See . Property dcat:accessURL is also used whenever the resource locator points to a service endpoint. |
+ |||
+ ++ |
+ + |
+ dcat:accessURL (M) |
+
+ dcat:Distribution
+ |
+
+ rdfs:Resource
+ |
+ See . Property dcat:accessURL is also used whenever the resource locator points to a service endpoint. |
+ |||
+ ++ |
+ + |
+ foaf:page
+ |
+
+
+
+ |
+
+ foaf:Document
+ |
+ See . + | +|||
|
+ Unique resource identifier (M) +* Dataset identifier (O) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series + |
+
+ dct:identifier (O) |
+
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . In RDF, this could also be represented as the URI of the dataset or of the dataset series. | +|||
|
+ Coupled resource (O) +* Operates On (O) (not in ISO 19115 core) +
|
+
+ Services + |
+
+ dcat:servesDataset (O) |
+
+
+ |
+
+
+
+ |
+ See . + | +|||
|
+ Resource language (C) +*Dataset language (M) +
|
+
+ Datasets +Dataset series + |
+
+ dct:language (O for dcat:Dataset and dcat:DatasetSeries, R for dcat:Catalog)
+ |
+
+
+
+
+ |
+
+ dct:LinguisticSystem
+ |
+ See . + | +|||
--- |
-
-
|
-+ | ||||||
|
+ Keyword (M) +* Keyword (O) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+
+ (see also binding for GeoDCAT-AP Extended) + |
+
+
+ |
+
+ rdfs:Literal
+ |
+
+ See . For datasets and dataset series, Keywords whose controlled vocabulary is the one of the INSPIRE spatial data themes are mapped to For services a syntax binding is provided in GeoDCAT-AP Extended only. + |
+ |||
|
+ Geographic bounding box (M) +* Geographic location of the resource (C) +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:spatial (O) |
+
+
+
+
+ |
+
+ dct:Location
+ |
+ See on the preferred format to be used in RDF for the representation of geometries. | +|||
|
+ Temporal reference (C) +* Temporal extent (O) +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:temporal (O) |
+
+
+
+ |
+
+ dct:PeriodOfTime
+ |
+ See . + | +|||
|
+ Temporal reference - Date of publication (C) +*Dataset reference date (M) – publication +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:issued (R for dcat:Catalog and O for dcat:Dataset and dcat:DatasetSeries)
+ |
+
+
+
+
+ |
+
+
+ Temporal Literal
+
+ |
+ See . + | +|||
|
+ Temporal reference - Date of last revision (C) +*Dataset reference date (M) – revision +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:modified (R for dcat:Catalog and O for dcat:Dataset and dcat:DatasetSeries)
+ |
+
+
+
+
+ |
+
+
+ Temporal Literal
+
+ |
+ See . + | +|||
|
+ Spatial resolution (C) +*Spatial resolution (O) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+ |
+
+
+
+ |
+
+ xsd:decimal
+ |
+ See . Property dcat:spatialResolutionInMeters can only be used when spatial resolution is expressed as distance in metres. |
+ |||
|
+ Lineage (M) +*Lineage (O) +
|
+
+ Datasets +Dataset series + |
+
+ dct:provenance (O) |
+
+
+
+ |
+
+ dct:ProvenanceStatement
+ |
+ See . + | +|||
|
+ Conformity (M) +* Report result (O) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+ (see also binding for GeoDCAT-AP Extended) + |
+
+
+
+ |
+
+ dct:Standard
+ |
+ See . dct:conformsTo can be used to specify only one of the cases supported in INSPIRE. i.e., when the degree of conformity is “conformant”. |
+ |||
|
+ Conformity Specification (M) +* Report result - Specification (O) (not in ISO 19115 core) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+
+
+
+ (see also binding for GeoDCAT-AP Extended) + |
+
+ rdfs:Resource
+ |
+
+
+ Temporal Literal
+
+ |
+ See . + | +|||
|
+ Conditions for access and use (M) +* Restrictions on the access and use of the resource (O) (not in ISO 19115 core) + |
+
+ Datasets +Dataset series +Services + |
+
+ dct:license (R for dcat:Catalog and dcat:Distribution, O for dcat:DataService), dct:rights (O) |
+
+
+
+
+ |
+
+
+ dct:LicenseDocument
+ |
+ See . + | +|||
|
+ Limitations on public access (C) +* Restrictions on the access and use of the resource (O) (not in ISO 19115 core) +
And: |
+
+ Datasets +Dataset series +Services + |
+
+ dct:accessRights (O) |
+
+
+ |
+
+ dct:RightsStatement
+ |
+ See . + | +|||
|
+ Responsible party (M) +* Responsible party (O) +
|
+
+ Datasets +Dataset series +Services + |
+
+
+
+ |
+
+
+ |
+
+
+ |
+ 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]]. | +|||
|
+
+
+
+ |
+
+
+
+ |
+
+
+
+
+ |
+ ||||||
|
+ Encoding (M) +*Distribution format (O) +
|
+
+ Datasets +Dataset series + |
+
+ dct:format (R), dcat:mediaType (O) |
+
+ dcat:Distribution
+ |
+
+ dct:MediaTypeOrExtent
+ |
+ See . See controlled vocabularies for encoding in . + | +|||
|
+ Maintenance information (R) +* Maintenance and update frequency (not in ISO 19115 core) +
|
+ + | +
+ dct:accrualPeriodicity (O) |
+
+
+
+ |
+
+ dct:Frequency
+ |
+ See . + | +|||
|
+ - not in [[INSPIRE-MD-REG]] - +* Metadata standard +implicit element + |
+ + | +
+ dct:conformsTo (R) |
+
+
+ |
+
+ dct:Standard
+ |
+ See . This element, not existing in ISO 19115, is just meant to provide the context for the specification of the metadata standard name and version. | +|||
|
+ - not in [[INSPIRE-MD-REG]] - +* Metadata standard name (O) +
|
+ + |
+ dct:title
+ |
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . + | +|||
|
+ - not in [[INSPIRE-MD-REG]] - +* Metadata standard version (O) +
|
+ + |
+ owl:versionInfo
+ |
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . This can be part of the information specified for metadata standard name. | +|||
|
+ Metadata date (M) +*Metadata date stamp (M) +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:modified (M) |
+
+
+ |
+
+
+ Temporal Literal
+
+ |
+ See . + | +|||
|
+ Metadata language (M) +*Metadata language (C) +
|
+
+ Datasets +Dataset series +Services + |
+
+ dct:language (O) |
+
+
+ |
+
+ dct:LinguisticSystem
+ |
+ See . + | +
-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--For dataset and data series (‘download’ function code)
-
dcat:accessURL (M)dcat:Distributionrdfs:Resourcedcat:accessURL is also used whenever the resource locator points to a service endpoint.--For dataset and data series (‘information’ function code)
-
foaf:pagedcat:Dataset
dcat:DatasetSeries
foaf:DocumentThis 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 of [[ISO-19115]], for which [[DCAT-AP-3]] does not provide a fully suitable syntax binding. GeoDCAT-AP Extended therefore complements GeoDCAT-AP Core with a more complete representation beyond [[DCAT-AP-3]].
---For dataset and data series (‘offlineAccess’ function code)
-
dcat:accessURL (M)dcat:Distributionrdfs:Resourcedcat:accessURL is also used whenever the resource locator points to a service endpoint.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 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.
---For dataset and data series (‘order’ function code)
-
dcat:accessURL (M)dcat:Distributionrdfs:Resourcedcat:accessURL is also used whenever the resource locator points to a service endpoint.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 the following two categories:
---For dataset and data series (‘search’ function code)
-
foaf:pagedcat:Dataset
dcat:DatasetSeries
foaf:DocumentPartial 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]].
Unique resource identifier (M)
-*not in ISO 19115 core
-dct:identifier (O)dcat:Dataset
dcat:DatasetSeries
rdfs:LiteralCoupled resource (O)
-*not in ISO 19115 core
-dcat:servesDataset (O)dcat:DataService
dcat:Dataset
dcat:DatasetSeries
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:LinguisticSystemKeyword value (M)
-*not in ISO 19115 core
-dcat:keyword (R)
dcat:theme (R)
(see also binding for GeoDCAT-AP Extended)
dcat:Dataset
rdfs:LiteralSee . 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:LocationTemporal extent (C)
-*Additional extent information for the dataset (vertical and temporal) (O)
-dct:temporal (O)dcat:Dataset
dcat:DatasetSeries
dct:PeriodOfTimeDate 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 LiteralDate 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 LiteralSpatial resolution (C)
-*Spatial resolution of the dataset (O)
-dcat:spatialResolutionInMeters (O)
dcat:Dataset
dcat:DatasetSeries
xsd:decimaldcat: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:ProvenanceStatementConformity (M)
-*not in ISO 19115 core
-dct:conformsTo (O)
(see also binding for GeoDCAT-AP Extended)
dcat:Dataset
dcat:DatasetSeries
dct:Standarddct: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:ResourceTemporal LiteralConditions 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:LicenseDocumentLimitations on public access (C)
-*not in ISO 19115 core
-dct:accessRights (O)dcat:DataService
dct:RightsStatementResponsible party (M)
-*Dataset responsible party (O)
-dct:publisher (M)
dct:creator (O)
dcat:Catalog
foaf:Agent
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:Distributiondct:MediaTypeOrExtentMaintenance information (R)
-*not in ISO 19115 core
-dct:accrualPeriodicity (O)dcat:Dataset
dcat:DatasetSeries
dct:Frequencydct:conformsTo (R)dcat:CatalogRecord
dct:Standarddct:titledct:Standard
rdfs:Literalowl:versionInfodct:Standard
rdfs:LiteralMetadata date (M)
-*Metadata date stamp (M)
-dct:modified (M)dcat:CatalogRecord
Temporal LiteralMetadata language (M)
-*Metadata language (C)
-dct:language (O)dcat:CatalogRecord
dct:LinguisticSystemThis 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 of [[ISO-19115]], for which [[DCAT-AP-3]] does not provide a fully suitable syntax binding. GeoDCAT-AP Extended therefore complements GeoDCAT-AP Core with a more complete representation beyond [[DCAT-AP-3]].
- -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 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 the following two 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.
+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 |
-
-
|
-
|
-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 |
-
-
|
-rdfs:Literal |
-See . In RDF, this could also be represented as the URI of the resource. | -
|
- Resource language (C) -*Dataset language (M) - |
-dct:language |
-
-
|
-dct:LinguisticSystem |
-See . | -
|
- Topic category (M) -*Dataset topic category (M) - |
-geodcatap:topicCategory |
-
-
|
-
-
|
-See and the controlled vocabulary for topic category in . | -
|
- Spatial data service type (M) -*not in ISO 19115 core - |
-geodcatap:serviceType |
-
-
|
-
|
-See . See controlled vocabulary for spatial data service type in . | -
|
- Keyword value (M) -*not in ISO 19115 core - |
-
-
|
-
-
|
-
-
|
-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) |
-
-
|
-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) |
-
-
|
-dct:PeriodOfTime |
-See . | -
|
- Date of publication (C) -*Dataset reference date (M) – publication - |
-dct:issued |
-
-
|
-Temporal Literal | -See . | -
|
- Date of last revision (C) -*Dataset reference date (M) – revision - |
-dct:modified |
-
-
|
-Temporal Literal | -See . | -
|
- Date of creation (C) -*Dataset reference date (M) - creation - |
-dct:created |
-
-
|
-Temporal Literal | -See . | -
|
- Spatial resolution (C) -*Spatial resolution of the dataset (O) - |
-
-
|
-
-
|
-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:QualityMeasurement |
-||
|
-
|
-rdfs:Literal |
-|||
|
- Conformity (M) -*not in ISO 19115 core - |
-prov:wasUsedBy |
-
-
|
-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) |
-
-
|
-dct:RightsStatement |
-See . | -
|
- Responsible party (M) -*Dataset responsible party (O) - |
-
-
|
-
-
|
-foaf:Agent |
-See . | -
dcat:contactPoint |
-
-
|
-vcard:Kind |
-||
|
-
|
-
-
|
-foaf:Agent |
-||
prov:qualifiedAttribution |
-
-
|
-prov:Attribution |
-||
| Responsible party role (M) | -dcat:hadRole |
-
-
|
-dcat:Role |
-See and controlled vocabulary for responsible party role in . | -
| *Metadata file identifier (O) | -dct:identifier |
-
-
|
-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 |
-
-
|
-vcard:Kind |
-See . | -
prov:qualifiedAttribution |
-
-
|
-prov:Attribution |
-||
| *Metadata character set (C) | -- |
-- |
-- |
-Metadata in GeoDCAT-AP are always in UTF-8. See . | -
Coordinate Reference System (M) -*Reference System (0) |
-geodcatap:referenceSystem |
-
-
|
-skos:Concept |
-See . | -
Temporal Reference System (C) -*Reference System (0) |
-geodcatap:referenceSystem |
-
-
|
-skos:Concept |
-See . | -
Character Encoding (C) -*Dataset character set (C) |
-cnt:characterEncoding |
-
|
-rdfs:Literal |
-See . | -
Spatial representation type – (M) -*Spatial representation type (O) |
-adms:representationTechnique |
-dcat:Distribution |
-skos:Concept |
-See . | -
|
+ INSPIRE metadata +*ISO 19115:2003 Core Profile + |
+ Property | +Domain | +Range | +Comments | +
|
+ Resource type (M) +*not in ISO 19115 core + |
+
+ geodcatap:resourceType
+ |
+
+
+
+
+
+ |
+
+
+ |
+ 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
+ |
+
+
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . In RDF, this could also be represented as the URI of the resource. | +
|
+ Resource language (C) +*Dataset language (M) + |
+
+ dct:language
+ |
+
+
+
+ |
+
+ dct:LinguisticSystem
+ |
+ See . + | +
|
+ Topic category (M) +*Dataset topic category (M) + |
+
+ geodcatap:topicCategory
+ |
+
+
+
+
+
+ |
+
+
+ |
+ See and the controlled vocabulary for topic category in . + | +
|
+ Spatial data service type (M) +*not in ISO 19115 core + |
+
+ geodcatap:serviceType
+ |
+
+
+ |
+
+
+ |
+ See . See controlled vocabulary for spatial data service type in . + | +
|
+ Keyword value (M) +*not in ISO 19115 core + |
+
+
+
+
+ |
+
+
+
+
+ |
+
+
+
+ |
+ 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) |
+
+
+ |
+
+ 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) |
+
+
+
+ |
+
+ dct:PeriodOfTime
+ |
+ See . + | +
|
+ Date of publication (C) +*Dataset reference date (M) – publication + |
+
+ dct:issued
+ |
+
+
+ |
+ + Temporal Literal + | +See . + | +
|
+ Date of last revision (C) +*Dataset reference date (M) – revision + |
+
+ dct:modified
+ |
+
+
+ |
+ + Temporal Literal + | +See . + | +
|
+ Date of creation (C) +*Dataset reference date (M) - creation + |
+
+ dct:created
+ |
+
+
+
+
+
+ |
+ + Temporal Literal + | +See . + | +
|
+ Spatial resolution (C) +*Spatial resolution of the dataset (O) + |
+
+
+ |
+
+
+
+ |
+
+ 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:QualityMeasurement
+ |
+ ||
|
+
+ |
+
+ rdfs:Literal
+ |
+ |||
|
+ Conformity (M) +*not in ISO 19115 core + |
+
+ prov:wasUsedBy
+ |
+
+
+
+
+
+ |
+
+ 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) |
+
+
+
+
+ |
+
+ dct:RightsStatement
+ |
+ See . + | +
|
+ Responsible party (M) +*Dataset responsible party (O) + |
+
+
+
+ |
+
+
+
+ |
+
+ foaf:Agent
+ |
+ See . + | +
+ dcat:contactPoint
+ |
+
+
+
+
+ |
+
+ vcard:Kind
+ |
+ ||
|
+
+
+
+
+
+
+
+
+ |
+
+
+
+
+
+
+ |
+
+ foaf:Agent
+ |
+ ||
+ prov:qualifiedAttribution
+ |
+
+
+
+
+
+
+
+ |
+
+ prov:Attribution
+ |
+ ||
| Responsible party role (M) | +
+ dcat:hadRole
+ |
+
+
+ |
+
+ dcat:Role
+ |
+ See and controlled vocabulary for responsible party role in . + | +
| *Metadata file identifier (O) | +
+ dct:identifier
+ |
+
+
+ |
+
+ 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
+ |
+
+
+ |
+
+ vcard:Kind
+ |
+ See . + | +
+ prov:qualifiedAttribution
+ |
+
+
+ |
+
+ prov:Attribution
+ |
+ ||
| *Metadata character set (C) | +
+ - + |
+
+ - + |
+
+ - + |
+ Metadata in GeoDCAT-AP are always in UTF-8. See . + | +
|
+ Coordinate Reference System (M) +*Reference System (0) + |
+
+ geodcatap:referenceSystem
+ |
+
+
+
+
+
+
+ |
+
+ skos:Concept
+ |
+ See . + | +
|
+ Temporal Reference System (C) +*Reference System (0) + |
+
+ geodcatap:referenceSystem
+ |
+
+
+
+
+
+
+ |
+
+ skos:Concept
+ |
+ See . + | +
|
+ Character Encoding (C) +*Dataset character set (C) + |
+
+ cnt:characterEncoding
+ |
+
+
+ |
+
+ rdfs:Literal
+ |
+ See . + | +
|
+ Spatial representation type – (M) +*Spatial representation type (O) + |
+
+ adms:representationTechnique
+ |
+
+ dcat:Distribution
+ |
+
+ skos:Concept
+ |
+ See . + | +
The following table provides an overview of the metadata elements in the INSPIRE metadata schema and in the core 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.
+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 | -
|---|---|---|---|---|---|
| INSPIRE | +Obligation | +ISO 19115 Core | +Obligation | +DCAT-AP | +GeoDCAT-AP | +
| Metadata point of contact | -M | -Metadata point of contact | -M | -- | Yes | -
| Metadata date | -M | -Metadata date stamp | -M | -Yes | -Yes | -
| Metadata language | -M | -Metadata language | -C | -Yes | -Yes | -
| - | - | Metadata character set | -C | -- - | Always UTF-8 | -
| - | - | Metadata file identifier | -O | -- | Yes | -
| - | - | Metadata standard name | -O | -- | Yes | -
| - | - | Metadata standard version | -O | -- | Yes | -
| Resource title | -M | -Dataset title | -M | -Yes | -Yes | -
| Temporal reference - Date of creation / publication / last revision | -C | -Dataset reference date | -M | -Partially (creation date not included) | -Yes | -
| Resource abstract | -M | -Abstract describing the dataset | -M | -Yes | -Yes | -
| Resource language | -C | -Dataset language | -M | -Yes | -Yes | -
| Topic category | -M | -Dataset topic category | -M | -- | Yes | -
| Geographic bounding box | -M | -Geographic location of the dataset (by four coordinates or by geographic identifier) | -C | -Yes | -Yes | -
| Character encoding | -C | -Dataset character set | -C | -- | Yes | -
| Temporal reference - Temporal extent | -C | -Additional extent information for the dataset (vertical and temporal) | -O | -Partially (temporal extent only) | -Partially (temporal extent only) | -
| Lineage | -M | -Lineage | -O | -Yes | -Yes | -
| Spatial representation type | -M | -Spatial representation type | -O | -- | Yes | -
| Encoding | -M | -Distribution format | -O | -Yes | -Yes | -
| Spatial resolution | -C | -Spatial resolution of the dataset | -O | -Yes (but only as horizontal ground distance) | -Yes | -
| Responsible organisation | -M | -Dataset responsible party | -O | -Partially (only 3 of the 11 responsible party roles are supported) | -Yes | -
| Resource locator | -C | -On-line resource | -O | -Yes | -Yes | -
| Coordinate reference system; Temporal reference system | -M; C | -Reference system | -O | -- | Yes | -
| Conformity | -M | -- | - | Yes | -Yes | -
| Resource type | -M | -- | - | Yes | -Yes | -
| Spatial data service type | -M | -- | - | - | Yes | -
| Keyword | -M | -- | - | Partially (only for datasets and dataset series) | -Yes | -
| Coupled resource | -C | -- | - | Yes | -Yes | -
| Unique resource identifier | -M | -- | - | Yes | -Yes | -
| Conditions for access and use | -M | -- | - | Yes | -Yes | -
| Limitations on public access | -M | -- | - | Yes | -Yes | -
| Maintenance information | -O | -- | - | Partially (only maintenance and update frequency) | -Partially (only maintenance and update frequency) | -
| Data quality – Logical consistency – Topological consistency | -C | -- | - | - | Partially (only conformance results) | -
| Data quality – Logical consistency – Conceptual consistency | -O | -- | - | - | Partially (only conformance results) | -
| Data quality – Logical consistency – Domain consistency | -O | -- | - | - | Partially (only conformance results) | -
| Metadata 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) | +
| ISO 19115 – CI_OnlineFunctionCode | +ISO 19115 – CI_OnlineFunctionCode | Description |
|---|
| ISO 19115 – CI_OnlineFunctionCode | +ISO 19115 – CI_OnlineFunctionCode | Property | Domain | Range | @@ -26622,10 +27405,10 @@
|---|
| ISO 19115 - MD_CharacterSetCode | +ISO 19115 - MD_CharacterSetCode | Description | IANA | |||
|---|---|---|---|---|---|---|
| ISO 19115 Core | +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 | +ISO 19115-1:2014 Discovery metadata for datasets and series (Table F.1) | +ISO 19115-1:2014 Path |
| ISO 19115 Core | +ISO 19115 Core | INSPIRE | -ISO 19115-1:2014 Discovery metadata for services (Table F.2) | -Path ISO 19115-1:2014 | +ISO 19115-1:2014 Discovery metadata for services (Table F.2) | +Path ISO 19115-1:2014 |
|---|