-
Notifications
You must be signed in to change notification settings - Fork 8
JSON-LD cannot validate, only JSON Schema can #88
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
Comments
My intention, which I can see is less-than-clear, was to state that an LD schema could be embedded into a JSON schema so there's a 1 - 1 mapping between the two.
Yeah I wasn't really aware of these. They could be OK to add but seem quite complex and (potentially) unnecessary compared to JSON Schema which is quite widely adopted. |
What is LD Schema? If you don't like RDF Shapes then delete section Alternatives |
Any schema that uses JSON LD, like those here https://schema.org/docs/schemas.html
My personal preferences have little to do with the specification. It would be dishonest to not share alternatives. If you believe there's an error, please make a contribution. |
Closing and will be handled in #122 |
JSON-LD is completely orthogonal to JSON Schema:
In addition, while the use of
credentialSchema
(in particular JSON Schema) is optional in VC, JSON-LD is necessary.So I'm puzzled by these statements:
In particular, the latter should be changed to refer to the RDF Shape languages (SHACL and SHEX), which provide data validation features comparable to JSON Schema
Closely related to #16
The text was updated successfully, but these errors were encountered: