QVT11 — QVTo Standard Library: Some operation's signatures seem to be erroneous.

• • QVTo Standard Library: Some operation's signatures seem to be erroneous. ** - the name in the signature of the operation allSubojectsOfType (8.3.4.7) has a typo. Rename correctly - the returned value in the signature of the operation raisedException (8.3.6.4) should better be Exception. - the asList (8.3.8.5) operation's signature is not correct for the types OrderedSet(T), Sequence(T), Bag(T). They shouldn't have any parameter. P.S: Why is this operation included in section 8.3.8 Operations List. I would recomend the creation of new sections for each collection type, instead. - OCLStdlib already defines toLower and toUpper operations. Since these operations may be considered as side-effects operations. I should clarify one of the possible situations: 1. toLower and toUpper are not intended to be side-effect operations. Remove them from the section. 2. toLower and toUpper are always intended to be side-effect operations, so that OCL Operations are discarded. This must be clarified. 3. both (side-effect and free side-effect) operations, are available in QVTtransformations. In this case I would change the name of QVTo std lib operations to distinguish. - In section (8.3.9) lastToUpper must be renamed as lastToLower. P.S: Why all the QVTo Std Lib operations have a subsection number, excepting String's operations?

allSubojectsOfType – see Issue 13989 resolution.
raisedException – Yes. But the Status operations are misleadingly under Transformation. Add a
missing section heading.
asList(T) – Yes, supersedes Issue 19146 resolution.
PS – see Issue 19146 resolution.
toLower – Yes. Make it clear that all String operations are immutable. Redirect OCL 2.4 synonyms to
OCL 2.4 deprecating the synonyms. We can also fix some bad typos, Boolean rather than
Integer/Real returns, references to the non-existent Float type and spurious matchXXX arguments.
lastToUpper – this seems to be a major bloat. Either name or description could change. Since the
name exists with an obvious functionality, correct the description.
PS Yes