What Changed in May 2026
The IETF JSONSCHEMA working group now lists draft-ietf-jsonschema-json-schema-00 as an active working group document. The Datatracker page shows a May 12, 2026 revision, a May 20, 2026 update, and an intended RFC status of Proposed Standard.
That is a meaningful governance step for JSON Schema. The working group charter says JSON Schema has existed across multiple Internet-Drafts but has not yet been published as an RFC, and the group goal is to produce a stable reference specification containing features and mechanisms that are in known use.
Why This Is Not an RFC Yet
The new document is still an Internet-Draft. The draft itself carries the normal IETF warning that Internet-Drafts are working documents, can change or be replaced, and should not be treated as permanent references.
The practical reading is narrow: this is a standards-track direction to monitor, not a new production dialect that schema authors should immediately declare. Existing schemas that target draft 2020-12 still need validator support for that dialect today.
What Validator Authors Should Watch
Appendix G says the draft consolidates the 2020-12 core and validation documents, moves terminology into a dedicated section, and reorders material around keywords, processing, output, and extensibility. Those are editorial and specification-structure changes, but they matter to implementors who need one reference point for behavior.
Validator authors should track how the working group handles output formats, vocabularies, annotation collection, $dynamicRef, and media type text as the draft evolves. Those areas are where small wording changes can affect interoperability tests, error displays, API request validation, and schema-driven editor tooling.
Guidance for Browser Tools
For local-first browser utilities, the near-term guidance is conservative: keep validating pasted JSON and schemas locally, keep exposing the declared $schema dialect, and avoid implying that the IETF draft has already become the final JSON Schema RFC.
The useful work now is compatibility reporting. A JSON formatter, diff tool, or API payload debugger can help developers see whether a schema uses draft-07, 2019-09, 2020-12, or a future standards-track dialect before the payload leaves the browser tab.