Rieks

Results 35 issues of Rieks

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...

pending close

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....

pending close

When a party in the role of holder uses an app in which to manage his credentials, this app is likely to have functionality that allows the holder to view...

When I glanced at the draft spec, it occurred to me that messages are being specified, which made me wonder why DIDComm isn't used for that.

type: question
artifact:companion-guide

You may want to consider adding links in the README for - the eSSIF-Lab project (https://essif-lab.eu/) - the eSSIF-Lab subgrantees solutions booklet (https://essif-lab.eu/wp-content/uploads/2022/09/essif-booklet-22a.pdf) - the eSSIF-Lab subgrantees project descriptions booklet...

In the VCDM, the term 'subject' is only **defined** in relation to claims, not in relation to credentials. Since a VC is a (non-empty) collection of claims, the phrase "subject...

[Section C](https://www.w3.org/TR/vc-data-model/#subject-holder-relationships) of the VCDM (subject-holder relationships) informs readers that IF (a particular subject-holder relationship exists), THEN (some specific things can be done). In practice, though, verifiers need to establish...

The spec defines "holder" as: "an entity that is in possession of a [credential](https://hyperledger.github.io/anoncreds-spec/#term:credential). In many use cases, the holder is also the identity [subject](https://hyperledger.github.io/anoncreds-spec/#term:subject)." Since the term "entity" isn't...

I don't think of myself as a newbie to DIDs (VCs, and SSI stuff), but nevertheless I find it difficult to grasp the ideas behind this (and some other) repo's....

bug
in progress

For (candidate) standards documents, it is a good practice that whenever a version is ratified or otherwise assigned some state, this is mentioned in the document itself with the date...