-
Key: UML25-667
-
Legacy Issue Number: 17507
-
Status: closed
-
Source: Dassault Systemes ( Mr. Tomas Juknevicius)
-
Summary:
I've encountered one slight problem in the superstructure XMI file of UML2.4.1 .
I've grabbed the ptc/2010-11-18 revision of Superstructure.xmi from here:
http://www.omg.org/spec/UML/2.4.1/On examining I see that all enumeration literals contain classifier="..." field serialized; e.g.:
> <ownedLiteral xmi:type="uml:EnumerationLiteral"
> xmi:id="Activities-CompleteActivities-ObjectNodeOrderingKind-unordered" name="unordered"
> classifier="Activities-CompleteActivities-ObjectNodeOrderingKind">
There are ~62 such places in Superstructure.xmi (I've not looked into Infrastructure.xmi, but I
think there will also be cases like this)Classifier metaproperty of EnumerationLiteral metaclass is derived in UML2.4.1 - per Figure 7.13 and
chapter 7.3.17
(EnumerationLiteral::classifier redefines the original InstanceSpecification::classifier, which is
not derived).Since derived fields are not usually serialized by XMI production rules (unless this is overridden,
which seems not to be the case),
I think these fields should be cleaned out. -
Reported: UML 2.4.1 — Thu, 19 Jul 2012 04:00 GMT
-
Disposition: Resolved — UML 2.5
-
Disposition Summary:
This issue has already been resolved by, or no longer applies to, the UML 2.5 Beta 1 specification.
Disposition: Closed - No Change -
Updated: Fri, 6 Mar 2015 20:59 GMT
UML25 — Surplus classifier field serialized in Superstructure.xmi
- Key: UML25-667
- OMG Task Force: Unified Modeling Language 2.5 (UML) FTF