Verifiable Credential Specifications Directory

Dearest Verifiable Credentials WG (bcc: Credentials CG),

On February 18th 2023, Manu Sporny wrote:
> An alternative proposal to provide a Verifiable Credential Specifications
Directory that points to other known work in the space, such as extensions
to proofs, schemas, evidence, terms of use, etc. did not seem to have
opposition. This will allow us to point to work happening in places like
the CCG, DIF, ToIP, IETF, ACDC, W3C, and weekend projects performed by
individuals. A PR will be raised shortly to create such a directory. The
difference between a directory and a registry is that the former puts less
decision making authority with the DID WG on whether or not an entry should
be included.

Per my action item from the W3C VCWG F2F in Miami, I have created a
"Verifiable Credential Specifications Directory" for consideration by the
VCWG:

https://github.com/msporny/vc-specs-directory

A summary of what this repository does:

   - It is NOT a registry -- it has no official standing; specifications
   listed in it are not vetted.
   - It is a directory that links to known specifications
   <https://msporny.github.io/vc-specs-directory/> in the Verifiable
   Credentials Ecosystem.
   - There are only three requirements
   <https://msporny.github.io/vc-specs-directory/#adding-a-specification-entry>
for
   getting into the directory: 1) pass the JSON Schema for your specification
   entry, 2) don't violate anyone else's intellectual property, and 3) don't
   create unreasonable legal, security, or moral issues that result in direct
   harm to others.
   - Adding a specification entry is as simple as committing a myspec.json file
   to the specifications/ directory.
   - All entries are syntax-checked using JSON Schema.
   - The directory is built from all of the specification entries and grouped
   by extension point
   <https://msporny.github.io/vc-specs-directory/#the-vc-specifications-directory>
in
   the Verifiable Credentials Data Model specification.
   - There are instructions on how you add a specification entry
   <https://github.com/msporny/vc-specs-directory/#verifiable-credential-specifications-directory>
(which
   are displayed on each new PR), and an example of such an addition in this
   PR <https://github.com/msporny/vc-specs-directory/pull/1>.

Please take a look at the directory to see if it matches the expectations
from the group. Please raise PRs for items that you feel need to be
changed/modified. This issue is being tracked in issue 909
<https://github.com/w3c/vc-data-model/issues/909> (please put further
commentary there).

-- manu

-- 
Manu Sporny - https://www.linkedin.com/in/manusporny/
Founder/CEO - Digital Bazaar, Inc.
News: Digital Bazaar Announces New Case Studies (2021)
https://www.digitalbazaar.com/