- From: Adam Powers via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Sep 2018 13:44:14 +0000
- To: public-webauthn@w3.org
apowers313 has just created a new issue for https://github.com/w3c/webauthn: == Editorial: WebAuthn or WebAuthN == Throughout the W3C WebAuthn spec, the spec / technology is referred to as "WebAuthn". In CTAP, it is sometimes referred to as "WebAuthn" (e.g. [here](https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html#u2f-authenticatorMakeCredential-interoperability)) and sometimes "WebAuthN" (e.g. [here](https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html#biblio-webauthn)). Third-party usage is becoming mixed as well. Part of this is because of the historical usage of AuthN to mean "authentication" versus AuthZ to mean "authorization". Should we revert back to the historical usage in the spec (e.g. WebAuthN)? Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1056 using your GitHub account
Received on Wednesday, 5 September 2018 13:44:15 UTC