INSPIRE Base Types

Created 3 years ago
197 statements

This is a draft RDF vocabulary for representing spatial data sets in INSPIRE as RDF. This vocabulary has been created using the “Guidelines for the RDF encoding of spatial data”.

The use of RDF is optional and does not supersede or replace the requirements regarding encoding specified in Clause 9 of the INSPIRE Data Specifications. This optional encoding is intended to support the e-government and open data community in Europe, which is increasingly looking at RDF to represent data.

This is a draft version. It has limitations and is expected to contain errors. Please report any issues or concerns in GitHub.

This ontology contains classes and properties that have been derived from the INSPIRE Base Types & Base Types2 application schemas. Additional classes implement types from the INSPIRE foundation schemas for which no suitable ontology representation has been identified yet.

The following properties with global scope (see guidelines for further details) have been added to this ontology, for re-use by importing ontologies:

  • beginLifespanVersion
  • endLifespanVersion
  • validFrom
  • validTo

During the derivation, the following mappings, alignments, and omissions have been applied:

  • Mappings:

    • Code list and enumeration values are mapped to skos:Concept.
    • Type Identifier is mapped to rdfs:Resource.
    • Type SpatialDataSet is mapped to dcat:Dataset.
    • Type PT_FreeText is mapped to rdf:langString.
    • Type TM_Position is mapped to time:TemporalPosition.
  • Alignments (through subsumption):

    • Property Contact.address is aligned to property locn:address.
  • Omissions:

    • The types Identifier and SpatialDataSet have not been converted. They are mapped as described before.
    • Property has been omitted. A value for this property can be encoded using the DC-Terms properties ‘created’, ‘issued’, and ‘modified’. See the guidelines for further details.

Version: 1.0.0