Question regarding genericode format (OASIS)

[heidivanparys]

I recently came across the following "OASIS Committee Specification":

Code List Representation (genericode) Version 1.0. Edited by G. Ken Holman. 06 April 2022. OASIS Committee Specification 02. https://docs.oasis-open.org/codelist/genericode/v1.0/cs02/genericode-v1.0-cs02.html. Latest stage: https://docs.oasis-open.org/codelist/genericode/v1.0/genericode-v1.0.html.

I found it via the Rolling Plan for ICT Standardisation of the EU, in the section e-Goverment.

Is this a format that re3gistry will support in the future?

[oscar9]

Dear @heidivanparys,
Thanks for your proposal. Right know, I wasn't aware of this format. We will study this specification and see if it’s possible and interesting to be implemented in the re3gistry software. Please, if any user finds this specification useful in some specific way let us know so we could assign a development priority in a better way with as much feedback and knowledge as possible.
Best regards,
Oscar

[heidivanparys]

I started asking around if this could be a useful format in the geo-community, see ISO-TC211/XML#224.

The interesting part is that the Publications Office of the European Union has voted on that specification.

Found via https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=codelist:

[heidivanparys]

I noticed the slide below in the presentation at FOSS4G 2022. Could you please confirm that Genericode indeed will be supported in the (near?/far?) future?

[jescriu]

After having analysed this enhancement the JRC INSPIRE team has decided to postpone its potential implementation waiting for the upcoming discussion on the future of the Re3gistry open-source software.
For the above-mentioned reason, this item is temporarily closed.