Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

references to schemas with different credential technologies. #33

Open
TelegramSam opened this issue Feb 5, 2024 · 4 comments
Open

Comments

@TelegramSam
Copy link
Contributor

No description provided.

@TelegramSam
Copy link
Contributor Author

ld creds:

  • covered by the w3c data model
    jwt creds:

sd-jwt creds:

w3c data model: https://www.w3.org/TR/vc-data-model/#types

The value of the type property MUST be, or map to (through interpretation of the @context property), one or more URIs.

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?

@TelegramSam
Copy link
Contributor Author

AnonCreds - URI, solved
SD-JWT - Unknown
LD-based credentials (anything that uses @context - Use context values other than the VC Datamodel URI?

@TelegramSam
Copy link
Contributor Author

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.

@TelegramSam
Copy link
Contributor Author

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"
],

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant