Sectorial EAA Catalogue — Education and Professional Qualifications

← Higher education

The Sectorial EAA Catalogue is a technical rulebook, produced within the DC4EU large-scale pilot (concluded in 2025), that defines all data models and schemas agreed at the European sectoral level for Education and Professional Qualifications. It implements the principles of the broader Sectorial Rulebook by specifying the concrete schemas, JSON structures, and EBSI registry entries that any compliant issuer or verifier must use.

In practical terms: when an institution issues a digital microcredential, an enrolment proof, a diploma, or a professional certificate in the DC4EU/EBSI lineage, the catalogue tells them which schema to follow, where to find it on the EBSI Trusted Schemas Registry, and what ELM structure to populate.

The full authoritative catalogue lives at github.com/dc4eu/educational-pilot/sectorial-eaa-catalogue. This page summarises the key concepts and points readers to the source for schema-level detail.

Three distinctions the catalogue forces

1. EAA ≠ Diploma

An EAA (Electronic Attestation of Attributes) is an attestation in electronic form. It is not the same as the original diploma. In Spain, for example, a diploma is legally an A3 paper document with specific weight and security features; in other Member States, the diploma may be a curated record in an institutional registry. The EAA does not replace the original — it carries equivalent legal value as an attestation about the same achievement.

This matters because some institutions assume “issuing an EDC” means generating the digital diploma. It does not: the diploma remains the diploma. The EDC is the electronic attestation alongside, or referencing, it.

2. EDC (OCB) ≠ EDC-W3C

The European Commission’s Online Credential Builder (OCB), provided by DG-EMPL, produces EDCs in a JSON-LD format that is inspired by W3C Verifiable Credentials but is not fully compliant:

  • Wraps fields under a top-level credential object instead of putting W3C fields at the root
  • Missing issuanceDate / expirationDate
  • No support for revocation / suspension
  • deliveryDetails are tied to OCB’s specific delivery mechanism

EDC-W3C corrects all of this. It is the W3C-VCDM compliant serialisation of ELM. Two profiles exist:

  • EDC-W3C VCDM 1.1: the profile used in the DC4EU pilot
  • EDC-W3C VCDM 2.0: the newer, optional profile in the catalogue; dual JSON Schema + SHACL validation architecture

Neither profile is named in the binding EUDI Wallet rules. Since Implementing Regulation (EU) 2026/1731 (in force 11 August 2026), the binding annexes of the EUDI Wallet implementing acts name SD-JWT VC and ISO/IEC mdoc for person identification data and for attestations (ETSI TS 119 472-1 profiles); the reference to W3C VCDM 1.1 in the original 2024 text is gone. W3C VCDM is not among the binding formats today, but the regulation’s recitals state that wallets should also support it, as the reference format for attestations in education, once new W3C VCDM profiles are available. ARF v3.0 currently treats W3C VCDM as optional and for non-qualified attestations only. See EUDI Wallet. Issuers and verifiers working with the catalogue should be prepared to support both VCDM versions to preserve backward compatibility.

3. ELM ≠ EDC

ELM (European Learning Model) is a conceptual ontology — the shared vocabulary of educational concepts. EDC is the application profile that implements ELM for digital credentialing. ELM describes what a learning achievement looks like conceptually; EDC says how to encode and sign it for legal verification.

Governance — who decides what

The catalogue raises a structural question: in the absence of a single central authority for education in the EU, who governs which credential types exist and how they evolve?

The pragmatic proposal from the DC4EU work is to assign governance by Directorate-General competencies, with Member States as co-decision-makers:

BodyScope
DG-EAC (Education, Youth, Sport and Culture)Primary, Secondary and Tertiary education
DG-EMPL (Employment, Social Affairs and Inclusion)Adult Education and TVET
Member StatesCo-decision on credential types relevant to national competencies

For each credential type in the catalogue, an “Attribute schema provider” is identified — the party responsible for creating and evolving that schema. ELM v3.2 acts as the common semantic thread across all entries.

What the catalogue contains

The catalogue groups schemas into four scopes. All schemas are JSON Schemas registered in the EBSI Trusted Schemas Registry (v3). For full schema URLs and example credentials, see the authoritative GitHub repository.

Foundational identity

AcronymPurpose
PID (Natural Person)Person Identification Data — compliant with eIDAS 2.0 and the EUDI Wallet ARF

Non-foundational identities

AcronymPurpose
EducationalIDPerson in an educational organisation context (with national extensions)
AllianceIDStudent or staff affiliated with a European university alliance
EuropeanStudentCardStudent mobility — based on DG-EAC’s service
MyAcademicIDStudent mobility identity via MyAcademicID and eduGAIN infrastructure
ProfessionalIDGeneral professional identity
DoctorIDMedical doctor identity
EngineerIDEngineer identity

