2025-02-06 - ARCH - Meeting Notes
Version | Date | Drafters |
---|---|---|
0.1.0 | 2025-02-06 | @Ali González - Missing people present to complete information |
Participants
[Pending to record]
Discussion topics
[Pending to complete]
Solve the issue of eIDAS 2 compatibility,
🤝 Agreements
An important note from today's architecture workgroup meeting is the proposal to be taken back to the wallet working group (to be presented by Ott and Ramkumar, if possible). This is the proposal from the architecture workgroup:
To solve the issue of eIDAS 2 compatibility, current scope of wallet building block would be split in two to consist of the technical wallet component building block and then a second "trust service" building block.
To achieve this, terminology of the current wallet building block should be updated and anything related to trust services (if such exist) to be removed from its scope. Ott Sarv estimates that this work could take one or two weeks. This should be discussed in the wallet working group next time the group gathers.
After polishing of the wallet building block, it can then be published once the working group agrees with the scope and the text is finalized. Architecture working group will review the final building block as soon as possible that has happened.
Trust service building block scope should be defined likely by the wallet and digital identity building block working groups. Trust service building block will be necessary to assure higher level compliance of various other technical components (such as wallet, digital identity, signature and other related software components).
Once the scope for trust services building block is ready, a dedicated working group will be called to start contributing to the trust service building block. This building block will be important for GovStack implementations that require a higher level compliance (such as within EU, but for example for Bosnia long term as a country that wishes to join EU ecosystem).