<div dir="auto">I support moving forward </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 6, 2025, 7:15 AM <a href="mailto:torsten@lodderstedt.net" target="_blank" rel="noreferrer">torsten@lodderstedt.net</a> via Openid-specs-digital-credentials-protocols <<a href="mailto:openid-specs-digital-credentials-protocols@lists.openid.net" target="_blank" rel="noreferrer">openid-specs-digital-credentials-protocols@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div name="messageBodySection">
<div>I support moving HAIP to implementers draft.</div>
</div>
<div name="messageReplySection">
<div>Am 5. Feb. 2025, 00:25 +0100 schrieb Bjorn Hjelm via Openid-specs-digital-credentials-protocols <<a href="mailto:openid-specs-digital-credentials-protocols@lists.openid.net" rel="noreferrer noreferrer" target="_blank">openid-specs-digital-credentials-protocols@lists.openid.net</a>>:<br>
</div>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#1abc9c">
<div>I support moving HAIP to Implementer’s Draft given the reasoning provided by DCP WG Chairs on today’s call.</div>
</blockquote>
<br>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#1abc9c">
<div>
<div>
<div>Kind Regards,</div>
<div>Bjorn</div>
</div>
</div>
</blockquote>
<br>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#1abc9c">
<div>
<div>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#e67e22">
<div>On Feb 5, 2025, at 8:08 AM, Joseph Heenan via Openid-specs-digital-credentials-protocols <<a href="mailto:openid-specs-digital-credentials-protocols@lists.openid.net" rel="noreferrer noreferrer" target="_blank">openid-specs-digital-credentials-protocols@lists.openid.net</a>> wrote:<br>
<br>
</div>
</blockquote>
</div>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#e67e22">
<div>
<div style="color:rgb(0,0,0)">
<div>Dear Working Group,</div>
<div> </div>
<div>As discussed on the Thursday working group call last week (and also on today’s working group call) we would like to get WG consensus that the current HAIP draft is ready to start the Implementer’s draft approval process.</div>
<div>Please respond to this email <strong>within the next 2 days, by Thur Feb 6th end of business hours in PST</strong>, whether you believe the current draft should proceed to the public review or not. (Apologies that we didn’t manage to get this email out after the Thursday call as originally discussed!)</div>
<div> </div>
<div>The HAIP document to be reviewed can be found here: <a href="https://openid.github.io/oid4vc-haip/openid4vc-high-assurance-interoperability-profile-wg-draft.html" rel="noreferrer noreferrer" target="_blank">https://openid.github.io/oid4vc-haip/openid4vc-high-assurance-interoperability-profile-wg-draft.html</a></div>
<div> </div>
<div>The primary reason for starting the (somewhat lengthy) implementer’s draft process at this point is that doing so now is the only way to publish an implementer’s draft and still hit the timeline to publish a final version of the spec by the end of June, which we want to do in order to hit the timelines promised to the EU, ISO, etc.</div>
<div> </div>
<div>We certainly don’t view this spec as final - this is very much just a step on the journey, and there may well be comments that arrive during the 45 day public review period that the working group chooses to fix before the voting period starts. There are also a number of open issues in the GitHub issue tracker that the working group wants to solve before we take HAIP to final (you can see the list currently tagged for 1.0 Final here: <a href="https://github.com/openid/oid4vc-haip/milestone/2" rel="noreferrer noreferrer" target="_blank">https://github.com/openid/oid4vc-haip/milestone/2</a> - please let the chairs know if you think anything is missing from that list).</div>
<div> </div>
<div>I feel having the public review period and receiving that feedback from a wider group of people is very important to ensuring the spec is the best it can be by the time it goes to final.</div>
<div> </div>
<div>The details of the Implementer’s draft approval process can be found here: <a href="https://openid.net/wg/resources/approving-specifications/" rel="noreferrer noreferrer" target="_blank">https://openid.net/wg/resources/approving-specifications/</a>.</div>
<div>This email is about the first bullet point on this list, which is sometimes called Working Group Last Call (WGLC).</div>
<div>The next steps are to start a 45-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). If all goes smoothly the official 7 day voting period will hopefully start on Mon 24th March.</div>
<div> </div>
<div>Kindest Regards,</div>
<div>Editors & Chairs</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<br>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#1abc9c">
<div>
<blockquote style="margin:5px 5px;padding-left:10px;border-left-width:thin;border-left-style:solid;border-left-color:#e67e22">
<div>
<div style="color:rgb(0,0,0)">Note that, a 7 days WGLC review period would have meant that a 45 days review would start on 24th of December, which overlaps with the Holidays. Therefore, also taking into account that it has been discussed a number of times and agreed in the WG that the WG would like to start the WGLC of OpenID4VCI once two specific PRs are merged, the DCP WG made a decision on Dec 17th WG call to do WGLC in 2 days</div>
<div><span>--</span><br>
<span>Openid-specs-digital-credentials-protocols mailing list</span><br>
<span><a href="mailto:Openid-specs-digital-credentials-protocols@lists.openid.net" rel="noreferrer noreferrer" target="_blank">Openid-specs-digital-credentials-protocols@lists.openid.net</a></span><br>
<span><a href="https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols" rel="noreferrer noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols</a></span><br>
</div>
</div>
</blockquote>
</div>
<div>--<br>
Openid-specs-digital-credentials-protocols mailing list<br>
<a href="mailto:Openid-specs-digital-credentials-protocols@lists.openid.net" rel="noreferrer noreferrer" target="_blank">Openid-specs-digital-credentials-protocols@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols" rel="noreferrer noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols</a><br>
</div>
</blockquote>
</div>
</div>
-- <br>
Openid-specs-digital-credentials-protocols mailing list<br>
<a href="mailto:Openid-specs-digital-credentials-protocols@lists.openid.net" rel="noreferrer noreferrer" target="_blank">Openid-specs-digital-credentials-protocols@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-digital-credentials-protocols</a><br>
</blockquote></div>