- From: Firstyear via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Jun 2023 01:03:12 +0000
- To: public-webauthn@w3.org
> Which is why we add a specific definition in the context of the specification, that can be referenced throughout the specification whenever the term is used. Part of this PR does just that, in support of the new method defined. I think what you're saying is "If we define it here, that will fix it, so everyone will use the term in the same consistent way". I'm saying "People are already using the term in a non-consistent way, and they will never change that behaviour no matter how much we define it". In fact, by trying to add the term "passkey" to the webauthn specification it may in fact make the situation worse as people will arrive at the specification with a preconceived notion of what a passkey is and that may lead to misinterpretation of the specification due to this. I think it's inappropriate to add a marketing term into a specification retroactively when it's already being used in various inconsistent ways in the public. That's all I have to say on the matter, I'll leave it to others to agree or disagree with this. -- GitHub Notification of comment by Firstyear Please view or discuss this issue at https://github.com/w3c/webauthn/pull/1901#issuecomment-1583718730 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 June 2023 01:03:14 UTC