Léon van Berlo

can't you split this into two specifications? Specification 1: * Add all elements of * IfcWall, IfcDoor, IfcWindow, IfcBuildingElementProxy * with a specific "TestPset.TestProp" * with value "Foo". Specification 2:...

maxoccurs can work on the specification:

> @berlotti I tried your approach with two specifications as I understood it from your suggestion with this ids: [gh_exclusion_test_2specs.ids.txt](https://github.com/buildingSMART/IDS/files/12452843/gh_exclusion_test_2specs.ids.txt) but it seems the restriction of spec2 has no effect...

the original reasoning: IFC entities don't need additional documentation for users; since that is always the official IFC documentation. Changed now to make the schema more symmetric.

I don't see this as an option for 1.0. There is a clear use-case defined very early on that projects start with requirements that are further specified over time. Adding...

Strong consensus and agreement

According to the principles and decision tree (https://github.com/buildingSMART/NextGen-IFC/wiki/Ten-principles-for-a-future-IFC) this is agreed. Checked with ISG. Proposal accepted.

Meets the requirements of https://github.com/buildingSMART/NextGen-IFC/wiki/Ten-principles-for-a-future-IFC Decision: call everything IfcPropertySet. No differentiation on quantity sets. Add additional information to the properties/sets about. This is related to the PDT (CEN) discussion to...

@klacol this is also strongly related to the EIR: https://github.com/buildingSMART/EIR/blob/master/examples/project%20and%20site%20properties/project_and_site_EIR.txt

This indeed keeps on coming back. How would we put that in the specification? Bringing in @CBenghi as a potential feature for the IDS diagnostics tool.