Missing concept action plan

### Aggregation

> * The concept usage 'Aggregation' for entity 'IfcActionRequest' in MVD 'GeneralUsage' is not modeled in UML
> * The concept usage 'Aggregation' for entity 'IfcController' in MVD 'GeneralUsage' is not modeled in UML
> * The concept usage 'Aggregation' for entity 'IfcElementAssembly' in MVD 'GeneralUsage' is not modeled in UML
> * The concept usage 'Aggregation' for entity 'IfcPerformanceHistory' in MVD 'GeneralUsage' is not modeled in UML
> * The concept usage 'Aggregation' for entity 'IfcProjectOrder' in MVD 'GeneralUsage' is not modeled in UML
> * The concept usage 'Aggregation' for entity 'IfcSlabElementedCase' in MVD 'GeneralUsage' is not modeled in UML
> * The concept usage 'Aggregation' for entity 'IfcWorkSchedule' in MVD 'GeneralUsage' is not modeled in UML

Two issues here:

* One, we're referring to a parent concept without a parametrization https://github.com/buildingSMART/IFC4.3.x-development/issues/118
* Two, IfcElementAssembly IfcSlabElementedCase (2nd removed, so not relevant). Should use the child concepts. Element (De)composition.

Solution:

- [x] @Moult Move Aggregation block in Markdown from IfcXElementCase to IfcX
- [x] @Moult (optional, but I'd we should) Create concept diagram for Aggregation concept
- @aothms Parametrize Aggregation concept with (IfcActionRequest IfcAudioVisualAppliance IfcBuildingSystem IfcCableSegment IfcChiller IfcCommunicationsAppliance IfcController IfcCoolingTower IfcDistributionSystem IfcElectricGenerator IfcElementAssembly IfcFurniture IfcPerformanceHistory IfcPermit IfcProjectOrder IfcSlabElementedCase IfcStructuralAnalysisModel IfcUnitaryEquipment IfcWorkSchedule) **minus IfcElement subtypes**
- [x] **well let's say we just open up this template to the applicable entity and remove parametrization from UML**
- [ ] @aothms Add IfcElement subtypes above to Element (De)composition
- [ ] @TLiebich (optional, but I'd we should) Revise "Aggregation" text http://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/concepts/Object_Composition/Aggregation/content.html to better reflect usage in scheduling domain and maybe remove the note that Aggregation about bidirectional concept because it seems to imply Aggregation in itself should not be used.

### Axis 2D Geometry

* The concept usage 'Axis 2D Geometry' for entity 'IfcCurtainWall' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Axis 2D Geometry' for entity 'IfcRamp' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Axis 2D Geometry' for entity 'IfcRampFlight' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Axis 2D Geometry' for entity 'IfcStair' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Axis 2D Geometry' for entity 'IfcStairFlight' in MVD 'GeneralUsage' is not modeled in UML

Solution:

- [x] @aothms Somehow simply missing in UML. Hopefully fixed by the time you read this.


### Body Geometry

* The concept usage 'Body Geometry' for entity 'IfcBridge' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcBridgePart' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcBuilding' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcBuildingStorey' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcFacility' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcFacilityPart' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcOpeningElement' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcOpeningStandardCase' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcProjectionElement' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcReinforcingBar' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcReinforcingMesh' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcSite' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Body Geometry' for entity 'IfcTendon' in MVD 'GeneralUsage' is not modeled in UML

Issues:

* Somehow the choice was made not to import this into UML. Can't recall the reason other than that I probably found this list too selective and hence insignificant. Everything can have a body geometry so no sense to parametrize this. Let's just assign this template to all subtypes of Ifc... (read below)
* Most of these are **not an IfcElement** The applicable root of this concept has to be changed to IfcProduct

Solution:

- [x] @aothms Change mode of this template to not be UML driven but applicable root driven
- [x] @Moult Change template root to IfcProduct

### Body Tessellation Geometry

* The concept usage 'Body Tessellation Geometry' for entity 'IfcElement' in MVD 'GeneralUsage' is not modeled in UML

Issue:

* No issue. This is a false positive.


Solution:

- [ ] @aothms Investigate

### Classification Association

* The concept usage 'Classification Association' for entity 'IfcAsset' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Classification Association' for entity 'IfcCostItem' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Classification Association' for entity 'IfcDistributionControlElement' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Classification Association' for entity 'IfcGeographicElement' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Classification Association' for entity 'IfcObjectDefinition' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Classification Association' for entity 'IfcPerformanceHistory' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Classification Association' for entity 'IfcTask' in MVD 'GeneralUsage' is not modeled in UML

Issues:


* According to @Moult the usage above is not intended use of classification. Is there parametrization for this concept necessary?

Solution:

- [x] @Moult to propose solution.

### Constraint Association

* The concept usage 'Constraint Association' for entity 'IfcConstructionResource' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Constraint Association' for entity 'IfcTask' in MVD 'GeneralUsage' is not modeled in UML

~~~xml

Constraints may be applied to a resource to indicate fixed work (such as total person-hours) or fixed usage (such as simultaneous workers).

Constraints may be applied to a task to indicate fixed task duration, fixed start or fixed finish, where _IfcMetric_.ReferencePath is set to the corresponding attribute on the _IfcTaskTime_ entity.

~~~


Issues:

* Sorry I don't really know what to make of this? Is this normative? It seems like just some sort of examples? The ParameterRule on `Constrained Attribute=` does not relate to a defined term it seems.
* It's probably also that the validation fails to recognize the parametrization as it does exit.

Solution:

- [x] @Moult Given that the examples relate to scheduling, please propose something.
- [ ] @aothms To look into validation issue.

### Control Assignment

* The concept usage 'Control Assignment' for entity 'IfcActionRequest' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Control Assignment' for entity 'IfcControl' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Control Assignment' for entity 'IfcCostSchedule' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Control Assignment' for entity 'IfcPermit' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Control Assignment' for entity 'IfcProjectOrder' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Control Assignment' for entity 'IfcWorkCalendar' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Control Assignment' for entity 'IfcWorkControl' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Control Assignment' for entity 'IfcWorkSchedule' in MVD 'GeneralUsage' is not modeled in UML


Issue:

* Inconsistent parametrization in mvdXML.

Solution:

- [x] @Moult Since this is bout scheduling please propose something. Is parametrization for this concept necessary? What's the rows with only applicability version the ones with two columns?

### Element Nesting

* The concept usage 'Element Nesting' for entity 'IfcJunctionBox' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Element Nesting' for entity 'IfcSanitaryTerminal' in MVD 'GeneralUsage' is not modeled in UML


Issue:

* You're not going to tell me these are the only two things that can be nested.

Solution:

- [x] @aothms remove parametrization on this concept and open up for all subtypes of IfcElement
- [x] @Moult Check wording in these two above cases to be sure it's exemplary

### Group Assignment

* The concept usage 'Group Assignment' for entity 'IfcGroup' in MVD 'GeneralUsage' is not modeled in UML

Issue:

- I think this is a versioning thing. That simply Groups of groups was conceived after I did the import. I recall some discussion.
- But I'm not happy with the concept as it stands. The concept now is `IfcGroup -> IfcRel -> IfcProduct`. This is wrong in two ways (a) I think it should be reversed (b) the entity on the right now should not be IfcProduct (IfcGroup isn't an IfcProduct) but IfcObject probably.

Solution:

- ? ~reverse template~. I see this is the same for the other assignment concepts as well. Let's keep as is then. It violates the idea the applicable (parametrizable) entity is on the left, but oh well
- [x] @aothms change applicable enitty
- [x] @aothms add parametrization for IfcGroup

### Material Constituent Set

* The concept usage 'Material Constituent Set' for entity 'IfcRailing' in MVD 'GeneralUsage' is not modeled in UML

Issue:

* Not sure, probably versioning thing.

Solution:

- [ ] @aothms to add parametrization

### Material Layer Set Usage

* The concept usage 'Material Layer Set Usage' for entity 'IfcCovering' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Material Layer Set Usage' for entity 'IfcPlateStandardCase' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Material Layer Set Usage' for entity 'IfcSlabStandardCase' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Material Layer Set Usage' for entity 'IfcStructuralSurfaceMember' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Material Layer Set Usage' for entity 'IfcWallStandardCase' in MVD 'GeneralUsage' is not modeled in UML

Issue:


* Two types of information mixed in one concept.
1. Nomination of material label names
2. Geometric positioning based on representation items specific to certain element types
* Deprecated/deleted entities
* The wrong parametrization was chosen, choosing use case 1.
* Material Labels like that should be used consistently regardless of using Constituents Layers or Profiles

Solution:

- [x] @Moult **Speculative** Create a concept "Composite Material Association" (or any other name) where we nominate material layer/constituent/profile names for certain element types regardless of whether the element uses Constituents Layers or Profiles
- [x] @aothms To change parametrization type to unary
- [x] @aothms To move material suggestions to novel template
- [x] @Moult To move definition in Markdown upwards to non deprecated entities

### Material Profile Set Usage

* The concept usage 'Material Profile Set Usage' for entity 'IfcBeamStandardCase' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Material Profile Set Usage' for entity 'IfcColumnStandardCase' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Material Profile Set Usage' for entity 'IfcCovering' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Material Profile Set Usage' for entity 'IfcFlowSegment' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Material Profile Set Usage' for entity 'IfcMemberStandardCase' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Material Profile Set Usage' for entity 'IfcStructuralCurveMember' in MVD 'GeneralUsage' is not modeled in UML

Issue:


* Probably same as above. Inconsistent usage.

Solution:

- [x] @Moult Verify whether this is indeed similar to the issue above
- [x] @Moult **Speculative** Create a concept "Composite Material Association" (or any other name) where we nominate material layer/constituent/profile names for certain element types regardless of whether the element uses Constituents Layers or Profiles
- [x] @aothms To change parametrization type to unary
- [x] @aothms To move material suggestions to novel template

### Object Nesting

* The concept usage 'Object Nesting' for entity 'IfcEvent' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Object Nesting' for entity 'IfcProcedure' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Object Nesting' for entity 'IfcTask' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Object Nesting' for entity 'IfcTaskType' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Object Nesting' for entity 'IfcWorkSchedule' in MVD 'GeneralUsage' is not modeled in UML

Issue:


* Missing parametrization for these elements

Solution:

- [x] @Moult Provide for each of the missing rows, what that element can be nested with.
- [ ] @aothms To model @Moult's suggestions in UML

### Object Typing

* The concept usage 'Object Typing' for entity 'IfcObject' in MVD 'GeneralUsage' is not modeled in UML

Issue:

* Aparrently we don't have a top level association between IfcObject - IfcTypeObject in UML

Solution:

- [x] @aothms To review and provide IfcObject - IfcTypeObject associations for all intermediate abstract entities if missing

Note that this will also be reflected in the entity where rules that are derived from the ObjectTyping concept.

### Port Nesting

* The concept usage 'Port Nesting' for entity 'IfcDistributionPort' in MVD 'GeneralUsage' is not modeled in UML


Issue:

* Is this for real? Can a port be nested with another port?

Solution:

- [x] @Moult @TLiebich @CyrilWaechter Please advise

### Product Local Placement

* The concept usage 'Product Local Placement' for entity 'IfcBridge' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Product Local Placement' for entity 'IfcBridgePart' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Product Local Placement' for entity 'IfcBuilding' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Product Local Placement' for entity 'IfcBuildingStorey' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Product Local Placement' for entity 'IfcDistributionPort' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Product Local Placement' for entity 'IfcFacility' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Product Local Placement' for entity 'IfcFacilityPart' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Product Local Placement' for entity 'IfcPositioningElement' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Product Local Placement' for entity 'IfcSite' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Product Local Placement' for entity 'IfcSpace' in MVD 'GeneralUsage' is not modeled in UML


Issue:

* I don't know why we have only IfcElement associated in UML. Probably a versioning issue. Are there any elements that **cannot** have a local placement? @TLiebich @peterrdf?

Solution:

- [x] @aothms Unless somebody objects I'll remove the parametrization to just have everything below IfcProduct be applicable.

### Product Placement

* The concept usage 'Product Placement' for entity 'IfcProduct' in MVD 'GeneralUsage' is not modeled in UML

Issue:

* This is an unparametrized concept.

Solution:

- [x] @Moult to review if there is anything meaningful written there. If yes, the documentation can move to either the ObjectPlacement attribute description if short. Or the IfcObjectPlacement entity markdown if longer. Or any other way as desired.

### Property Sets for Objects

* The concept usage 'Property Sets for Objects' for entity 'IfcObject' in MVD 'GeneralUsage' is not modeled in UML

Issue:

* This is probably general documentation. Not the association of a pset to IfcObject

Solution:

- [x] @Moult to review if this is important documentation to keep and if so, move to e.g IfcPropertySet or IsDefinedBy.

### Quantity Sets

* The concept usage 'Quantity Sets' for entity 'IfcDistributionElement' in MVD 'GeneralUsage' is not modeled in UML

Issue:

* No idea why there is specific documentation for Qsets on this entity

Solution:

- [x] @Moult to review if this is important documentation to keep and if so, move somewhere else.

### Spatial Composition

* The concept usage 'Spatial Composition' for entity 'IfcBridgePart' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Composition' for entity 'IfcBuildingStorey' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Composition' for entity 'IfcFacilityPart' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Composition' for entity 'IfcSpace' in MVD 'GeneralUsage' is not modeled in UML


Issue:

* Missing parametrizations

Solution:

- [x] @Moult @TLiebich @peterrdf to supply missing entries. **!!Also new rows need to be added for IfcMarinePart and what not!!**

### Spatial Container

* The concept usage 'Spatial Container' for entity 'IfcBridgePart' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Container' for entity 'IfcBuildingStorey' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Container' for entity 'IfcFacilityPart' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Container' for entity 'IfcSite' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Container' for entity 'IfcSpace' in MVD 'GeneralUsage' is not modeled in UML


Solution:

- [ ] @Moult @TLiebich @peterrdf same as above

### Spatial Containment

* The concept usage 'Spatial Containment' for entity 'IfcBeam' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcBuildingElementProxy' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcChimney' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcColumn' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcCovering' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcDistributionElement' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcDoor' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcElementAssembly' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcFeatureElement' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcMember' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcPlate' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcRailing' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcRamp' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcRampFlight' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcShadingDevice' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcSlab' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcStair' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcStairFlight' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcTransportElement' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcWall' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Containment' for entity 'IfcWindow' in MVD 'GeneralUsage' is not modeled in UML

Issue:

* No issue. Issue with validator.


Solution:

- [ ] @aothms Maybe fix validator, maybe not.

Alternative solution:

- [ ] This is the issue we talked about several months ago. I feel like this list is outdated (probably only 2x3'ish entities) and not always argumented clearly. E.g can a IfcDistributionElement not be part of the IfcSite as brought up by @NickNisbet? We can also just remove the parametrization if there is consensus that the current list is too outdated. That way the documentation entries would still show up based on the applicability of the concept.

### Spatial Decomposition

* The concept usage 'Spatial Decomposition' for entity 'IfcBuildingStorey' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Decomposition' for entity 'IfcProject' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Decomposition' for entity 'IfcSite' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Spatial Decomposition' for entity 'IfcSpace' in MVD 'GeneralUsage' is not modeled in UML


Solution:

- [x] @Moult @TLiebich @peterrdf same as above

### Type Body Geometry

* The concept usage 'Type Body Geometry' for entity 'IfcBeamType' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Type Body Geometry' for entity 'IfcColumnType' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Type Body Geometry' for entity 'IfcCoveringType' in MVD 'GeneralUsage' is not modeled in UML
* The concept usage 'Type Body Geometry' for entity 'IfcMemberType' in MVD 'GeneralUsage' is not modeled in UML


Issue:

* Inconsistent parametrization. Currently we just don't assoiciate it. Again, I feel like this list is too outdated/selective to be useful. Most if not all TypeObjects should be able to have body.

Solution:

- [x] @aothms to remove parametrization so that the concept is applicable to any TypeObject to retain the documentation in these four cases.