You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jsonschema uses HTTP client library reqwest which pulls in a lot of dependencies (#18). Also, the requests are blocking and responses are not cached (Stranger6667/jsonschema#75). But it looks like the resolver is not used internally to validation but only if the caller calls it. So this might not be a problem us, especially if reqwest is made optional (Stranger6667/jsonschema#137), as we can do our own HTTP resolution (edit: maybe just using reqwest as well), e.g. alongside resolution for JSON-LD Context documents.
Another library is schemafy (mentioned in #21 (comment)) which generates types from schemas at compile time. But it doesn't have full support for the latest JSON Schema drafts. Its use may be limited here since I think we want to be able to validate credentials against arbitrary schemas at runtime.
The text was updated successfully, but these errors were encountered:
Note that CCG-hosted specs are not official standards or recommendations, but are a good focal point to consider due to industry and implementer participation, with the possibility of being adopted as a standard at places like W3C and IETF.
A credential's
credentialSchema
may specify a URI for a JSON Schema file for validating the credential. (https://w3c.github.io/vc-data-model/#proofs-signatures)A Rust library for JSON Schema is jsonschema.
jsonschema
uses HTTP client library reqwest which pulls in a lot of dependencies (#18). Also, the requests are blocking and responses are not cached (Stranger6667/jsonschema#75). But it looks like the resolver is not used internally to validation but only if the caller calls it. So this might not be a problem us, especially ifreqwest
is made optional (Stranger6667/jsonschema#137), as we can do our own HTTP resolution (edit: maybe just usingreqwest
as well), e.g. alongside resolution for JSON-LD Context documents.Another library is schemafy (mentioned in #21 (comment)) which generates types from schemas at compile time. But it doesn't have full support for the latest JSON Schema drafts. Its use may be limited here since I think we want to be able to validate credentials against arbitrary schemas at runtime.
The text was updated successfully, but these errors were encountered: