Minutes IETF126: jsonschema
minutes-126-jsonschema-00
| Meeting Minutes | JSON Schema (jsonschema) WG | |
|---|---|---|
| Date and time | 2026-07-22 09:30 | |
| Title | Minutes IETF126: jsonschema | |
| State | Active | |
| Other versions | plain text | |
| Last updated | 2026-08-14 |
minutes-126-jsonschema-00
Minutes for the JSONSCHEMA WG IETF 126, 2026-07-22 These minutes are based heavily on input from <https://ietfminutes.org/>, with edits by Paul Hoffman. See <https://datatracker.ietf.org/meeting/126/session/jsonschema> for the full meeting materials. The JSONSCHEMA Working Group met at IETF 126 to discuss the progress of its core document, [draft-ietf-jsonschema-json-schema](https://datatracker.ietf.org/doc/draft-ietf-jsonschema-json-schema/). Lisa Dusseault presented the [JSON Schema Draft Status, issues and next work](https://datatracker.ietf.org/meeting/126/materials/slides-126-jsonschema-json-schema-draft-status-issues-and-next-work-00) slides. The draft is being structured to address three distinct readers in sequence: schema authors, schema implementers, and those who are extending schemas. Sections 4 and 5 of the draft have been populated with hopefully practical, domain-specific examples to illustrate both the syntax and the practical "why" behind various keywords. The group discussed aligning terminology with existing standards like JSONPath (RFC 9535). There was active discussion of using "JSON value" to describe parsed data structures (the data model) instead of "JSON text," which implies raw byte streams. There was a lot of discussion around defaults and the use of the "default" keyword. This also led to discussion of meta-schemas and extensibility. Separately, there was a request to review the document for RFC 2119-style "SHOULD" requirements that are in fact just implementation guidance. Andy Newton, the area director for the WG, highlighted that other SDOs and IETF working groups are already taking normative references to JSON Schema. He encouraged the group to meet or beat its May 2027 milestone. Paul Hoffman noted that finishing the current chartered work efficiently is a prerequisite for any future rechartering to address new features.