[Openid-specs-ab] 2nd Call for Adoption of the OpenID Federation Wallet Architectures Draft

[Giuseppe De Marco]

Hi Brian,

I am very sorry for the animosity that I sense behind your words.
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:

- Process: [Removed text implying the specification has been adopted by a
WG](https://github.com/peppelinux/federation-wallet/pull/3)
- DCP WG common goals and harmonization: [Move text about possible use of
metadata to issue](https://github.com/peppelinux/federation-wallet/pull/23)
- Removal of pending TBD for draft 02: [feat: editorial improvements and
added terms and sections](
https://github.com/peppelinux/federation-wallet/pull/24/files)

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:

- Replacing TBD: [feat: Implementation Considerations for Offline Flows
using Trust Chain JWT header parameter](
https://github.com/peppelinux/federation-wallet/pull/27)
- Replacing "...": [section: Wallet Checking the Non-Revocation of its
Wallet Provider](https://github.com/peppelinux/federation-wallet/pull/28)
- Replacing "...": [Credential Issuers Establishing Trust in the Wallet](
https://github.com/peppelinux/federation-wallet/issues/29Credential Issuers
Establishing Trust in the Wallet)

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.
I suppose to make this using the CI/CD, producing the final draft with
traditional ascii sequence diagrams.
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.

I realize that unfortunately, this may not necessarily be enough, and this
situation is probably exacerbated by my tiredness.
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.

The time of this Working Group is of inestimable value, and I intend to
repay it with due diligence.

See you soon for the next call for adoption.

Best regards,
Giuseppe

Il giorno gio 19 set 2024 alle ore 14:22 Brian Campbell via Openid-specs-ab
<openid-specs-ab at lists.openid.net> ha scritto:

> 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.
>
> On Fri, Sep 13, 2024 at 1:43 AM Nat Sakimura via Openid-specs-ab <
> openid-specs-ab at lists.openid.net> wrote:
>
>> Dear AB/C WG:
>>
>> This is to start the second call for the adoption of the Wallet
>> Architectures Draft.
>>
>> The draft has addressed the comments gained during the last CfA as
>> follows:
>>
>> - removing Appendix A;
>> - adding a prominent warning that the draft is not final;
>> - examples in the draft that were previously marked TBD have also been
>> added.
>>
>> As previously discussed [1], the call will run for a week till
>> 2024-09-20.
>>
>> [1]
>> https://lists.openid.net/pipermail/openid-specs-ab/2024-September/010420.html
>>
>> Best regards,
>>
>> Nat Sakimura
>> Co-Chair, AB/Connect Working Group.
>>
>>
>> _______________________________________________
>> Openid-specs-ab mailing list
>> Openid-specs-ab at lists.openid.net
>> https://lists.openid.net/mailman/listinfo/openid-specs-ab
>>
>
> *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.*_______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-ab
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20240919/1e294327/attachment.html>