[Openid-specs-fapi] A couple of asks to the WG as an editor

[Kosuke Koiwai]

I’m happy to review trivial PRs so real FAPIers can work on the real
contents.

Kosuke

On Thu, Oct 30, 2025 at 6:43 Ralph Bragg via Openid-specs-fapi <
openid-specs-fapi at lists.openid.net> wrote:

> Hi Nat,
>
> I’m supportive of you just fixing the references preferably. Will review
> the PR.
>
> Kind Regards,
> Ralph
>
> Ralph Bragg
>
> Chief Technology Officer
>
> M.
>
>
>
> +447890130559
>
> T.
>
>
>
> +44 20 4583 6770
>
> ralph.bragg at raidiam.com
>
> *From: *Openid-specs-fapi <openid-specs-fapi-bounces at lists.openid.net> on
> behalf of Nat Sakimura via Openid-specs-fapi <
> openid-specs-fapi at lists.openid.net>
> *Date: *Thursday, 30 October 2025 at 5:19 am
> *To: *FAPI Working Group List <openid-specs-fapi at lists.openid.net>
> *Cc: *Nat Sakimura <nat at sakimura.org>
> *Subject: *[Openid-specs-fapi] A couple of asks to the WG as an editor
>
> Hi FAPI WG.
>
> I am writing this not as a co-chair, but as an editor of FAPI1.
>
> We are in the process of aligning the text with the ISO comments we
> received for FAPI1.
>
> https://bitbucket.org/openid/fapi/pull-requests/548
>
> Is a bit of shuffle around of the clauses and fixing broken links etc.
> This is a fairly big PR but quite simple, so if you guys could just check
> it and approve it, it would be great. That will cause less concern for me
> to get into conflicts.
>
> The second ask is to give me a mandate to fix trivial things, like change
> a RFC to an RFC etc. Creating PRs for each of those comments will create
> more work fo you and me. Just directly fixing them would be more
> productive.
>
> Best regards.
>
> Nat Sakimura
> _______________________________________________
> Openid-specs-fapi mailing list
> Openid-specs-fapi at lists.openid.net
> https://lists.openid.net/mailman/listinfo/openid-specs-fapi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20251030/d26c80b6/attachment.htm>