Dion Moult

Pset_MaterialConcrete mentions aggregate and admixture but not binder

1

Aggregates are covered by MaxAggregateSize. Admixture type are covered by AdmixturesDescription (e.g. superplastisizer), and perhaps should also have an AdmixturesAmount (volume measure) to be complete. Notably missing is information about...

There is a note saying it is deprecated in the docs but it doesn't seem officially deprecated in the schema itself.

ModelReference and ModelNumber properties need further distinction in their description

1

The two properties sound very similar to a non-expert. It would be good for @billeast to help provide a sentence distinguishing the two: http://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/Pset_ManufacturerTypeInformation.htm - ModelReference http://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/Pset_ConstructionOccurence.htm - ModelNumber

Does this need to be fixed in the schema? I can help in the docs side.

A note that this is misspelled but I am still reviewing it with @billeast

Clarification required on the inheritance and override behaviour of classification references

3

The object typing and object properties concepts in chapter 4 describe how for things like properties, materials, predefined type, etc are all inherited and overridden with particular rules. What isn't...

How to represent multiple materials in a layer?

3

I'm setting up project libraries and wondering how are multiple materials in a layer represented? E.g. in a wall commonly insulation and framing will occur in the same layer.

Should IfcPlate be a fallback for an ambiguous IFC classification?

3

IfcWall description has this sentence: > An arbitrary planar element to which this semantic information is not applicable (is not predominantly vertical), shall be modeled as [IfcPlate](http://localhost:5000/IFC/RELEASE/IFC4x3/HTML/lexical/IfcPlate.htm). Is this sentence...

IfcComplexProperty is deprecated but IfcPhysicalComplexQuantity isn't - should it be?

2

Proposal: also deprecate IfcPhysicalComplexQuantity. I don't see why it should be treated differently to IfcComplexProperty.

EXPRESS functions use uppercase IFC classes, is this correct?

4

For example on this page: http://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcSurfaceStyle.htm  The IFC class is ALLCAPS (and hyperlinked, which leads to a broken link here). Should it be allcaps? If not, that's something to...