<div dir="ltr"><div>Thanks Nat, <br></div><div><br></div><div>I have to be honest though, I only glanced at the document and my first and only thought was that a 28 page pdf diff is unlikely to have content appropriate for errata. <br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 23, 2025 at 9:40 AM Nat Sakimura <<a href="mailto:nat@sakimura.org" target="_blank">nat@sakimura.org</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"><div dir="ltr">As I have promised in the call today, I have created a file highlighting the differences between the final and proposed errata. <div><br></div><div>Clearly, the newly added "Abstract" does not work. The text does not represent Part 2. </div><div>Also, "Abstract" should not be there as for FAPI 1 at least, we are drafting according to the ISO Directive Part 2. </div><div>Adding it does not help. It should be removed. </div><div><br></div><div>Besides that, I spotted that BCP195 needs to be added to the Normative reference as it is referred to with a "shall" now. </div><div><br></div><div>Finally, I note that this is not a "corresponding update", as I understand. </div><div><br></div><div>Cheers, </div><div><br></div><div>Nat</div><div><br></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2025年4月23日(水) 21:29 Brian Campbell via Openid-specs-fapi <<a href="mailto:openid-specs-fapi@lists.openid.net" target="_blank">openid-specs-fapi@lists.openid.net</a>>:<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>I do think it's problematic to publish what are effectively breaking changes as errata. With little to no indication that there are substantive changes or even what they are. That comment is really in regard to the errata updates to OpenID Connect Core and CIBA Core (corresponding WG's cc'd). I'd suggest those actions be revisited to at least provide readers some indication of the breaking change. <br></div><div><br></div><div>Although the prospective FAPI 1.0 errata were described as corresponding updates, I don't see what I would have expected in the document based on my understanding of corresponding. Maybe I missed it or my understanding is wrong. It is difficult to assess what has changed when the errata update includes a whole reformatting of the document. <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Apr 14, 2025 at 12:44 PM Michael Jones via Openid-specs-fapi <<a href="mailto:openid-specs-fapi@lists.openid.net" target="_blank">openid-specs-fapi@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>
<div lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:11pt">The proposed errata changes to FAPI 1.0 Advanced are at
<a href="https://openid.bitbucket.io/fapi/openid-financial-api-part-2-1_0.html" target="_blank">https://openid.bitbucket.io/fapi/openid-financial-api-part-2-1_0.html</a> but not yet published to <a href="http://openid.net/specs/" target="_blank">openid.net/specs/</a>. I think it makes sense to do so.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">I’ll note that the corresponding errata updates to OpenID Connect Core and CIBA Core have been published there. See
<a href="https://openid.net/specs/openid-connect-core-1_0-36.html" target="_blank">https://openid.net/specs/openid-connect-core-1_0-36.html</a> and
<a href="https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0-06.html" target="_blank">
https://openid.net/specs/openid-client-initiated-backchannel-authentication-core-1_0-06.html</a>.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Is the working group supportive of publishing draft 10 to <a href="http://openid.net/specs/" target="_blank">openid.net/specs/</a>?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">I do have one editorial question. Why is it that the title in
<a href="https://bitbucket.org/openid/fapi/raw/92a88dfb26fc6d95f22f305f85eb2308fec0f5f3/FAPI_1.0/openid-financial-api-part-2-1_0.md" target="_blank">
the source</a> is<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:0.5in"><span style="font-size:11pt;font-family:"Courier New"">title: FAPI security profile 1.0 - Part 2: Advanced - draft 10 incorporating errata set 1<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">whereas the title in <a href="https://openid.bitbucket.io/fapi/openid-financial-api-part-2-1_0.html" target="_blank">
the draft</a> is<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:0.5in"><b><span style="font-size:11pt">FAPI security profile 1.0 - Part 2: Advanced - draft 10 incorporating errata set 1 - 1<u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="font-size:11pt">(with the extra “ – 1” at the end)?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"> Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"> -- Mike<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
</div>
_______________________________________________<br>
Openid-specs-fapi mailing list<br>
<a href="mailto:Openid-specs-fapi@lists.openid.net" target="_blank">Openid-specs-fapi@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-fapi" rel="noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-fapi</a><br>
</div></blockquote></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-fapi mailing list<br>
<a href="mailto:Openid-specs-fapi@lists.openid.net" target="_blank">Openid-specs-fapi@lists.openid.net</a><br>
<a href="https://lists.openid.net/mailman/listinfo/openid-specs-fapi" rel="noreferrer" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-fapi</a><br>
</blockquote></div></div>
</blockquote></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>