search

buildingSMART / IFC4.4.x-development

Development of IFC 4.4
Other
8 stars 6 forks source link

Tracking the big issues #11

Open Moult opened 3 years ago

Moult commented 3 years ago

This is a tracking issue only, not intended to propose any solutions, but merely to keep a record of big ideological discussions that need time and further discussion to be resolved into smaller, more implementable proposals. I will keep this updated as more turn up.

  1. Should individual IfcPropertySets or IFC properties get a GUID
  2. Should finer grained classes and psets be introduced for parts of doors, windows, etc
  3. Can IFC serialisations be referenced and instanced
  4. Landscape IFC needs a project in itself
  5. Should documents have a GlobalId
  6. The documentation should clarify usecases for rooted relationships
  7. Should relationships be merged and have GlobalId tracking optional
  8. There are potentially missing unit types
  9. How are design options supported
  10. Should there be psets for IT system security
  11. Material categories should be reviewed with a dedicated team as well as relevant psets identified
  12. Qto quantity names are inconsistent in their naming of widths, height, length, depth, and thickness
  13. Should there be an IfcColourLegend of sorts to show preset colours that represent property values as opposed to appearance
  14. How should high polygon proxy objects be referenced
  15. A full alignment with X3D and potentially new glTF PBR textures is required. Currently IFC only has partial support
  16. Should IFC ship computer parsable descriptions to aid vendors in providing documentation for users
  17. There are too many ways to specify colours in IFC. Can they be simplified?
  18. Should IFC store details about mappings to aid standardised migration between versions?
  19. Potentially a bunch of work to be done to support soil properties
  20. Proposal for an "extends to" roof / wall relationship
  21. Proposal to merge the semantics of openings with CSG operations in the representation tree
  22. Proposal to define more situations of IfcConstraint (or another mechanism) on creating parametric geometry in IFC
  23. Proposal for IfcMaterial to be rooted
  24. A bunch of proposed upgrades to IfcRelSpaceBoundary
  25. Proposal for a 3D lattice grid object, potentially for modular design