You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
RieksJ
changed the title
Update requested for Figure 4 (VC Creation Flow Diagram)
Update requested for section 6.1 (VC creation)
May 8, 2023
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
The text was updated successfully, but these errors were encountered: