Managing Verifiable Presentations with Mixed W3C Verifiable Credentials Data Models (1.1 and 2.0)

[KiruthikaJeyashankar]

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'

[jogu]

Note that there's an issue open to add a format identifier for w3c vcdm 2.0: #5

I'm not sure I fully understand the question you're asking - I'm not a w3c expert, but I would expect that if the wallet is returning both a VCDM 1.1 and a VCDM 2.0 credential in a single response then each would be encoded into separate entries in vp_token and hence the presentation of the VCDM 1.1 credential should have a 1.1 @context, and the presentation of the VCDM 2.0 credential should have a 2.0 @context. If that is what is being done I'm not sure how the canonization problem arises?