For a target UML metamodel that handles templates, an Alf classifier template parameter maps to a UML classifier template parameter with an owned parametered element. If the Alf classifier template parameter has a generalization, then that maps to a constraining classifier of the UML classifier parameter. In that case, the parametered element must be of the same kind as the constraining classifier (e.g., the parametered element must be a class if the constraining classifier is a class, etc.).
However, currently the generated parametered element is always a data type (which is the default in the case of no constraining classifier). Since the parametered element is also mapped as specializing the constraining classifier, the resulting model is thus invalid if the constraining classifier is anything but a data type.
seidewitz
commented
7 years ago
For a target UML metamodel that handles templates, an Alf classifier template parameter maps to a UML classifier template parameter with an owned parametered element. If the Alf classifier template parameter has a generalization, then that maps to a constraining classifier of the UML classifier parameter. In that case, the parametered element must be of the same kind as the constraining classifier (e.g., the parametered element must be a class if the constraining classifier is a class, etc.).
However, currently the generated parametered element is always a data type (which is the default in the case of no constraining classifier). Since the parametered element is also mapped as specializing the constraining classifier, the resulting model is thus invalid if the constraining classifier is anything but a data type.