Site Admin

Issuer

W3C, EBSI

Learner

Subject, Holder

W3C, EBSI

Verifier

Verifier

W3C, EBSI

? is this the platform, the organization, the instructor, all of the above?

Issuer

W3C, EBSI

?

Trusted Accreditation Organisations (TAO), verifiable data registry

W3C, EBSI

admin-001

Site Admin

As a site admin, I want to configure the Open edX platform to allow sharing verified credentials with credentials holders, which may be the subject or the subject’s chosen credentials network

1

admin-004

Site Admin

As a site admin, I want to restrict which claims can be asserted by course and organization.

1

admin-002

Site Admin

As a site admin, I want to create and manage cryptographic proof of the identity of my organization – the issuer – and associate that proof with my Open edX deployment to support issuing verifiable credentials

1

admin-003

Site Admin

As a site admin, I want to create and manage cryptographic proof of identity for “tenants” of my deployment like organizations, or specific courses

admin-002

3

admin-005

Site Admin

As a site admin, I want to revoke verified credential, making the non-verifiable, in the case that some intervening issue, say identity fraud or cheating, is discovered.

admin-006

Site Admin

As a site admin, I want to share my cryptographic keys with public registries of issuers: https://ec.europa.eu/digital-building-blocks/wikis/display/EBSIDOC/EBSI+Verifiable+Credentials+Playbook

admin-007

Site Admin

As a site admin, I want to import cryptographic keys created off platform for use with verified credential issuance

admin-008

Site Admin

As a site admin, I want to choose which platform attainments can be asserted in a verified credential.

learner-001

Learner

As a learner, I want to create verifiable claims that assert my attainments earned on the Open edX platform

verifier-001

Verifier

As a verifier, I want to discover and use the issuers public key to verify the integrity of verifiable credentials in an automated way.

learner-002

Learner

As a learner, I want to create assertions that I have completed 1 or more courses

learner-001

1

learner-003

Learner

As a learner, I want to be able to time limit the validity of assertions that I create.

learner-001

1

learner-004

Learner

As a learner, I want the system to assert my identity in a verifiable way to ensure my credentials are valid and portable

1

learner-005

Learner

As a learner, I want to freely move my verified credentials, say between networks or wallets, without the need to interact with the issuer.

1

learner-006

Learner

As a learner, I want to retract an assertion that I have requested so that future attempts to validate that assertion will fail.

?

learner-007

Learner

As a learner, I want the history of my verifiable credentials to be delete along with my other data if I make a request to delete my account.

?

learner-008

Learner

As a learner, I want the ability to ensure credentials will be verified even after I have deleted my account [Capturing this, though I do not think we can support and it would be a lower priority.]

learner-009

Learner

As a learner, I want to choose exactly which claims are included in an issued verifiable credential of the assertions that are supported by the platform

learner-010

Learner

As a learner, I want to create assertions that I have completed 1 or more programs

2

learner-011

Learner

As a learner, I want to create assertions that I have completed 1 or more degrees

2

learner-012

Learner

As a learner, I want to create assertions related to progress milestones within a course or learner sequence.

3

user-004

Learner

As a learner, I was to bring my own DID if I have an existing identity associated with a TAO, or similar.

user-001

User

As a user, I want to opt in to having a Decentralized Identifier Document (DID) for my Open edX identity

user-002

User

As a user, I want to have the ability to retract my Decentralized Identifier Document (DID) – this will render credentials unverifiable

user-003

User

As a user, I want to verify my identity to support robust verifiable credentials – this should leverage existing user verification best practices whether the ID verification, real name, or otherwise.

user-005

User

As a user, I want to have access to a verifiable DID if my account is connected via SSO or Social Auth