<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Is the intention to have this behave like two more formats for claims (and being sources for aggregated/distributed claims), plus to extend claims documents like a signed userinfo JWT and VC-JWT/VC-LD-PROOF to be officially specced out as being embeddable within an id_token?<br class=""><div><br class=""></div><div>Or do we see {VC,VP}_{JWT,LD} and aggregated/distributed claims as different concepts?</div><div><br class=""></div><div>My feeling is that the existing id_token and userinfo data are abstractly presentations (secured through transport and bearer security rather than some possession proof). The process to get a credential for later presentation is new protocol (and hence the new claims/credential provider spec work).</div><div><br class=""></div><div>How do others anticipate this integration working?</div><div><br class=""></div><div>-DW</div><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 12, 2021, at 5:30 AM, Kristina Yasuda via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" class="">openid-specs-ab@lists.openid.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">The intent was to define claims that can be used both inside ID Token (implicit flow/SIOP), and in UserInfo response (code flow). There are use-cases that use VC/VPs with OpenID Connect not just in SIOP (implicit flow with user-controlled OP) but also with the 'conventional' code flow, and I believe we need a generic way that works for both.</div><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class=""><br class=""></div><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">Best,</div><div style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt;" class="">Kristina</div></div></blockquote></div><br class=""></body></html>