vc-examples

Example Verifiable Credentials (@credential-handler/vc-examples)

Example Verifiable Credentials. Beyond being useful for general testing, these are also in use on the Verifiable Credential Playground.

[!WARNING] The Verifiable Credentials in this repository are primarily created for the Verifiable Credentials Playground. Consequently, they should not be considered production ready credentials and they may be missing many necessary production and stability focused features. Please only use them for experimentation.

Table of Contents

• Background
• Install
• Usage
• Contribute
• License

Background

Credentials added to this package are used on the VC Playground’s Issuer tool.

Install

• Node.js 18+ is required.

Development

To install locally (for development):

git clone https://github.com/credential-handler/vc-examples.git
cd vc-examples
npm install

To run test:

npm test

To check credentials against local (and remote) contexts:

npm run check

This uses jsonld.js’s “Safe Mode” to to check for missing terms.

All local example context files are added as static contexts mapped to their future publication URLs via jsonld-document-loader.

Usage

Add / Update a Verifiable Credential

To add or update credentials in the ./credentials directory:

1. Within the ./credentials directory, create a new directory for the credential. Make sure to use kebab case for the directory name.
2. Inside the newly created credential directory, add a credential.json file. This file should contain all the necessary information for the credential, including the issuer, credential subject, and other relevant data, for example ./credentials/movie-ticket/credential.json. The credential MUST be conformant to VC Data Model 1.1.
3. Additionally, place a logo image file for the credential in the corresponding directory. The image file should be in either JPG or PNG format, for example ./credentials/movie-ticket/image.png.

Add / Update a Credential Context

To optionally add or update contexts in the ./contexts directory:

1. If you wish to include a context for a credential, create a new directory for the context in the ./contexts directory. Make sure to use kebab case for the directory name. It should contain a file v1.json that should contain the JSON-LD context definition for the credential, for example ./contexts/movie-ticket/v1.json. The context MUST be conformant to VC Data Model 1.1.
2. Please note that once a context is created, it becomes locked and cannot be modified. If you want to update or make changes to a context, you must create a new context file with a new version within the context directory. For instance, if you want to update the context for the “Alumni” credential, create a new file named v2.json containing the updated JSON-LD context definition within ./contexts/alumni. The previous version,v1.json, should be retained in the directory without any modifications.
3. Please make sure that the context URLs for the contexts created in the ./contexts directory follow the format: https://contexts.vcplayground.org/examples/foo-bar/v1.json.
4. In case you need to add a custom vocabulary documentation, you can include a vocab directory within your ./contexts/foo-bar context directory. Inside the ./contexts/foo-bar/vocab directory, you can define the vocabularies within an index.html file.

Get the path to credentials directory

import {credentialsDir} from '@credential-handler/vc-examples';

Get the path to contexts directory

import {contextsDir} from '@credential-handler/vc-examples';

Tools

To generate a JSON array of context URLs used in these examples, run the following command:

$ npm -s run extract

To generate a dump of JSON objects (one per image) describing each image as a relatedResource, run the following command:

$ node related-resouces.js

The intent is for these objects to be used (where needed) in VCs or other documents where their digestMultibase values are needed.

Hash-based URLs for contexts

This is an experimental feature. We have provided redirects using identifiers created from the SHA-256 hashed canonicalized JSON (JCS) of the JSON-LD contexts in this repository at their Naming things with Hashes (RFC6920) .well-known URLs. For example:

/.well-known/ni/sha-256/deb95693d486afdb1909289e399d398a4c8bceeea12f405c32359ea81c98b48a /contexts/utopia-natcert/v2.json

Sadly, RFC6920 does not currently support a method for expressing that JCS was used in the creation of these URLs, but the above absolute path would be consistent across domain names which implemented RFC6920 + JCS for their context URLs.

Repr-Digest

In addition to the above URLs, Repr-Digest fields are provided in the responses to the human-friendly named URLs, such that the hash can be compared with cashes, stored copies, etc. For example:

HEAD /contexts/utopia-natcert/v2.json HTTP/1.1
Host: examples.vcplayground.org

HTTP/1.1 200 OK
Content-Type: application/ld+json
Repr-Digest: sha-256=deb95693d486afdb1909289e399d398a4c8bceeea12f405c32359ea81c98b48a
Link: </.well-known/ni/sha-256/deb95693d486afdb1909289e399d398a4c8bceeea12f405c32359ea81c98b48a>; rel="alternate"; type="application/ld+json"

Contribute

See the contribute file!

PRs accepted.

If editing the Readme, please conform to the standard-readme specification.

License

New BSD License (3-clause) © Digital Bazaar

This site is open source. Improve this page.