Dion Moult

IfcWall IfcWallType These are valid scenarios: 1. IfcWallType.PredefinedType = PARTITIONING, IfcWall.PredefinedType = NULL 2. IfcWallType.PredefinedType = USERDEFINED, IfcWallType.ElementType = FOOBAR, IfcWall.PredefinedType = NULL 3. IfcWallType.PredefinedType = NOTDEFINED, IfcWall.PredefinedType = PARTITIONING...

Isn't this already explained here sufficiently? https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/concepts/Object_Attributes/Object_Predefined_Type/content.html

Running into the same problem with NVIDIA GeForce GTX 1650: ``` nvidia-smi  :) Tue Oct 17 16:00:30 2023 +---------------------------------------------------------------------------------------+ | NVIDIA-SMI 535.113.01 Driver Version: 535.113.01 CUDA Version: 12.2 |...

This is resolved now, right? The solution is that it's now transparent to the user.

To clarify, I believe what should be proposed here to solve is to introduce a concept similar to MappedRepresentation, but instead of happening at a representation + associated type level,...

@mtveerman 1. No, it is not an exporter problem. Building elements can share representation so long as they follow the mapped representation concept, which requires the representation to be mapped...

I write lengthy descriptions. Does that help? ``` IFCBUILDINGSTOREY Name ObjectType Elevation Qto_BuildingStoreyBaseQuantities GrossHeight ``` ... rendered like this: 

> for communication with end users I would rather use the domain language like the German "Feuerwiderstandsklasse". I think we should add this to the recommendation for implementers to simply...

> why do we have description and instruction on specification level, what is the difference between both? My interpretation is that the description describes why the specification exists, why it...

> I thought that is defined in the meta data of our IDS file, i.e. purpose and milestone. No need to repeat for each element. The IDS is a group...