<div dir="ltr"><div>Chairing or co-chairing working groups is a challenging task that can, unfortunately, leave some people unhappy.<br></div><div><br></div><div>However, I believe that statement is a gross mischaracterization of both Joseph's actions and intentions. </div><div><br></div><div>I must admit I'm not familiar with an OIDF code of conduct or lack thereof, but the statements made certainly seem as though they border on inappropriateness. <br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 13, 2024 at 3:09 PM Tom Jones via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" 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="auto"><div>I object to oid4 parameters in a federation document for a different reason. There should be no dependency in federation that limits what protocols are used for wallets.</div><div dir="auto"><br></div><div dir="auto">Joseph has been objecting to specs that might step on his scope for a long time. And then uses his prerogative as chair to avoid talking about issues there because they don't fit his own objectives. Something is really broken here.</div><div><br></div><div>thx ..Tom (mobile)</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 13, 2024, 1:31 PM Joseph Heenan via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" 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>Hi all<div><br></div><div>A couple of comments:</div><div><br><div><blockquote type="cite"><div><span style="font-family:Aptos,sans-serif;font-size:11pt">[Openid-specs-ab] Call for Working Group Adoption of OpenID Federation Wallet Architectures 1.0</span></div><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"><u></u><u></u></div><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"> There's been some discussion of the contribution and whether it should be adopted as-is<u></u><u></u></div><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"> Joseph thought that some metadata values currently defined there should be in other specs<u></u><u></u></div><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"> In the long term, everyone responding to him agreed with him<u></u><u></u></div><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"> There was disagreement on whether adoption should wait for these values to be first defined elsewhere</div></div></div></blockquote><div><br></div><div>There is no need at all to hold up adoption of this spec - the metadata items that are outside of the scope of this specification and hence belong in other specs should simply be removed and (if not already) submitted to the correct working group so that the important work of getting a profile of Federation for wallets can proceed. This could happen very quickly.</div><br><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"><u></u><u></u></div><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"> These were written down now to enable interoperable implementations of wallet ecosystems using Federation to be developed<u></u><u></u></div><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"> Mike asked Nat to be ready to make the adoption decision as chair next week<u></u><u></u></div><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"> Since John and Mike are authors</div></div></div></blockquote><div><br></div><div>It is important to clarify that this is a decision for the working group to make, not the chairs, as per <a href="https://openid.net/wordpress-content/uploads/2017/06/OIDF-Policy-Process-Document-Final-6-19-2017.pdf" rel="noreferrer" target="_blank">https://openid.net/wordpress-content/uploads/2017/06/OIDF-Policy-Process-Document-Final-6-19-2017.pdf</a> - it is clear to me that adoption currently cannot proceed as there are unresolved comments and the ’substantial support’ bar for consensus has not been reached, nor has a formal vote been started. I suggest we instead attempt to reach consensus on the 22nd call, unless we manage to reach consensus sooner via email.</div><br><blockquote type="cite"><div><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"><u></u><u></u></div><div style="margin:0in;font-size:11pt;font-family:Aptos,sans-serif"> Giuseppe sent a detailed message describing each of the defined metadata parameters and their purpose</div></div></div></blockquote><div><br></div>Unfortunately I’m travelling this week / at a conference so haven’t had a chance to properly digest the responses yet, but I hope to do so within the next week. However my objection is not to the purpose of the parameters, but to them not being Federation specific nor needed to make federation work for wallets, and hence must not be in a document with the current title when there are much more appropriate documents for them to be in. The fact that at least one of the proposed parameters also doesn’t actually work is a separate issue.</div><div><br></div><div>Thanks</div></div><div><br></div><div>Joseph</div><div><br></div></div>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net" rel="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" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
</blockquote></div>
_______________________________________________<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>
<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>