Current ETSI messages JSON schemas only have a single top-level "additionalProperties": false flag.
This single flag only prevents additional fields being added to the top-level object, and does not apply to the child objects such as "message" and its own sub-objects in our case.
This has two main drawbacks:
- any random extra field can be added to a child object and pass validation tools
- any optional field with a typo will not be detected by validation tools
This can be linked to issue #546
Current ETSI messages JSON schemas only have a single top-level
"additionalProperties": falseflag.This single flag only prevents additional fields being added to the top-level object, and does not apply to the child objects such as
"message"and its own sub-objects in our case.This has two main drawbacks:
This can be linked to issue #546