Repository files navigation

Credentials are a part of our daily lives; driver's licenses are used to assertthat we are capable of operating a motor vehicle, university degrees can be usedto assert our level of education, and government-issued passports enable us totravel between countries. This specification provides a mechanism to expressthese sorts of credentials on the Web in a way that is cryptographically secure,privacy respecting, and machine-verifiable.

We encourage contributions meeting theContributionGuidelines. While we prefer the creation of issuesand Pull Requests in the GitHub repository, discussions also occuron thepublic-vc-wgmailing list.

• Group page:https://www.w3.org/2017/vc/WG/
• Charter:https://www.w3.org/2022/06/verifiable-credentials-wg-charter.html
• Chairs
  • Brent Zundel - @brentzundel

• Use Cases
• Data Model
• Implementation Guide
• Data Model Test Cases

• W3C Credentials Community Group Mailing List (Incubation)
• W3C Verifiable Credentials WG Mailing List (Standardization)

1. Anyone can open a PR on the repository. Note that for the PR to be merged,the individual must agree to theW3C Patent Policy.
2. Once a PR is opened on thev2.0 branch, chairs and editors make judgementcall on whether changes are substantive or editorial.

   Editorial

   Mark with "editorial" tag

   Substantive

   Mark with "substantive" tag.

3. W3C CCG is automatically notified of PRs as they are raised and discussed.
4. PRs are usually merged in 7 days if there is adequate review and consensus,as determined by the Chairs and Editors.

The VCWG has a set ofdeliverablesand atimelinelisted in the most recentVCWG charter

There are times where Github Pages will fail to build with nondescript errorssuch as "Page build error." or "Symlink does not exist within your site'srepository". You will need to run github-pages locally to debug such errors.To run github-pages, which uses Ruby and Jekyll locally, you will need toset up a working Ruby and Bundle environment.

After you have installed Ruby and Bundle, you will need to do the following:

gem install jekyll github-pages

Then create aGemfile file in the top level directory with the followingcontents:

source 'https://rubygems.org'gem 'github-pages'

Then run the following command:

bundle exec jekyll serve --watch --force_polling

You should be able to see the page build errors in detail upon running thecommand above.