RLS — Inability of representing range values (Figure21/Table120)

The 'choice' attribute of RoLo Attribute Definition class (Table 120) can only represent a list of discrete values. In case of ranged attributes that have minimum and maximum value, it cannot be well expressed.

One possible resolution is to introduce a new class, RoLo Attribute RangeValue, which is derived from RoLo Attribute Value and has 'minValue' and 'maxValue' attributes of type of RoLo Attribute SingleValue.

solution suggested in the summary is sufficient for this issue. But similar
issues may rise if we kept on using the current definition of RoLo Attribute
SingleValue class defined as an enumeration of types which is not extendable by
users. Thus, in order to make the RoLo Attribute structures more extendable and
flexible, we restructure these classes to use type templates. In addition, some
more sentences are added to clarify how RoLo attribute and related structures
are to be used.
Also from issue 14006, there are too many classes of similar functionality.
Especially, usage of RoLo Attribute Definition Set was unclear and distinction
between RoLo Attribute and RoLo Parameter (Set) was not clear. Thus, the
following reorganization of class structure is proposed:

• Remove the RoLo Attribute SingleValue, RoLo Attribute Value, RoLo
  Attribute ValueList, RoLo Attribute Type classes that were used to represent
  variations of type/value pair. InStread, Make RoLo Attribute class to be a
  template class. By this change, RoLo Attribute can be used for any time that
  is required for attributes.
• Separate ‘attribute’ and ‘parameter’ explicitly, and describe their differences.
  Here, attributes are ‘constant’ parameters that users cannot change.
  Parameters are user-changeable attributes. As requested by summary, we
  will prepare several template types for the datatype of parameter. This is for
  convenience, and users can always extend this to any types on demand. Simplify the attribute set/attribute definition set class structures for clarity.
  Some attributes (such as min/maxOccurence in RoLo Attribute Definition) are
  not necessary any more due to the introduction of templates (users can
  always define types with these occurrence limits).