technical-guidelines
technical-guidelines copied to clipboard
All data specifications - Convert enumerations into codelists
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:
-
Change of the Article 4:
- old formulation
- new formulation
- old formulation
-
Removal of the enumeration concept from the “Stereotypes” section:
-
Removal of the “Enumerations” section:
-
Change of the Article 6:
- old formulation
- new formulation
- old formulation
-
Removal of the “Enumerations” section from the feature catalogue and conversion of the enumerations into codelists (ONLY TGs which define enumerations):
- The following values are used for the missing tags:
- Extensibility = none
- Identifier = http://inspire.ec.europa.eu/codelist/<name_of_enumeration>
- Values = The allowed values for this code list comprise only the values specified in the INSPIRE Registry.
- The following values are used for the missing tags:
-
Removal of any reference to enumeration (if applicable):
- E.g. AF TG
- E.g. AF TG
-
Change of the stereotype from “enumeration” to “codeList” in the UML
Relevant legislation
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.
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