buildingSMART / buildingSMART/IFC4.x-development
Proposal - mechanism to add semantics to unrooted classes
- Dominant language
- Python
- Stars
- 234
- Forks
- 123
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 5
Description
Very often we reuse data (especially geometries) in a model where it is unclear if this is for semantic reason (the elements should be in sync) or for storage efficiency.
The IfcReference - if changed into a rooted class - could provide a way to add this additional semantic dimension to unrooted elements.
Also, its usage should be extended to not only be used in metrics and applied values.
The problem might be that it would make it more difficult to enforce the correct class for attributes, though this is also the case in the current implementation.
With such a mechanism we could reuse local placements (named user coordinate systems), points (shared between an element and a dimensioning), etc. more effectively.
Contributor guide
Research direction
Start by reviewing the current IfcReference concept and how it is used in metrics and applied values. Define whether changing it to a rooted class can express semantic reuse for unrooted elements such as local placements and points, while considering attribute class enforcement. Done means the proposal resolves the intended scope and its constraints clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100