Léon van Berlo
Léon van Berlo
Better to have a painful change now (while the standard is not final yet); than a deepening wound later... Dare to do the right thing!
Awesome suggestion. Exactly what this repository is for. Thank you!
Principle agreement on this. Find solutions case-by-case. PS: keep IfcIndexedPolyCurve, but on two (or three) star conformance level
Could you elaborate on the 'for various reasons'? Maybe we can fix those... We are moving more and more to partial IFC exchange where files are just snapshots at a...
There are many solutions for querying and filtering IFC on request. The technical roadmap (hopefully public soon) identified that we need a new 'Exchange Information Requirements' that can serve for...
This choice is already made. See https://github.com/buildingSMART/NextGen-IFC/wiki/Towards-a-technology-independent-IFC This is the whole reason we are gathering these issues.
WHERE rules only exist in EXPRESS. We need to make IFC language independent. Some kind of restriction could be a solution here, but WHERE rules only apply to the STEP...
Agree the term can be confusing. We tend to use 'early binding definitions for late binding implementation' lately. What do you think of that?
The combination of namespaces is valid XSD; not all tools support it. We will create documentation on how to deal with it.
- change the namespace of xs: to ids: - generate your classes - change the namespace back from ids to xs for the xsd components