search

inspire-eu-rdf / inspire-rdf-guidelines

INSPIRE data in RDF
http://inspire-eu-rdf.github.io/inspire-rdf-guidelines/
13 stars 4 forks source link

RDF guideliness and data specifications #34

Closed nicky508 closed 7 years ago

nicky508 commented 7 years ago

Currently we have been working on a cadastral dataset.

The RDF guideliness maintain:

"This document specifies an experimental encoding rule for representing spatial data sets in INSPIRE as RDF. The use of RDF is optional and does not supersede or replace the requirements regarding encoding specified in Clause 9 of the 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."

Does this mean that the data still has to comply to the data specifications? If so, a lot of data in the dataset will be lost, because of the compliance which is demanded by the specification. While RDF can be the solution to capture the more rich data in the inspire dataset.

jechterhoff commented 7 years ago

As far as I'm concerned, the cadastral information that is covered by the INSPIRE data specifications (like Cadastral Parcels) should be represented as defined by the INSPIRE RDF guidelines and draft vocabularies.

For example, if the dataset contains a cadastral parcel, encode it as a cp:CadastralParcel with applicable properties like cp:CadastralParcel.geometry.

If your dataset contains more data (than what is covered by the INSPIRE schemas), then you are certainly allowed to add that in any way you see fit

jechterhoff commented 7 years ago

Extensions are allowed. We added another section on this topic to the guidelines.