vc-data-model
vc-data-model copied to clipboard
w3c
W3C Verifiable Credentials v2.0 Specification
Hi, I think that there is an error in the example 4 about the type of the degree mentioned https://www.w3.org/TR/vc-data-model/. You are using "type" to indicate the type of the...
There are lots of use-cases in which a VC that contains claims about different subjects is to be used in situations where more than one of these subjects need to...
A very common use case in the VC ecosystem is the presentment of VCs as VPs. Usually, the verifier is interested in whether the holder is the legitimate subject of...
There are some stylistic differences across images - would be good to make them more consistent: - center all content in the top level containers - have consistent content border...
Currently we have: `assertionMethod` -> issuing credentials `authentication` -> signing verifiable presentations I suggest we add support for `capabilityInvocation` and `capabilityDelegation`, and we harmonize the ZCAP-LD / object capabilities APIs...
In [section 4.4](https://w3c.github.io/vc-data-model/CR/2019-03-26/#credential-subject), the term 'credentialSubject' is defined, suggesting a relation between the credential in which it is included and a 'Subject', i.e. an entity about which claims are made....
I know that the current spec is only about a data model. However, it does discuss how credentials can be "realized" in the JSON and JSON-LD syntaxes, and it suggests...
@David-Chadwick your comment in issue #135 about having to be online to verify the referenced credential is a larger challenge in general. VC should be verifiable w/out going to the...
We should consider having something in the data model that specifies how to display a credential in a consistent way, for example, a link to a Web Component for rendering...
I’m puzzling through some simple verifiable claims for bootstrapping some of the basic functions of the classic web of trust (both explicit what actually existed, as well what people falsely...
