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

Status of what? #35

Closed
David-Chadwick opened this issue Dec 8, 2022 · 3 comments
Closed

Status of what? #35

David-Chadwick opened this issue Dec 8, 2022 · 3 comments
Assignees
@msporny
Labels
before-CR This issue needs to be resolved before the Candidate Recommendation phase. pr exists

Comments

@David-Chadwick
Copy link
Contributor

There is some confusion about the semantics of the credentialStatus field, whether it refers to the status of the credential or the verifiable credential. (see w3c/vc-data-model#991) Clearly both the underlying credential (e.g. degree certificate) and the digitally signed VC have their own separate validity periods and statuses. This confusion is carried through into the status list specification in that the statusPurpose in not precise enough.
It has been stated that vc-status-list-2021 can apply to both the credential and the verifiable credential, in which case the statusPurpose must clearly specify to which of these this list applies.
The follow values for statusPurpose are suggested

credentialRevocation - the credential has been revoked (even though the cryptographic proof of the verifiable credential is still valid)
proofRevocation - the cryptographic proof of the verifiable credential has been revoked. This does not imply that the enclosed credential has been revoked, only that the verifiable credential has been revoked. The status of the credential is unknown.
credentialSuspension - the credential has been suspended. This may be reversed at a later time.

I am not sure it makes sense to have a proofSuspension. What does this mean and when would it apply?
@msporny msporny added the before-CR This issue needs to be resolved before the Candidate Recommendation phase. label Sep 10, 2023
@msporny
Copy link
Member

msporny commented Dec 28, 2023

Quite a bit has happened in the VCDM since this issue was raised. The VCDM now only defines what constitutes a "verifiable credential". The status field for a "verifiable credential" has to do with whether or not the "verifiable credential" has been revoked or not. This might be for any reason, and just because the "verifiable credential" has been revoked doesn't mean that the underlying credential is revoked. That said, if the "verifiable credential" has been revoked, then it shouldn't be used to drive any business process that requires the "verifiable credential" to not be revoked (or suspended).

I will add some explanatory text about this in a PR.

@msporny msporny self-assigned this Dec 28, 2023
@msporny msporny mentioned this issue Dec 28, 2023
Merged
@msporny
Copy link
Member

msporny commented Dec 28, 2023

PR #106 has been raised to address this issue. This issue will be closed once PR #106 has been merged.

@msporny
Copy link
Member

msporny commented Jan 13, 2024

PR #106 has been merged, closing.

@msporny msporny closed this as completed Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@msporny msporny

Labels
before-CR This issue needs to be resolved before the Candidate Recommendation phase. pr exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@msporny @David-Chadwick