Sometimes the representation based in the metamodel is too complex, and some simplifications can be
taken. As an example, when representing multiplicities, the UML MM has a very complex way to do that.
However a compact string representation for multiplicities already exists and is widely used. The HUTN
should allow the users to use the special textual representations when available.
For instance: the string datavalue "1..5" culd be used instaed of
... Multiplicity {range: MultiplicityRange {lower="1";upper="5";}}
Suggestion for resolution: Enhance the configuration Metamodel with a ElementSubstitutionConfig
metaclass declaring the replacement and the string convention to be used
(attributes 'the_element : ModelElementRef' and 'replacementSpec : String')
The 'replacementSpec' may reference an OCL function defined at some place

When referencing an instance (ClassInstanceRef), the user needs to look at the metamodel in order
to know if it is a contained reference or a non contained reference (BNF rules 22 and 23).
Suggestion 1 for resolution: Use a "forward" prefix keyword when referencing contained instances that
are fully represented in another place (that are not inlined).
Suggestion 2 for resolution : Use a "ref" keyword when referencing non contained instances and use no
keyword to reference contained instances not inlined.
Note: The resolution of this issue may depend on the resolution of "need to improve readability when
referencing instances"