I would consider change log for administration purposes. Like putting up the bill of manhours or gibr management an overvoew. BUT NOT for making the design better or definite.
@Hans_Lammerts You mentioned change log for administration purposes, so let’s accept this which is true.
So, do you think
IfcOwnerHistory would be better to improve or not?
Also, I mentioned maybe in short term it causes complexity and increases in file size, but in the near future when bSI or some individuals implemented “federated” IFC, it won’t increase file size because you can divide an ifc file to many small but integrated parts. Fore instance, some ifc files that just hold change logs, some hold materials, some hold products, some hold projects, some hold sites, …
So, it seems that all of us agree about improving
IfcOwnerHistory but see it with different views, for instance @sergej wants protect his change logs and share just preferred ones which is good
And I have the same view too, but see a CDE as an “integrated distributed system(s)” which is what we see in new generation of platforms and is one step ahead of ISO 19650