UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — Section: 17/17.5.7

  • Key: UML22-305
  • Legacy Issue Number: 10802
  • Status: closed  
  • Source: CNAM ( Jean-Frederic Etienne)
  • Summary:

    Missing constraint for template binding in classifier context There seems to be an omitted constraint for template binding in the context of the classifier metaclass on page 667. Indeed, there is no restriction to the kind of template element to which a classifier can be bound. For example, nothing forbids a class to be bound to a data type or association or even an operation defined as template. There is a need for a constraint similar to the one defined on page 57, where it is stated that a classifier can only specialize classifiers of a valid type. Something like, self.templateBinding -> forAll(tb | self.oclIsKindOf(tb.signature.template.oclType)) Note that the variable oclType is not a valid OCL expression, even though it is referenced more than once in the UML Superstructure document (e.g definition of maySpecializeType on page 58). We therefore here assume that the oclType expression returns the associated metatype of the uml element to which it is applied. Thanks in advance for any feedback Jean-Frédéric Etienne

  • Reported: UML 2.1.1 — Mon, 5 Mar 2007 05:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    This is covered in constraint [1] of TemplateParameterSubstitution, section 17.5.5.
    Revised Text:
    Disposition: Closed, no Change

  • Updated: Fri, 6 Mar 2015 20:58 GMT