- From: Nick Steele via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Jun 2023 19:21:26 +0000
- To: public-webauthn@w3.org
Unfortunately the term passkey has already been introduced to the standard indirectly, because passkeys are a type of WebAuthn credential and it's weird to treat them like we're saying Voldemort's name. Passkeys have existed for over a year, they are a relatively understood concept amongst this community, and in my opinion, to _avoid_ saying the word passkey would cause _more_ confusion and hinder any greater understanding of it by the dev community at large. Trying to not say 'passkey' by replacing it with `isUserVerifyingPlatformAuthenticatorOrHybridTransportAvailable` is just going to be far and away more confusing and less helpful than calling `isPasskey` > there are no less than 4 definitions of passkey Well that's a great reason to say the definition here, in the standard, from which passkeys are based. To @emlun's point we don't even need to define it ourselves, just link or reiterate FIDO's definition. I'd be fine adding a note to it about what it has in regards to spec terminology, but I'd say we have the most authority outside of the FIDO alliance to say what a passkey is or isn't Passkeys are going to be the majority type of credential used with the WebAuthn API, to avoid the term because some other companies have already defined it incorrectly is cutting off the nose to spite the face. -- GitHub Notification of comment by nicksteele Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1901#issuecomment-1595180860 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 June 2023 19:21:28 UTC