Please describe your proposed solution.
eIDAS specifies a base schema and an extended schema standard to address DIDs when communicating with domestic service providers such as hospitals.
We will research the translations for the administrative languages for each EU country and create an entry in our JSON library for it. Some countries might have more than one official language so we will find and implement those differences as well.
If the solution would not be implemented, each developer would have to reinvent the wheel, which would be very inefficient and prone to errors.
The solution is for the broader SSI - world and usable as a universal library.
We have recently become a contributing member of the ToIP, and have joined their working groups (Technology Stack, Ecosystem Foundry WG) to discuss and promote the library.
We hope that everyone interested in developing solutions working with DIDs across the EU will find this library easy to implement.
How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?
TL;DR: We are matching translation data according to eIDAS schema.
eIDAS will most probably become a blueprint for international standards.
This library will pave the way for other identity projects seeking to align with these standards.
Therefore, our project solves key issues moving forward in compliance with key regulations, international project scoping, lowering development costs and improving the recognition of the Atala Prism learning program.
How do you intend to measure the success of your project?
Any DID-project - including current Atala Prism projects - intending to work with services in the EU will be using the eIDAS standard; thus, we expect a reasonably good acceptance of our work results.
Our output will be publicly shared from the beginning on GitHub.
Feedback loops with the Atala Prism team and ToIP members will ensure the sound quality of the outcome.
Means of measure could be stars, forks, and pull requests on GitHub, but also referencing discussions in Atala, ToIP, DIF or Hyperledger working groups.
Please describe your plans to share the outputs and results of your project?
Our output will be publicly shared from the beginning on GitHub.
Feedback loops with the Atala Prism team and ToIP members will ensure the sound quality of the outcome.
Means of measure could be stars, forks, and pull requests on GitHub, but also referencing discussions in Atala, ToIP, DIF or Hyperledger working groups.
If the project gets accepted by the broader SSI community, we can expect an increasing level of participation.