BACM12 — Translation of owns associations to TTL

The translation of MOF XMI to TTL incorrectly assigns ownership of the owns_4 association to ValueCharacteristic as ValueCharacteristic.owns_4. The translation program uses a heuristic - if an association is sourced at a class that is a subclass of BACMRelation, it is treated as a leg of that class and given a name that is <class_name>.<association_name>. Associations named "owns", "aggregates" or "generalizes" should be excluded from this heuristic as they have fixed semantics (composition, aggregation, specialization) that are not conditioned by the relationship class semantics. Thus has appeared in the TTL as "ValueCharacteristic.owns_4", which should be named "owns_4".
This change does not affect the specification document, the EA model or the MOF XMI.

Add a test in make_qname to correct this

Add test to make_qname to not prefix the source class name to an association of the name of the unstereotyped association contains 'owns'. The owns_4 association is a unique case because the association is represented in the UML as an association stereotyped class, and the source qualification rules would apply, except that owns is a special association used in the UML to indicate that the existence of the target is dependent on the existence of the source.