Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lessons learned by an independent implementation of the Digital Identity Wallet in Europe #73

Open
jaromil opened this issue Sep 12, 2024 · 1 comment
Assignees
Labels
session Breakout session proposal track: Wallets

Comments

@jaromil
Copy link

jaromil commented Sep 12, 2024

Session description

I'll introduce challenges and pitfalls emerging while implementing the digital identity wallet in Europe (EUDI ARF).

Our team has independently implemented the EUDI ARF specification and released all code free open-source, a beta demo is also available as an online application at didroom.

This was a journey through some shocking revelations and frustrations shared by other large-scale pilots in Europe, so I'll do my best to extract critical insights that can guide other digital identity initiatives and avoid similar setbacks in the future.

Session goal

Share a critical perspective on EUDI ARF based on facts

Additional session chairs (Optional)

@andrea-dintino

Who can attend

Anyone may attend (Default)

IRC channel (Optional)

#eudi-arf

Other sessions where we should avoid scheduling conflicts (Optional)

#10, #12

Instructions for meeting planners (Optional)

Since I am required to give the presentation remotely, I would need a time slot for UTC+2.

Agenda for the meeting.

  • Quick overview of EUDI ARF
  • critical responses
  • wrong security assumptions
  • wrong privacy assumptions
  • viable alternatives we see
  • Q&A

Links to calendar

@jaromil jaromil added the session Breakout session proposal label Sep 12, 2024
@tpac-breakout-bot
Copy link
Collaborator

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
session Breakout session proposal track: Wallets
Projects
Status: No status
Development

No branches or pull requests

4 participants