EAA ConformanceETSI TS 119 472-1 (v1.2.1) clause 5.1
EAA-5.1-01:Clause 5 EAAs must be implemented as SD-JWT VC
- shall
- Ordinary EAA
- QEAA
- PuB-EAA
- SD-JWT VC
- Issuer
- Verifier
Spec text
SD-JWT VC EAA shall be implemented as a Selective Disclosure JSON Web Token based Verifiable Credential (SD-JWT VC) as specified in IETF SD-JWT VC.
ETSI TS 119 472-1 (v1.2.1), clause 5.1, page 27.
In plain English
When you implement an EAA according to clause 5 of TS 119 472-1, the wire format must be SD-JWT VC, the IETF Selective Disclosure JSON Web Token format for Verifiable Credentials. You cannot use plain JWT-VC, raw JWS, or the W3C Verifiable Credential JSON-LD form here; those belong to the mdoc track in clause 6 or the W3C track in clause 7.
Why it matters
The EUDI Wallet ecosystem assumes a small set of canonical wire formats so that any wallet, issuer, and verifier can interoperate without negotiation. SD-JWT VC is the JSON-flavoured profile assessors will check for, and downstream rules in clause 5 only apply if this base format requirement is met.
Common mistakes
- Issuing a plain JWS-VC and labelling it as a clause 5 EAA.
- Using a non-SD-JWT JWT and relying on bespoke disclosure logic.
- Mixing W3C VCDM JSON-LD payloads under an SD-JWT VC media type.
Conformance check
Auto-tested. Use the action in the sidebar to run a Self-Assessment for this control.