Issue #14 is concerned with rules for identifying properties of INSPIRE classes that have identical semantics. The goal is to re-use property definitions in INSPIRE RDF vocabularies where appropriate and to avoid duplicate definitions.
To support this, we may want to create a common INSPIRE property dictionary, which unambiguously specifies all properties used within the INSPIRE data models. It would provide a unique place to define properties, together with any additional information like mapping to properties from external vocabularies.
Aspects to consider for such a dictionary:
How it would handle definitions from external vocabularies (e.g. if an INSPIRE property would be mapped to a property from an external vocabulary)
When it could actually be introduced
If there should only be an implicit link between properties of the INSPIRE model and dictionary entries or if the model should contain explicit link information
Description
Issue #14 is concerned with rules for identifying properties of INSPIRE classes that have identical semantics. The goal is to re-use property definitions in INSPIRE RDF vocabularies where appropriate and to avoid duplicate definitions.
To support this, we may want to create a common INSPIRE property dictionary, which unambiguously specifies all properties used within the INSPIRE data models. It would provide a unique place to define properties, together with any additional information like mapping to properties from external vocabularies.
Aspects to consider for such a dictionary: