search

buildingSMART / IFC4.4.x-development

Development of IFC 4.4
Other
8 stars 6 forks source link

Proposal to move Status property up in the hierarchy #2

Open Moult opened 2 years ago

Moult commented 2 years ago

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?

aothms commented 2 years ago

I think I brought up a similar point somewhere. It's a bit of a difficult situation where there are on the one hand a lot of specific leaf property sets (maybe the earliest ones) in combination with some "interface-like" more generally applicable ones (newer?).

My 2cts. I think it's too late in the game now to try and do this. If we do it for status we should do it for others too and that kind of reshuffling we should save for IFC5 where the "property inheritance" mechanism will be a bit better thought out.

Moult commented 2 years ago

Agree that this is a rather general problem, and perhaps best put on hold because it's quite a big gnarly task to review all the leaf properties.