IfcRelConnectsPortToElement used to be used to connect an IfcPort to an IfcDistributionElement. Then the documentation changed and said to use IfcRelNests instead ... except when the port is dynamically connected (my interpretation of dynamic is wireless, perhaps?).
Based on this forum thread, Thomas Liebich considers it "essentially deprecated", so I propose to officially deprecate it, and if there is a need to distinguish fixed vs dynamic ports, move that into a Pset.
If this is agreed, I can make a list of all the places to fix it in the documentation.
Description of the proposal:
IfcRelConnectsPortToElementused to be used to connect anIfcPortto anIfcDistributionElement. Then the documentation changed and said to useIfcRelNestsinstead ... except when the port is dynamically connected (my interpretation of dynamic is wireless, perhaps?).Based on this forum thread, Thomas Liebich considers it "essentially deprecated", so I propose to officially deprecate it, and if there is a need to distinguish fixed vs dynamic ports, move that into a Pset.
If this is agreed, I can make a list of all the places to fix it in the documentation.
Describe how it contributes to the objectives set in https://github.com/buildingSMART/NextGen-IFC/wiki/Towards-a-technology-independent-IFC:
What do we win:
What do we loose <-- can we fix this typo?
Schema impact:
Instance model impact:
Backwards compatible:
Automatic migration possible:
Additional implications:
- Note that not all points need to be satisfied! Backwards compatibility and file size are not concerns.