Added IFC4 schema

[rubendel]

Since the point of this test case (presumably) is to verify that the implementation detects that there are no IFCWALL in the IFC whilst the specification is REQUIRED, I think the spec should have the IFC4 ifcVersion otherwise it will already fail on that.

[berlotti]

thank you!

[Moult]

I don't think this is right, I asked whether or not the ifcVersion should affect the pass/fail state, and the answer I was given was that it shouldn't, the ifcVersion is pure metadata. https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases-ids.md#pass-specification-version-is-purely-metadata-and-does-not-impact-pass-or-fail-result

[rubendel]

Hmm last time I was in a discussion about this that wasn't the case, but I have missed quite a few of the meeting lately.
A few reasons for making the IFC schema more significant:

• Pre-check validation of IDS specs, for example non existing attributes, inverses, derived attributes, all of those require knowledge of the applicable schema(s).
• When we added this to Specification (it was first in the Header) the idea was that you can have one IDS, that works for 2 different schemas, by having 2 specifications; one for schema X and one for schema Y. Logically they would check the same thing, but depending on the IFC schema, only one would be executed each time.

[Moult]

Maybe file a new issue so it can be discussed again?

[rubendel]

Yes good idea

[rubendel]

#103