- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Thu, 24 Mar 2022 21:06:49 -0400
- To: public-credentials@w3.org
On 3/20/22 3:51 AM, Nikos Fotiou wrote: > Related to that, EBSI’s “Verifiable Exchange Scenarios” are a useful > guideline > https://ec.europa.eu/digital-building-blocks/wikis/display/EBSIDOC/EBSI+Verifiable+Presentation+Exchange+Guidelines#EBSIVerifiablePresentationExchangeGuidelines-VerifiablePresentationExchangeScenarios > Similar to what Tobias said, I cannot see how CHAPI can be used in use > cases B and C. Thank you, Nikos, that is helpful! CHAPI is not designed for B and C (and never was) -- the point of contention is Case A: Same-device flow. CHAPI can solve for that use case for a high percentage of the market while not falling into the NASCAR, scheme, app URL traps that Dmitri has outlined. How does OIDC/SIOP solve for that use case? That is -- where's the mediator for SIOP? -- manu -- Manu Sporny - https://www.linkedin.com/in/manusporny/ Founder/CEO - Digital Bazaar, Inc. News: Digital Bazaar Announces New Case Studies (2021) https://www.digitalbazaar.com/
Received on Friday, 25 March 2022 01:07:07 UTC