The nesting relationship IfcRelNests is a special type of the general composition/decomposition (or whole/part) relationship IfcRelDecomposes. The nesting relationship can be applied to all non physical subtypes of object and object types, namely processes, controls (like cost items), and resources. It can also be applied to physical subtypes of object and object types, namely elements having ports. The nesting implies an order among the nested parts.
EXAMPLE A nesting of costs items in an IfcCostSchedule is the composition of complex cost items from other cost items. The order of the nested cost items underneath the parent cost item is determined by the order of the list of RelatedObjects.
EXAMPLE A nesting of IfcTask's within a work schedule is the composition of a parent work task from more specific sub work tasks. The order of the sub tasks underneath the parent task is determined by the order of the list of RelatedObjects.
Decompositions imply a dependency, i.e. the definition of the whole depends on the definition of the parts and the parts depend on the existence of the whole. The behaviour that is implied from the dependency has to be established inside the applications.
HISTORY New entity in IFC2.0
IFC4 CHANGE The attributes RelatingObject and RelatedObjects are demoted from the supertype IfcRelDecomposes, and RelatedObjects is refined to be a list. The use of IfcRelNests is repurposed to be a nesting of an ordered collections of parts.
|1||GlobalId||IfcGloballyUniqueId||Assignment of a globally unique identifier within the entire software world.|
|2||OwnerHistory||OPTIONAL IfcOwnerHistory||Assignment of the information about the current ownership of that object, including owning actor, application, local identification and information captured about the recent changes of the object, |
> NOTE only the last modification in stored - either as addition, deletion or modification.
> IFC4 CHANGE The attribute has been changed to be OPTIONAL.
|3||Name||OPTIONAL IfcLabel||Optional name for use by the participating software systems or users. For some subtypes of IfcRoot the insertion of the Name attribute may be required. This would be enforced by a where rule.|
|4||Description||OPTIONAL IfcText||Optional description, provided for exchanging informative comments.|
|5||RelatingObject||IfcObjectDefinition||The object definition, either an non-product object type or a non-product object occurrence, that represents the nest. It is the whole within the whole/part relationship.|
> IFC4 CHANGE The attribute has been demoted from the supertype IfcRelDecomposes and defines the ordered nesting relationship.
|6||RelatedObjects||LIST [1:?] OF IfcObjectDefinition||The object definitions, either non-product object occurrences or non-product object types, that are being nestes. They are defined as the parts in the ordered whole/part relationship - i.e. there is an implied order among the parts expressed by the position within the list of RelatedObjects.|
> IFC4 CHANGE The attribute has been demoted from the supertype IfcRelDecomposes and defines the ordered set of parts within the nest.
IfcRoot assigns the globally unique ID. In addition it may provide for a name and a description about the concept.
Ownership, history, and merge state is captured using IfcOwnerHistory.
ENTITY IfcRelNests SUBTYPE OF (IfcRelDecomposes); RelatingObject : IfcObjectDefinition; RelatedObjects : LIST [1:?] OF IfcObjectDefinition; WHERE NoSelfReference : SIZEOF(QUERY(Temp <* RelatedObjects | RelatingObject :=: Temp)) = 0; END_ENTITY;