vc-use-cases
vc-use-cases copied to clipboard
w3c
Verifiable Credentials Use Cases
Need to review and Update Editor/Author section to verify it's correct.
The [VC Use-cases document](https://www.w3.org/TR/verifiable-claims-use-cases/) talks about the ability of issuers to revoke credentials that they issued, but it does not mention who should be able to check whether or not...
The use cases should speak to "amending" a verifiable credential... specifically, how this might be different from "disputing" a credential, and how an amendment might be added by the original...
"She is able to retrieve this because it is available from many places _often_ the Internet." "often" should probably read "over".
I just read @jandrieu's post of Monday 16-8-2021, 32:16 CEST to the Credentials Community Group (I have no clue about a link to make it easier to reference), called "Diagrams...
Related to: - https://github.com/w3c/vc-data-model/issues/930 - https://github.com/w3c/vc-data-model/issues/931 - https://github.com/w3c/vc-data-model/issues/932 The second (multiple subjects) is all that's _officially_ supported today. I'd like to see some good multi-subject credentials have a place in...
There is a number of issues in the VCDM that are talking about holder binding: https://github.com/w3c/vc-data-model/issues?q=is%3Aissue+is%3Aopen+label%3Aholder-binding. We should add use cases to make it more clear what people really require...
but word "amend" doesn't appear in VC Data model. might be worth doing a quick prune of any mention of amend from both diagram and any use-cases where it is...
