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

### Describe the inspiration for your proposal I want to enforce that "nothing goes unseen" by the schema - for example to safeguard against misspelled property names, ensure that extension...

proposal

### Describe the inspiration for your proposal In the discussion about the format registry, someone proposed that formats in the registry include a schema that validates them. Implementations could then...

proposal

### Describe the inspiration for your proposal Currently, the "date-time" format with string type only accepts timestamp strings in RFC 3339 format. RFC 9557 is an update to RFC 3339....

validation
proposal

We need a section in Core that defines what we expect from tooling around support for feature proposals. Basically, proposals are OPTIONAL but RECOMMENDED. Tooling must also specify in their...

core

### What kind of change does this PR introduce? clarification ### Issue & Discussion References - Closes #1231 ### Summary Adds a security note about performing network operations when encountering...

### Describe the inspiration for your proposal Open API already has defined several formats that are arguably useful outside of the context of their spec, but I don't think we...

proposal

Draft 2020-12 [7.3.1. ](https://json-schema.org/draft/2020-12/json-schema-validation#section-7.3.1)[Dates, Times, and Duration](https://json-schema.org/draft/2020-12/json-schema-validation#name-dates-times-and-duration) states: >Date and time format names are derived from [RFC 3339, section 5.6](https://www.rfc-editor.org/info/rfc3339). The duration format is from the ISO 8601 ABNF as...

validation
proposal

@jviotti also pointed out the metaschemas diverge on this change. > Actually it's a bit more subtle. While the spec indeed says SHOULD in some cases, the meta-schemas often still...

### What is unclear? Is it legal to use a non-canonical identifier in a `$schema` keyword to refer to a metaschema? e.g. if I have this document: ```json { "$id":...

For 2019-09, the meta-schema was split along the vocab boundaries, and each vocab got its own, and the top-level meta-schema simply referenced these individual ones. With vocabs being put into...