Coming back from the SDG EU OOTS Subgroup Evid and the "interoperable EMREX bridge comments"
I have to reopen the ticket from V1.6 also for V2.0 for the sake of a future real interoperability of ELMO XSD serialisation with today's UML data models for data exchange in the education domain:
https://github.com/emrex-eu/elmo-schemas/issues/57
Focussing on the citizenship and country codelist:
Neither it is possible to express "Kosovo" or "South Sudan" or any other changes of the last decade made it in the 9 year old "cedefop/europass version".
Also: When you use this country code list for citizenship, the "no citizenship" option is missing.
URIs in the semantic web today provide functioning governance mechanisms - once done right.
"Using URIs can lead to link rot" is true when governance is too weak or backward-compatibility is a bigger issue than forward compatibility - especially in cases where codelists were used that do not support both, "up-to-date situation" and "historical values".
Today to my understanding a lot of eGovernment projects focus on stable URI, vocabularies and governance.
The ISO makes yearly updates according to the political situation.
I suggest to consider using an up-to-date country code list and to rediscuss the "link rot issue" in the "interoperability talks" with DG EMPL ELM or DG DIGIT Emrex Bridge Activities. Same is true for language codelist or NUTS or any other codelists that may be subject to frequent changes.
Thank you in advance,
Sebastian, Member of the SDG Subgroup MAP and EVID; Responsible for the German standardisation activity [XBildung.de](www.xbildung.de)
https://github.com/emrex-eu/elmo-schemas/blob/e7a8de0d58d418d9bc36860bf9d62a1db7ececd5/schema.xsd#L5
Coming back from the SDG EU OOTS Subgroup Evid and the "interoperable EMREX bridge comments" I have to reopen the ticket from V1.6 also for V2.0 for the sake of a future real interoperability of ELMO XSD serialisation with today's UML data models for data exchange in the education domain: https://github.com/emrex-eu/elmo-schemas/issues/57
Focussing on the citizenship and country codelist:
Neither it is possible to express "Kosovo" or "South Sudan" or any other changes of the last decade made it in the 9 year old "cedefop/europass version".
Also: When you use this country code list for citizenship, the "no citizenship" option is missing.
URIs in the semantic web today provide functioning governance mechanisms - once done right. "Using URIs can lead to link rot" is true when governance is too weak or backward-compatibility is a bigger issue than forward compatibility - especially in cases where codelists were used that do not support both, "up-to-date situation" and "historical values".
Today to my understanding a lot of eGovernment projects focus on stable URI, vocabularies and governance. The ISO makes yearly updates according to the political situation.
I suggest to consider using an up-to-date country code list and to rediscuss the "link rot issue" in the "interoperability talks" with DG EMPL ELM or DG DIGIT Emrex Bridge Activities. Same is true for language codelist or NUTS or any other codelists that may be subject to frequent changes.
I see two options for the "country and regions" codelist: a) either the real ISO 3166 list including 2 and 3 digit versions as referred to by the SDG EU OOTS TDD EEA Country code list https://ec.europa.eu/digital-building-blocks/sites/pages/viewpage.action?pageId=706382160 or b) to use the Publications Office authority table on Countries and regions. https://op.europa.eu/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/country
Thank you in advance, Sebastian, Member of the SDG Subgroup MAP and EVID; Responsible for the German standardisation activity
[XBildung.de](www.xbildung.de)