Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
“Standard JSON Schema” is not an official name for a separate language or competing specification. It is usually informal shorthand for JSON Schema that follows a particular specification dialect. The useful question is which dialect and validator compatibility you need—not whether to choose “standard” JSON Schema over JSON Schema.
JSON and JSON Schema are different things
JSON is a data interchange format. JSON Schema is a declarative language for describing the structure and constraints of JSON values. The JSON Schema project defines it as “a declarative language for defining structure and constraints for JSON data.” JSON Schema’s official overview and glossary explain the distinction.
A schema describes rules; a validator is software that checks whether a JSON document conforms to those rules. The schema and the tool that evaluates it are not the same thing. The project’s overview describes this validator role.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →What “standard JSON Schema” usually means
The phrase is ambiguous unless the speaker defines it. Official JSON Schema materials do not identify “Standard JSON Schema” as a distinct specification. Someone using the phrase may simply mean a schema written to the JSON Schema specification, or may have a particular version or compatibility target in mind. Ask which dialect they mean rather than assuming there is a separate standard. The official specification page identifies the project’s released specifications.
| Term | What it means | What to clarify |
|---|---|---|
| JSON | A data interchange format. | Do not use this name for the schema language. |
| JSON Schema | A language and specification for describing JSON data and its constraints. | Identify the dialect when version compatibility matters. |
| JSON Schema dialect | A version’s set of keywords and evaluation semantics. | State the target, such as 2020-12. |
| “Standard JSON Schema” | Informal wording, not a separate specification identified by the project. | Ask what version or compatibility target the phrase refers to. |
| JSON Schema validator | Software that evaluates JSON instances against a schema. | Check the implementation’s dialect and vocabulary support. |
Which JSON Schema version should you use?
The project’s specification page identifies 2020-12 as the current released version. The Core and Validation specifications for 2020-12 were published on 16 June 2022, according to the official specification links. “Current” does not mean that every validator supports every feature, so confirm the version supported by the software that will evaluate your schema.
Older dialects are not completely compatible with 2020-12, according to the project’s Understanding JSON Schema learning material. If you are migrating a schema or sharing it across tools, check the actual dialect and implementation rather than relying on the label “standard.”
Declare the dialect with $schema
Include $schema at the root of a schema to identify its dialect. The project’s dialect and vocabulary reference says this declaration also identifies the meta-schema that can be used to validate the schema itself. For example:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object"
}If $schema is absent, an implementation may rely on external configuration or make assumptions about which dialect to apply. An explicit declaration makes the intended version clearer to people and tools.
Check more than the version when choosing a validator
Two validators can differ in supported features even when they are used with the same dialect. Before relying on a schema, check the implementation’s support for the dialect and the vocabularies your schema uses. The specification is divided into Core and Validation documents and includes vocabulary-specific meta-schemas; the official specification page outlines that structure.
Pay particular attention to format. The project’s format reference is not among the supplied source URLs, so no link should be added here; official guidance in the project materials states that implementations may support only subsets of built-in formats or perform partial validation. Do not assume that every validator enforces every format string identically. Confirm its documented behavior for the formats that matter to your application.
Is JSON Schema an IETF RFC?
Do not treat “standard JSON Schema” as evidence that it is an IETF RFC. In a January 13, 2025 update, the project said it no longer publishes specifications through the IETF and described itself as independent. See “Moving Toward a Stable Spec” for that publication-process context.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
