bSI-InfraRoom / bSI-InfraRoom/IFC-Specification
reasons to differentiate between a direct attribute Mountable and the property set Pset_KerbCommon
- Dominant language
- No language data
- Stars
- 27
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
why is the attribute Mountable be directly associated to IfcKerb, and not added to Pset_KerbCommon. Direct attributes to subtypes of IfcProduct are (mostly?) deprecated in IFC4 and it is not advisible to add new ones. It is a better practise to use Psets consistently.
At the same time, the attribute PredefinedType :: IfcKerbTypeEnum is missing. It is part of the IFC modeling style, that all leafnode subtypes of IfcElement do have a predefined type (even if there would only be USERDEFINED; NOTDEFINED as a placehollder for now.
There is a Pset_KerbStone - does it suggest that STONE should be a predefined type of IfcKerb?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.