Léon van Berlo

1. Yes. The purpuse is to add x,y,z, coordinates of the IFC origen and the angle (original bimserver features for projects since 0.8 I believe) 2. The wizard is adding...

Principle solution: #123=IFCPRODUCT (... $345, ...) just one thing of certain type #345=IFCTYPEPRODUCT (......, , , IFCDOOR/DOUBLESWING, ...) Decision: cutting point at IfcElement ór IfcProduct, depending on the implications. Consensus...

Decision: cutting point at IfcElement ór IfcProduct, depending on the implications. Consensus that IfcProduct is the best, but only when implications can be handled in a reasonable way. Thank you...

Meets the requirements of https://github.com/buildingSMART/NextGen-IFC/wiki/Ten-principles-for-a-future-IFC

Good topic! The objectified relations are introduced as a solution to make it easy to add relations between objects, without having to change the objects. This is a solution to...

now using IFC defined types, still with fixed values. We might need to make a list of what xs base types map to what ifc defined types (with fixed units)....

Reconsider SELECTs that are currently in the schema, and try to avoid them in the schema. Use Interfaces in other languages (like UML), but only in a way that the...

changed documentation to "Author of the IDS can provide an identifier to the specification. This is intended to be a machine readable identifier. Beware: because of the possibility to combine...

That was indeed the reason for the decision.

The current XSD pattern is not supporting this. There is a plan to migrate to a more advanced regex dialect, but that is on the roadmap for 1.x or 2.x