-
Notifications
You must be signed in to change notification settings - Fork 99
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
Claims: Schema has invalid URI for bundle spec ref #241
Comments
Actually, we might make this issue more general to ensure the base bundle schema's (This happens to be the only schema referenced by another, currently... but perhaps we'd want to ensure all schemas in the |
Minor note: JSON Schema reference URIs are not expected to be traversable; they are only identifiers, not locators. "Even though the value of a $ref is a URI, it is not a network locator, only an identifier. This means that the schema doesn’t need to be accessible at that URI, but it may be. It is basically up to the validator implementation how external schema URIs will be handled, but one should not assume the validator will fetch network resources indicated in $ref values." https://json-schema.org/understanding-json-schema/structuring.html#reuse So it's up to validators to gather all the schemas they're going to need using out-of-band knowledge, and use the From a human point of view, though, having the schema available at its |
Tracking the work in cnabio/cnab.io#15; closing this ticket. |
The Claim schema has a $ref field associated with its
bundle
property pointing to a URI that doesn't exist. (http://cnab.io/v1/bundle.schema.json
)We should ensure this URI exists and/or update it accordingly.
I hit this in an attempt to validate a generated claim programmatically; the library used attempted to fetch the ref'd schema but errored out as it was not found.
The text was updated successfully, but these errors were encountered: