Glossary

← Foundations

Short definitions of the terms used across this site, from eIDAS 2.0 and the EUDI Wallet to the two verifiable credential stacks and the education formats. The list merges the glossaries of the Badges guide v1.1 (EUNIS SIG, July 2026), Badges and Digital Credentials in Higher Education, and the VC guide v1.1 (EUNIS SIG, July 2026), Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC, updated where regulation has moved on and extended with other terms the site uses. Each entry links to the page that explains the term in full.

For the distinctions that cause most confusion (badge, credential and microcredential; data model and proof mechanism; selective disclosure and unlinkability), start with the Vocabulary.

Jump to: A  ·  B  ·  C  ·  D  ·  E  ·  H  ·  I  ·  J  ·  L  ·  M  ·  O  ·  P  ·  Q  ·  R  ·  S  ·  T  ·  U  ·  V  ·  W

A

  • ARF (Architecture Reference Framework): The technical reference the Commission and Member States maintain for building EUDI Wallets, covering roles, formats, protocols and trust anchors. It is revised often and is not binding in itself: where it differs from the implementing acts, the acts prevail. See EUDI Wallet ARF.

B

  • Batch issuance: A workaround used in SD-JWT VC deployments: the issuer hands the holder many single-use copies of the same credential, so a different copy can be shown each time. It reduces correlation between verifiers but not collusion with the issuer, and it keeps the holder dependent on the issuer for fresh copies. See Selective disclosure vs unlinkability.
  • bbs-2023 (BBS): A Data Integrity cryptosuite for W3C-VC in which the issuer signs once and the holder derives a new, mathematically fresh proof for every presentation, so the proofs themselves cannot be linked. Metadata such as a status-list index or a unique identifier can still correlate presentations unless the design hides it. See Selective disclosure vs unlinkability.
  • Bitstring Status List: The W3C mechanism for publishing credential status as a compressed list of bits, formerly StatusList2021. It supports revocation and suspension as separate states and is the status mechanism of the W3C-VC stack, including the EBSI registries. See The W3C-VC stack.

C

  • Canonicalisation: Turning a credential graph into one deterministic form before it is signed, so that documents with the same meaning always produce the same signature. Data Integrity proofs depend on it; the “rdfc” in cryptosuite names such as ecdsa-rdfc-2019 refers to RDF canonicalisation. See The W3C-VC stack.
  • CLR (Comprehensive Learner Record): The 1EdTech standard for a transcript-like record that gathers many achievements of one learner in a single verifiable document. CLR 2.0 was released alongside Open Badges 3.0 in May 2024 and shares its alignment with the W3C data model. See Open Badges.
  • @context: The declaration in a JSON-LD credential that maps each field name to a published, governed definition. In W3C-VC it is part of the signed payload, so the issuer signs the meaning of the data together with the data. See The W3C-VC stack.
  • Credential: A formal statement by a trusted authority that someone holds a qualification, competence or right. What makes it a credential is the institutional trust, and where relevant the legal weight, behind it, not the medium. See Vocabulary.
  • Credential type: What a credential attests (a degree, an enrolment, a professional qualification), as opposed to the format that carries it. The same type can travel in different formats, which is why the type should be characterised before a format is chosen. See Vocabulary.

D

  • Data Integrity: The W3C family of proofs embedded in a credential and computed over its canonical form. It supports several cryptosuites (ecdsa-rdfc-2019, eddsa-rdfc-2022, bbs-2023), so the proof layer can change while the data model stays the same. See The W3C-VC stack.
  • Data model: The part of a credential format that defines how content is structured and where its meaning is defined. In principle it is independent of the proof mechanism that secures it; the two stacks differ in how far they keep the two apart. See Two stacks, not two flavours.
  • DC4EU (Digital Credentials for Europe): The EU large-scale pilot for credentials in education and social security, which tested the wallet-oriented EDC lineage on EBSI with both W3C-VCDM and SD-JWT VC payloads. It ended in 2025; its blueprints, the Sectorial EAA Catalogue and its final report are its legacy, not a production service. See EBSI and DC4EU.
  • DID (Decentralised Identifier): An identifier that can be resolved and verified without depending on a single central registry operator. In the W3C-VC stack it identifies issuers; in EBSI, legal entities are identified with did:ebsi. See EBSI and DC4EU.
  • Digital badge: An image or icon that marks participation or achievement inside one platform. Without structured metadata or a verification mechanism it cannot leave that platform as evidence; it is not the same as an Open Badge. See Vocabulary.
  • Digital credential: A credential that is issued, stored and shared in digital form. In its strong sense, as a verifiable credential, it is tamper-evident and can be checked cryptographically without asking the issuer. See Vocabulary.

