Doug Belshaw
FinWave Japan本人確認のデジタル化に向けた新たな一歩💡
金融庁が #VerifiableCredentials を用いた実証実験結果を公表しました。マイナンバーカードを用いた認証でなりすましリスクの低減を確認。犯収法への対応など実用化に向けた検証が進んでいます✅
Instead of static badge images, what if we used SVG radar charts as living views over Open Badges v3 / VC data, showing how practice is recognised across contexts and over time?
Featuring Open Recognition ideas and Serge Ravet’s Recognition Practices Occupational Framework.
https://blog.dougbelshaw.com/polygonal-badges/
#OpenBadges #OpenRecognition #VerifiableCredentials #DigitalBadges #SkillsRecognition
larinyoThe JWT ecosystem already uses this principle: IANA maintains a centralised registry of claim definitions — a semantics-linking mechanism.
@context achieves the same binding, but decentralised and domain-controlled. Which is what the rulebook model requires.
"Semantics are essential but linking credentials to their semantics is unnecessary" is a contradiction.
A recurring objection to my EUDI Wallet analysis: "Semantics come from rulebooks, not JSON-LD. @context is unnecessary."
I agree with the premise. Not the conclusion.
If vocabularies are in rulebooks, how does a credential tell a verifier which rulebook governs it? @context is a machine-readable link from the credential to its vocabulary. Not embedding semantics — linking to them.
EdTech companies, European EdTech Alliance, national associations:
Have Your Say on EUDI Wallet regs is open until early March. A clear contribution explaining that your products use W3C-VC, the regulatory gap affects market access, and linked data is essential for semantic interoperability — this carries weight.
Collective industry input amplifies individual voices.
Full analysis for reference: see my pinned post.
If your company builds credential issuance or verification on W3C Verifiable Credentials — the draft EUDI Wallet Implementing Regulations affect your product roadmap.
Three formats referenced: mdoc, SD-JWT VC, W3C-VC. Only the first two receive scaffolding — encoding tables, presentation profiles, issuance protocols, revocation rules.
W3C-VC: formally included, practically excluded.
Have Your Say open until early March.
#EdTech #EUDIWallet #eIDAS2 #VerifiableCredentials #OpenStandards
A critical gap: Token Status List (mandated for mdoc/SD-JWT VC) supports only permanent revocation.
Several Member States legally require suspension — temporary withdrawal with possibility of reactivation.
Bitstring Status List (W3C Recommendation, validated in EBSI/DC4EU) natively supports both revocation AND suspension.
Regulation 2024/1183 contemplates suspension. The Implementing Acts eliminate it.
#eIDAS2 #VerifiableCredentials #TrustServices #EUDIWallet #DigitalIdentity
Data Integrity with BBS cryptosuites enables native unlinkability — the strongest privacy-by-design pathway for verifiable credentials.
European cryptographers criticised the EUDI Wallet in 2024 for insufficient unlinkability provisions.
Annex XIV lists format identifiers for SD-JWT VC and mdoc. Nothing for ldp_vc/ldp_vp. BBS-secured W3C-VCs cannot be presented through regulated protocols.
I've submitted a detailed analysis to the European Commission's Have Your Say consultation on the EUDI Wallet Implementing Regulations.
Core finding: W3C Verifiable Credentials are formally referenced in the regulatory framework — but without the operational scaffolding to function.
Four asymmetries. Eight types of regulatory action needed.
Thread 🧵
#EUDIWallet #eIDAS2 #VerifiableCredentials #DigitalSovereignty #HaveYourSay #OpenStandards