Re: Discussion (or lack thereof) on registry removal PR

I think we should push back a bit on this. There should be no reason to block a higher-level architectural topic like a registry based on browser internal algorithms.

Maybe one path is to split the TAG review into two pieces. In WebAuthn, we do many TAG reviews for a single version of a spec.

Tim

From: Marcos Caceres <caceres_m@apple.com>
Date: Thursday, October 9, 2025 at 12:19
To: Tim Cappalli <timcappalli@cloudauth.dev>
Cc: public-fedid-wg@w3.org <public-fedid-wg@w3.org>
Subject: Re: Discussion (or lack thereof) on registry removal PR


It might be good to wait for the TAG’s feedback on the spec, including Registries.

Note that, as co-editor of the spec, I’ve recused myself from providing a TAG position/feedback, so my opinions on the matter won’t be part of the TAG’s feedback.

What’s blocking the TAG from providing feedback is the lack of algorithms, which is blocked on us landing:
https://github.com/w3c-fedid/digital-credentials/pull/306


And:
https://github.com/w3c-fedid/digital-credentials/pull/372


That will unblock the TAG and they should provide good feedback on what we should do about the Registry (and hopefully good rationale either way for deleting it or continuing to include it… or something in between).


On 9 Oct 2025, at 22:42, Tim Cappalli <timcappalli@cloudauth.dev> wrote:


Hi all - I'm slightly concerned that there have been zero discussions/comments on the registry removal PR that has been open for 17 days.

This has been an important and contentious topic over the past year, and we really need some discussion or comments in support or against to help bring us to conclusion.

Please add your thoughts: https://github.com/w3c-fedid/digital-credentials/pull/376


Tim