126.96.36.199 Type Element Nesting
Hosted components may be specified on types, following the same rules as defined for corresponding occurrences.
On type objects, hosted components do not have types defined, but serve as placeholders indicating that occurrences of the enclosing type object shall use a duplicate list of hosted components, where the types are defined at each occurrence.
This relationship differs from IfcRelAggregates, which is used to define explicit decomposition of elements at specified placement; this nesting relationship indicates an arbitrary composition of elements, where placement is defined parametrically -- either implicitly (material profile, layer, or constituent association) or explicitly (constraint association).
The order and naming of components may be significant based on parameterized material association. For example, if the IfcElementType has an associated IfcMaterialLayerSet, then layers are constructed according to material associations of each nested IfcElement, and the Name of each IfcMaterialLayer must correspond to the Name of each IfcElement.
The following diagram shows the generic classes and relationships used when applying this concept. In addition, concepts may have particular importance to common or standardised industry practices and scenarios. For these specific usage scenarios, the tables below shows a recommended list of general usage patterns that users may adopt.