New fields may appear
A higher version can add fields. A file written today stays valid.
A format is only usable when you know what you can rely on. This page says exactly that.
From version 1.0 one rule applies, and it is binding.
A higher version can add fields. A file written today stays valid.
No field is removed, renamed or redefined. What 1.0 meant, 1.7 still means.
Anyone building a reader ignores unknown fields rather than failing. One reader then handles every later version.
Is a fund, distributor or insurer missing something? No separate variant of the format is needed.
Every statement carries an extensions object. An organisation hangs its own fields under a reverse domain key. That key is theirs; the rest of the file stays the standard's.
"extensions": {
"nl.filmfonds.v1": { "dossiernummer": "2026-114" },
"com.example-distributor.v2": { "deliverySpec": "…" }
}
The same is allowed per stage. A reader that does not know the key skips it.
Each version has a published JSON schema at a fixed address. Every statement points to it, so a recipient can always verify a file, ten years from now and even if this site is gone.
Version 1.0 does not arrive on a date but on a condition: when a number of real productions have completed the form and it is clear which questions do not work in practice. Until then every change is free. After that it costs ten years.
Twelve stages, four answers, IPTC mapping.
A thirteenth stage. Coverage made stage-appropriate instead of image and sound everywhere.
Its own block for AI material, the AI agent as a separate option, extensions, and a published schema.