Update to W3C VC DMv2
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 125
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
The current specification is based on the W3C VC DM v1.
The W3C VC DM v2 is about to be published as a Candidate Recommendation. It contains a number of differences to the v1 DM. Importantly all VC DM v2 VCs must have an @context property. More importantly, securing them using SD-JWT is indicated in a different way to securing a non-W3C VC with SD-JWT. Specifically the typ is set to vc+ld+json+sd-jwt (in the latest draft version of the specification), rather than vc+sd-jwt which is used by the SD-JWT VC draft.
Therefore a number of changes will be needed to the OpenID4VCI specification if it is to cater for the W3C VC DM v2.
This issue is a placeholder to indicate that some changes will be needed in order to accommodate the W3C VC DM v2.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by reviewing the OpenID4VCI specification sections covering W3C VC DM and SD-JWT, then compare the v1 and v2 requirements described in the issue. Done means defining and implementing the necessary specification changes for W3C VC DM v2 support.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100