EDC-W3C VCDM 1.1: the pilot profile

The data models below form the catalogue’s VCDM 1.1 set, as used in the DC4EU pilot. All are W3C-VCDM 1.1 compliant ELM serialisations.

AcronymCredential type
EDC-W3CGeneric ELM-based credential — baseline for any educational/professional achievement
EUHEMCEuropean Higher Education Microcredential
EUVETMCEuropean Vocational Education & Training Microcredential
EUHEPOEEuropean Higher Education Proof of Enrolment
EUHEDEuropean Higher Education Diploma
EUHEDSEuropean Higher Education Diploma Supplement
EUHETOREuropean Higher Education Transcript of Records
EUUSCEuropean Upper Secondary Education Certificate
EUUSTOREuropean Upper Secondary Education Transcript of Records
CPSCertificate of Professional Suitability
AMTAccreditation of Medical Training
CPDContinuous Professional Development
PTCProfessional Training Certificate

EDC-W3C VCDM 2.0 — forward-looking, optional

The same set of credentials is in migration to the W3C-VCDM 2.0 profile with a dual validation architecture: a JSON Schema enforces syntactic constraints; a SHACL shape (referenced via ShaclValidator2017) enforces semantic/ontological constraints on the RDF graph derived from the JSON-LD through its ELM v3.2 context. Both layers are referenced from the credential’s credentialSchema array.

AcronymCredential typeVCDM 2.0 status
EDC-W3C v2Generic VCDM 2.0 baseline (reused SHACL shape for education credentials)✓ Available — SHACL only (no JSON Schema needed at this level)
EUHEMCHigher Education Microcredential✓ JSON Schema + SHACL + unsigned/signed JAdES examples
EUVETMCVET Microcredential✓ JSON Schema + SHACL + examples
EUHEPOEHE Proof of Enrolment✓ JSON Schema + SHACL + examples
EUHEDHE Diploma✓ JSON Schema + SHACL + examples
EUHEDSHE Diploma Supplement✓ JSON Schema + SHACL + examples
EUHETORHE Transcript of Records✓ JSON Schema + SHACL + examples
EUUSCUpper Secondary Certificate✓ JSON Schema + SHACL + examples
EUUSTORUpper Secondary Transcript of Records✓ JSON Schema + SHACL + examples
CPSCertificate of Professional Suitability⏳ Pending VCDM 2.0 artefacts
AMTAccreditation of Medical Training⏳ Pending VCDM 2.0 artefacts
CPDContinuous Professional Development⏳ Pending VCDM 2.0 artefacts
PTCProfessional Training Certificate⏳ Pending VCDM 2.0 artefacts

Regulatory status: neither profile is in the binding wallet annexes.

Today those annexes name SD-JWT VC and mdoc. A recital of 2026/1731 says wallets should also support W3C VCDM, the reference format in education, once new profiles exist. Within the catalogue, VCDM 2.0 is additive, not a replacement: issuers and verifiers should plan to support both.

Why this matters

For issuers (universities, professional bodies)

  • Choose the right schema for each credential type — generic EDC-W3C only when no specific type applies
  • Reference the EBSI Trusted Schemas Registry record (not an ad-hoc schema)
  • Align ELM field population to the catalogue’s conventions for cross-border verifiability

For verifiers (relying parties, partner institutions, employers)

  • Know which catalogue version a presented credential conforms to (1.1 vs 2.0)
  • Resolve schema URIs through EBSI registries before validation
  • Validate against both JSON Schema (syntax) and — increasingly — SHACL (semantics, in VCDM 2.0)

For wallets (EUDI Wallet and sectoral wallets)

  • Recognise educational and professional credential types from this catalogue
  • Render credentials according to ELM displayParameter conventions
  • Treat W3C renderMethod as a direction, not a feature to build on yet. It attaches display instructions to the individual credential, inside the signed object, rather than to its type; but its specification is an early W3C draft, explicitly experimental, and wallets do not support it yet (VC guide v1.1, EUNIS SIG, July 2026, Verifiable Credentials in Higher Education: W3C-VC and SD-JWT VC). ELM displayParameter remains the catalogue’s convention; see The W3C-VC stack.
  • Where the wallet handles W3C VCDM (optional in EUDI Wallets under ARF v3.0, for non-qualified attestations only), support both the VCDM 1.1 and VCDM 2.0 profiles for compatibility

For policy

  • The catalogue is the de facto European reference for educational EAAs
  • Its evolution informs the next batches of Implementing Acts under eIDAS 2.0
  • Cross-border recognition workflows depend on shared catalogue alignment across Member States

Resources

Authoritative sources

EU code repositories

Related EU specifications

Related pages on this site

← HE recommendations  ·  Higher education