Root- and sub-node schemas are supposed to be allowed to use the 'not' keyword directly to express a schema against which the instance isn't supposed to be successfully validated. It shall work in the same way as the allOf, anyOf, oneOf-based validation except the keyword implies a single sub-schema against which an instance will be anti-evaluated. Signed-off-by: Serge Semin <Sergey.Semin@xxxxxxxxxxxxxxxxxxxx> --- Please see the next email message for the patch context: Link: https://lore.kernel.org/netdev/20230313225103.30512-16-Sergey.Semin@xxxxxxxxxxxxxxxxxxxx --- dtschema/meta-schemas/base.yaml | 2 +- dtschema/meta-schemas/nodes.yaml | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/dtschema/meta-schemas/base.yaml b/dtschema/meta-schemas/base.yaml index 1dd005c53467..96d0a82febc6 100644 --- a/dtschema/meta-schemas/base.yaml +++ b/dtschema/meta-schemas/base.yaml @@ -50,7 +50,7 @@ properties: propertyNames: enum: [ $id, $schema, title, description, examples, required, allOf, anyOf, oneOf, definitions, $defs, additionalProperties, dependencies, dependentRequired, - dependentSchemas, patternProperties, properties, if, then, else, + dependentSchemas, patternProperties, properties, not, if, then, else, unevaluatedProperties, deprecated, maintainers, select, $ref ] required: diff --git a/dtschema/meta-schemas/nodes.yaml b/dtschema/meta-schemas/nodes.yaml index 7568169a7907..0b2c8f750624 100644 --- a/dtschema/meta-schemas/nodes.yaml +++ b/dtschema/meta-schemas/nodes.yaml @@ -26,6 +26,7 @@ propertyNames: - unevaluatedProperties - deprecated - required + - not - allOf - anyOf - oneOf -- 2.39.2
