RLS — Hierarchical relationship for instances of CRS and RoLo Data Spec

• Some applications need to handle unlimited number of CRSs and
  their corresponding structures of RoLo Data Specification.

For example, suppose that a human counting application that can
connect camera systems that are mounted various rooms. Because
the origin of CRS used in each camera system is different from
each other, corresponding RoLo Data Specification is different.
It means that the application need to recognize unbounded number
of RoLo Architectures.

In order to avoid such situations, we can utilize hierarchical
relations among CRSs. In the case of above example, we define a
generic CRS, by which a CRS used in each camera system is
defined a kind of a derived CRS of the generic CRS. In the same
time, the human counting application is designed to accept the
generic CRS and corresponding RoLo architecture. Then, the
application can handle each derived CRS and its corresponding
RoLo architecture.

• In order to realize such functionality, we should introduce the
  following mechanisms to define relations among CRSs and among
  RoLo architectures.

• To define a hierarchical relation between two CRSs, we introduce
  a CRS Hierarchical Relation class. In the class, baseCRS and
  subCRS are specified. The baseCRS is a generic CRS and the
  subSRC is a derived CRS.

Whole relations of CRSs shall form a lattice structure.

• To define a hierarchical relations between two RoLo Data
  Specifications, we introduce a class for RoLo Data
  Specifications, in which baseSpec and subSpec is specified. The
  baseSpec is a generic RoLo Data Specification and subSpec is a
  derived RoLo Data Specification.

Whole relations of RoLo Data Specifications shall form a lattice
structure.

• To define a hierarchical relations between two RoLo Element
  Specifications, we introduce a class for RoLo Element
  Specifications, in which baseSpec and subSpec is specified. The
  baseSpec is a generic RoLo Element Specification and subSpec is
  a derived RoLo Element Specification.

Whole relations of RoLo Element Specifications shall form a lattice
structure.

Instead of introducing a new class to represent hierarchical relationship among
instances, use the don’t-care functionality in the original specification. However,
as there were not enough description in the original specification and also as
there were some errors, do some reorganization to clarify this.