MatthiasWeise

Regarding the scope of the Structural Analysis Domain: Better use this definition: https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/ifcstructuralanalysisdomain/content.html Regarding point to point connection: If those points are at different locations I would expect to connect...

It should be fine to represent the foundation as a point connection only. It is on purpose that there is no point member, because a zero dimensional structural element does...

> Furthermore, I wonder if there is a way to describe a solid element (used in the structural analysis model) using Ifc structural entities. No, that is currently out of...

Thanks for fast feedback!

Yes, a warning would be good to avoid misspelling of predefinedType. Actually, I wanted to check if USERDEFINED is allowed or not. I would argue that we should allow USERDEFINED,...

I was more thinking that we need both, USERDEFINED to be unspecific about what user defined type should be selected and to use any other value not being in the...

What was the reason for making datatype mandatory? I agree that ignoring a statement for PROHIBITED is not a good idea, but adding a reserved keyword ANY would lead to...

> If I recall the discussion correctly it was something along the lines of: we know this might be a struggle for some, but in the long term is going...

> That's indeed the question. Previously the idea has been that an IDS implementation should be as light weight as possible. E.g no inheritance, because it needs schema knowledge. You...

> Why do we say the use case is not valid? The problem with PROHIBITED and PSET/PNAME/DATATYPE/VALUE is, that you most likely do not want to negate the datatype. The...