Improve layering of info standards

Combining layers of class library seems too difficult – e.g. instituting corporate layers down to project.

1. There is a limit of inheritance of 1 level when using composition, so while you can set up
   CLIB1
   CLIB2
   CLIB3

To include things from CLIB1 in CLIB3 in this scenario, you need to include CLIB1 in
CLIB3. In existing scenarios, we have looked at there are several class libraries at the
bottom level, so all the bottom level class library fragments need to be included in both
2 and 3, which is a bit of a management nightmare since none of this is considered an
error.

1. With the idea of corporate class libs, we find you may have classes, attributes,
   enumerations with more items than you want in a project. The only way of removing
   things in a composition/inheritance scenario is by making things obsolete.
   This might not really be the correct concept here, but even if we use it, there is no
   visible indication in the UI as to this so using the CLIB with lots of obsolete items is
   sufficiently difficult that it encourages not using composition and instead setting things
   up individually and deleting unwanted items.