bSI-InfraRoom / IFC-Specification

IfcDoc baseline to produce the documentation
26 stars 25 forks source link

Project Representation Context 3D - are Constraints missing? #537

Open pjanck opened 1 year ago

pjanck commented 1 year ago

https://bsi-infraroom.github.io/IFC-Documentation-Tunnel/4_4_0_0/general/HTML/schema/templates/project-representation-context-3d.htm

NOTE The 3D shape representations with the representation identifier "Body" are linked to the 3D geometric representation subset with context identifier "Body" and context type "Model".

These rules are not encoded in a constraint. Should we introduce these? (They are in a NOTE, though.)

Related, perhaps? https://github.com/buildingSMART/IFC4.3.x-development/issues/579

larswik commented 1 year ago

According to ISO/IEC Directives Part2 a NOTE "is used for giving additional information intended to assist the understanding or use of the text of the document.". It also states that "Notes shall not contain requirements". Does the NOTE state a requirement or not? If it is a requirement then constraints should be added.

pjanck commented 1 year ago

Adding Project Representation Context 2D: https://bsi-infraroom.github.io/IFC-Documentation-Tunnel/4_4_0_0/general/HTML/schema/templates/project-representation-context-2d.htm

NOTE The 2D shape representations with the representation identifier "FootPrint" are linked to the 2D geometric representation subset with context identifier "FootPrint" and context type "Plan".

The decision should be applied to both.