Dear all,
Sikt, currently maintaining the ELMO format, propose two additional changes to ELMO version 1.7.
Following the meeting on the 28.10.2022 with the EMREX community it was decided that some issues were to be postponed to ELMO version 2.0, some issues were to be closed and some to be solved with the existing elements already present in ELMO 1.6. This consultation letter will only deal with the issues proposed for ELMO 1.7, but will provide additional information on the issues not to be included in ELMO version 1.7 such as why they are not considered for this current version.
The deadline for feedback on these issues is Sunday 31.11.2022. Feedback can be sent to elmo-contact(a)sikt.no<mailto:elmo-contact@sikt.no>.
The two issues up for discussion are issue #65 and issue #64. These issues should only require minor changes in the documentation of certain elements. These changes will not break backwards compatibility.
Click here to read the GitHub issue #65<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…>. Issue #65 deals with the need for the address of an issuer of a result for German Upper Secondary School Diplomas as an identifier. To solve this issue, we propose that we introduce address as an identifier for the issuer element.
Click here to read the GitHub issue #64<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…>. Issue #64 deals with the different kinds of diplomas for German Upper Secondary School. To solve this, we propose that we add a line of text to the documentation of the level element, which explains how to make your own local level-type and how to make sure they are unique cross borders. It should be noted one should not expect that these local level types are understood cross borders.
The following issues are not up for consideration for ELMO version 1.7.
Issues to be solved using the existing elements in ELMO 1.6:
* Issue #68<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> is a country specific issue and should not be formally included in ELMO. Can be solved by using the extention element. Proposal for an extension has been communicated.
* Issue #67<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> is a country specific issue and should not be formally included in ELMO. Can be solved by using the extention element. Proposal for an extension has been communicated.
* Issue #63<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> can be inferred from an already existing element languageOfInstruction.
* Issue #61<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> is a country specific issue and should not be formally included in ELMO. Will be solved by using the extention element.
Issues to be considered closed and won't be solved:
* Issue #66<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> will be closed due to the fields are already present in ELMO.
* Issue #62<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> will be closed as it is a proposed change to the EMREX protocol, not the ELMO format. The issues has been moved to https://github.com/emrex-eu/standard/issues<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…>.
Issue blocked by external factors:
* Issue #59<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> proposes we align name types and more with eIDAS minimum data set. This will not be considered until the eIDAS 2.0 directive being completed.
Lastly, we have issues to be considered for ELMO 2.0 at a later date:
* Issue #60<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> will break backwards compatibility and is therefore not in consideration for ELMO version 1.7.
* Issue #58<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> will break backwards compatibility and is therefore not in consideration for ELMO version 1.7.
* Issue #57<https://nor01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> will break backwards compatibility and is therefore not in consideration for ELMO version 1.7.
Best regards,
Mathias Christian Hjertholm
Head Engineer
Geir Vangen
Senior Digital Advisor
[cid:image001.png@01D8F5A6.103BF250]
Sikt - Kunnskapssektorens tjenesteleverandør
