<div dir="ltr"><div>Hi Brian,<br><br>I am very sorry for the animosity that I sense behind your words.<br>For the part that has been updated with respect to draft number 2, according to the last call for adoption feedbacks received, I report below the evidence of the work made so far:<br><br><div>- Process: [Removed text implying the specification has been
adopted by a WG](<a href="https://github.com/peppelinux/federation-wallet/pull/3">https://github.com/peppelinux/federation-wallet/pull/3</a>)</div><div>-
DCP WG common goals and harmonization: [Move text about possible use of
metadata to
issue](<a href="https://github.com/peppelinux/federation-wallet/pull/23">https://github.com/peppelinux/federation-wallet/pull/23</a>)<br></div><div>- Removal of pending TBD for draft 02: [feat: editorial improvements and added terms and sections](<a href="https://github.com/peppelinux/federation-wallet/pull/24/files">https://github.com/peppelinux/federation-wallet/pull/24/files</a>)<br></div><div><br></div></div><div>For the part on which you still found me lacking, and for which I feel deeply mortified, I have proceeded to create the following PRs and issues:<br><br>- Replacing TBD: [feat: Implementation Considerations for Offline Flows
using Trust Chain JWT header
parameter](<a href="https://github.com/peppelinux/federation-wallet/pull/27">https://github.com/peppelinux/federation-wallet/pull/27</a>)<br></div><div>- Replacing "...": [section: Wallet Checking the Non-Revocation of its Wallet Provider](<a href="https://github.com/peppelinux/federation-wallet/pull/28">https://github.com/peppelinux/federation-wallet/pull/28</a>)</div><div>- Replacing "...": [Credential Issuers Establishing Trust in the Wallet](<a href="https://github.com/peppelinux/federation-wallet/issues/29Credential">https://github.com/peppelinux/federation-wallet/issues/29Credential</a> Issuers Establishing Trust in the Wallet)<br></div><div><br></div><div>For the sequence diagrams still represented in the mermaid notation language I have to compile and therefore replacing them with the compiled result, within the final build.</div><div>I suppose to make this using the CI/CD, producing the final draft with traditional ascii sequence diagrams.<br></div><div>For this I am open to kind of suggestion that might get the draft CI/CD aligned with the current or next practices for the openid specs in this field.<br></div><div><br>I realize that unfortunately, this may not necessarily be enough, and this situation is probably exacerbated by my tiredness.<br>Therefore, I think it is appropriate to take a few weeks to review everything with greater care and attention. I will then re-propose the draft, advanced to version 03, to the attention of the working group.<br><br>The time of this Working Group is of inestimable value, and I intend to repay it with due diligence.<br><br>See you soon for the next call for adoption.<br><br>Best regards,<br></div>Giuseppe<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno gio 19 set 2024 alle ore 14:22 Brian Campbell via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="auto"><div dir="ltr"><div dir="ltr">Regardless of the other controversies surrounding the potential adoption of this draft, I'll reiterate that I believe it is inappropriate to ask for the WG's time and energy to consider adopting or even reviewing a document with blatant errors and omissions. A quick look at the contributed document reveals entire sections containing nothing more than three dots as placeholders for content and figures displaying unrendered textual markup, presumably meant for sequence diagrams. These issues undermine the draft's credibility and make it difficult to evaluate. I'd request that these kinds of problems be addressed before bringing the document to the WG for further consideration.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 13, 2024 at 1:43 AM Nat Sakimura via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">openid-specs-ab@lists.openid.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Dear AB/C WG: <div><br></div><div>This is to start the second call for the adoption of the Wallet Architectures Draft. </div><div><br></div><div>The draft has addressed the comments gained during the last CfA as follows: </div><div><br></div><div><div>- removing Appendix A;</div><div>- adding a prominent warning that the draft is not final;<br></div><div>- examples in the draft that were previously marked TBD have also been added.</div></div><div><br></div><div>As previously discussed [1], the call will run for a week till 2024-09-20. </div><div><br></div><div>[1] <a href="https://lists.openid.net/pipermail/openid-specs-ab/2024-September/010420.html" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.openid.net/pipermail/openid-specs-ab/2024-September/010420.html</a></div><div><br></div><div>Best regards, </div><div><br></div><div>Nat Sakimura</div><div>Co-Chair, AB/Connect Working Group. <br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr"><br></div>
</div></div></div>
_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-ab" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote></div></div></div>
</div>
<br>
<i style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:rgb(255,255,255);font-family:proxima-nova-zendesk,system-ui,-apple-system,system-ui,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;color:rgb(85,85,85)"><span style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;background:transparent;font-family:proxima-nova-zendesk,system-ui,-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,Ubuntu,Cantarell,"Helvetica Neue",Arial,sans-serif;font-weight:600"><font size="2">CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you.</font></span></i>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-ab" rel="noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote></div>