All data specifications - code list descriptions -> link to INSPIRE registry

[heidivanparys]

Change proposal description

For all data specifications: replace the code list descriptions with a link to the code list in the INSPIRE registry.

Addressed TG

All data specifications.

Location

This will impact sections 5.3.2 "Feature catalogue" and Annex C "Code list values".

Issue faced

The IR on the interoperability of spatial data sets and services will be amended soon, see also this presentation from the 13th MIG meeting: the code list and enumeration values in the regulation will be replaced with a reference to the INSPIRE registry.

Proposed solution

As a consequence, all data specifications should be updated when the amendment is in force: the code list values should be removed and a reference to the relevant code list in the INSPIRE registry should be added instead.

Pull request

TBD when all the data specifications are on GitHub.

Additional information

Kind of issue

Technical issue

Relevant legislation

"Common code lists" in the IR on the interoperability of spatial data sets and services

Impact on IR

No impact.

Impact on INSPIRE validator

No impact.

Linked issue

N/A

Impact on INSPIRE XML schemas

No impact.

Linked issue

N/A

Impact on INSPIRE code lists

No impact

Linked issue

N/A

Change proposer

Heidi Vanparys, helpdesk facilitator.

References

This issue was created after investigating issues #3 and #1 and discussing those during the subgroup meeting of 01-07-2021. Resolution of this issue would solve those two issues.

[heidivanparys]

It was suggested during the subgroup meeting of 01-07-2021 to create a new issue and to close #1 and #3 instead. The reason is that the proposed solution there did not take into account the forthcoming amendment of the IR on the interoperability of spatial data sets and services.

As written above, this solution was suggested during the subgroup. To all subgroup members: if you agree with the issue description, created right after that subgroup meeting, could you please give a thumbs up to this comment? If enough members agree, I can apply the "approved" label and the issue could then be discussed already at the MIG-T meeting next week.

[laers]

Please have in mind that there exist code lists in data specification that is not in the INSPIRE Register. Even though the code list has an identifier as an URI pointing to the INSPIRE Register. For instance http://inspire.ec.europa.eu/codelist/InstallationNatureValue from TG DS BU. (annex C).

I do not have the entire overview but it seems that all code lists from the extended data models are not in the INSPIRE Register. How to handle those? Is the scope/mandate of this action to update only the code list descriptions which occurs in the Register today? The code lists from the TG DSs should not be removed before all code lists is to be find in the Register.

[MarcoMinghini]

The INSPIRE MIG-T approved the change proposal during the 66th MIG-T meeting. In the next step, the proposal will be moved to the MIG for the final endorsement.

[MarcoMinghini]

The INSPIRE MIG approved the change proposal, since no objections were raised during the two week scrutiny period from July 12 to July 26, 2021. The change can be now implemented.

[fabiovinci]

Here are the main changes introduced in the TGs:

• Change text in red, from "Annex C" to "the INSPIRE Registry", for each codelist in the Feature catalogue:

• Updated of Annex C, removing the codelist values and changing the text in red, from “table below” to “INSPIRE Registry”:

NOTE: regarding the codelists related to the extended data models, the related values will remain, for the moment, in the TGs since these codelists are not available in the INSPIRE Register.

[fabiovinci]

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.