Against the proposition - Only those presentation information, that cannot be directly related to a single product, have to be wrapped within the IfcAnnotation

[Aniobodo]

The IfcAnnotation has the proposition that Only those presentation information, that cannot be directly related to a single product, have to be wrapped within the IfcAnnotation.
I find this condition unnecessary. It actually makes it difficult for products to be annotated properly.
Please relax this proposition.

[aothms]

I'd tentatively agree, but I think it'd be helpful for the discussion if you could provide some (hopefully graphical) examples.

I've also seen people use decompositions, where a fixture has (several) annotation(s) that are selected based on the drawing context.

The benefit is that you can make the annotation more semantic than what is possible when you include the same content directly as an item on the product representation.

[Aniobodo]

The image above shows a prefabricated reinforcement module. This module, including its annotation, is modelled as IfcElementAssembly.

• Each of the green linear objects is an IfcReinforcingBar.
• Each of the grey linear objects is an IfcBuildingElementProxy. It's function is to hold the IfcReinforcingBar in place during handling and installation.
• The objects in red belong to the IfcAnnotation. These non-physical objects provide information and installation guide.

As seen above and for the cases where a model contains multuple reinforcement modules, this annotation provides information that is very specific to a particular module. That is the reason I want the annotation to stay with the module.
Also, adding this annotation as part of the product representation could be misleading, because it is just an annotation and not part of the module's shape.

[Aniobodo]

The image above shows a prefabricated reinforcement module. This module, including its annotation, is modelled as IfcElementAssembly.

• Each of the green linear objects is an IfcReinforcingBar.
• Each of the grey linear objects is an IfcBuildingElementProxy. It's function is to hold the IfcReinforcingBar in place during handling and installation.
• The objects in red belong to the IfcAnnotation. These non-physical objects provide information and installation guide.

As seen above and for the cases where a model contains multuple reinforcement modules, this annotation provides information that is very specific to a particular module. That is the reason I want the annotation to stay with the module. Also, adding this annotation as part of the product representation could be misleading, because it is just an annotation and not part of the module's shape.

There is also another annotation note captured in the image above but is added. That is the typical reinforcement label: 11x Ø12@150-L:2071.
This typically reinforcement label is need for the structural checks drawing context. That’s two different annotations for different contexts.