Digital Credentials Consortium Integration

[e0d]

Digital Credentials Consortium Integration

Abstract

The Digital Credentials Consortium is a network of leading international universities designing an open infrastructure for academic credentials.

Further details are available here.

This issue proposes designing and implementing an integration between the Open edX platform and the DCC sign-and-verify service and the mobile-based wallet application.

Context and Background

The DCC credential specification was created by a consortium that includes a number of edX partners and Open edX users. The specification is aligned with W3C verifiable credentials initiatives. There is a clear connection between open learning and open credentials standards that emphasize learner ownership and control of attainments.

There is an existing, adjacent, implementation of integration with the DCC sign-and-verify service and mobile wallet. However, there is no direct integration with the Open edX platform. The existing integration is written in python and works with the Django framework. Both technologies are core to the Open edX platform architecture.

Prior art:

• Sign and verify service
• Docs for the MIT ODL integration with xPRO
• The source of the OL-Django app
• The mitol-django-digital-credentials library for integrating with DCC

Scope and Approach

The design should consider integrating with Open edX existing credential store in a loosely coupled way. DCC integration should be optional. Enabling it and configuring it should use project standards like feature flags.

Ideally, the integration can leverage the existing library. Ideally the Open edX project developers and ODL can collaborate on enhancing and maintaining the library.

Value and Impact

To be written

Milestones

[e0d]

There is a European standard that should be considered here.

[dmitrizagidulin]

Hi @e0d and team.

We've looked over the VC-Use Cases and VC-Edu Use Cases document, through the lens of it informing a possible OpenEdx/DCC Wallet integration roadmap.

By that document's terminology, OpenEdX serves as a Issuer Provider role.

We think that the use case E.4 "Online Classes" from Section 3.1 - Education would make the most sense to focus on at the start. A separate use-case would be the provision of a VC wallet through an OpenEdX site, but that seems out of scope maybe for an initial start. Happy to provide more detailed information on workflows and this use-case.

[e0d]

My understanding is that Open Badges v3 will be compatible with the DCC platform, so we should target that rather than anything more specific.