Identifying the schema version to a consuming application

[pixeltrix]

Since there's no version or other such property in the JSON schema, what's the expected approach for identifying the version of the schema to validate against?

There is a reference to using the media type header in an early JSON Schema RFC - is this the intended way?
https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-02#section-11.2

Whilst this works for HTTP-transmitted data what about long term storage of submissions and keeping track of what version they were created against?

[colmjude]

Thanks, this is a fair and important point.

Our current position is:

• Not every standard needs a version field in each document, but for planning submissions we think this is needed.
• The rules for what counts as a valid submission can change over time.
• So we need each submission to show which version of the rules it was checked against.
• This helps with consistent validation, audit checks, and later reviews.

What we want to do:

• Put a clear version field in the payload itself, so the version stays with the submission record wherever it is stored.

Why this is not already in place:

• We first focused on getting the core data model into a stable shape.
• We did not want to add a version field too early while the model was still moving quickly.

We will take this forward as a change to the core specification.