Why are IFC details exposed end users?
I've been looking at demos of infrastructure products that support IFC exchanges for bridges. Without pointing fingers at specific vendors, many seem to require end users to know a lot of detail about the IFC specification. The products seem to require the end user to assign IFC classes and attributes to bridge elements. For example, in one product after an extruded shape of a precast concrete I-Beam was created the user had to tell the software the object was a precast concrete I-Beam and assign the IfcBeam class and set the type enum.
This seems error prone and unnecessary. Through the UI, the user could have assigned any class and type resulting in a very poor model.
Why are these IFC details exposed to end users? It seems to me that the fine grain details of IFC should be left to software developers and hidden from the end user. Importing and exporting models that conforms to an MVD should be seamless.