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.

Sign up for GitHub

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

Jump to bottom

Why is the only value of ScopedCredentialType "ScopedCred" as opposed to "ScopedCredential"? #291

Closed
bzbarsky opened this issue Nov 4, 2016 · 3 comments
Closed

Why is the only value of ScopedCredentialType "ScopedCred" as opposed to "ScopedCredential"? #291

bzbarsky opened this issue Nov 4, 2016 · 3 comments
Labels
priority:implementation subtype:renaming type:editorial
Milestone
Last Working Draft

Comments

@bzbarsky
Copy link

bzbarsky commented Nov 4, 2016

Is there a reason we're trying to save a few characters at the cost of confusion here?
@equalsJeffH equalsJeffH added this to the WD-04 milestone Nov 7, 2016
@equalsJeffH
Copy link
Contributor

yes, we could spell it all out, though, the enum values may change. see also #296

@equalsJeffH equalsJeffH modified the milestones: CR, WD-04 Nov 9, 2016
@vijaybh vijaybh mentioned this issue Jan 24, 2017
Closed
@AngeloKai AngeloKai mentioned this issue Feb 17, 2017
Closed
@selfissued
Copy link
Contributor

We need to decide this (and other) renaming issues for the Implementer's Draft, since they change the API.

@jyasskin
Copy link
Member

jyasskin commented May 4, 2017

This was obsoleted by #432, which renamed the enum value to "public-key".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority:implementation subtype:renaming type:editorial
Projects
None yet
Milestone
Last Working Draft
Development

No branches or pull requests
4 participants
@jyasskin @equalsJeffH @bzbarsky @selfissued