bSI-InfraRoom / bSI-InfraRoom/IFC-Specification
Consistent use of element status property
- Dominant language
- No language data
- Stars
- 27
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Two issues regarding property Status.
1.
Many of the recently added IfcBuiltElement subtypes do not have property Status in their Pset_XxxCommon (in some cases such Pset does not even exist):
IfcBearing
IfcCaissonFoundation
IfcCourse
IfcDeepFoundation
IfcEarthworksElement
IfcEarthworksFill
IfcKerb
IfcMooringDevice
IfcNavigationElement
IfcPavement
IfcRail
IfcReinforcedSoil
IfcTrackElement
IfcBuiltElement, now being non-abstract, also should have Status (as should all instantiable subtypes of IfcElement).
Status (and possibly Reference) should be in Pset_ElementCommon, applicable to all IfcElement subtypes?
2.
PEnum_ElementStatus value OTHER is unclear: how should it be treated differently from UNSET? Following the same logic as in PDT enums, it would be USERDEFINED, and there should be a property (UserDefinedStatus) to capture the value.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.