Andreas Geiger
Andreas Geiger
Current version: ENTITY IfcVertex SUPERTYPE OF (ONEOF (IfcVertexPoint)) SUBTYPE OF (IfcTopologicalRepresentationItem); END_ENTITY; Solution: ENTITY IfcVertex ABSTRACT SUPERTYPE OF (ONEOF (IfcVertexPoint)) SUBTYPE OF (IfcTopologicalRepresentationItem); END_ENTITY;
ifcXML configuration file missing in all IFC versions starting with 4.0.2.1. In the older versions the link is available but broken.
As I understand it, 2 type B segments are missing from the illustration in the specification. Compare with the attached sketch. 
The text in the specification for IfcFontWeight and the WhereRule are different. Either 'bold' should be added to the WhereRule or should '600' used for bold, than this has to...
In the IFC file for property and quantity templates are some errors. In all versions of the specification base entity for the templates is IfcProject instead of IfcProjectLibrary. For each...
the links withhin the property set definition xml files to the corresponding xml schema file are invalid. This applies to all specifications from IFC4 onwards. In addition this schema file...
Please add the missing texture file for all specification of IFC4 upwarwards supporting the IfcImageTexture entity. 
The properties VacancyRateInCategoryNow and VacancyRateInCategoryFuture are defined by the data type IfcPositiveRatioMeasure. The values are given in percentage 0%
The coordinate order of the geographic reference position in the example for IfcRigidOperation [E.7.2 - Geographic Referencing Rigid Operation](https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/annex_e/placements-and-gis-referencing/geographic-referencing-rigid-operation.html) is incorrect. Accoring to [EPSG:4258](https://epsg.io/4258) the coordinate order is latitude, longitude....