<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I support adoption of specification.<div><br></div><div>- Harri<br id="lineBreakAtBeginningOfMessage">
<div><br><blockquote type="cite"><div>On 3. Jan 2025, at 14.27, Joseph Heenan via Openid-specs-digital-credentials-protocols <openid-specs-digital-credentials-protocols@lists.openid.net> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hi all<div><br></div><div><div><div>As discussed in various recent WG meetings the OpenID for Verifiable Presentations specification currently technically belongs to the Connect/AB working group (as it was started before the DCP WG existed), so now the specification has moved to Implementer’s Draft 3 (and the IPR protections locked in) we need to do a “call for adoption” to move it to the Digital Credentials Protocols working group.</div><div><br></div><div>This is an official call for adoption of “OpenID for Verifiable Presentations” document: <a href="https://openid.net/specs/openid-4-verifiable-presentations-1_0-ID3.html">https://openid.net/specs/openid-4-verifiable-presentations-1_0-ID3.html</a>.</div></div><div><br></div><div>Please reply on the mailing list and let us know if you are in favor or against adopting this draft as a WG document, by Jan 17th.</div></div><div><br></div><div>Many thanks</div><div><br></div><div>Joseph</div><div><br></div><div><br></div></div></div>-- <br>Openid-specs-digital-credentials-protocols mailing list<br>Openid-specs-digital-credentials-protocols@lists.openid.net<br>https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols<br></div></blockquote></div><br></div></body></html>