Specification

https://w3c.github.io/vc-recognized-entities/

Explainer

https://w3c.github.io/vc-recognized-entities/#introduction

Links

• The WG's request for this TAG review: https://w3c.github.io/vc-wg/minutes/2026-07-21-er.html#5861
• Previous early design review, if any: None
• An introduction to the feature, aimed at unfamiliar audiences: https://w3c.github.io/vc-recognized-entities/#introduction
• A description of the problems that end-users were facing before this proposal: https://w3c.github.io/vc-recognized-entities/#use-cases
• Alternatives considered: https://w3c.github.io/vc-recognized-entities/#relationship-to-other-technologies
• Examples of how to use the proposal to solve the end-users' problems: https://w3c.github.io/vc-recognized-entities/#ecosystem-examples
• What do the end-users experience with this proposal: https://w3c.github.io/vc-recognized-entities/#ecosystem-examples
• User research you did to validate the problem and/or design, if any: Feedback and in-depth discussion from production deployments (CA DMV, NACS, Conexxus, TruAge) and pilot programs (DHS, EU DPP, UN, GS1, NAPHSIS)
• Test Suite: N/A, will be created when transitioning into CR, expectations will be to follow existing pattern for VC test suites at https://w3c.github.io/vc-data-integrity/implementations/#test-suite-reports resulting in additions to the VC ecosystem conformance dashboard: https://canivc.com/

The specification

• Follows the Web Platform Design Principles.
• Includes Security and Privacy Considerations sections based on answers to the Security/Privacy Questionnaire.
  • NOTE: The VCWG has volunteered to follow the new Threat Modelling approach championed by the Security IG, which largely replaces the traditional Security/Privacy Considerations section with a new Threat Model section: https://w3c.github.io/vc-recognized-entities/#threat-model and a more comprehensive Threat Model document: https://w3c.github.io/vc-recognized-entities/threat-model/

Where and by whom is the work is being done?

• GitHub repo: https://github.com/w3c/vc-recognized-entities/
• Primary contacts:
  • Manu Sporny (@msporny), Digital Bazaar, Editor
  • Phil Archer (@philarcher), GS1, VCWG Chair
  • Ivan Herman (@iherman), W3C, Staff Contact
  • Steve Capell (@onthebreeze), United Nations Transparency Protocol, Invited Expert
• Organization/project driving the specification: GS1, UNTP, VCWG
• This work is being funded by: GS1, National Association of Convenience Stores, GoSource, Conexxus, Digital Bazaar
• Primary standards group developing this feature: W3C VCWG
• Incubation and standards groups that have discussed the design:
  • Rebooting the Web of Trust / Internet Identity Workshop Incubation (2022-2023): https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/final-documents/verifiable-issuers-and-verifiers.md
  • Credentials CG Incubation (2023-2026): https://www.w3.org/Search/Mail/Public/search?keywords=verifiable+issuers+verifiers+recognition&subject=MINUTES+&lists=public-credentials
  • Credentials CG Final Report (2026): https://www.w3.org/community/reports/credentials/CG-FINAL-vc-recognition-20260320/index.html

Feedback so far

• Active horizontal reviews: https://github.com/w3c/vc-recognized-entities/issues/95
• Multi-stakeholder feedback: See "Incubation and standards groups that have discussed the design" above and the meeting minutes here -- https://w3c.github.io/vc-wg/minutes/#er
• Major unresolved issues with or opposition to this specification: No major unresolved issues
• Status/issue trackers for implementations: None yet

You should also know that...

We are planning to enter Candidate Recommendation as soon as we have received horizontal reviews and responded to requests for changes. This is one of the reviews that is gating our entrance into Candidate Recommendation. Our goal is to enter Candidate Recommendation during W3C TPAC 2026.

<!-- Content below this is maintained by @w3c-tag-bot -->

---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1249