Issue 12570: UML2 issue regarding Redefinition (uml2-rtf) Source: International Business Machines (Mr. James Bruck, nobody) Nature: Uncategorized Issue Severity: Summary: For practical reasons, we would like to consider certain properties of redefinable elements to be inheritable (or possibly derived from the redefined element). For example, if one were to redefine a property, then if the type of a redefining property were not explicitly set, it could inherit (or derive) the type from the redefined property. This would save on space in the serialized model and also help keep the model in a consistent state at all times, if for example the type of the redefined property were to change. Currently, there are constraints mentioning that the Type of the redefining property must be 'consistent' with that of the redefined property, any resolution would have to consider modifying such constraints to take redefinition into account. Other properties that could be considered inherited would be do/entry/exit actions of a state and, target of a transition amongst others. I believe this might be a similar argument to issue 12530. Resolution: Revised Text: Actions taken: July 10, 2008: received issue Discussion: End of Annotations:===== c: Maged Elaasar , Anthony Hunter Subject: UML2 issue regarding Redefinition X-Mailer: Lotus Notes Release 7.0 August 18, 2005 From: James Bruck Date: Thu, 10 Jul 2008 14:00:08 -0400 X-MIMETrack: Serialize by Router on D25ML03/25/M/IBM(Release 7.0.3FP1|February 24, 2008) at 07/10/2008 14:00:09, Serialize complete at 07/10/2008 14:00:09 Hi Juergen, Could you please raise the following issue with the UML2 spec. and create an issue number. Thanks, - James. ------------------------------------------------------------ For practical reasons, we would like to consider certain properties of redefinable elements to be inheritable (or possibly derived from the redefined element). For example, if one were to redefine a property, then if the type of a redefining property were not explicitly set, it could inherit (or derive) the type from the redefined property. This would save on space in the serialized model and also help keep the model in a consistent state at all times, if for example the type of the redefined property were to change. Currently, there are constraints mentioning that the Type of the redefining property must be 'consistent' with that of the redefined property, any resolution would have to consider modifying such constraints to take redefinition into account. Other properties that could be considered inherited would be do/entry/exit actions of a state and, target of a transition amongst others. I believe this might be a similar argument to issue 12530. ------------------------------------------------------------