<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;"><meta http-equiv="content-type" content="text/html; charset=us-ascii"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>Dear DCP Working Group Members,</div><div><br></div><div>As discussed on the Friday working group call we would like to get WG consensus that the OpenID4VP draft is ready to start the final specification approval process.</div><div><br></div><div>Please respond to this email within the next 7 days, by end of Sunday 20th April, whether you believe the draft should proceed to the public review or not. </div><div> </div><div>The OpenID4VP document to be reviewed can be found here: <a href="https://openid.net/specs/openid-4-verifiable-presentations-1_0-26.html">https://openid.net/specs/openid-4-verifiable-presentations-1_0-26.html</a></div><div><br></div><div>There are a couple of normative changes that we discussed during the working group meeting on Friday to work on during working group last call:</div><div><br></div><div>1. revamp vp formats: <a href="https://github.com/openid/OpenID4VP/pull/500">https://github.com/openid/OpenID4VP/pull/500</a></div><div><br></div><div>2. Specifies value matching for mdocs via a reference to cbor-to-json: <a href="https://github.com/openid/OpenID4VP/pull/538">https://github.com/openid/OpenID4VP/pull/538</a></div><div><br></div><div>3. Remove references to ISO 18013-7 to avoid confusion due to it using OID4VP ID2: https://github.com/openid/OpenID4VP/issues/519</div><div><br></div><div>4. Remove anoncreds for now (hoping to add it back in 1.1) due to lack of implementation experience with DCQL etc: <a href="https://github.com/openid/OpenID4VP/pull/539">https://github.com/openid/OpenID4VP/pull/539</a></div><div><br></div><div>We’d also expect some editorial/non-normative changes during WGLC.</div><div><br></div><div>We also discussed scheduling a meeting to talk about the sd-jwt vcld pr: <a href="https://github.com/openid/OpenID4VP/pull/459">https://github.com/openid/OpenID4VP/pull/459</a> (a separate email about this will follow shortly.)</div><div><br></div><div>If there are other topics working group members think need to be handled before the specification moves to final please reply to this email with details.</div><div><br></div><div>This is very much just a step on the journey, and it is likely that comments will arrive during the 60 day review period that the working group chooses to fix before the voting period starts.</div><div><br></div><div>The details of the specification approval process can be found here: https://openid.net/wg/resources/approving-specifications/.</div><div><br></div><div>This email is about the first bullet point on this list "Obtain working group consensus to propose foundation-wide approval of the draft specification", which is often called Working Group Last Call (WGLC).</div><div>The following steps are to start a 60-day Foundation-wide review, followed by the 7 day voting period (the poll itself will open 7 days before the end of the Foundation-wide review ends).</div><div><br></div><div>Kindest Regards,</div><div>Editors & Chairs</div><div><br></div></div></body></html>