Cardinality of Constraint Properties in DSP Spec Unclearly Stated #212
Description
Bug Report
Describe the Bug
Properties leftOperand, operator and rightOperand are only required if no and, andSequence, or, or xone (logical operator sub-objects) is used.
Type: normative
Expected Behavior
Constraint table clearly distinguishes the two cases: implicit and and explicitly stated logical operator sub-objects, where in the first case leftOperand, operator and rightOperand are required and in the second case must not be used, while one of the logical operator sub-objects is mandatory in the second case and none of them must be used in the first case.
Observed Behavior
Detailed Description
Problem seems to be, that the JSON schema is not correctly represented, when the table in the specification is auto-generated.
Possible Implementation
You will likely use two tables for both cases to fix the problem in the specification. Another point to consider, aside from fixing the specification, is to completely prohibit the implicit "and," as implicit elements in a specification always leave room for interpretation.