Correct functional semantics of AOM constraint model package

Description

In the current revsion of the AOM, the constraint_model package contains a number of
functions that are defined on the wrong classes or in the wrong way. These are:

  • assumed_value; currently defined both on C_DOMAIN_TYPE and on C_PRIMITIVE_OBJECT (repetition)

  • any_allowed, currently defined as an attribute on ARCHETYPE_CONSTRAINT, but can in fact be
    defined functionally in terms of other attributes on all classes

  • valid_value, currently defined on C_DOMAIN_TYPE, but needed on C_COMPLEX_OBJECT and C_PRIMITIVE_OBJECT

  • default_value, currently defined on C_DOMAIN_TYPE, but needed on C_COMPLEX_OBJECT and C_PRIMITIVE_OBJECT

Status

Assignee

JeffJ

Reporter

JeffJ

Raised By

None

Priority

Minor
Configure