Dion Moult

Here's the table for Object Nesting: RelatingObject | RelatedObjects -- | -- IfcActionRequest | IfcActionRequest IfcAlignment | IfcReferent IfcConstructionResource | IfcConstructionResource IfcCostItem | IfcCostItem IfcEvent | This is wrong, IfcEvent...

Here's the review on Port Nesting: IfcDistribution port has this description, I've annotated it inline: > [The ]()[Port Nesting](http://localhost:8001/schema/templates/port-nesting.htm) concept applies to this entity. Sure. I personally reckon these sentences...

Product Placement review: > The concept usage 'Product Placement' for entity 'IfcProduct' in MVD 'GeneralUsage' is not modeled in UML Will just move docs to ObjectPlacement attribute. Makes more sense...

Property sets for objects: > The concept usage 'Property Sets for Objects' for entity 'IfcObject' in MVD 'GeneralUsage' is not modeled in UML Nothing meaningful. Already repeated in IfcPropertySet docs....

Quantity sets: > The concept usage 'Quantity Sets' for entity 'IfcDistributionElement' in MVD 'GeneralUsage' is not modeled in UML Nothing new. Deleted.

This table is for Spatial Decomposition, but if you read it right to left you get Spatial Composition :) RelatingObject | RelatedObjects --- | --- IfcProject | IfcSite IfcProject |...

Spatial Container & Spatial Containment: My feel is that this _should_ be the rule and not go into any further detail: RelatingStructure | RelatedElements --- | --- IfcSpatialElement | IfcAnnotation...

> meaning that if a concept usage is not specified, it is illegal. Rather it has been used to enhance the documentation ... Wait, it is illegal or it is...

A note @aothms not sure if you've done it already but I updated the table in https://github.com/buildingSMART/IFC4.3.x-development/issues/403#issuecomment-1059089846

Here's an attempt: > Concepts may have particular importance to common or standardised industry practices and scenarios. The table below shows a recommended list of general usage patterns that users...