ABSTRACT This definition may not be instantiated
The decomposition relationship, IfcRelDecomposes, defines the general concept of elements being composed or decomposed. The decomposition relationship denotes a whole/part hierarchy with the ability to navigate from the whole (the composition) to the parts and vice versa.
Decompositions may be constrained by requiring both, the whole and its parts, to be of the same type - thus establishing a nesting relationship. Or they may require some form of physical containment, thus establishing special types of aggregation relationships.
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 decomposition relationship can be applied in a recursive manner, i.e. a decomposed element can be part in another decomposition. Cyclic references have to be prevented at application level.
Assignment of a globally unique identifier within the entire software world.
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,
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.
Optional description, provided for exchanging informative comments.
Ownership, history, and merge state is captured using IfcOwnerHistory.
IfcRoot assigns the globally unique ID. In addition it may provide for a name and a description about the concept.
|Click to show 2 hidden inherited concepts Click to hide 2 inherited concepts
ABSTRACT SUPERTYPE OF (ONEOF
SUBTYPE OF (IfcRelationship);