E

  • EAA (electronic attestation of attributes): The eIDAS 2.0 term for a signed statement about a person’s attributes, such as a qualification, held in or presented from a wallet. It comes in three legal categories: non-qualified EAA, QEAA and PuB-EAA, which are technically alike but differ in legal effect. See eIDAS 1.0 vs eIDAS 2.0.
  • EBSI (European Blockchain Services Infrastructure): A permissioned blockchain run by the Commission and Member States that hosts shared trust registries: the TIR, the TSR, a DID registry and status registries. It underpins the DC4EU/EBSI lineage of EDC. See EBSI and DC4EU.
  • ECTS (European Credit Transfer and Accumulation System): The European credit system for expressing learning volume, based on student workload. Under the Council Recommendation on microcredentials, workload is stated in ECTS credits wherever possible, and ELM has a field for it. See European Digital Credentials.
  • EDC (European Digital Credentials): Digitally signed credentials whose content is structured with the European Learning Model, so their meaning is shared across Member States. There are two lineages: Europass/EDCI, in production, and the wallet-oriented DC4EU/EBSI lineage, built mainly on W3C VCDM. See European Digital Credentials.
  • EDCI (European Digital Credentials Infrastructure): The Commission’s infrastructure behind Europass digital credentials. Credentials are JSON-LD files structured with ELM and sealed with qualified electronic seals under eIDAS; learners can keep them in their Europass profile. See Europass / EDCI.
  • eIDAS (1.0 and 2.0): The EU rules on electronic identification and trust services. eIDAS 1.0, Regulation (EU) 910/2014, gave legal effect to qualified signatures and seals; eIDAS 2.0, Regulation (EU) 2024/1183, adds the EUDI Wallet, electronic attestations of attributes and privacy requirements such as Article 5a(16). See eIDAS 1.0 vs eIDAS 2.0.
  • EIF (European Interoperability Framework): The Commission’s 2017 framework for interoperable public services. It names four layers, legal, organisational, semantic and technical, under integrated public service governance; the site uses it to place the credential ecosystem layer by layer. See Interoperability map.
  • ELM (European Learning Model): The EU’s semantic model for learning and qualifications data: EQF level, ECTS credits, learning outcomes, assessment, quality assurance and more. It gives EDC its shared meaning and, in the W3C-VC stack, is referenced directly from the @context. See European Digital Credentials.
  • EMREX: A European network through which students transfer verified study results from one institution to another, used notably in Erasmus mobility. The Badges guide expects EDC to be the format for EMREX integration; Open Badges are not part of that infrastructure. See Use-case scenarios: Erasmus mobility.
  • EQF (European Qualifications Framework): The eight-level reference framework that makes qualifications comparable across European countries. The EQF level is a core ELM field and, where applicable, part of the information a microcredential should carry. See European Digital Credentials.
  • Erasmus Without Paper (EWP): The network that lets higher education institutions exchange mobility data, such as learning agreements, nominations and transcripts of records, electronically between their systems. Where an institution’s connection accepts it, ELM data from an EDC can help prepare the Learning Agreement. See Workforce and mobility.
  • ESCO (European Skills, Competences, Qualifications and Occupations): The EU’s multilingual classification of skills and occupations. Credentials can reference ESCO concepts, which gives education and the labour market a common vocabulary for skills. See Workforce and mobility.
  • EUDI Wallet (European Digital Identity Wallet): The wallet each Member State must provide under eIDAS 2.0, by 24 December 2026, for identity data and attestations. Its supported formats decide what holders can keep: since Implementing Regulation (EU) 2026/1731 the binding formats are SD-JWT VC and mdoc, with W3C VCDM foreseen for education once profiles exist. See EUDI Wallet ARF.
  • Europass: The EU platform for skills, qualifications and mobility documents. It hosts the issuing and viewing tools of EDCI and lets learners store and share their European Digital Credentials from a personal profile. See Europass / EDCI.

