Managing Verifiable Presentations with Mixed W3C Verifiable Credentials Data Models (1.1 and 2.0)
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
Hello,
We need assistance understanding how to manage Verifiable Presentations (credential format - ldp_vp) that include VCs with both W3C Verifiable Credentials Data Model 1.1 and W3C Verifiable Credentials Data Model 2.0.
Usecase
- A wallet holder can download W3C Verifiable Credentials Data Model 1.1 and 2.0 credentials.
- They are required to present both sets of credentials to the Verifier.
- Given this use case, how should the Wallet construct the Verifiable Presentation’s “
@context” property?
Issue
- We are currently creating a Verifiable Presentation with its “
@context” property value set only to the W3C Verifiable Credentials Data Model 1.1 context, and we are encountering canonicalization issues.
More details are attached below:
'Canonization failed:', { [jsonld.SyntaxError: Invalid JSON-LD syntax; tried to redefine "VerifiableCredential" which is a protected term.]
name: 'jsonld.SyntaxError',
details:
{ code: 'protected term redefinition'
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
Read the linked W3C Verifiable Credentials Data Model 1.1 and 2.0 sections on presentations, then reproduce the reported ldp_vp canonicalization error involving the protected VerifiableCredential term. Done means documenting or confirming how a presentation containing credentials from both versions should construct its @context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100