buildingSMART / buildingSMART/IFC4.x-development
Deprecate IfcSpatialStructureElement CompositionType
- Dominant language
- Python
- Stars
- 234
- Forks
- 123
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 5
Description
Originally brought up by @jmirtsch here: https://forums.buildingsmart.org/t/spatial-composition-restraints/1129
@TLiebich has given his support to removing this arbitrary restriction in the forum thread.
The CompositionType attribute creates an arbitrary "three levels" of possible nesting, with no where rule enforcing it, and remains largely to legacy reasons from what I can read in the thread.
It was also mentioned here: https://github.com/buildingSMART/NextGen-IFC/issues/35
So - I propose we finally deprecate this attribute? Grep the docs for "Composition" and strip out those sentences?
Contributor guide
Research direction
Start by grepping the repository for "Composition" and reviewing the linked forum discussion and NextGen-IFC issue for the intended scope. Done means the relevant IFC4.x documentation consistently reflects deprecation or removal of the IfcSpatialStructureElement CompositionType restriction, with no outdated references remaining.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100