Issue 4726: TaggedValue in TaggedValue (uml2-superstructure-ftf)
Source:  (, )
Nature: Uncategorized Issue
Severity: 
Summary: According to the UML 1.4 metamodel, a ModelElement can contain any number of
taggedValues, of type TaggedValue [UML 1-4, pp. 2-76].

However, because a TaggedValue itself is a ModelElement [UML 1-4, pp. 2-76],
it can itself contain taggedValues.

The question is: is this really intended? And if so: please explain the
semantics of such a construction.

If not, at simple well-formedness rule 

	self.taggedValue = { }

attached to TaggedValue would do the trick.
Resolution: see above, resolved
Revised Text: 
Actions taken:
December 5, 2001: received issue
March 8, 2005: closed issue
Discussion: 
Discussion:
Stereotypes can extend any class of a metamodel. Stereotypes or tagged values
(attributes) can thus be extended themselves by stereotypes. As an example, stereotypes
and tagged values could be marked to express the author of the stereotype. By the Author
(Name, Date).
Add explanations to the current semantics text for Stereotypes :
(current text)
A stereotype is a limited kind of metaclass that cannot be used by itself, but must always
be used in conjunction with one of the metaclasses it extends. Each stereotype may
extend one or more classes through extensions as part of a profile.
Similarly, a class may be extended by one or more stereotypes. An instance of a
stereotype is linked to an instance of an extended metaclass (or stereotype) by virtue of
the extension between their types.
(Add)
Any metaclass from the reference metamodel can be extended with stereotypes. This
includes, in the case of the UML, metaclasses such as “Class”, “State”, “Activity”,
“Transition” but also metaclasses from the profile package such as “Profile” or
“Stereotype”.
End of Annotations:=====
From: Thomas Schaumburg <thomas.schaumburg@hiq.dk>
To: "'issues@omg.org'" <issues@omg.org>
Subject: TaggedValue in TaggedValue
Date: Wed, 5 Dec 2001 15:13:52 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-UIDL: Xd`!!pMOe9:OMe9En_d9

According to the UML 1.4 metamodel, a ModelElement can contain any
number of
taggedValues, of type TaggedValue [UML 1-4, pp. 2-76].

However, because a TaggedValue itself is a ModelElement [UML 1-4,
pp. 2-76],
it can itself contain taggedValues.

The question is: is this really intended? And if so: please explain
the
semantics of such a construction.

If not, at simple well-formedness rule 

   self.taggedValue = { }

attached to TaggedValue would do the trick.

          Brgds
                      Thomas Schaumburg