As an editor of the specification, I'm requesting a TAG review of VC-JWTs.

Verifiable Credentials (VCs) permit several forms of providing security around the data model. JWTs provide a widely deployed approach to signing information. This specification provides the details necessary to utilize JWTs as a securing mechanism for verifiable credentials.

• Explainer: vc-jwt-explainer
• Specification URL: VC-JWT - Latest Draft
• Tests: final tests tbd, WIP Tests
• User research: n/a
• Security and Privacy self-review: Security/Privacy
• GitHub repo (if you prefer feedback filed there): VC-JWT Repo
• Primary contacts (and their relationship to the specification):
  • Brent Zundel (@brentzundel), VCWG Chair, Gen
  • Kristina Yasuda (@Sakurann), VCWG Chair, Microsoft
  • Orie Steele (@OR13), Editor, Transmute
  • Michael Jones (@selfissued), Editor, Independent
  • Michael Prorock (@mprorock), Editor, mesur.io
• Organization(s)/project(s) driving the specification: W3C Verifiable Credentials Working Group
• Key pieces of existing multi-stakeholder review or discussion of this specification: n/a
• External status/issue trackers for this specification: Issue Tracker

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• Relevant time constraints or deadlines: The VCWG is planning to take this specification to Candidate Recommendation in September 2023 (at W3C TPAC), reviews before that time frame (ideally, by the end of July 2023) would be ideal.
• The group where the work on this specification is currently being done: W3C Verifiable Credentials Working Group
• Major unresolved issues with or opposition to this specification:
  • There is some consideration over whether or not plain JSON representations should be covered in this specification or at IETF
• This work is being funded by: The members of the W3C VCWG that are actively participating in the development of these specifications including funding from the US Federal Government, the European Commission, and the Canadian Federal Government.

You should also know that...

• This work intersects heavily with the Verifiable Credentials v2.0 work, which is also something that the TAG will be actively reviewing around the same time.

We'd prefer the TAG provide feedback as: ☂️ open a single issue in our GitHub repo for the entire review