Thomas Krijnen

@TLiebich I'm fully agreeing on that statement. Do you have an idea on how we can put that into words? For example as a sentence above the "General Usage" table...

I think it's good. The question perhaps is whether it needs a bit more explanation, such as: > The concept diagram above provides a generic mechanism to fulfil such practices...

Wonderful. Is it an idea to just write it in the template.html instead of appending to each and every markdown. Maybe with some intelligence to check if there is actually...

> but if an IfcSite does not have a representation But it would have a placement right? So it does establish a local origin. Or you could have a cartesian...

This is on purpose. It's made like that as a consequence of https://forums.buildingsmart.org/t/propertysets-of-ifcspace/3997/7 This was also discussed in an issue here but can't find it now.

+1 plates can be equally vertical and walls can be slanted.

http://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/Pset_TransportElementCommon.htm ? Edit: applicability is on the abstract superytpe

Agreed. We can also make it only applicable to IfcTransportElement if you feel better about it. We should then check the infra repo what the state was at that point....

(note deprecation of entity attribute is currently a md only change and can be done by anybody)

> IfcAnnotation/SUPERELEVATIONEVENT => Product Linear Placement & Product Relative Positioning (IfcAlignment) > > IfcAnnotation/WIDTHEVENT => Product Linear Placement & Product Relative Positioning (IfcAlignment) Note that currently the Geometry templates don't...