Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[USE CASE] openHPI #12

Open
4 of 13 tasks
alexandermuehle opened this issue Oct 25, 2021 · 1 comment
Open
4 of 13 tasks

[USE CASE] openHPI #12

alexandermuehle opened this issue Oct 25, 2021 · 1 comment

Comments

@alexandermuehle
Copy link

Actor

openHPI platform, learner, relying party

Submitter

Alexander Mühle (Hasso Plattner Institute) as part of DiBiHo project

User Story

OpenHPI is the free life long learning platform of the Hasso Plattner Institute offering courses focused on IT topics for a less technical audiences. Certificates earned via openHPI should be able to be presented at relying parties such as potential employers. In addition the openHPI platform may use the issued Verifiable Credentials as entry requirements of other openHPI courses.

Data Concepts

Types of credentials:

  • (Proctored) Credentials
  • Record of Achievements
  • Confirmation of Participation

The subject of the Verifiable Credentials should be able to be either pseudonymous or tied to a natural person.

Templates for the visual presentation of the Verifiable Credential content may be provided by the platform.

Restrictions

This information must be readable with a standard text viewer, the verifiable credential must allow for machine processing.
The person, organization or object about which a statement is made as part of a verifiable claim must be readable in the plain text of the verifiable claim in such a way that verification is possible without the use of digital tools.

VC, DID

Tags

Select any of the below that apply and/or add your own at the bottom.

  • issuer-to-subject
  • subject-to-relying-party
  • system-to-system
  • peer-to-peer
  • subject-initiated
  • workforce
  • k-12
  • post-secondary
  • informal
  • e2e (i.e. issuer-to-subject-to-relying-party)
  • multiple-issuers (i.e. multiple parties involved in credential issuance)
  • single credential
  • complex credential
@kayaelle
Copy link
Collaborator

kayaelle commented Nov 5, 2021

Thank you for submitting this use case. If you are able to join us on a Monday call, it'd be great to walk through it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants