Verifiable Credential Schemas with Open API Specification

Friends,

I wanted to share a project we did a few weekends back regarding the
extension feature of verifiable credentials related to schemas:
credentialSchema.

Before reviewing it, you may wish to refresh on this section of the TR:
https://www.w3.org/TR/vc-data-model/#data-schemas

In short, we use Open API Specification 3 a lot, and it supports JSON
Schema for validating data, we've found the tooling to be widely supported.

There is previous work in this area at the W3C CCG:

https://github.com/w3c-ccg/vc-json-schemas

Why the need for a new credentialSchema
*type?*
The TLDR is that this simpler version aligns with our use case for securing
verifiable credentials associated with supply chain traceability.

In fact, we use this approach to automatically generate vocabularies and
contexts for supply chain credentials today:

https://github.com/w3c-ccg/traceability-vocab/tree/main/docs/openapi/components/schemas/credentials

The approach above uses some extensions to OAS which are not standard, and
I don't believe necessary for many use cases,
so we pulled the simplest parts of the work out into a standalone spec,
that only addresses schema validation of verifiable credentials.

https://github.com/transmute-industries/vc-credential-schema-open-api-specification

We have heard requests / threats that if we define credentialSchema, we
need to define at least 1 type for it, so that the feature is testable.

The working group now has at least 2 options to evaluate for
*credentialSchema type.*
Regards,

OS

-- 
*ORIE STEELE*
Chief Technical Officer
www.transmute.industries

<https://www.transmute.industries>