search

INSPIRE-MIF / technical-guidelines

Community for the discussion of change proposals to the INSPIRE Technical Guidance documents.
https://inspire-mif.github.io/technical-guidelines
29 stars 15 forks source link

All data specifications - Convert enumerations into codelists #130

Closed fabiovinci closed 4 months ago

fabiovinci commented 10 months ago

Change description

The "enumeration" concept and the enumeration's values were removed from Regulation (EU) No 1089/2010. All the enumerations shall be converted into codelists and managed in the INSPIRE Registry.

Implementation of changes

This change has an impact on several parts of the TGs:

Relevant legislation

Commission Regulation (EU) 2023/2431 of 24 October 2023 amending Regulation (EU) No 1089/2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services

Consolidated text: Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services

Additional information

Impact on INSPIRE validator

Yes, a specific check needs to be added for enumerations that are converted into codelists, since the related values are no longer checked during the schema validation step.

Linked issue

N/A

Impact on INSPIRE XML schemas

Yes, the enumerations shall be removed from the xsd and the datatype of the related attributes need to be changed. image image

Linked issue

Convert enumerations into codelists_Change from 1089 amendment #89

Impact on INSPIRE UML

Yes

Impact on INSPIRE Registry

Yes, the enumerations shall be converted into codelists.

Linked issue

https://github.com/INSPIRE-MIF/helpdesk-registry/issues/91

fabiovinci commented 9 months ago

This change was applied to all the converted TGs. The issue will remain open as a placeholder to apply the same fix to the TGs that will be converted and published in the next releases.