The SEDRIS Data Representation Model
APPENDIX B - Constraints Property Characteristic Constraints |
---|
Consider a <Property Characteristic> instance C and a DRM object P such that C is a component of P, where P is a <Property> instance or a <Table Property Description> instance.
The attribute_value_type of the characteristic_value field of C shall correspond to the value type imposed by the meaning of P, except in the case where the meaning field of P specifies an EA bound to the abstract value type EDCS_AVT_ENUMERATION and the meaning field of C specifies one of the qualitative EVs EVC_NOT_APPLICABLE, EVC_MISSING, EVC_VALUE_WITHHELD, EVC_MULTIPLE, or EVC_UNDESIGNATED. In that case, C shall be bound to the abstract value type EDCS_AVT_INTEGER with a characteristic_value that does not correspond to the numeric value of a valid EE for the given EA.
If the attribute_value_type of the characteristic_value field of C is not numeric, C shall not have an EV with an applicability of numeric as its meaning.
Consider another, distinct <Property Characteristic> instance C2 that is also a component of P.
The meaning field values of C and C2 shall be distinct.
If C specifies EVC_MINIMUM_VALUE and C2 specifies EVC_MAXIMUM_VALUE, the characteristic_value of C shall be less than or equal to that of C2.
A <Property Characteristic> component of a <Property> instance P qualifies the information in P, so it shall not conflict with the information already present in P. In the case of multiple <Property Characteristic> components for the same <Property> instance, they shall not conflict with one another.
A <Table Property Description> instance T shall have at most one <Property Characteristic> component specifying the EVC_MAXIMUM_VALUE for the set of <Data Table> cell elements corresponding to T.
No FAQs supplied.
|