search

w3c / webauthn

Web Authentication: An API for accessing Public Key Credentials
https://w3c.github.io/webauthn/
Other
1.18k stars 171 forks source link

Editorial: WebAuthn or WebAuthN #1056

Closed apowers313 closed 6 years ago

apowers313 commented 6 years ago

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) and sometimes "WebAuthN" (e.g. here). 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)?

emlun commented 6 years ago

@agl asserts we should go with "WebAuthn". I agree that this looks prettier.

selfissued commented 6 years ago

I think the most important thing is for us to be consistent and use the same spelling every time. I'm fine with either spelling. I do get that "AuthN" is commonly used in the industry and so understand why some would prefer "WebAuthN".

emlun commented 6 years ago

How do we make a decision?

equalsJeffH commented 6 years ago

The lower cased "Authn" is also commonly used in the industry, just saying. I prefer the lower case "WebAuthn", which is what I've been consistently using, but can live with either if it's a big deal.

rlin1 commented 6 years ago

Decision last week was to standardize on WebAuthn (lower case n)

agl commented 6 years ago

From 2018-09-12 call: it's "WebAuthn".

nadalin commented 6 years ago

@emlun Please make sure all instances use lowercase "n" and close

rlin1 commented 6 years ago

Quick search in index.bs today didn't find any WebAuthN in the document.

emlun commented 6 years ago

All instances in the WebAuthn spec currently use lowercase "n". Please re-open this if there's anything else we need to do, like include style guidance in the spec preamble or something.