buildingSMART / buildingSMART/bSDD
How to specify the relationship between a class and a pset being modelled as class with type "GroupOfProperties"?
- Dominant language
- Python
- Stars
- 193
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
Psets from IFC4.3 are represented as class with class type "GroupOfProperties" (see for instance Pset_ActorCommon with URI [ https://identifier.buildingsmart.org/uri/buildingsmart/ifc/4.3/class/Pset_ActorCommon](https://identifier.buildingsmart.org/uri/buildingsmart/ifc/4.3/class/Pset_ActorCommon)).
The applicable class of Pset_ActorCommon is [IfcActor](https://identifier.buildingsmart.org/uri/buildingsmart/ifc/4.3/class/IfcActor), but how are both linked together?
I was wondering if a ClassRelationship shall be used, but can not find a proper relation type.
However, it seems (at least based on available URIs) that the Pset_ActorCommon might be modelled as a property as well (see: [ https://identifier.buildingsmart.org/uri/buildingsmart/ifc/4.3/class/Pset_ActorCommon/prop/Pset_ActorCommon](https://identifier.buildingsmart.org/uri/buildingsmart/ifc/4.3/class/Pset_ActorCommon/prop/Pset_ActorCommon)).
If not, why do we have different URIs?
But still, I cannot see a way how both are linked together (except using the Pset text field in ClassProperties, which seems to be a rather weak name-based relationship without any further obvious logic). Another option according to the specification (in particular double-checking with ISO 23386) might be the ParentClassCode text field in Class, which however does not seem to be populated in the IFC4.3 dictionary.
If there is a link/relationship between both, can you kindly provide an example how such structures should be properly represented in the bSDD JSON file?
Furthermore, if a relationship between the classes IfcActor and Pset_ActorCommon exist, and if Pset_ActorCommon identifies all Properties via ClassProperty definition already, do I have to repeat the definition of ClassProperties in IfcActor as well?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.