json-schema-spec icon indicating copy to clipboard operation
json-schema-spec copied to clipboard

The JSON Schema specification

Results 247 json-schema-spec issues
Sort by recently updated
recently updated
newest added

re: `draft-bhutton-json-schema-validation-01`: The defined format descriptions in 7.3.1 - 7.3.7 use consistent language: "A string instance is valid against this attribute if ..." The language in 7.3.8 is different, simply...

[Core 6.4 Regular Expressions](https://json-schema.org/draft/2020-12/json-schema-core#section-6.4) doesn't explicitly list "." as one of permitted regular expression constructs. This seems to be an oversight. I propose adding it to the list of simple...

_In #1434, @karenetheridge left a [comment](https://github.com/json-schema-org/json-schema-spec/pull/1434#pullrequestreview-1618682543) regarding special-casing meta-schema validations. This issue continues that conversation._ When validating a schema with a meta-schema that contains an subschema with a different `$schema`...

This is somewhat trivial but I think this is more correct. The string is a simple type, not multiple types.

***IMPORTANT: This changes how meta-schemas are organized but not really how they work.*** Relevant to this discussion: - [whether optional vocabs make sense](https://github.com/orgs/json-schema-org/discussions/342) - [URI naming scheme](https://github.com/json-schema-org/json-schema-spec/issues/1401) - [adding keyword...

Relates to #1444 and #1449

Status: Blocked

This discussion was split from #1391. See also #898. Historically, `integer` was added to the `type` keyword even though it's not distinguishable in JSON from `number`. Also, some time ago,...

The spec allows `"type": []`, but in the validation vocabuary there is a 'minItems: 1' for the "type" property. This seems inconsistent. For details see this issue I filed earlier...

When defining mutually exclusive if-statements (`if`, `else-if`, `else-if`, etc.), JSON Schema currently requires nesting with the `else` statements. For shallow cases, this works fairly well. For example: ``` { "if":...

proposal

The pattern of using oneOf to describe a choice between two types has become ubiquitous. ```json { "oneOf": [ { "$ref": "#/$defs/aaa" }, { "$ref": "#/$defs/bbb" } ] } ```...

proposal