Sam Goto

Ah, I realize that this may be a duplicate of #85. Feel free to close as a duplicate if you believe so too.

> Can you link to the relevant section of the questionnaire? https://w3ctag.github.io/security-questionnaire/#non-fully-active

> I think there's a good argument for saying this is the wrong layer of the stack to make such a requirement I think this is the key thing to...

> To be consistent with [other permission policy names](https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md) like publickey-credentials-get and identity-credential-get, @samuelgoto suggests we use the name digital-credential-get and I agree. I still think we should try to...

It registers them with the OS.

That's how the matchers work. The matchers are provided by the wallet (when the wallet registers the credentials they hold to the OS), so it is wallet (webasm) code, but...

It registers credentials metadata (e.g. the attributes, values, etc) that it chooses to and thinks is sufficient to provide good matches (i.e. the query language + metadata + wasm needs...

LGTM++

> This is not the fundamental issue that this group intends to solve. Instead, the primary objective of this group is to come up with a browser API for identity...

LGTM and added chromium issue to the PR description: https://g-issues.chromium.org/issues/357094234