Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a Terminology Section #50

Closed
jcjones opened this issue Mar 23, 2016 · 6 comments
Closed

Add a Terminology Section #50

jcjones opened this issue Mar 23, 2016 · 6 comments
Assignees
Milestone

Comments

@jcjones
Copy link
Contributor

jcjones commented Mar 23, 2016

Some terms like Relying Party are known sources of confusion. We should add a terminology section to the specification that explains particular terms.

If you have a known confusable term, please add a comment to this issue so I can pick those up, too.

@jcjones jcjones self-assigned this Mar 23, 2016
@leshi
Copy link
Contributor

leshi commented Mar 23, 2016

Some quick thoughts: Webapp Authentication Backend, Webapp Backend, Authentication Backend, Authentication Server, Webapp Server

@nicola
Copy link

nicola commented Mar 30, 2016

OpenID uses Relying Party maybe it is a good idea to keep it and explain the term.

@jcjones
Copy link
Contributor Author

jcjones commented Mar 30, 2016

Also, "Authenticator"

@flpm
Copy link
Member

flpm commented Apr 6, 2016

I took a first pass and made an initial list of terms. There are some generic terms we may not want to include, but since it's easier to cut I kept them anyway:

account
assertion
assertion challenge
assertion extension
attestation
attestation certificate
attestation challenge
attestation core
attestation header
attestation key
attestation statement
authentication
authenticator
authenticator attestation GUID (AAGUID)
authenticator data
authenticator operation
authenticator session
blacklist
browser
certificate authority (CA)
client
client data
client data hash
client extension
client platform
contextual binding
credential
credential extension
credential identifier
credential type
cryptographic algorithm
cryptographic key
cryptographic proof
cryptographic signature
DAA root key
device
Direct Anonymous Attestation (DAA)
effective top-level domain plus one (eTLD+1)
embedded authenticator
encoded client data
endorsement key
extension identifier
external authenticator
friendly fraud
global correlation handle
hash algorithm
intermediate CA
local storage
origin
privacy CA
private key
promise
public key
public suffix plus one (PS+1)
raw data
relying party
relying party identifier (RPID)
request
RogueList
root CA
script
secure context
server
standard extension
test of user presence
transaction authorization
user
user agent
user verification
user verification index (UVI)
web application
whitelist

@jcjones
Copy link
Contributor Author

jcjones commented Apr 8, 2016

Sorry for the delay on this; it's taking a bit more time than I anticipated, so it ran into today.

jcjones added a commit that referenced this issue Apr 8, 2016
This is a first pass, placing the Terminology section just before
Acknowledgements.

I made a pass through, attempting to ensure the first use of a term within
a given section was always linked back to the definition.

I also made an effort to always spell out "WebAuthn Relying Party" for the first
use in each section, and remove the use of "RP" (excepting the use of "RP ID").

There are some more whitespace cleanups as well, though I tried to minimize them.
vijaybh pushed a commit that referenced this issue Apr 12, 2016
This is a first pass, placing the Terminology section just before
Acknowledgements.

I made a pass through, attempting to ensure the first use of a term within
a given section was always linked back to the definition.

I also made an effort to always spell out "WebAuthn Relying Party" for the first
use in each section, and remove the use of "RP" (excepting the use of "RP ID").

There are some more whitespace cleanups as well, though I tried to minimize them.
@jcjones
Copy link
Contributor Author

jcjones commented Apr 13, 2016

Closed by e3dc893; follow-ons to continue as needed.

@jcjones jcjones closed this as completed Apr 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants