Corrigendum #2597

Harmonise extensibility of code lists

Added by Alessandro Sarretta almost 5 years ago. Updated over 4 years ago.

Status:New
Priority:Normal
Assignee:-
Category:-
Target version:-
Corrigendum:An harmonisation of the extensibility used in the codelists is needed, given the misalignments present among Technical Guidelines, Implementing Rules, UML models, Registry. This issue has been reported for the INSPIRE Environmental Monitoring Facilities but it could be present in other themes.
In case of EMF, the extensibility should be defined as "none", as described in the UML model and the values be included in the INSPIRE Registry.
INSPIRE document/system:IR ISDSS [Implementing Rules for Interoperability of Spatial Data Sets and Services], TG EF [Data specification on Environmental monitoring facilities]
Submitting Organisation: Discussion (link):https://themes.jrc.ec.europa.eu/discussion/view/34147/extensibility-of-code-lists-in-inspire-ef

Description

The extensibility of some of the code lists in INSPIRE EF is different between the Technical Guidelines, Implementing Rules and other resources.

There are some problems:

1. The code lists ProcessTypeValue, ResultAcquisitionSourceValue, MeasurementRegimeVaue, ResultNatureValue, MediaValue are marked in the Technical Guidelines (page 28) and in the Consolidated UML data model (html preview) with extensibility none which is contradicting with the definition in the Implementing Rules and in the INSPIRE code list register (set to "any (Empty code list)").

2. Two code lists are not included in the INSPIRE EF Technical Guidelines Annex C despite that the description in the chapter 5 points to the Annex C. Those code lists are: SpecialisedEMFTypeValue and PurposeOfCollectionValue.

More details are present in the following discussions:

History

#1 Updated by Alessandro Sarretta over 4 years ago

  • Corrigendum changed from An harmonisation of the extensibility used in the codelists is needed, given the misalignments present among Technical Guidelines, Implementing Rules, UML models. This issue has been reported for the INSPIRE Environmental Monitoring Facilities but it could be present in other themes. to An harmonisation of the extensibility used in the codelists is needed, given the misalignments present among Technical Guidelines, Implementing Rules, UML models, Registry. This issue has been reported for the INSPIRE Environmental Monitoring Facilities but it could be present in other themes. In case of EMF, the extensibility should be defined as "none", as described in the UML model and the values be included in the INSPIRE Registry.
  • INSPIRE document/system IR ISDSS [Implementing Rules for Interoperability of Spatial Data Sets and Services] added

Also available in: Atom PDF