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

The JSON Schema specification

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

This issue is _not_ intended to make fundamental changes, just address the overly-broad "implementation-defined" behavior by excluding obviously problematic behaviors. Doing this does not preclude further changes to `$schema` and/or...

Type: Bug
core

Currently, our plain name fragments are restricted to the US-ASCII subset of the relevant XML plain name fragment syntax. Now that we support IRIs should we expand this as well?...

Type: Enhancement
core

There is currently no normative language requiring "$schema" to be respected. Particularly for supporting optional vocabularies without requiring custom code (see #1300), there needs to be a mandatory requirement to...

Type: Enhancement
core

Because XML is/was the most likely need for cross-media-type fragment identifiers. Fixes #901

Type: Maintenance
core

Fixes #1311.

Priority: High
annotation
validation

Splitting this off from #1059 which also discussed "$id" (see PR #1291 for that part), @MikeRalphson raised the use case of a meta-schema included in a schema, but not as...

Type: Enhancement
core

This section: > [7.7.1.3. ](https://www.ietf.org/archive/id/draft-bhutton-json-schema-01.html#section-7.7.1.3)[Annotations and Applicators](https://www.ietf.org/archive/id/draft-bhutton-json-schema-01.html#name-annotations-and-applicators) In addition to possibly defining annotation results of their own, applicator keywords aggregate the annotations collected in their subschema(s) or referenced schema(s). should...

Type: Maintenance
core
annotation

Note: Other folks (@jdesrosiers ? @karenetheridge ?) came up with this a while ago and apparently I objected to it (which I 100% believe but no longer recall the reason)....

Priority: High
Type: Bug
core
annotation
validation

I had a realization today about what the text in [section 10.3.2.1](https://json-schema.org/draft/2020-12/json-schema-core.html#section-10.3.2.1) says about the annotation result of `properties` > The annotation result of this keyword is the set of...

Type: Maintenance
re-use / addlProps
annotation

In [§8.2 Implementation Requirements](https://www.ietf.org/archive/id/draft-bhutton-json-schema-validation-01.html#section-8.2) (for the `content*` keywords), we have: > Implementations MAY offer the ability to decode, parse, and/or validate the string contents automatically. However, it MUST NOT perform...

Type: Enhancement
Priority: High
Type: Security
validation