- From: =JeffH via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Jun 2016 20:55:18 +0000
- To: public-webauthn@w3.org
hm.. In looking at the spec, I notice that although we have named our
overall ceremonies "registration" and "authentication" (a ceremony
includes the user as an explicit component of the model), the
underlying API artifacts are named as variations on "credential" and
"assertion" respectively, e.g.:
```
Promise < ScopedCredentialInfo > makeCredential (
Account accountInformation,
sequence < ScopedCredentialParameters > cryptoParameters,
BufferSource attestationChallenge,
optional unsigned long
credentialTimeoutSeconds,
optional sequence < Credential > blacklist,
optional WebAuthnExtensions credentialExtensions
);
Promise < WebAuthnAssertion > getAssertion (
BufferSource assertionChallenge,
optional unsigned long assertionTimeoutSeconds,
optional sequence < Credential > whitelist,
optional WebAuthnExtensions assertionExtensions
```
Thus I wonder about (re-)naming these two major extension subclasses
as "credential extensions" and "assertion extensions".
--
GitHub Notification of comment by equalsJeffH
Please view or discuss this issue at
https://github.com/w3c/webauthn/issues/131#issuecomment-228180934
using your GitHub account
Received on Thursday, 23 June 2016 20:55:21 UTC