json-schema-spec
json-schema-spec copied to clipboard
json-schema-org
The JSON Schema specification
(By "is not defined" I don't mean that it's considered and left as "undefined" behavior; I mean it's not addressed at all.) In [Slack](https://json-schema.slack.com/archives/CT7FF623C/p1660688416888499), we had a short discussion around...
This would **not** significantly change anything about the behavior of `$vocabulary`. While there are ambiguities in the current wording, I will be filing thoughts on clarifying those as separate issues....
given the illustration there https://json-schema.org/understanding-json-schema/reference/enum it would be good to add a precision that the enum validation, for string, is case sensitive , and so introducing in the sample list...
'properties' keyword is defined in chapter 10.3.2.1 of the [core specification](https://json-schema.org/draft/2020-12/draft-bhutton-json-schema-01#section-10.3.2.1): *Validation succeeds if, for each name that appears in both the instance and as a name within this keyword's...
Add "." to the permitted simple atoms, for issue #1469. Consistently format the regex examples.
In some of the discussion around annotation-only or SVA (simple value annotation) keywords, some commenters seem to suggest the "@" naming scheme would be useful for writing custom keywords. This...
Fixes https://github.com/json-schema-org/json-schema-spec/issues/1480 to omit the sentence about omitting the keyword, as `allOf` etc do. Also fixes a small markdown error while I'm touching that section.
@karenetheridge noted that there wasn't an ADR for this, and I agreed there probably should have been. Relates to https://github.com/json-schema-org/json-schema-spec/issues/1077 and https://github.com/json-schema-org/json-schema-spec/issues/1358.
Figured it'd be better in it's own folder than with the primary specs. The folder already existed and housed the schema file.