Tim Cappalli
Tim Cappalli
Closes #345 Closes #58 Closes #85 Closes #69 Closes #136 Closes #211 Closes #212 Closes #213 Closes #214 Closes #215 Closes #226 Closes #240 Closes #256 Closes #257 Closes #280...
The goal of a `create` call in this spec is to assist with credential manager selection, and then essentially get out of the way (which is slightly different than `get`...
I find the most confusing part is the return of `DigitalCredential` interface, while the members make sense `protocol` and `data`, the fact that a `DigitalCredential` is returned is confusing. Maybe...
This is a complicated ecosystem. We need a dedicated terminology section at the beginning of the spec (probably between scope and model). We have a bunch of definitions scattered throughout...
Both [get](https://www.w3.org/TR/digital-credentials/#requesting-a-digital-credential-across-origins) and [create](https://www.w3.org/TR/digital-credentials/#issuing-a-digital-credential-across-origins) calls are allowed in cross-origin iframes in the spec. These cross-origin requests can be confusing and even misleading to users. We should: 1. Add considerations for...
Both [get](https://www.w3.org/TR/digital-credentials/#requesting-a-digital-credential-across-origins) and [create](https://www.w3.org/TR/digital-credentials/#issuing-a-digital-credential-across-origins) calls are allowed in cross-origin iframes in the spec. These cross-origin requests can be confusing and even misleading to users. Client platforms and credential managers may...
Explainer: https://github.com/w3c/webauthn/wiki/Explainer:-Credential-Manager-Trust-Group-Key
## Description Most WebAuthn clients today use the "security key" terminology in authenticator / credential selection dialogs to represent external authenticators. Additional form factors have been introduced in the market...
@stephenmcgruer there was a discussion earlier in the year / last year around ensuring that the payment bit was stored with and backed up with the WebAuthn credential. I believe...