UML25 — Clarification on the semantics of Multiplicities

Title: Clarification on the semantics of Multiplicities
Where: section 7.5.3
Nature of Issue: Clarification
Severity of Issue: Minor
Full Description of the Issue:
Multiplicitie: both ValueSpecification should be of the same type and of a type which has a total ordering defined on it and upper should be superior to lower.

Actually, given the definitions of the operations lowerBound and upperBound, lowerValue should have type
Integer and upperValue should have type UnlimitedNatural. More precisely, if lowerValue is not null, then
lowerValue.integerValue() should not be null, and if upperValue is not null, then upperValue.unlimitedNaturalValue()
should not be null. (There is already a constraint that upperBound() >= lowerBound()).