| Set a concise non-empty title at the top level of the schema to explain what the definition is about | |
| Set a non-empty description at the top level of the schema to explain what the definition is about in detail | |
| Set a non-empty examples array at the top level of the schema to illustrate the expected data | |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/cableNumber/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/cableNumber/format |
| Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types | /properties/conflictType/enum – /properties/conflictType/type |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/electrodeNumber/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/electrodeNumber/format |
| Setting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types | /properties/name/enum – /properties/name/type |
| Avoid keywords that don't apply to the type or types that the current subschema expects | /properties/tubeNumber/format |
| For interoperability purposes, the JSON Schema specification advises against the use of `format` values that are not explicitly defined by the specification | /properties/tubeNumber/format |