Issue 6317: UML2 Super/Instances (uml2-superstructure-ftf)
Source: The MathWorks (Mr. Alan Moore, alan.moore(at)mathworks.co.uk)
Nature: Uncategorized Issue
Severity: 
Summary: 03-08-02.pdf


In Figure 120, "l1", which I believe is an InstanceSpecification appears to
be nested inside another (anonymous) InstanceSpecification, ":Car". However,
looking at the metamodel for Instances, one InstanceSpecification cannot own
another. So, in the repository for the diagram in Figure 120, which model
element owns the InstanceSpecification "l1"? This is important because for
example when it comes to delete ":Car" how does the repository know to
delete "l1"?
Resolution: 
Revised Text: 
Actions taken:
October 15, 2003: received issue
March 9, 2005: closed issue
Discussion: 
Just because there is a composition relationship between the ‘real’ instances (in the
runtime system being modeled) does not mean there need be a composition between the
InstanceSpecifications used to model them. The Issue points out a fairly obscure example
with structured classes but the same would apply if instances of 2 classes were shown
with a composition between them. Similarly the fact that some shapes are nested in
others.
Disposition: Closed, no change
End of Annotations:=====
From: "Moore, Alan" <AlanM@artisansw.com> 
To: issues@omg.org 
Subject: UML2 Super/Instances 
Date: Wed, 15 Oct 2003 10:44:18 +0100 
X-Mailer: Internet Mail Service (5.5.2653.19) 


03-08-02.pdf


In Figure 120, "l1", which I believe is an InstanceSpecification appears to
be nested inside another (anonymous) InstanceSpecification, ":Car". However,
looking at the metamodel for Instances, one InstanceSpecification cannot own
another. So, in the repository for the diagram in Figure 120, which model
element owns the InstanceSpecification "l1"? This is important because for
example when it comes to delete ":Car" how does the repository know to
delete "l1"?