H

  • HAIP (High Assurance Interoperability Profile): An OpenID Foundation profile that fixes the options of OpenID4VCI and OpenID4VP for high-assurance use, with SD-JWT VC and mdoc credentials, so that wallets, issuers and verifiers can interoperate. The EUDI Wallet relies on it. See The SD-JWT VC stack.
  • Holder: The person, or their wallet, who receives a credential, keeps it and decides when to present it. One of the three roles of the verifiable credential model, with issuer and verifier. See Verifiable credentials.
  • Holder binding: What ties a credential to its rightful holder, so that having a copy of the file is not enough to present it. In SD-JWT VC it uses a holder key named in the cnf claim; in W3C-VC it uses the proof layer and keys held in the wallet. Device-bound keys raise questions for credentials that must last decades. See Credential lifecycle.
  • Hybrid cell: The site’s name, after the VC guide, for the one combination that crosses the two stacks: a W3C data model credential secured with SD-JWT through VC-JOSE-COSE. It works in one direction only and is useful as a transition path. See Two stacks, not two flavours.

I

  • Interpretation drift: When a signed value stays cryptographically valid but issuer and verifier come to read it differently, because its meaning is defined outside the signature. It is the main semantic risk of flat-claim formats for long-lived credentials. See W3C-VC vs SD-JWT VC.
  • ISCED-F: The UNESCO classification of fields of education and training (ISCED-F 2013), used as a controlled list for the subject area of a programme or qualification. See European Digital Credentials.
  • Issuer: The organisation that creates and signs a credential, such as a university. Verifiers must be able to confirm both its identity and its authority to issue that type of credential. See Verifiable credentials.

J

  • JSON Schema: A language for checking the structure of a JSON document: which fields are required, their types and formats. It validates shape, not meaning; in Europe schemas can be registered in the EBSI TSR. See The W3C-VC stack.
  • JSON-LD: JSON for Linked Data: ordinary JSON plus an @context that turns the document into an RDF graph whose terms resolve to published definitions. It is the serialisation of the W3C data model. See The W3C-VC stack.

L

  • LE→LE (legal entity to legal entity): A data transfer model in which one institution sends data directly to another without the citizen in the middle, for example through SDG/OOTS, Europass/EDCI or a direct API. See Decision framework.
  • LE→NP (legal entity to natural person): A data transfer model in which an institution issues a credential to the learner, who keeps it and shares it as needed. Both EDC lineages support it. See Decision framework.
  • LE→NP→LE (citizen-mediated): A data transfer model in which the learner receives a credential in a wallet and presents it to a relying party such as another university or an employer. It is the main design target of eIDAS 2.0 and the EUDI Wallet. See Decision framework.
  • Liability curve: The VC guide’s way of comparing formats as a cost profile over a credential’s lifetime rather than an entry price: one stack costs more up front and stays flat, the other starts cheap and climbs in steps at each reissuance. See Credential lifecycle.

M

  • mdoc (ISO/IEC mobile document): The CBOR-based mobile document format of ISO/IEC 18013-5 and related standards, first designed for the mobile driving licence. It is one of the two binding EUDI Wallet formats, with SD-JWT VC, but it is not a verifiable credential in the W3C or IETF sense. See EUDI Wallet ARF.
  • Microcredential: As defined by the EU Council Recommendation of June 2022, the record of learning outcomes gained through a small volume of learning, assessed against transparent standards and shareable. It is defined by its learning outcomes and quality assurance, not by its format. See Vocabulary.

