Open TelegramSam opened 9 months ago
AnonCreds - URI, solved
SD-JWT - Unknown
LD-based credentials (anything that uses @context
- Use context values other than the VC Datamodel URI?
https://www.w3.org/TR/vc-data-model-2.0/#types for w3c data models. is URI or resolves to a URI via LD @context
expansion.
it appears that credentials may contain multiple sub types. should all types be recognized?
Two options for declaring an issuer as 'authorized': all types and contexts, or must ignore sections that don't include relevant types.
examples of contexts used for verification:
[ "https://www.w3.org/2018/credentials#VerifiableCredential", // "https://w3id.org/citizenship#PermanentResident" "https://purl.imsglobal.org/spec/vc/ob/vocab.html#OpenBadgeCredential" // "https://contexts-file-hosting.glitch.me/data.jsonld#KELICourseCredential" // "https://example.com/indicio#courseCompletion" // "https://example.com/indicio#KELICourseCredential" // "https://example.com/examples#CustomContext", // "https://example.com/examples#KELICourseCredential" ],
ld creds:
sd-jwt creds:
w3c data model: https://www.w3.org/TR/vc-data-model/#types
the schema URI most be the URI that is or is mapped to via the @context properties
Note, the inclusion of
VerifiableCredential
(https://www.w3.org/2018/credentials#VerifiableCredential
) is necessary for all credentials, and is not the relevant schema we are linking to. The PermanentResident is the schema in question.Examples: https://www.w3.org/2018/credentials#VerifiableCredential, https://w3id.org/citizenship#PermanentResident
Openbadges https://purl.imsglobal.org/spec/vc/ob/vocab.html#OpenBadgeCredential https://example.com/examples#KELICourseCredential
CredentialSubject > Type contains the type we care about for open badges, which appears different than use in normal VCs.
Do we instead use external definitions like Presentation Defintion, since they are more straigtforward?