Implications by university function

← Higher education

The choice of credential format has different implications depending on which part of the institution is involved. This page maps those implications for the most commonly affected functions.

The implications for each function draw on the Badges guide v1.1 (EUNIS SIG, July 2026), Badges and Digital Credentials in Higher Education. The boxes add, for five of the functions, the question that function should own and one action it can take this academic year, following the VC guide v1.1 (EUNIS SIG, July 2026), Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC. None of these questions needs the format debate to be settled first.

Registry and Student Records

EDC requires integration with a trusted issuer infrastructure, qualified digital signatures, and DID management. This is a significant IT and governance project with a realistic timeline of 12–24 months for production readiness.

Open Badges can be issued via integrations with existing learning management systems or standalone platforms with substantially lower overhead and a much shorter implementation timeline.

These should be planned on separate tracks with separate timelines. Do not delay badge implementation while waiting for EDC infrastructure.

Question to own: Will this credential still verify, and still mean what we meant, when the graduate is fifty? The registry has the longest time horizon of any function: semantic drift, suspension and reissuance all end up on its desk, usually with a graduate waiting.

Action now: Inventory the credential portfolio on the five dimensions set out in Choosing a stack (lifespan, audience, semantic density, status complexity, regulatory exposure), separating the thirty-year objects from the one-term ones. That inventory, not a vendor meeting, is the first artefact of a format decision.

Quality Assurance

EDC microcredentials require compliance with the ELM microcredential definition: assessed, scoped, stackable, and QA-referenced (EQAR-registered or national QA agency). This is a governance requirement, not a technical one.

Open Badges do not impose these requirements — which is simultaneously a flexibility and a risk. Institutions issuing Open Badges for activities that do not meet the EU Council Recommendation definition risk creating expectations of recognition that will not be met.

The QA office should be involved in defining which activities qualify for Open Badge recognition, and separately, which qualify for EDC microcredential status under the Recommendation.

Question to own: Can our compliance be inspected as an artefact, or only reconstructed from behaviour? Where validation rules are JSON Schemas and SHACL shapes registered in the EBSI Trusted Schemas Registry, they are dated, immutable and retrievable; where they live in application code, they can only be shown through process audits.

Action now: Bring the credential format into the QA framework review instead of leaving it to IT procurement. EQF level, ECTS workload and the QA reference are semantic objects, and where they sit in the credential is a QA matter.

International and Mobility Office

EDC is the format that will matter for formal recognition workflows: Lisbon Recognition Convention digital processes, EMREX data exchange, and Erasmus+ digital infrastructure. Open Badges are not currently part of that recognition infrastructure and cannot substitute for EDC in these processes.

The international office should understand the distinction clearly when advising students on how to document their learning for recognition purposes.

Question to own: Will a partner we have never coordinated with read our credential exactly as we issued it? Shared ontologies are paid for once; bilateral mappings are paid for again with every new partnership.

Action now: Ask your three most active partner institutions which stack their pilots use. The answer shows your real interoperability perimeter; a mismatch found now costs a conversation, found at scale it costs a mapping project.

IT / Systems

The technical demands of EDC and Open Badges are substantially different and should not be conflated in architecture planning:

RequirementOpen BadgesEDC
Integration with LMS/SISTypically simple (plugin or API)Complex (ELM-compliant data extraction)
Identity managementWeak binding (email typical)Strong (eIDAS identity required for issuer)
Digital signaturesNot required (v2.1); optional (v3.0)Required (qualified seal or QTSP-issued)
DID managementNot requiredRequired (DC4EU/EBSI lineage)
Wallet integrationBadge wallets / portfoliosEuropass (file-based delivery); EBSI-conformant wallets; an EUDI Wallet only where the national wallet supports the optional W3C VCDM format (see EUDI Wallet)
Schema governanceMinimalActive (EBSI Trusted Schemas Registry)
Revocation / SuspensionOptionalDC4EU/EBSI: revocation and suspension supported (W3C Bitstring Status List or equivalent). EDCI/Europass: more limited revocation mechanisms.
Implementation timelineWeeks to monthsMonths to years

Plan these as two distinct workstreams. Conflating them leads to either delaying Open Badge implementation unnecessarily or underestimating EDC complexity.

Question to own: What is our reissuance liability curve, and what does our national wallet actually support today? Running two lanes means two issuance pipelines, two key-management disciplines and two status infrastructures, though the split is uneven: a high-volume fast lane on familiar JWT tooling and a low-volume formal lane. See Credential lifecycle for when reissuance is forced.

Action now: Obtain in writing which formats and proof suites your Member State’s EUDI Wallet supports and has committed to on its roadmap. Include how it will handle credentials meant to last decades: current issuance flows are built around short-lived attestations refreshed with tokens, and a thirty-year credential outlives all of them.

Communications and Marketing

Open Badges have strong social sharing mechanics — integration with professional networks, embeddable in email signatures and portfolios, visually recognisable. This is a genuine engagement and marketing asset.

EDC credentials are primarily for official institutional processes. Their value is in recognition, not visibility. This may evolve as the EUDI Wallet becomes publicly available and learners can present their credentials in a citizen-facing interface.

A combined strategy — EDC as the formal record, Open Badge as the social artifact — captures the value of both.

Legal and Data Protection

EDC under eIDAS 2.0 has clear GDPR implications: holder-controlled storage, selective disclosure, and defined data processor roles. The issuing institution is the data controller for the credential record; the holder controls distribution.

Selective disclosure is not unlinkability. Revealing only some attributes does not stop colluding verifiers from correlating repeated presentations of the same credential; of the two verifiable credential stacks, only W3C-VC secured with bbs-2023 makes presentations unlinkable at the level of the proof, and even then status-list indices and credential identifiers must be designed not to correlate. 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. See Selective disclosure vs unlinkability.

Open Badges issued via third-party standards-compliant infrastructure require careful review of data processing agreements. The institution should ensure it retains control of learner data and that the processor’s terms are compatible with GDPR obligations.

The data protection officer should be involved in both workstreams from the governance design phase — not as an afterthought.

Question to own: Is unlinkability a property of our format, or a promise in our procedures? Both can be compliant, but in a supervisory inspection an architecture that embeds minimisation is easier to defend than a file of procedures asserting it (Articles 5(2) and 25 GDPR).

Action now: Review credential projects already under way. If their documents treat “selective disclosure” and “unlinkability” as the same thing, record it as a finding: fixing the vocabulary now is cheaper than fixing the architecture later.

← Combination model  ·  Higher education  ·  HE recommendations →