Schema error

Schema draft mismatch: definitions versus $defs, draft 2019-09 versus 2020-12

Symptom

The validator reports 'can't resolve reference', MissingRefError or 'no schema with key or ref' when loading the schema, before the message is tested.

Cause

Release 2027 migrated to JSON Schema draft 2020-12 ($defs, https references); Release 2026 uses draft 2019-09 with definitions. The schemas refer to external code lists on sivi.org that the validator must know. Since the final Release 2027 messages 5, 6 and 15 also refer to the code-list file next to the schema for AFDSWI and AFDCOA, by a relative file name (…-afdCodelists.json#/$defs/AFDSWI).

Fix

Use a validator that supports both drafts (AJV: Ajv2019 and Ajv2020). Register the code lists under the URL the schema uses, and the code-list file under its file name. AJV 8.17 encodes the brackets in that file name twice; then also register the file under the key the error message names. The WTP Data Lab validator does this automatically.

Check your own message for this and all other errors with the free validator: schema, code lists and consistency checks in one report. Validate a message