feat: add vcld feature - #50
Conversation
Signed-off-by: Lukas.J.Han <lukas.j.han@gmail.com>
Signed-off-by: Lukas.J.Han <lukas.j.han@gmail.com>
Signed-off-by: Lukas.J.Han <lukas.j.han@gmail.com>
Signed-off-by: Lukas.J.Han <lukas.j.han@gmail.com>
Dtitkaio
left a comment
Dtitkaio
left a comment
There was a problem hiding this comment.
Sorry for the late review. I left some comments!
|
|
||
| // Sample data (will be expanded) | ||
| const sampleDoc: JsonLdDocument = { | ||
| '@context': 'https://www.w3.org/2018/credentials/v1', |
There was a problem hiding this comment.
Strictly speaking, the context has to include all the metadata in the ld part, in our case, including degree and its elements, i.e., type and name. maybe, we can use an example defined in jsonld playground.
https://json-ld.org/playground/
maybe Person??
There was a problem hiding this comment.
I guess, we would like to add json-ld processing when it is needed. The problem is it is not specified in the standard. If I had to guess, we may want to add the semantic processing at least for a verifier after verifying the credential for business logic.
There was a problem hiding this comment.
maybe, we can return the decoded credential with ld part processed after verification??
2 participants
No description provided.