Track rename issues to maintain consistency

[AngeloKai]

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:

• hashAlg -> hashAlgorithm? #326:
  • hashAlg -> hashAlgorithm
• Too generic names? #329:
  • Attachment -> CredentialAttachment
  • getAssertion -> ?
• Consider scoping Account and ClientData #312:
  • Account -> RelyingPartyAccount
  • ClientData -> AuthenticationClientData
• Too generic names? #329:
  • Attachment -> CredentialAttachment
  • getAssertion -> ?
• "ScopedCred" enum should be "scoped-cred" #328:
  • ScopedCred -> scoped-cred
• Refine meaning of PublicKeyCredentialType to be "signature & assertion format (and version thereof)" #296:
  • Too much to list at once
• Why is the only value of ScopedCredentialType "ScopedCred" as opposed to "ScopedCredential"? #291:
  • ScopedCred -> ScopedCredential
• excludeList and allowList should be excludeCredentials and allowCredentials #327:
  • allowList -> allowCredentials
  • excludeList -> excludeCredentials
• "rp" isn't a widely enough known acronym?, should be relyingParty instead? #325:
  • rpId -> relyingPartyId
  • rpDisplayName -> relyingPartyDisplayName
• tokenBinding member of ClientData should be tokenBindingId #323:
  • tokenBinding -> tokenBindingID

Please feel free to keep adding issues on this thread.

[AngeloKai]

Additional issues related to renaming:

• adopt consistent terms for RP server-side and client-side components #80:
  • script / browser scripts / javascript / etc. -> RP client-side component
  • the server / server / servers / WebAuthn Relying Party's server -> RP server-side component
• do not totally lose the term "WebAuthn Relying Party" #180:
  • Relying Party -> WebAuthn Relying Party
• References to "algorithm" and "alg" should be same string #351:
  • Use the same reference when talking about algorithm and alg

[equalsJeffH]

@AngeloKai thanks for this shepherding effort.

wrt #180, it should more accurately be described as..

• Relying Party -> WebAuthn Relying Party [at 1st use of [RP] in major sections]

[equalsJeffH]

perhaps we ought to edit (and sort) the list in the original post rather than have a disjointed list spread across multiple posts?

that said, we should include pointers to relevant PRs, e.g.:

• PR Rename Account and ClientData fixes #312 #344 has further discussion of Consider scoping Account and ClientData #312

[vijaybh]

Possible link to #60 since we are discussing rationalizing namespace wrt Credential Management.

[equalsJeffH]

a convenient way to group issues/PRs is to use the github.com "label" functionality. So I've created "subtype:" labels, e.g., "subtype:renaming", and assigned the latter to all the issues/PRs listed above at this time. that makes it one-click easy to get a list of so-labeled items.

[selfissued]

We should verify that all the renaming issues use the subtype:renaming lablel and then close this issue.

[equalsJeffH]

AFAIK we are consistently using the "subtype:renaming" label and so am closing this issue.