Verifiable Credentials Overview

This is a new doc (13 June 2024) that seems to serve as an introductory / big picture primer on the subject.

https://w3c.github.io/vc-overview/#ecosystem-overview

SD-JWT-based Verifiable Credentials (SD-JWT VC)

Selective Disclosure (4 Mar 2024 version)

https://datatracker.ietf.org/doc/html/draft-ietf-oauth-sd-jwt-vc-03

This draft clarifies that declaring a vct (Verifiable Credential Type) is mandatory in SD-JWT context but also that the actual vct definitions are out of scope of the draft. People within their own ecosystems should come up with those.

Our idea is to create eduPersonIdentityCredental , voPersonCredential, etc.

VC JSON Schema Specifications

18 December 2023

People now feel that the JSONs should be checked against a schema, just like XML schemas. These are the JSON Schmas, and the draft is about VC validation against schemas

https://www.w3.org/TR/vc-json-schema/#json-schema-specifications

eduPerson

The good ol' eduPerson spec

https://wiki.refeds.org/display/STAN/eduPerson+%28202208%29+v4.4.0

VC data model

https://www.w3.org/TR/vc-data-model-2.0/#names-and-descriptions

OpenBadges v3 (Now a W3C VC)

https://1edtech.github.io/openbadges-specification/ob_v3p0.html#credentialsubject

Here we have a simple credentialsubject declaration at B.1.22

This is also featured here: https://www.w3.org/TR/vc-data-model-2.0/#credential-subject 
In the examples the CredentialSubject is extended quite random ways (degree and spouse)

Subcommittee

https://wiki.refeds.org/display/STAN/VC+Subcommittee

Use Cases

Linkedin (major displayer) advice on Badge strategy

https://www.linkedin.com/advice/0/what-best-practices-designing-issuing-digital

Use Case - OJS ORCID (question) review credit plugin

https://github.com/pkp/orcidProfile/issues/181

Question: Expiration - quality - RAF-like stuff

Nils's suggestion: Base Identity education credential set == personalized

Two outcomes

Credental Request - how to do it?

Can you request for "student or nothing"?