json-schema-spec
json-schema-spec copied to clipboard
json-schema-org
The JSON Schema specification
Fixes the "$id" side of #1059, as @jdesrosiers was the only objector to that part and eventually [dropped his alternate proposal](https://github.com/json-schema-org/json-schema-spec/issues/1059#issuecomment-761151057). Note that, syntactically, this is backwards-incompatible, but it is...
While we discuss initial base IRIs, at no point do we make it clear that it's advantageous to allow an application to supply a retrieval IRI or other IRI for...
I think this is probably what was intended - I don't see any reason for the arrays in this example to be nested. If I'm wrong and this is how...
Issue #1294 (implemented by PR #1295) includes a better explanation of optional vocabulary use cases, specifically supporting annotation-only vocabularies without needing any custom code. Currently, implementations SHOULD process optional vocabularies...
Per the [§8.1.2](https://www.ietf.org/archive/id/draft-bhutton-json-schema-01.html#name-the-vocabulary-keyword) of the core spec: > The "$vocabulary" keyword is used in meta-schemas to identify the vocabularies available for use in schemas described by that meta-schema. It is...
Depends on https://github.com/json-schema-org/json-schema-spec/pull/1085 I'll rebase this once ☝️ is merged. Updates the output schema file to match the new structure as described by the specification. Follow-up to #1249. I've tested...
Here's a fist draft for an ADR for decoupling from JSON Schema. I'm sure it needs some cleanup and fleshing out in places. I'll revise tomorrow. The scope of this...
[This discussion](https://mailarchive.ietf.org/arch/msg/json/GeISHnEGytrJqqtR86qjzOTeUt8/) on the IETF JSON mailing list brought up that this language in [§6.3 Mathematical Integers](https://www.ietf.org/archive/id/draft-bhutton-json-schema-01.html#section-6.3) is problematic: > For consistency, integer JSON numbers SHOULD NOT be encoded with...
It's common to make a virtualenv inside of your cloned repo to ensure that you have the right enviornment for that repository, and .venv is a common convention for that...