w3c / vc-use-cases

Verifiable Credentials Use Cases
https://w3c.github.io/vc-use-cases/
Other
50 stars 22 forks source link

Update requested for section 6.1 (VC creation) #142

Open RieksJ opened 1 year ago

RieksJ commented 1 year ago

In section 6.1, step 3 says 'verifiy identity'. This suggests that the issuer will somehow learn some identity (presumably that of Jane). It also suggests that this is sufficient to generate and subsequently issue the credential.

In the real world, if Jane navigates to a web site and sends it some request (let's limit that here to the case where the request is for getting a credential of a specific kind issued), then the first thing that needs to be done is for the issuer to determine whether or not it is going to honor or reject the request (which some might call 'access control'), and only after it has been established that the request is going to be honored, the issuer will determine what the specific content is going to be of the credential type that was specified in the request). These are two activities, which #141 summarizes as "providing a credential".

After that, the actual credential can be generated (the particular JSON, JSON-LD, ..., and proofs/signatures added) and issued.

This issue calls for changing both the figure and also the steps as described below the figure such that it becomes consistent with #141