Dion Moult

I was working on checking out the standard cases and came across the door docs which reminded me about this issue. What are the changes of getting a decision on...

OK, let's not rush it then, even from a markdown change it's potentially significant from what I see.

Proposal for classification association: It sounds as though the only parameterisation is in IfcDistributionControlElement. The relationships are all about external references. Edit: evidence is because in IFC2X3 the original usecase...

If it were a property set, it would have to be applied to a lot of stuff. It's definitely not restricted to distribution control elements. It would extend to spatial...

Proposal for constraint association: All the 4 out of 5 constraints make sense to me, and in fact in the process of implementing. One of them I think _could_ be...

For control assignment: I know about half of these in detail, and the other half I know the theory but never implemented. I'm not quite sure what the question is...

After verbal discussion: Classification: will convert to library. - [x] @aothms: Parameterisation to be deleted. - [x] @Moult: to restructure Markdown and create new issue on crazy REST API stuff....

@aothms are we missing a diagram for element connectivity? The reason I ask is because there is this quote on IfcWall's docs: > Walls with openings that have already been...

By the way, to solve the constraint one instead of writing documentation to cover it, I'll just convert them into diagrams since that explains it much clearer. Here's a snapshot...

Here is the completed table for controls RelatingControl | RelatedObject -- | -- IfcActionRequest | IfcActor IfcControl | IfcObjectDefinition IfcCostItem | IfcProduct IfcCostItem | IfcProcess IfcCostItem | IfcResource IfcCostItem |...