From 382af5dbe6255d08879d35f23b89e35c948da90f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fernando=20Guss=C3=A3o=20Bellon?= <129398445+fg55b@users.noreply.github.com> Date: Wed, 19 Jun 2024 14:08:59 -0300 Subject: [PATCH] Update IfcBuildingElementProxy.md Added a note advising on the preferred usage of IfcBuiltElement to represent generic built elements. Additionally, the order of the 'HYSTORY' section was changed to maintain a chronological order within changes and notes. --- .../Entities/IfcBuildingElementProxy.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/schemas/shared/IfcSharedBldgElements/Entities/IfcBuildingElementProxy.md b/docs/schemas/shared/IfcSharedBldgElements/Entities/IfcBuildingElementProxy.md index 3f1e134e1..41f779e9a 100644 --- a/docs/schemas/shared/IfcSharedBldgElements/Entities/IfcBuildingElementProxy.md +++ b/docs/schemas/shared/IfcSharedBldgElements/Entities/IfcBuildingElementProxy.md @@ -7,9 +7,12 @@ _IfcBuildingElementProxy_ may be used: * To exchange special types of building elements for which the current specification does not yet provide a semantic definition. * To represent building elements for which the participating applications can not provide a semantic definition. +> HISTORY New entity in IFC2x. + > IFC4.3.0.0 CHANGE _IfcBuildingElementProxy_ should no longer be used as spatial placeholders or provisions. Use _IfcVirtualElement_ instead. -> HISTORY New entity in IFC2x. +> NOTE It is advised not to use _IfcBuildingElementProxy_ to represent an arbitrary built element, but to use a direct instantiation of _IfcBuiltElement_ instead. + ## Attributes