We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
type
Currently, we define JsonSchema2023 term in https://www.w3.org/ns/credentials/v2 (which will be renamed to JsonSchema). That term defines [email protected] == "@type".
JsonSchema2023
JsonSchema
[email protected] == "@type"
Separately, JSON Schema defines type in it's meta-schema (downloadable from https://json-schema.org/draft/2020-12/schema).
I believe this will mean that things break in JSON-LD world when you try to include the full JSON Schema document within the original VC.
The text was updated successfully, but these errors were encountered:
this is being addressed:
Sorry, something went wrong.
@andresuribe87 can this be closed?
decentralgabe
No branches or pull requests
Currently, we define
JsonSchema2023
term in https://www.w3.org/ns/credentials/v2 (which will be renamed toJsonSchema
). That term defines[email protected] == "@type"
.Separately, JSON Schema defines
type
in it's meta-schema (downloadable from https://json-schema.org/draft/2020-12/schema).I believe this will mean that things break in JSON-LD world when you try to include the full JSON Schema document within the original VC.
The text was updated successfully, but these errors were encountered: