Interoperability of Digital Credentials
Download as PPTX, PDF0 likes313 views
This document discusses standards, technology, and governance for ensuring interoperability of diplomas using blockchain. It proposes a basic ontology to describe learning opportunities, specifications, and credentials. Europass verifiable claims are proposed to structure credential data using eIDAS seals for proof. Decentralized identifiers could link credentials to personal identities and accreditations. The EBSI notarization service could provide an immutable proof of authenticity without long-term PKI signing. Governance requires a stakeholder-led, cross-sectoral approach across identity, education, and employment to agree common standards.
Interoperability of Digital Credentials
- 1. Diplomas Track Deep Dive: Ensuring Interoperability Anthony F. CAmilleri EBSI Diplomas use case group 22th & 23rd October 2019 EBSI use case groups Joint workshop
- 3. Standards ENSURING WE SPEAK THE SAME LANGUAGE
- 4. Design Brief for an Effective Learning Standard
- 5. Addresses all Levels of Education
- 6. Aligned with European Recognition Instruments
- 8. Applicable to the whole course lifecycle
- 10. Free & Open Source
- 11. Current Standards for Education ELMO/EMREX (Higher Education: supporting transfer of student data between institutions) Qualifications Metadata Schema / EQF Learning Object Metadata (learning objects) Schema.org Courses (course catalogues) PLOTEUS Learning Opportunity data model (course catalogues) Open Badges (credentials) ISO / CEN Standards
- 12. No Existing Standard fully reflects lifelong learning
- 13. A new Meta-Model for Interoperability Extend the scope, purpose and use Qualifications Metadata Schema (legislative basis)
- 16. (Learning) Achievement (Learning) Activities lead to Assessment (of learning) prove A Basic Ontology of a Learning Process
- 17. (Learning) Achievement (Learning) Activities lead to Assessment (of learning) prove A Basic Ontology of a Learning Process (Learning) Outcomes (Learning) Entitlements knowledge | skills autonomy & responsibility
- 18. OPPORTUNITIES Describe an offer by an organization to direct an activity which leads to a learning outcome (proven by an assessment) Examples include: courses, apprenticeships, voluntary experiences, etc. SPECIFICATIONS specify what can be learned, what can be done and how it can be assessed. Examples include: occupational profiles, competence frameworks, curricula, skill classifications CREDENTIALS Describe a claim about an individual such as which activities they have done, and their achievements proven by assessments. Examples include: attendance certificate, degree, diploma supplement, letter of recommendation 1 2 3 A Basic Ontology of a Lifecycle Concepts
- 19. Specifications are interrelated and build on each other… Lesson Plan Course Curriculum Occupational Standard provide vocabulary provide scaffold implemented by implemented by
- 20. …always using the same basic concepts Lesson Plan Course Curriculum Occupational Standard provide vocabulary provide scaffold implemented by implemented by
- 21. Learning Opportunities 21 Learning Opportunity Specification Learning Opportunity Add information about offer at a space and time, by a specific organisation Qualification Special type of (achievement) learning opportunity specification
- 22. Credentials 22 Learning Opportunity Credential Add info about (a) individual’s specific performance on the learning opportunity and (b) their grades Qualification Award Special type of credential
- 23. Europass Verifiable Claims: A High Level Structure Credential Metadata Claim Proof Issuer Data (eIDAS Legal Person & Accreditation association) Issuer Data Other Identifiers Credential Type Qualification Award Enrolment; Participation Exam Result; Activity Specification + History Assessment Specification + History + Grades Achievement Specification + History + Grades eIDAS eSeal (as per directive on qualified eSeals) Other Proofs (accepted but not legally admissible) Person (eIDAS Natural Person) Person (Other Identifiers) Specification: What was done Grade: To which level was it done? History: Where, When, How was it done and who directed it?
- 24. Technology CREATING A RELIABLE TRUST INFRASTRUCTURE
- 25. Europass Verifiable Claims: A High Level Structure Credential Metadata Claim Proof Issuer Data (eIDAS Legal Person & Accreditation association) Issuer Data Other Identifiers Credential Type Qualification Award Enrolment; Participation Exam Result; Activity Specification + History Assessment Specification + History + Grades Achievement Specification + History + Grades eIDAS eSeal (as per directive on qualified eSeals) Other Proofs (accepted but not legally admissible) Person (eIDAS Natural Person) Person (Other Identifiers) Specification: What was done Grade: To which level was it done? History: Where, When, How was it done and who directed it? Problematic
- 26. Organisational Identifiers Require Organisational eID: which can cost up to €600/year No in-built way to link to organisation to natural person: large organisations must manage permissions to physical device Organisational eID says nothing about Accreditation as an Educational Organisation Multiple Education-Specific Identifiers which are generally not interoperable.
- 27. Accreditation via Verifiable Credentials and DIDs Government issues VC to QA Authority (authorisation to accredit) National QA Authority issues VC to University (authorisation to issue degrees) University issues VC to Rector (authorisation to sign degrees on behalf of University) Rector issues VC to student (educational diploma) Advantage: No need to collect accreditation data from MS. Only requires the root to be in a verifiable registry. The rest of the authorisations can be done through claims with each claim embedding the claim above.
- 28. Personal Identifiers Not Feasible to issue diplomas to verified national eIDs. Use of only default metadata fields from eIDAS produces multiple identification exceptions (name changes etc). Decentralised Identifiers linked to eIDs may provide a more automatable, easier to use, and persistent workflow.
- 29. PKI-based Proofs Diplomas signed via PKI need to be resigned approx. every 5-7 years. For user-convenience this requires use of cloud-based resigning services. Cloud-dependency makes self-sovereignty impractical
- 30. EBSI- Notarisation obviates the need for e-signing NOTARISATION ALLOWS AN IMMUTABLE GUARANTEE OF AUTHENTICITY.
- 31. Linking these Ideas to the EBSI Roadmap Issuer Credential Issued by Organisation Identified through DID VC issued to Organisation to award it ‘Right to Issue’ Identity linked to eIDAS eSeal Credential Subject Identified through DID; Credential issued to wallet linked to Identity Link to national eID Proof Notarisation via EBSI Explore legally valid Notarisation V1 V2 VC Concept
- 32. Governance CREATING A RELIABLE TRUST INFRASTRUCTURE
- 33. Efforts for Self- Sovereign Identity and Verifiable Credentials need to be connected through Educational Standards CONNECTING EDUCATIONAL DATABASES IS ABOUT MUCH MORE THAN IDENTITY
- 34. “Who do I Call to decide on Educational Standards?”
- 35. Some principles for a governance system Stakeholder-Led Member-State Endorsed Publicly Consulted Long-Term Governed Brief to Manage Standards for Organisational Identifiers Personal Identifiers Accreditations Proofs Data Interchange between Institutions Data Interchange between Institutions / Students / Employers Data Interchange between MS Courses, Skills, Learning Outcomes, Achievements
- 36. “Lock ‘em Up” (until a standard is agreed)
- 37. Need for a Cross- Sectoral Approach Identity, Technology, Education, Employment stakeholders and regulators need to come together for real impact