Open tpaviot opened 4 years ago
This is indeed the aim, good observation. For full compatibility with EXPRESS we currently rely on some extensions to get consistent attribute ordering for example, but indeed the aim is to eliminate those.
With regard to retaining EXPRESS attribute order in UML I don't see a need for an extension. If an association end is owned by the associated class, then the properties corresponding to association ends do have order in their owning class. Is there a reason why the IFC4 UML does not use class ownership of respective association ends?
I have a radically stripped down version of the XMI in IFC4.3.x-development if there is any interest. I believe it would also be possible to remove a good deal of EA markup while retaining extension data.
The current xmi schema seems to be generated using Enterprise Architect, and includes many EA specific markups. The xmi file should contain the model definition only, and drop everything else. This will result in a smaller file size, and a software independent model.