Torsten Lodderstedt

yes, we have found an appropriate solution that is described in the OID4VP DC API Profile. I close this issue.

> Reacting to this first statement > > > I have been told a couple of times the fundamental issue this group wants to solve is to find an alternative...

> First part sounds like the beginning of `/etc/hosts` but for browsers... If we don't give users agency / control over these experiences, they will just do it at the...

> Second part seems ok, but could be shortened to "not covering issuance & presentation in the same set of APIs is a vendor lock in tactic, and OIDC solves...

> I feel like making developers lives harder is less important than protecting user data... using encryption carefully is also part of the solution to your concerns regarding vendor lock....

> I could be in person, talking over bluetooth / QR Codes to get a credential (issuance in proximity), but later remote presenting with OIDC4VP (remote presentation without physical proximity)....

@RByers thanks for taking the time for explaining your perspective (both in the meeting and in your comment). I have come to the conclusion that just replacing custom schemes with...

@RByers thanks for your feedback. I think this is a good basis for working on a good solution. I forgot to mention one thing regarding market adoption. My assumption is...