The semantics of IfcRelNests as opposed to IfcRelAggregates was obviously changed in IFC4. While in IFC2x3 the difference was whether the parts and the whole of a composition are of the same or different type, in IFC4 the difference is whether the parts have an inherent order or not. I don’t want to debate if a fundamental change of semantics without changing the name of an entity type is appropriate. I just want to point out that the specification lags a bit behind that change: the supertype IfcRelDecomposes still mentions that “Decompositions may be constrained by requiring both, the whole and its parts, to be of the same type - thus establishing a nesting relationship.” This will cause confusion. If there is a different place to post such smaller issues, I will be glad to move this somewhere else.
Hi Helga,
I think reporting here is fine. You could also create an issue on the GitHub against the schema:
Eventually, we’ll sync the bSI GitHub and Forum (Discourse) with an API.