json-schema-spec
json-schema-spec copied to clipboard
The JSON Schema specification
A remedy for #1160.
I sent a request to the debian-perl folks to package my implementation for Debian. They are concerned that I bundle the metaschema files but there is no associated licence; additionally...
Fixes #1140 Without bookending or initial resolution, describing how dynamic references work becomes much more straightforward. This is provided as a draft PR just to show what the change might...
- $id cannot have a fragment at all, so separate it from the common definiiion - $ref, $dynamicRef, $recursiveRef must be a iri-reference to a schema location: when the fragment...
## This PR - We have "JSON text" in notational conventions, so there's no need to reference the application/json media type - Since the document references an equivalence relation between...
This replaces https://github.com/json-schema-org/json-schema-spec/pull/1200, as it was decided the change cannot go into the patch release.
Resolves #1121
Resolves #1069 Relates to #1070 & #1071 Happy to take opinions on the content of 👇. It all works pretty well, though, so I don't think I'll be changing the...
TL;DR Moving the discussion from https://github.com/OAI/OpenAPI-Specification/issues/348 to JSON Schema folks. Hi All, For enums, we can now only list the values, for example: ``` cvv_check: type: string title: CVV check...
Linter
Per @Relequestual's recommendation, I'm creating a ticket about a linter and to collect linting rules that people would want. When authoring a JSON schema, it is desirable to have a...