IFC Backwards compatibility

[ReD_CoDE]

I don’t know about current topics inside the MSG & ISG, and wasn’t in last summit, but I think IFC at the moment has two vital issues:

1. One is related to its structure which one of the main issues is “backwards compatibility”
2. The second is about the data/information exchange, which fortunately @Moult shared the part of the issue in his insights

The non-permanent GUIDs

+1 on @jonm’s suggestion, assuming there isn’t a usefulness of having UUIDs for things like PSets? For instance, let’s say in an ideal future we can reference one IFC file from another. The architect models a room. He references a IFC files from a sustainability consultant. The sustainability consultant is only responsible for adding relationships and psets, and so therefore ideally his IFC file only contains those relationship and pset definitions. Or maybe the QS has an IFC file that only con…

But this is just a small part of the whole picture

I think the MSG & ISG teams should focus on two areas, one is related to IFC and one to IfcDoc
I will share my insights in the near future, after submitting articles in Automation in Construction journal