Issue 13257: ParameterableElement as a formal template parameter (uml2-rtf)
Source: International Business Machines (Mr. James Bruck, nobody)
Nature: Revision
Severity: Significant
Summary: Say we want to expose a  ParameterableElement as a formal template parameter.   
If we want to create the following    List<E>,   then the template parameter would refer to some parameterable element E whose type we would have to choose (say uml:Class).   
Now, say we wanted to create  List< Interface >,  or List < Class >,  or List < DataType >.    I don't think we would be able to then create TemplateParameterSubstitution for all these elements since the type of formal and actual parameters are inconsistent. 

The problem is that we must pick a concrete type for that ParameterableElement - we can't for example use Classifier as the template parameter because it's abstract.

Resolution: 
Revised Text: 
Actions taken:
January 14, 2009: received issue
Discussion: 

End of Annotations:=====
ubject: Issue with UML2 spec
X-Mailer: Lotus Notes Release 7.0 August 18, 2005
From: James Bruck <jbruck@ca.ibm.com>
Date: Wed, 14 Jan 2009 15:05:28 -0500
X-MIMETrack: Serialize by Router on D25ML03/25/M/IBM(Release 7.0.3FP1|February 24, 2008) at
 01/14/2009 15:05:32,
        Serialize complete at 01/14/2009 15:05:32



Hi Juergen, 

I would like to raise the following issue with the UML2 spec. 


Name:James Bruck 
Company: IBM 
mailFrom: jbruck@ca.ibm.com 
Notification: Yes 
Specification: OMG Unified Modeling Language (OMG UML), Superstructure 
Section: 17.5 
FormalNumber: ptc/2008-05-05 
Version: Version 2.2, Beta 1 
RevisionDate: 05/01/08 
Page: 619 
Nature: Issue 
Severity: Major


Say we want to expose a  ParameterableElement as a formal template parameter.   
If we want to create the following    List<E>,   then the template parameter would refer to some parameterable element E whose type we would have to choose (say uml:Class).   
Now, say we wanted to create  List< Interface >,  or List < Class >,  or List < DataType >.    I don't think we would be able to then create TemplateParameterSubstitution for all these elements since the type of formal and actual parameters are inconsistent. 

The problem is that we must pick a concrete type for that ParameterableElement - we can't for example use Classifier as the template parameter because it's abstract.