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

allow changing $schema in resource subschemas #12

Closed
karenetheridge opened this issue May 9, 2020 · 2 comments
Closed

allow changing $schema in resource subschemas #12

karenetheridge opened this issue May 9, 2020 · 2 comments
Labels
draft-next features, changes not applicable until a future draft specification - MAY Status: Blocked

Comments

@karenetheridge
Copy link
Owner

As explicitly described in json-schema-org/json-schema-spec#914 -- examine $schema wherever it (legally) appears and adjust evaluation semantics accordingly (including turning on/off keyword support via $vocabularies).

But as per json-schema-org/json-schema-spec#808 (comment) --

... implementations at least SHOULD check $schema and if available $vocabulary, but are free to error out on unknown or known but unsupported (e.g. old drafts) values.

(Support for earlier drafts' semantics may be covered in a separate issue, to be implemented separately.)

@karenetheridge
Copy link
Owner Author

blocked on #13 -- until then, we don't do anything special with the $schema keyword anyway.

@karenetheridge karenetheridge added the draft-next features, changes not applicable until a future draft label May 27, 2020
@karenetheridge
Copy link
Owner Author

As of version 0.513 we now accept different values in the $schema keyword.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
draft-next features, changes not applicable until a future draft specification - MAY Status: Blocked
Projects
None yet
Development

No branches or pull requests

1 participant