buildingSMART / buildingSMART/IFC4.x-development
Proposal to move Status property up in the hierarchy
- Dominant language
- Python
- Stars
- 234
- Forks
- 123
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 5
Description
Status is how you determine which "phase" (DEMOLISH, EXISTING, NEW, NOTKNOWN, OTHER, TEMPORARY, UNSET) a project is in. However right now it belongs to things like Pset_WallCommon. This makes it very troublesome to do a very common usecase which is to filter by phase: you'd have to filter Pset_WallCommon.Status, Pset_SlabCommon.Status, Pset_DoorCommon.Status, etc.
Proposal: should this pset move up to the IfcProduct level? Or IfcObject?
Contributor guide
Research direction
Review the current Status property placement on Pset_WallCommon, Pset_SlabCommon, and Pset_DoorCommon, then trace how those property sets relate to IfcProduct and IfcObject. Done means reaching a decision on the appropriate hierarchy level and documenting the resulting specification change.
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