CIO Higher Ed - IT Governance, IT Management, Innovation, eGovernment, IT security & risk management, Enterprise Architecture

Joined February 2010
169 Photos and videos
Lluís Alfons Ariño retweeted
Notición! A la práctica significa que cualquier grupo de investigación afiliado a una institución española podrá enviar sus artículos a #ORE para que sean publicados allí, sin coste, si pasan la revisión por pares abierta. Esto será operativo a partir de este otoño🚀
✅ España se incorpora a @OpenResearch_EU, la plataforma pública de publicación científica en acceso abierto impulsada por la Comisión Europea. 📖 @cienciagob representará a nuestro país en la plataforma a través de la @FECYT_Ciencia. ciencia.gob.es/Noticias/2026…
4
190
588
50,063
Without Commission W3C-VC adaptations, each Member State decides independently. Spain defines its EAA mapping. Germany does the same. Neither aligned. Same regulatory work, 27 times instead of once — with divergent results. The antithesis of harmonisation. #EUDIWallet #eIDAS2
1
1
31
EdTech companies building on W3C Verifiable Credentials — a thread on why the draft EUDI Wallet Implementing Regulations affect your product roadmap directly. 🧵 Three credential formats referenced. Only two with regulatory scaffolding. #EdTech #EUDIWallet
1
25
DC4EU validated W3C-VC credentials across 36 institutions, 10 countries. The schemas exist. The technology works. The regulatory scaffolding doesn't. If your product uses W3C-VC, Have Your Say is open until early March. Your voice matters. #EdTech #HaveYourSay #eIDAS2
1
10
European EdTech Alliance, EdTech Europe, national associations: A collective contribution to Have Your Say on W3C-VC regulatory support carries more weight than individual inputs. The format question is a market access question for EU SMEs. #EdTech #EUDIWallet #HaveYourSay
10
The question is not whether Europe needs W3C-VC - the Commission already answered that by referencing it. The question is whether it will complete the scaffolding-or leave a format formally included but practically excluded.
1
27
The draft regulations reference three credential formats: mdoc, SD-JWT VC, and W3C-VC (via ETSI TS 119 472-1 clause 7). For mdoc and SD-JWT VC: complete encoding tables, presentation profiles, issuance protocols, revocation rules. For W3C-VC: none of the above.
1
2
49
3 credential formats are not redundancy; each occupies a distinct functional space mdoc: proximity presentation SD-JWT VC: lightweight remote presentation W3C-VC: rich semantics, linked data, native unlinkability, suspension support Complementary-Only 2 with regulatory support.
1
1
30
The Have Your Say consultation is open until early March. If you work in education, professional qualifications, digital identity, trust services, or cross-border credential verification — your input matters. Full analysis here: 🔗 ec.europa.eu/info/law/better…
1
3
39
The fix isn't complicated: The Commission should issue a standardisation request to ETSI ESI for a European HAIP covering all three formats. The schemas exist. The pilots validated them. What remains is integration, not invention. 8 types of regulatory action identified.
1
1
33
The suspension gap: Token Status List (chosen for mdoc/SD-JWT VC) supports only permanent revocation Several Member States legally require suspension Bitstring Status List (W3C-native) supports both Regulation 2024/1183 contemplates suspension. The Implementing Acts eliminate it
1
1
27
The investment at stake: DC4EU: €19M, 80 orgs, 23 States — built on W3C-VC EBSI: PID developed in W3C-VCDM by the Commission itself Catena-X, Gaia-X: W3C-VC for industrial attestations Education sector: complete EAA catalogue in W3C-VC Validated. Proven. Without regulatory home
1
1
40
The EU Parliament resolution of 22 Jan 2026 on technological sovereignty calls for: ✅ Open standards ✅ No vendor lock-ins ✅ Governance without centralised corporate control Published two weeks before these draft regulations — which do the opposite for credential formats.
1
1
29
The sovereignty dimension: mdoc → governed by ISO/IEC, driven by Apple/Google SD-JWT VC → governed by IETF/OpenID(US Big Tech) W3C-VC → semantic layer is decentralised, jurisdiction-controlled Full regulatory support to the first two. Most sovereignty-aligned format nothing.
1
1
35
Why does this matter? Only JSON-LD W3C-VC supports semantic interoperability. An architect's qualification from Spain and a Berufsqualifikation from Germany can be understood as equivalent, without bilateral mapping. SD-JWT VC and mdoc transport data. W3C-VC transports meaning.
1
2
34
This creates four asymmetries: 1⃣ No PID encoding tables for W3C-VC 2⃣ No Commission adaptations for W3C-VC attestations 3⃣ No presentation profile for embedded proofs 4⃣ No regulated issuance protocol A format that can be referenced but not operationally used.
1
2
43