Dion Moult

Also related to this is that a number of elements do not have a correlating status pset. Important ones like IfcSpace, IfcVirtualElement, IfcGeographicElement: https://community.osarch.org/discussion/1485/how-do-you-phase-certain-ifcclasses#latest

> all these material sets, compound profiles, etc. are basically just workarounds Completely agree for later stage BIM models. For early stage BIM models however I think the material sets...

@aothms at a guess maybe it was coded alongside the "CorrectPredefinedType" rule so just an oversight? I don't see any reason for the two to be correlated.

Yes, if supported, the same criteria as attributes would apply. I also am not a fan of supporting these, but apparently there is a usecase for them.

Here's another proposal: what if the number was rounded to the same number of decimal places as what the IDS author specifies? E.g. if the author asks for a length...

Cheers. Ping @LeeGregory12d I saw this bug in 12D but I wasn't sure who to contact.

BTW in IfcOpenShell we've invented a facet syntax inspired by IDS that you can use in custom scripts in the meantime. It looks something like this: ``` IfcElement, PsetA.Material=wood +...

This is correct. However from the perspective of IDS, it "auto-fetches" the ObjectType if PredefinedType = USERDEFINED.

It's a bit unfortunate to write this because this is such an important part of IFC. The only reason we have "USERDEFINED" is because that's what STEP / EXPRESS forces...

Psets can also be assigned to tasks, resources, material layers / material profiles, or material layer sets / profile sets ... etc. We currently support all of these. I see...