Issue 9841: EnumerationLiteral should constrain InstanceSpecification (uml2-rtf) Source: Adaptive (Mr. Pete Rivett, pete.rivett(at)adaptive.com) Nature: Uncategorized Issue Severity: Summary: EnumerationLiteral currently inherits from InstanceSpecification. However it does not make sense for it to have all the capabilities of the latter, for example Slots. Therefore a constraint should be added to EnumerationLiteral as follows: slot.isEmpty Furthermore it does not make sense for EnumerationLiteral to have a separate classifier than its Enumeration. So the following redefinition should be added: enumeration {redefines classifier} (alternatively if this is felt too complex there should be a constraint {classifier.isEmpty) Another option would be for EnumerationLiteral to inherit from ValueSpecification - as suggested by the name of the class (other Literal classes are subtypes of ValueSpecification). However this would probably be too major a change to justify the benefit. Resolution: Revised Text: Actions taken: June 27, 2006: received issue Discussion: End of Annotations:===== ubject: Issues on UML Superstructure ptc/06-04-02 Date: Tue, 27 Jun 2006 12:43:49 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Issues on UML Superstructure ptc/06-04-02 Thread-Index: AcaZ/dlF+QD4/39YSAGMBlnmCT7VfQ== From: "Pete Rivett" To: Cc: "Branislav Selic" X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id k5RJTtCv030903 Three separate issues. EnumerationLiteral should constrain InstanceSpecification --------------------------------------------------------- EnumerationLiteral currently inherits from InstanceSpecification. However it does not make sense for it to have all the capabilities of the latter, for example Slots. Therefore a constraint should be added to EnumerationLiteral as follows: slot.isEmpty Furthermore it does not make sense for EnumerationLiteral to have a separate classifier than its Enumeration. So the following redefinition should be added: enumeration {redefines classifier} (alternatively if this is felt too complex there should be a constraint {classifier.isEmpty) Another option would be for EnumerationLiteral to inherit from ValueSpecification - as suggested by the name of the class (other Literal classes are subtypes of ValueSpecification). However this would probably be too major a change to justify the benefit.