buildingSMART / buildingSMART/IFC4.x-development
Ordering of formally (derived?) attributes could use improvement
Open
allocated
allocated-core
ifc-update-out
- Dominant language
- Python
- Stars
- 234
- Forks
- 123
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 5
Description
I recently found that IfcGeometricRepresentationSubContext pages were erroring out. After fixing that (I hope my fix is OK I'm not too familiar with the UML yet) I found the ordering quite unintuitive. I suspect this is coming from the ordering in UML, I assume there is some sort of "explicit" order for express output. However for a user the derived attributes come in a very strange order of 5, 3, 6, 4. Is this something to fix in UML?
Contributor guide
Assessment
This issue has not been assessed yet.