[webauthn] Track rename issues to maintain consistency

AngeloKai has just created a new issue for 
https://github.com/w3c/webauthn:

== Track rename issues to maintain consistency ==
A number of renaming request has been added to the issue list. Opening
 up this issue to track all the related request so we have a holistic 
view of all the changes requested: 

- https://github.com/w3c/webauthn/issues/326:
   - hashAlg -> hashAlgorithm 
- https://github.com/w3c/webauthn/issues/329: 
   - Attachment -> CredentialAttachment 
   - getAssertion -> ? 
- https://github.com/w3c/webauthn/issues/312:
   - Account -> RelyingPartyAccount
   - ClientData ->  AuthenticationClientData
- https://github.com/w3c/webauthn/issues/329: 
   - Attachment -> CredentialAttachment 
   - getAssertion -> ? 
- https://github.com/w3c/webauthn/issues/328:
   - ScopedCred -> scoped-cred
- https://github.com/w3c/webauthn/issues/296:
   - Too much to list at once 
- https://github.com/w3c/webauthn/issues/291:
   - ScopedCred -> ScopedCredential 
- https://github.com/w3c/webauthn/issues/327:
   - allowList -> allowCredentials
   - excludeList -> excludeCredentials
- https://github.com/w3c/webauthn/issues/325:
   - rpId -> relyingPartyId
   - rpDisplayName -> relyingPartyDisplayName
- https://github.com/w3c/webauthn/issues/323:
   - tokenBinding -> tokenBindingID

Please feel free to keep adding issues on this thread. 

Please view or discuss this issue at 
https://github.com/w3c/webauthn/issues/353 using your GitHub account

Received on Friday, 17 February 2017 21:13:01 UTC