Page History

...

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.

A set of Check Values check values is required for these comparators:

If a Measurement Unit an associated unit with a measurement variable is specified, the corresponding Item values must have interconvertible Measurement Units (either explicitly or by default)reflect the values using the associated units specified. Refer to ItemRef/@UnitsItemOID. Proper conversion of units must be done as part of the Range Check. If a Measurement Unit is not specified, the corresponding Item values must not have Measurement Units (either explicitly or by default)range check.

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 or MeasurementUnitRef 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.