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
The identity space has recently seen a surge in interest, particularly from governmental entities, in what is known as the three-party model. This model is seen as an advancement from the current two-party identity systems, and involves a verifier (website), a holder (wallets), and issuers working together to enable the exchange of identity documents such as ISO mDocs or W3C VCs. However, this ecosystem currently lacks native browser support, and instead relies on general purpose and cumbersome primitives like OS intents. In this session, we aim to explore the use cases and overall landscape of this growing ecosystem and consider whether and how browser APIs could be leveraged to support it.
Session goal
Answer the following questions: are there browser vendors interested in this space? what are the most compelling use cases? what are the web platforms APIs that seem to have an intersection in this space? where should we meet to continue this discussion?
Session description
The identity space has recently seen a surge in interest, particularly from governmental entities, in what is known as the three-party model. This model is seen as an advancement from the current two-party identity systems, and involves a verifier (website), a holder (wallets), and issuers working together to enable the exchange of identity documents such as ISO mDocs or W3C VCs. However, this ecosystem currently lacks native browser support, and instead relies on general purpose and cumbersome primitives like OS intents. In this session, we aim to explore the use cases and overall landscape of this growing ecosystem and consider whether and how browser APIs could be leveraged to support it.
Session goal
Answer the following questions: are there browser vendors interested in this space? what are the most compelling use cases? what are the web platforms APIs that seem to have an intersection in this space? where should we meet to continue this discussion?
Additional session chairs (Optional)
@samuelgoto
IRC channel (Optional)
#id-wallets
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
#28, #16, #4, #27
Estimated number of in-person attendees
20-45 people
Instructions for meeting planners (Optional)
No response
Agenda, minutes, slides, etc. (Optional)
The text was updated successfully, but these errors were encountered: