BACM — Can other property names in this specification be “modified”?

The issue refers to the metamodel schema for instancing n-ary associations that are represented in the metamodel by an association stereotyped class and a single association named "related". The specification text states that when an instance is created, the legs of the instance instantiate the "related" meta-association but may be assigned distinct (role) names. The UML specification uses a similar device to allow n-ary associations from its MOF metamodel. In BACM, such n-ary associations are typically restricted to instances of a specific meta-class (e.g. AbstractBusinessObject). NOTE: this issue was accidentally combined with BACM-34 and is separated with this issue.

Changing of names is allowed in instancing

When an instance is created of an association, the instance becomes a member of the association type. When instances can be named, there are no restrictions on the names that can be used. When an association instance is created, the link ends become instances of the owned ends and member ends of the association and must satisfy the semantics of those owned ends and member ends with respect to instance types and quantification. These instances are reinterpreted as MOF associations, creating a new MOF model that is consistent with the MOF metamodel.