ArturTomczak

You're correct with the `"RelatedIfcEntityNamesList": [ "IfcBeamLINTEL" ]` example. You can't use USERDEFINED because that is not a defined class in IFC dictionary. I know there is a dichotomy between...

The 'Identifier' should be the place for that. Why do you find it 'not strictly machine readable' and how we could improve that in 1.1?

I see your point now. The identifier is often used as you suggest ('01.02' etc), and it doesn't say what format should be followed. I disagree that it should be...

https://github.com/buildingSMART/IDS/pull/369 resolves it

You're right, indeed it's the same issue, but let's keep this one given the IFCxIDS samples provided and try to resolve here. I see you also addressed it in #206....

Apologies, my bad; missed the two tests while implementing tolerance tests at the last minute.

They are not linked. What's more, we're most probably getting rid of those property set classes in the next update of the IFC dictionary to avoid those complexities.

The first official version of the standard is "1.0" (https://standards.buildingsmart.org/IDS/1.0/ids.xsd). Technically and in the schema it's [v1.0.0](https://github.com/buildingSMART/IDS/releases/tag/v1.0.0) (version="1.0.0"). All previous versions, like 0.9.7, were premature and changed with time, and...

I thought we agreed on this during the last phase - the ifcVersion should be a requirement, not just metadata. So if IDS says ifcVersion="IFC4.0", the IFC file in version...

I was there too, when working on the early version of IfcTester... Some of the assumptions of IDS were to be as much as possible explicit, schema-agnostic, computationally simple, and...