All data specifications - certain codelist identifiers contain the wrong value "codeList" instead of "codelist"

[fabiovin]

The identifiers of the codelists, i.e. the URL pointing to the INSPIRE registry, are wrong because they contain the value "codeList" with an uppercase "L".
The right values are with the lowercase.

See the related issues in the Registry helpdesk and in the Validator helpdesk.

Any reporting of the same error in other TGs is more than welcome.

[heidivanparys]

All TGs should be checked for this issue. A quick check of some data specifications shows me that at least the data specifications for Addresses and Protected Sites have the same issue, even in the boilerplate text:

From INSPIRE-MIF/helpdesk-validator#407 (comment)

The URL in camel case is an old and wrong URL that was available when the INSPIRE registry was firstly released.
It has then been corrected to the lowercase one. The camel case version has been kept in order to guarantee the backward compatibility.

Do we have a reference to a decision that clearly states that the lowercase version is the one to be used?

[heidivanparys]

Subgroup meeting 01-07-2021: issue presented, no objection from the group to move it further in the governance process.

[heidivanparys]

I updated the title of this issue to reflect that this is applicable to more data specifications than just EF.

[MarcoMinghini]

The INSPIRE CT approved the change proposal during today's 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]

The fix was introduced to the following TGs: EF, EL, GE, HY, PS, SD, US, during the release 2023.2.
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.

[fabiovinci]

The fix is introduced to the following TGs: AF, HB, HH, PF, and TN during the release 2024.1.
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.