Giuseppe Verduci

I edited the following IFC files: classification/pass-occurrences_override_the_type_classification_per_system_1_3.ifc classification/fail-occurrences_override_the_type_classification_per_system_2_3.ifc classification/pass-occurrences_override_the_type_classification_per_system_3_3.ifc Now there is only one IFCWALL (this IFCWALL is involved in all three test cases) and no other extra entities to...

Test Cases Name restrictions will match any result

2

In the following test cases: https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases-attribute.md#pass-name-restrictions-will-match-any-result-13 https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases-attribute.md#pass-name-restrictions-will-match-any-result-23 https://github.com/buildingSMART/IDS/blob/master/Documentation/testcases-attribute.md#pass-name-restrictions-will-match-any-result-33 according to me "any" should be "all". The restriction filters out many attributes (name and description), and all attributes should respect the...

The IDS 1.0 schema allows multiple entities in the requirements section. An attached example demonstrates this, which I believe is unintended behavior. [entities.zip](https://github.com/user-attachments/files/16749487/entities.zip)