UPR 1.0 FTF Avatar
  1. OMG Issue

UPR — The specification property of a UPRConstraint cannot be a string

  • Key: UPR-4
  • Status: open  
  • Source: Model Driven Solutions ( Ed Seidewitz)
  • Summary:

    In the definition of the UPRConstraint::comparisonOperator in subclause, it is assumed that the name of the comparison operator is given by the string value of the constraint specification property. However, UML requires that a constraint specification evaluates to a Boolean value, not a string (see the well-formedness constraint Constraint::boolean_value, UML 2.5.1,

    An alternative would be to require the constraint specification property to be an opaque expression returning a Boolean value, whose body is the name of the comparison operator. If the language property was also required to be "UPR", then this would indicate that the comparison for the constraint was to be carried out using the semantics as given in the UPR specification.

  • Reported: UPR 1.0b1 — Sat, 9 Feb 2019 00:03 GMT
  • Updated: Tue, 9 Jul 2019 14:20 GMT
  • Attachments: