2025-02-28 - bb-wallet - Meeting Notes

Date

Feb 28, 2025 2:00 PM CET

Discuss the scope of work required to bring Wallet BB to release state, including trust services, action items, and contributions from working group members

Two proposed options:
1. Having a separate trust services specification and wallet specifications
2. Following the current specification published
Ott has mapped the wallet features which need to change as per the EIDAS requirements, but declined to share the document in the public domain.
The member agreed that documenting pros and cons for each approach will help better decision-making.
Few members pointed out that if someone has an issue with the current specification, then they should share a detailed report during the review phase, pointing out which part of the specification has an issue. For example, mapping EIDAS terms on a table which do not comply with the current wallet specification.

There was a discussion on the role of trust services and whether they should be included in the wallet specification or not.
There were differing opinions on whether trust services, which comes from EIDAS 1.0, is actually impacting the current wallet specification.
Torsten and other members pointed out that the current specification is a high-level conceptual document and needs further refinement, but can be shared for review as the 1st version of the specification.
It was also agreed that wallet components should be refined to align terminology across frameworks.

Agreement that the Wallet Working Group should publish its work only when consensus is reached.
Specification should be shared with the experts in the community to review and get feedback as soon as possible.

Concern raised about W3C’s decision to merge Verifiable Credentials (VC) standards with the federated identity model.
Some members argued that the existing wallet specification needs updates to align with evolving standards.
Others stressed that waiting for standards to stabilize would result in indefinite delays.
Decision made to work in an agile mode and move forward with the current version while keeping future updates in mind.

Kristo appraised us about the discussion on funding for wallet specification development within GovStack.
GovStack has a budget for paying contributors. A facilitator role is compensated at around €800/day, and contributors are allowed up to two compensated days per month.
Concerns raised about intellectual property (IP) ownership and open-source licensing.
Members debated whether privately developed work should be integrated into GovStack specifications.
Kristo to talk to GovStack’s legal team to clarify IP and licensing issues.