json-schema-spec
json-schema-spec copied to clipboard
json-schema-org
The JSON Schema specification
Similarly to encountering unknown keywords, implementations should raise an error for unknown dialects.
Following @handrews' discussion on [disallowing non-vocab keywords](https://github.com/orgs/json-schema-org/discussions/241), we decided that this is a feature that we want in order to help guarantee forward compability. The spec needs to be updated...
The current feature set of JSON Schema needs to be cataloged so that unstable features can be identified. Once that is done, any unstable features that are required for basic...
Related to #1339, we need to add language that requires implementations to disable unstable features as the default behavior.
Following #1337, we need to update the spec to identify and properly catagorize the remaining unstable features.
@jdesrosiers wrote an [intro post](https://json-schema.org/blog/posts/future-of-json-schema) regarding the move away from IETF and the direction we're heading from the point of view of increasing stability. We need another post that describes...
(This issue will likely need to be moved to the site repo as the changes will be implemented there, but for now it's being created here for tracking purposes.) After...
@jdesrosiers' [Proposal: New Spec Development Lifecycle Model](https://github.com/orgs/json-schema-org/discussions/234) (SDLC) needs formal documentation. There may be a few things to work out, but the concept is mostly defined.
clarify that `readOnly` applies to any value, not just properties. Re-format `true` and `false` code values Resolves #1402
Relates to https://github.com/orgs/json-schema-org/discussions/724 and https://github.com/json-schema-org/json-schema-spec/pull/1505. Depends on #1518 Depends on #1512 (will likely need rebase after those merge) The Core spec was a lot, but it was fairly straightforward. This...