O

  • Open Badges: The 1EdTech standard for portable, verifiable digital badges carrying structured metadata on issuer, recipient, criteria and evidence. Version 3.0, released in May 2024, aligns badges with the W3C data model; badges remain strong for visibility and engagement but lack the regulated semantics of EDC. See Open Badges.
  • OpenID4VCI: OpenID for Verifiable Credential Issuance: the OpenID Foundation protocol a wallet uses to request and receive a credential from an issuer, built on OAuth 2.0. It is the issuance protocol of the EUDI Wallet. See The SD-JWT VC stack.
  • OpenID4VP: OpenID for Verifiable Presentations: the OpenID Foundation protocol a verifier uses to ask a wallet for credentials and receive a presentation. It is format-neutral, and it is the remote presentation protocol most SD-JWT VC deployments and the EUDI Wallet use. See The SD-JWT VC stack.

P

  • PID (person identification data): The core identity attestation in the EUDI Wallet, with a mandatory attribute set defined in Implementing Regulation (EU) 2024/2977. Since 2026/1731 it is issued in SD-JWT VC and mdoc formats. See EUDI Wallet ARF.
  • Post-quantum transition: The future move to signature algorithms that resist attack by quantum computers. In W3C-VC it is a change of proof layer that keeps the credential’s content and meaning, though new proofs must still reach each holder; in SD-JWT VC it means reissuing the credential. See Credential lifecycle.
  • Proof mechanism: The part of a credential format that secures it: what the signature covers, how selective disclosure works and what properties presentations have. In W3C-VC it is a separate layer; in SD-JWT VC it is the format itself. See Two stacks, not two flavours.
  • PuB-EAA (also written PubEAA): An electronic attestation of attributes issued by, or on behalf of, a public body responsible for an authentic source. It has the same legal effect as a QEAA and may suit universities that national law makes responsible for records such as degrees. See eIDAS 1.0 vs eIDAS 2.0.

Q

  • QA reference: The reference to the quality assurance that covers the issuing institution or programme, usually a national agency or one registered in EQAR. The type of quality assurance is one of the elements the Council Recommendation asks every microcredential to state. See European Digital Credentials.
  • QEAA (qualified electronic attestation of attributes): An attestation of attributes issued by a qualified trust service provider. It has the same legal effect as a lawfully issued paper attestation across the EU. See eIDAS 1.0 vs eIDAS 2.0.
  • QTSP (qualified trust service provider): A trust service provider that a national supervisory body has granted qualified status, and that appears in its Member State’s trusted list. QTSPs issue qualified certificates for signatures and seals and, under eIDAS 2.0, QEAA. See eIDAS 1.0 vs eIDAS 2.0.
  • Qualified signature or seal: An electronic signature (for a person) or seal (for an organisation) that meets the eIDAS requirements for the highest legal effect across the EU. Europass/EDCI credentials carry qualified seals. See eIDAS 1.0 vs eIDAS 2.0.

R

  • RDF graph: The set of subject, predicate and object statements that a JSON-LD document expresses once read through its @context. It is what SHACL validates. See The W3C-VC stack.
  • refreshService: A W3C data model property in which a credential carries a pointer to the service that can renew it, so the route to renewal travels with the credential itself. See Credential lifecycle.
  • Relying party: Any organisation that requests and checks credentials, for example a university in admissions. In the EUDI Wallet, relying parties must register in their Member State from 24 December 2026 and declare which attributes they will ask for and why. See EUDI Wallet ARF.
  • renderMethod: A reserved W3C data model property for attaching display instructions to an individual credential inside the signed object. Its specification is still an early, experimental W3C draft. See The W3C-VC stack.
  • Revocation: Withdrawing a credential permanently, for example after an error or fraud. It is supported by both Bitstring Status List and Token Status List; unlike suspension, it cannot be undone. See Credential lifecycle.

