Add support for VerifiableCredential DataModel 2.0

[paullatzelsperger]

Feature Request

Support for VC DataModel 2.0 should be added, in order to be fully compliant with the Decentralized Claims Protocol specification.

This includes the following aspects:

• support for VCs secured with JOSE enveloping proofs (JWT) including EnvelopedVerifiableCredentials
• support for VPs secured with JOSE enveloping proofs (JWT) including EnvelopedVerifiablePresentations: this includes being able to create them (in IH)
• extending the CredentialFormat enum to reflect these additional forms.

Limitations

• From the specification it follows, that VC2.0 presentations may only contain VC2.0 credentials - mixing and matching of VC1.0 and VC2.0 is not possible. Whether a VC/VP is 1.1 or 2.0 must be derived from the context: "https://www.w3.org/ns/credentials/v1" vs "https://www.w3.org/ns/credentials/v2"

• Similarly, VC 2.0 presentations must use the EnvelopedVerifiablePresentation type, and must only contain EnvelopedVerifiableCredentials (spec):

  Verifiable Credentials secured in verifiable presentations MUST use the Enveloped Verifiable Credential type defined by the [VC-DATA-MODEL-2.0].

  Verifiable Presentations in verifiable presentations MUST use the Enveloped Verifiable Presentation type defined by the [VC-DATA-MODEL-2.0].

• There will only be support for JOSE proofs in EDC's implementation of VC2.0, i.e. no embedded proofs (LD proofs) or COSE!

Which Areas Would Be Affected?

the identity-trust meta-module, IdentityHub

Why Is the Feature Desired?

full compliance with DCP's profiles

Solution Proposal

• Add support for verifying VC2.0 Presentations and Credentials #4707
• Add support for creating VC2.0 Presentations IdentityHub#518 this is the "writing" side of things

Note: at a later stage, IdentityHub will also have to issue credentials, i.e. create VC2.0 Credentials