Copyright © 2024 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.
This document serves as an unofficial list of all known Verifiable Credential specifications whether they are released by a global standards setting organization, a community group, an open source project, or an individual.
This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/.
This document is not a formal registry nor is it intended to become a Registry Track document per the W3C Process.
Comments regarding this document are welcome. Please file issues directly on GitHub, or send them to public-vc-wg@w3.org ( subscribe, archives).
This document was published by the Verifiable Credentials Working Group as a Group Note using the Note track.
This Group Note is endorsed by the Verifiable Credentials Working Group, but is not endorsed by W3C itself nor its Members.
This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
The W3C Patent Policy does not carry any licensing requirements or commitments on this document.
This document is governed by the 03 November 2023 W3C Process Document.
This section is non-normative.
This document serves as an unofficial directory for all known Verifiable Credential specifications whether they are released by a global standards setting organization, a community group, an open source project, or an individual.
The Verifiable Credentials Data Model is designed to be extended by 3rd party specifications to address a variety of real world use cases. Examples of extensions include, but are not limited to, new types of Verifiable Credentials and ways of expressing credential status, schema validation, evidence, refreshing, terms of use, and cryptographic suites for securing credentials.
In order to add a new specification to this directory, an implementer submits a modification request for this directory, as a pull request on the repository where this directory is hosted.
Here is an example:
{
"name": "Example VC",
"summary": "Used to demonstrate examples for Verifiable Credentials.",
"specification": "https://example.github.io/example-spec/",
"category": "vc",
"maintainerEmail": "maintainer@community.example",
"maintainerName": "Example Community Group",
"maintainerWebsite": "https://example.github.io/",
"vocabulary": ["https://example.github.io/vocabularies/example.yml"]
}
The modification request MUST adhere to the following policies:
The Editors of this directory MUST consider all of the policies above when reviewing additions to the directory and MUST reject directory entries if they violate any of the policies in this section. Entities registering additions can challenge rejections first with the W3C Verifiable Credentials Working Group and then, if they are not satisfied with the outcome, with the W3C Staff. W3C Staff need not be consulted on changes to the directory, but do have the final authority on directory contents. This is to ensure that W3C can adequately respond to time sensitive legal, privacy, security, moral, or other pressing concerns without putting an undue operational burden on W3C Staff.
Any submission to the directory that meets all of the criteria listed above will be accepted for inclusion. The specifications listed in this directory enumerate all known specifications, without choosing between them.
The specification entry format MUST conform to the JSON Schema for a specification entry. Each field is documented below:
Field | Description |
---|---|
name |
A short human readable name for the specification. For example: Status List
(v2021) .
|
summary |
A one sentence description for the specification. For example: A credential
status list with herd privacy characteristics.
|
specification |
An URL that resolves to a human readable specification. For example:
https://w3c.github.io/vc-status-list-2021/ .
|
category |
The Verifiable Credential extension category of the specification, which can
be one of the following values: credentialStatus , credentialSchema ,
evidence , media-type , securing , refreshService , termsOfUse , or vc .
For example: credentialStatus .
Note
The extensions might define a |
maintainerName |
A person or organization which responds to contact requests. For example:
W3C Verifiable Credentials Working Group .
|
maintainerEmail |
An email to send contact requests. For example:
public-vc-wg@w3.org .
|
maintainerWebsite |
An website to send contact requests. For example:
https://www.w3.org/groups/wg/vc .
|
vocabulary |
An array of URLs that contain machine-readable vocabulary information in
yml2vocab or JSON-LD format. For example:
["https://raw.githubusercontent.com/w3c/vc-status-list-2021/main/contexts/v1.jsonld"] .
|
As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.
The key words MUST and MUST NOT in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
Specification | Description |
---|
Specification | Description |
---|
Specification | Description |
---|
Specification | Description |
---|
Specification | Description |
---|
Specification | Description |
---|
Specification | Description |
---|
Specification | Description |
---|