Bridging Language Barriers: An Open Translation Library for eIDAS Connectors

[GENERAL] Name and surname of main applicant

Marcus Ubani

[GENERAL] Email address of main applicant

ir@larissa.health

Additional applicants

Wibke Ubani

[GENERAL] Please specify how many months you expect your project to last (from 2-12 months)

3

[GENERAL] Please indicate if your proposal has been auto-translated into English from another language.

No

[GENERAL] Does your project have any dependencies on other organizations, technical or otherwise?

Yes

[GENERAL] If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.” .

eIDAS implementation has been set as regulation. In the EU context regulations are mandatory implementations, but governments have freedom on the way of how to implement the set of rules regarding to their own means. Also, not all governments have implemented their standard set, yet.

Our interim solution would be adding an additional field in the library to provide guidance for developers, specifying the current implementation status of each country.

Being open-sourced and of interest to our own needs, implementation updates will be monitored by us and the wider community.

[GENERAL] Will your project’s output/s be fully open source?

Yes

[GENERAL] If NO, please describe which outputs are not going to be open source. If YES, please write “Project will be fully open source.”

Project will be fully open source.

[METADATA] Category of proposal

Dev Tools, API or Library

[IMPACT] 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.

[IMPACT] 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.

[IMPACT] 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.

[IMPACT] 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.

[CAPABILITY/ FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability?

Wibke (2011) and Marcus (2008) have been working in Marketing for over a decade now.

Both are Atala Prism Pioneers. Together they have founded Larissa.Health, a platform focused on digital Midwifery in hybrid health.

Marcus has been in web technologies as an entrepreneur and with APIs, where JSON is a common standard, since 2010. He is also SPO of BIRTH Pool.

Both team members, Wibke and Marcus, have been in research.

[CAPABILITY/ FEASIBILITY] What are the main goals for the project and how will you validate if your approach is feasible?

The goal is met when all countries in the library have at minimum one translation according to the specification of eIDAS.

A further breakdown is below.

[CAPABILITY/ FEASIBILITY] Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.

With Ramp-up (1), Countries (28), and the additional documentation-close out (1), we see a total count of 30 Milestones.

We are meeting the timeline if we manage to deliver:

Month 1 ~ 30% Ramp-up, creating the foundational structure, 8 countries & meetings

Month 2 ~  65% 10 countries & meetings

Month 3 ~100% 10 countries & meetings, additional documentation and Close-out

Depending on our work schedule and the outlined dependencies, we will be potentially able to complete all deliverables within a shorter timeframe.

We are using the EU metric system so decimals are divided with "," and thousands with ".".

We are assuming a valuation of ~0,265 EUR-ADA.

We have excluded tax events.

We have applied a freelancer's average German hourly rate of around 100EUR.

===================================

1. Ramp-up (~20 hours => 2000€ ~ 7.500ADA ):
2. Defining the library structure
3. Create a collection of participating EU member countries
4. Create Documentation (Readme etc.)
5. Implementation (~60hours => 6.000€ ~ 22.500ADA )
6. For each country, there must be
7. Research the amount of official languages per country
8. Verify the current status of the country in the eIDAS progress
9. Add country data to the eIDAS standard dataset
10. Add country data to the eIDAS extended dataset
11. Verify dataset.
12. additional comments
13. Meeting with Atala Prism and ToIP working groups (~4 hours => 400€ ~ 1.500ADA)
14. Additional documentation and Close-out (~3 hours => 300€ ~ 1.150ADA)

===================================

32.650ADA => 32.500 ADA Funding Request

[CAPABILITY/ FEASIBILITY] Please describe the deliverables, outputs and intended outcomes of each milestone.

Each country will have its representation in the library.

Each representation will reference the current progress, the number of official languages used, and the respective translations.

The GitHub repository will show the progress transparently.

[RESOURCES & VALUE FOR MONEY] Please provide a detailed budget breakdown of the proposed work and resources.

We have another proposal, where we will meet with Atala Prism and ToIP working groups.

If both proposals get funded, we will ensure that there is no double spending requested from the Catalyst funds and request a lesser amount.

You can find the proposal here: Open library of international birth certificates issuance processes and issuing agencies.

1. The EU currently has 27-28 member states with 24 official languages
2. Some countries have more than one administrative language
3. Researching, structuring, and formatting the data for these countries is time intensive and should be done only once
4. After having created the library, it will only have to be maintained (updated, expanded, reduced)
5. eIDAS will most probably become a blueprint for international standards.
6. This library will pave the way for other identity projects seeking to align with these standards.

We will use resources of the eIDAS website, for rapid proto-typing and time efficiency we will include the power of LLMs (e.g. ChatGPT or MPT), and manually verify the results.

[RESOURCES & VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

Creating a fully open-sourced library will reduce future work and costs for developers working in the field of decentralized identity.

It will also reduce the error rate for international application working with eIDAS.

Furthermore, does any active development reference to Atala Prism and the broader SS community improve the outreach of Cardano.

[IMPORTANT NOTE] The Applicant agreed to Fund10 rules and also that data in the Submission Form and other data provided by the project team during the course of the project will be publicly available.

I Accept