json-schema-spec
json-schema-spec copied to clipboard
The JSON Schema specification
We permit empty fragments in `$id`, and say nothing at all about fragments in `$schema`. IMO we should prohibit all kinds of fragments in both keywords' URIs. cross-reference: https://github.com/OAI/OpenAPI-Specification/issues/2433#issuecomment-756389903
This is just a bug fix for an accidental oversight. I'm hoping it's non-controversial as I don't think any of us meant to allow arbitrary behaviors for unrecognized keywords. When...
https://json-schema.org/understanding-json-schema/reference/array.html#unevaluated-items This is a request to add the docs for this property behavior.
Currently, the Relative JSON Pointer (RJP) specification only specifies how to evaluate an RJP with a document reference. This is actually challenging as typical in-memory representations of JSON documents do...
This is quite a change, so I'd be happy to walk anyone through it. ## Summary Following the idea from [this thread](https://github.com/orgs/json-schema-org/discussions/63#discussioncomment-2960665) and [this thread](https://github.com/orgs/json-schema-org/discussions/63#discussioncomment-2968029), this PR changes the concept...
(I don't see this mentioned elsewhere, but if it is, feel free to redirect). We now have at least a few examples of explicitly *deprecated* keywords (or more broadly behavior)....
Proposal: Add a defined format for Mac Address. The schema already has support for IPv4 and IPv6 data types. It would be useful to have support for the colon delimited...
The GitHub Actions setup is equivalent to the Travis CI configuration with two differences: - The GitHub Action setup does not set the `TAG` environment variable, as it didn't seem...
I noticed a few places where the spec is using several different phrasings to mean the same thing. This PR aligns them to what we agreed it should be called...
Resolves https://github.com/json-schema-org/json-schema-spec/issues/1112 Adds the `requireAllExcept` keyword.