Support for Verifiable Credentials Data Model 2.0 [OpenBadges 3.0]

[bsandmann]

Summary

This feature request is to update the Hyperledger Identus project to support the W3C Verifiable Credentials Data Model 2.0. This update is required to be be OpenBades 3.0 compliant. For further discussion on what OpenBadges 3.0 is and why to achieve compatibility with it, please refer to the Achieve compatibility with OpenBadges 3.0 [Summary].

Current Situation

Currently, Identus is aligned with the VC Data Model 1.1 specification, which is still the latest final version of the VC Data Model, but that should change in the next weeks, basically replacing it with 2.0.

Proposed Changes

The primary changes required to support VC Data Model 2.0 involve updating property names for fields inside the credential data-model. I assume that other upcoming developments (e.g. eIDAS 2.0) are also targeting the VC Data Model 2.0 [can someone confirm this?].

The main changes are:

1. Replace issuanceDate with validFrom
2. Replace expirationDate with validUntil
3. Update the default-JSON-LD context from https://www.w3.org/2018/credentials/v1 to https://www.w3.org/ns/credentials/v2

For handle and verify a VC these changes have also to be made in the Identus SDKs.

As of my knowledge this should not have an effect on the VP.

These changes, while minor, represent a breaking for exisiting VCs in the wild. While it is possible to maintain backward compatibility and make the issuing of 1.1 optional I'd personally would opt for a clean break and only support 2.0 when creating new credentials with the Identus API. This would make the change much easier to implement and test. The only relevant party I'm aware of with is currently on Mainnet and would seem to suffer from this change seems to be Socious.

[yshyn-iohk]

All OpenBadges 3.0-related issues are moved to the cloud-agent backlog. We cannot start working on this feature right now, as we have to add JSON-LD VC type and align the model with VCDM 2.0