Legacy Issue Number: 9962
Source: Dassault Systemes ( Nerijus Jankevicius)
Now, when link is not Link and is not Relationship, tool
>> developers must use
>> a lot of hacks for handling this "special kind of instance"
>> as path, to
>> create special algorithms for "relatedElements" calculation,
>> to prevent
>> type changes to regular classifier and for many other situations.
>> Why Link metaclass was removed? Why all subclasses of
>> Instance were removed?
>I don't know. I personally would like to see an explicit Link class in
>the Instances metamodel - see the MOF Core specification (abstract
>semantics chapter - which is purely descriptive and does not add these
>Instance extensions to MOF or UML) for what I have in mind. I would
>support adding this all into UML since it would be a non-disruptive
>(forward compatible) extension.
>> Node instance and Component instance "different handling" and
>> creates a lot problems also, because it is not possible to
>> recognize them in
>> the model (classifier could be unspecified).
Reported: UML 2.5 — Tue, 25 Jul 2006 04:00 GMT
Updated: Sun, 8 May 2016 05:25 GMT