It is good practice to manage code lists separately from an application schema. In INSPIRE, code lists are managed in the INSPIRE code list register and other registries. The INSPIRE code list register supports representations in different formats (including RDF/XML) through content negotiation.
We propose that the RDF/XML representation of INSPIRE code lists shall model these code lists using skos:ConceptScheme and code list values using skos:Concept. This includes extensions to INSPIRE code lists.
NOTE 1: Extensions of INSPIRE code lists can be published / mirrored in the INSPIRE registry. However, it is questionable if this is feasible for dynamic or very large lists.
NOTE 2: Guidelines for setting up registers for additional code list values and how to register additional values in these registers is currently being discussed in the INSPIRE working group on registers and registries.
Description
It is good practice to manage code lists separately from an application schema. In INSPIRE, code lists are managed in the INSPIRE code list register and other registries. The INSPIRE code list register supports representations in different formats (including RDF/XML) through content negotiation.
We propose that the RDF/XML representation of INSPIRE code lists shall model these code lists using skos:ConceptScheme and code list values using skos:Concept. This includes extensions to INSPIRE code lists.
NOTE 1: Extensions of INSPIRE code lists can be published / mirrored in the INSPIRE registry. However, it is questionable if this is feasible for dynamic or very large lists.
NOTE 2: Guidelines for setting up registers for additional code list values and how to register additional values in these registers is currently being discussed in the INSPIRE working group on registers and registries.
Discussion Item
Any comments to the proposal?