⏳ Final call! You still have time to submit your session proposal or scientific paper for the EUNIS26 Congress by 1 March 2026.👉https://eunis.org/eunis2026/call-for-submissions/
Share your expertise, connect with peers, and be part of #EUNIS26 at West Univeristy of Timișoara, Romania, 2–4 June 2026.
This isn't about one format over another — it's about equal scaffolding for all three formats already in the framework.
Equal treatment ≠ equal value for every domain. For sectors needing cross-border semantics, linked data isn't optional.
#EUDIWallet #HaveYourSay
On production readiness: W3C VCDM credentials are already protected in production following ETSI TS 119 182-1 signature profiles with qualified e-seals under eIDAS.
Not a future proposition. Operational reality.
#W3C #eIDAS2 #OpenStandards
Saying that semantics are essential but that linking credentials to their semantics is unnecessary is a contradiction.
@context doesn't embed semantics. It links to them. The credential declares "this is what I mean" — rather than leaving the verifier to guess.
The JWT ecosystem already relies on this principle.
IANA maintains a centralised registry of claim definitions — a semantics-linking mechanism.
@context does the same, but decentralised and domain-controlled. Which is what the rulebook model requires.
#VerifiableCredentials
If vocabularies are defined in rulebooks, the question becomes:
How does a credential tell a verifier WHICH rulebook governs it, which version, and how to map claims to definitions?
@context is precisely this: a machine-readable pointer from credential to vocabulary.
I've received a recurring objection to my EUDI Wallet analysis:
"Semantic interoperability comes from rulebooks, not JSON-LD. @context is unnecessary."
The premise is correct. The conclusion doesn't follow.
Here's why 🧵
#EUDIWallet #eIDAS2
This isn't about one format over another — it's about equal regulatory scaffolding for all three.
But equal treatment ≠ equal value for every domain.
Where cross-border semantic interoperability is essential, linked data is the reason sectors chose W3C-VC.
#EUDIWallet #HaveYourSay
Production readiness: W3C VCDM credentials are already protected following ETSI TS 119 182-1 profiles with qualified e-seals under eIDAS.
Not theoretical. Operational across education and professional qualifications today.
#W3C #OpenStandards #VerifiableCredentials
JWT already relies on this principle. IANA maintains a centralised claim registry — a semantics-linking mechanism.
@context does the same, decentralised and domain-controlled. Exactly what the rulebook model requires.
"Semantics essential, linking unnecessary" = contradiction.
#eIDAS2
If vocabularies live in rulebooks, the question is: how does a credential tell a verifier which rulebook governs it?
@context: a machine-readable pointer from the credential to its vocabulary. Not embedding semantics — linking to them.
#LinkedData #W3C
Recurring objection to my EUDI Wallet analysis: "Semantics come from rulebooks, not JSON-LD. @context is unnecessary."
The premise is correct. The conclusion doesn't follow.
Thread 🧵
#EUDIWallet #eIDAS2 #VerifiableCredentials
@context lets sectors map existing vocabularies into credentials without replacing them.
Education: ELM. Automotive: Catena-X. Finance: sector standards.
All via URI, gaining semantic interoperability.
Only JSON-LD W3C-VC does this natively.
#LinkedData #VerifiableCredentials
European EdTech Alliance, national associations: a collective Have Your Say contribution on W3C-VC regulatory support carries institutional weight.
The credential format question is a market access question for European SMEs.
#EdTech #EUDIWallet #HaveYourSay
DC4EU validated W3C-VC across 36 institutions, 10 countries. Schemas exist. Technology works.
Regulatory scaffolding doesn't.
If your EdTech product uses W3C-VC: Have Your Say open until early March. Your operational evidence matters.
#EdTech #HaveYourSay #eIDAS2
EU's semantic infrastructure — ELM, ESCO, EQF, ELI — is European EdTech's global differentiator.
Only JSON-LD W3C-VC integrates it natively. Marginalise the format = marginalise Europe's competitive advantage in credential tech.
#EdTech #LinkedData #EUDIWallet
mdoc presentation = Apple/Google OS APIs. SD-JWT VC = OpenID Foundation protocols.
W3C-VC with Data Integrity = any conformant software, no proprietary APIs.
Draft regs give full support to the platform-dependent formats. None to the most SME-accessible.
#EdTech #OpenStandards
EdTech thread 🧵
Draft EUDI Wallet regs reference W3C-VC but give it no scaffolding. If your products use W3C-VC for credential issuance/verification, your roadmap is directly affected.
Three formats. Only two can complete a lifecycle in the Wallet.
#EdTech #EUDIWallet #eIDAS2
For rectors' conferences (EUA, CRUE, HRK, France Universités, CRUI, CRUP): a collective contribution carries institutional weight individual inputs cannot replicate.
The credentials infrastructure you helped build needs regulatory support now.
#EuropeanUniversities
If your institution participated in DC4EU, EBSI, or any W3C-VC initiative: Have Your Say is open until early March.
Operational experience from education is the evidence the Commission needs.
You don't need 25 pages. Your voice matters.
#HaveYourSay #EUDIWallet
For professional bodies: Token Status List (mdoc/SD-JWT VC) supports permanent revocation only.
Several Member States legally require suspension.
Bitstring Status List (W3C-VC) supports both. But has no regulatory scaffolding.
Reg. 2024/1183 contemplates suspension.
#eIDAS2
Without Commission adaptations, each Member State defines W3C-VC mappings independently.
Spanish university credential ≠ compatible with German verifier. Not a technical limit — a regulatory gap.
The opposite of Bologna/EEA goals.
#EuropeanEducationArea
Education chose W3C-VC because cross-border recognition requires linked data — machines understanding qualifications from different jurisdictions refer to the same concept.
No other format does this natively. It's the one without regulatory support.
#LinkedData #eIDAS2
Thread for colleagues in European higher education 🧵
DC4EU built its education credential ecosystem on W3C-VC: 6 types, 36 institutions, 10 countries. ELM v3.2 for semantic interoperability.
Draft EUDI Wallet regs leave it without scaffolding.
#HigherEducation #EUDIWallet
Full analysis with 8 recommendations: Have Your Say, open until early March.
If you work on VCs, digital identity, or education/professional qualifications — contribute.
#EUDIWallet #VerifiableCredentials #HaveYourSay
ec.europa.eu/info/law/bet...
Recommendation: standardisation request to ETSI ESI for a European HAIP covering all three formats, incl. JSON-LD W3C-VC with embedded proofs.
European institutional ownership of the identity presentation layer.
#EUDIWallet #eIDAS2 #OpenStandards
ETSI clause 7 offers three schema options incl. ShaclSchemaCredential — formal RDF graph validation beyond JSON Schema.
Without Commission adaptations, two issuers can produce incompatible W3C-VC QEAA, both ETSI-compliant.
#SHACL #LinkedData #W3C
Token Status List (SD-JWT VC): "valid"/"invalid" only. Permanent revocation.
Bitstring Status List (W3C Rec, validated in EBSI/DC4EU): supports revocation AND suspension.
Several Member States legally require suspension.
#eIDAS2 #VerifiableCredentials #TrustServices
@context in JSON-LD: every property links to an ontology via URI. Machines determine credentials from different jurisdictions refer to the same concept.
SD-JWT VC: flat pairs. mdoc: namespace IDs. W3C-VC: self-describing linked data.
#LinkedData #SemanticWeb #Interoperability
Data Integrity with BBS cryptosuites: native unlinkability for verifiable credentials.
Annex XIV lists formats for SD-JWT VC and mdoc. Nothing for ldp_vc/ldp_vp. BBS-secured W3C-VCs can't use regulated protocols.
#VerifiableCredentials #BBS #PrivacyByDesign
