...
Range Checks using Comparator and CheckValue
When using Comparator and Check Value each Range Check CheckValue, each range check represents a one-sided constraint. Multiple Range Checks range checks can be used to specify more complex constraints , (e.g., an upper and lower bound would require two Range Checks2 range checks).
Each constraint is equivalent to:
...
If an actual data value fails the constraint, it is either rejected (a Hard hard constraint) or a warning is produced (a Soft soft constraint).
For the following comparison operators, one Check Value check value is required.
LT | Less than |
LE | Less than or equal to |
GT | Greater than |
GE | Greater than or equal to |
EQ | Equal to |
NE | Not equal to |
A set of Check Values check values is required for these comparators:
IN | One of listed values |
NOTIN | Not any of list values |
If a Measurement Unit measurement unit is specified, the corresponding Item values must have interconvertible Measurement Units measurement units (either explicitly or by default). Proper conversion of units must be done as part of the Range Checkrange check. If a Measurement Unit measurement unit is not specified, the corresponding Item values must not have Measurement Units measurement units (either explicitly or by default).
...
Example | ||||||
---|---|---|---|---|---|---|
|
Example | ||||||
---|---|---|---|---|---|---|
|
Range Checks using FormalExpression
When using FormalExpression a Range Check range check can represent anything , (e.g., one-sided or multi-sided multisided checks). These type of checks must not provide CheckValue or Comparator as they would all be expressed in the FormalExpression itself. The FormalExpression takes the value of the ItemData element and returns a boolean value which is the result of the expression. Multiple FormalExpressions can be provided if each has a different Context attribute, allowing the same expression to be represented in forms appropriate to multiple systems. Multiple different expressions, with different meanings, must be represented as separate RangeChecks
...