Hello, Zoltan
Thanks for the feedback.
In my opinion, following the Column example, we should be able to export any element segment or part also as an IfcElementAssembly.XXXXXXX (Adding the corresponding enumeration value and populating the Object Type attribute accordingly.
(see also @sergej 's comment on this thread → openings in IfcSpatialElement - #6 by sergej )
What I also would like to have natively is a similar feature to the one we use when exporting containers (such as IfcStair, IfcCurtainWall, etc…). We can choose whether we want to keep the subclasses hierarchy or not. Imagine that “Column”, you can export (map) it as a simple IfcColumn for one particular exchange scenario and as different IfcElementAssemblyType instances for other more granular scenarios (such as an OFF site fabrication).
As architects dealing with Off-site based and modular design methods, there is a need for such a way of modelling and IFC-based delivery.