S

  • Salted hash: A hash calculated over a claim value combined with a random salt. SD-JWT uses it to hide undisclosed values while keeping them bound to the issuer’s signature. See The SD-JWT VC stack.
  • SD-JWT: Selective Disclosure for JWTs, IETF RFC 9901 (November 2025). Claims that may be disclosed selectively are replaced in the signed token by salted hashes, and the holder receives the original values separately to reveal one by one. See The SD-JWT VC stack.
  • SD-JWT VC: The IETF credential format built on SD-JWT, an IETF OAuth working group specification not yet published as an RFC at the time of writing. It uses flat key-value claims, salted-hash disclosure and semantics defined outside the token through vct and Type Metadata. Structure and proof form one object. It is a binding EUDI Wallet format. See The SD-JWT VC stack.
  • Selective disclosure: Showing only some attributes of a credential in a presentation, such as the degree title without the grades. Both stacks offer it; it is not the same as unlinkability. See Selective disclosure vs unlinkability.
  • SHACL (Shapes Constraint Language): The W3C language for validating the meaning of an RDF graph: value ranges, membership of controlled vocabularies, constraints on the issuer. It produces a machine-readable validation report, and SHACL shapes can be registered in the EBSI TSR. See The W3C-VC stack.
  • Suspension: Putting a credential on hold while a question is resolved, with the option of restoring it later without reissuance. Bitstring Status List supports it; Token Status List in the European profiles does not. See Credential lifecycle.

T

  • TIR (Trusted Issuers Registry): The EBSI registry that records which legal entities are accredited to issue which types of credential, so a verifier can check authority as well as identity. See EBSI and DC4EU.
  • Token Status List: The IETF status mechanism used with SD-JWT VC, an IETF OAuth working group specification not yet published as an RFC at the time of writing. In the European profiles it supports revocation only: a credential is valid or invalid, with no suspended state, although the specification itself defines one. See The SD-JWT VC stack.
  • Trust framework: The legal, organisational and technical rules that decide who may issue what and how verifiers know it. It complements the credential format: a valid credential from an unaccredited issuer carries no legal meaning. See Trust frameworks.
  • Trusted list: A list, published by each Member State and linked from the EU List of Trusted Lists (LOTL), of qualified trust service providers and their services. Verifiers use these lists as trust anchors. See Trusted lists.
  • TSR (Trusted Schemas Registry): The EBSI registry where JSON Schemas and SHACL shapes are anchored with a cryptographic hash. Entries are dated and never deleted, only superseded, which makes validation auditable years later. See EBSI and DC4EU.
  • Two lanes: The pattern most universities are expected to follow: SD-JWT VC for short-lived, simple credentials such as student ID or enrolment, and W3C-VC for long-lived, semantically dense, regulated ones such as degrees and formal microcredentials, produced from one underlying record. See Choosing a stack.
  • Type Metadata: The resolvable description of an SD-JWT VC type: display information and a link to a JSON Schema through schema_uri. It describes structure but does not formalise how a verifier should validate meaning. See The SD-JWT VC stack.

U

  • Unlinkability: The property that two presentations of the same credential cannot be connected, whether by one verifier or by several comparing notes. Article 5a(16) of Regulation (EU) 2024/1183 prohibits tracking and correlation of users after issuance and requires the wallet framework to enable unlinkability where an attestation does not require identifying the user. bbs-2023 delivers it cryptographically; batch issuance only approximates it. See Selective disclosure vs unlinkability.

V

  • VC-JOSE-COSE: The W3C specification for securing a W3C data model credential by wrapping it in a JOSE or COSE envelope, including an SD-JWT option. It is the hybrid cell: the W3C data model can travel with SD-JWT’s mechanism, but not the other way round. See Two stacks, not two flavours.
  • vct: The verifiable credential type of an SD-JWT VC: a URI saying what kind of credential it is, which can be resolved to its Type Metadata. See The SD-JWT VC stack.
  • Verifiable credential: A digitally signed attestation built around three roles: an issuer who signs it, a holder who keeps and presents it, and a verifier who checks it without contacting the issuer. W3C-VC and SD-JWT VC are two stacks that implement this model. See Verifiable credentials.
  • Verifier: The party that checks a presented credential: the signature, the issuer’s identity and authority, and the current status. Called a relying party in eIDAS 2.0. See Verifiable credentials.

W

  • W3C VCDM (Verifiable Credentials Data Model): The W3C standard for the structure of verifiable credentials, now at version 2.0 (validity via validFrom and validUntil; 1.1 is legacy). It is a data model, serialised as JSON-LD and secured by a separate proof layer, and it underpins Open Badges 3.0 and the DC4EU/EBSI lineage of EDC. See The W3C-VC stack.

← Cross-sector recommendations  ·  Foundations