| Previous | Table of Contents | Next |
In human readable textual representations of MOF Models it is sometimes useful to use simpler names for model elements than
used in other representations. Some examples include the elimination of white space, and the shortening of long names. In
addition it may be useful to allow certain shorthands given above by removing name clashes that may arise when placing previously
separated names into the same namespace. For example, a MOF model may have the same name for an enumeration label as for a
boolean attribute name. In this case it would be impossible to use both an attribute with the enumeration as a type and the
boolean attribute as adjectives for the same class configuration. However, by renaming either the enumeration label or the
boolean attribute name, the clash can be avoided.
A renaming configuration allows any MOF Model Element whose name has a rendering in HUTN (Package, Class, Attribute, Reference,
Association, Association End, Enumeration label) to be assigned a new name for the purposes of configuring an HUTN representation
of the model. This is done using an instance of the
RenameConfig metaclass (see 5.1.10, “RenameConfig?).