IfcTester not properly check PredefinedType requirements
My colleagues and I are being challenged with limiting PredefinedTypes in a model. The small example I have to illustrate is attached along with the IDS. We want to, in this example case, limit all IfcBeam entities to have PredefinedType to be either BEAM or PILECAP. BEAM is an official predefined type and PILECAP is user defined.
For the attached file, I expect four IfcBeam entities to pass because their predefined type is BEAM or PILECAP, either directly on the IfcBeam entity, or inherited through an IfcBeamType entity. Two IfcBeam entities are expected to fail because their types are JOIST and GRADEBEAM.
Only the single entity with IfcBeam.PredefinedType=BEAM is passing.
Is this a bug in IfcTester? Is this a misunderstanding on our part on how IDS is supposed to work?
Comments
@Moult any ideas as to why IfcTester (and other IDS checkers) can identify entities from a predefined type enumeration for applicability but not requirements?
By sheer luck, I got this to work. The key was to have IfcBeam be the requirement and IfcBeam with predefined type enumeration {BEAM;PILECAP}.
I don't know why this works instead my original attempt, so if someone has an explanation, please share.