You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some use cases it is important to know if a wallet currently is accepted by a recognised identification data issuer within a common trust framework.
For example, recognised identities enables usage in contexts that require legal assurance, and it could enable wallet backup recovery based on trusted re-identification.
@sander we would like to discuss this at a later point. Perhaps you can join one of our SIGs, I will reach out when the time has come :)
Thanks, happy to contribute. For the current EUDI Wallet pilots going on it would be great to start collecting more eIDAS-related characteristics and products soon.
Do you mean joining the meetings from this SIG, or one of the other SIGs of the foundation?
For some use cases it is important to know if a wallet currently is accepted by a recognised identification data issuer within a common trust framework.
For example, recognised identities enables usage in contexts that require legal assurance, and it could enable wallet backup recovery based on trusted re-identification.
I suggest to add a field:
identityTrustFramework
eidas_qc
: EU/EEA Trusted List qualified certificate under eIDASeidas_eid
: eIDAS-Network eID under eIDASeidas_pid
: European Digital Identity Framework PID under revised eIDAS (note: N/A to all so far)I’ve only listed the eIDAS-related frameworks that I know, but likely more are applicable to the listed wallets and agents.
Alternatively, have one boolean property per trust framework so that it becomes easier to process in for example a spreadsheet.
The text was updated successfully, but these errors were encountered: