IFC 4x3 Data Architecture (Modification)

Industry Foundation Classes (IFC) Architeture version 4.3.x overview (Figure 1) shows data squema layers where Core layer represent the root of tree. Interoperability and Domain layers are exposed to principle of inheritance, wich does not occur for Resource entities (8.x.x.x). So, i think the overview can not help to understand well it. Usually, the diagrams of architeture data are phylogenetic trees like graphical representations of evolutionary relanshionships and them are fundamentally important in modern taxonomy used in a wide variety of practical applications.

Figure 1. IFC Architeture version 4.3.x overview

Schramm T. et al. (2021) on their research say phylogenetic trees are important tools for understanding evolution, yet actors envolved on Projects are read and interpret them correctly. The researchs investigated 1197 diagrams focused on important aspects of evolutionary relanshonships and comparing results (Figure 2). The most of studies, root on left and below positions are the main way to representation hierachy of trees.

Figure 2. Root on diagrams

Resource entities on IFC schema are end-uses, so them support Core entities for all specification on schema. In this case, i suggest two triangles to represent IFC data. Kernel and extensions (Core layer) on the top of the smallest triangle, representing the base of the structure above, the big one (Interoperability and Domain layers). This condition clarifies about that resource entities do not inherit from Core layer. So, opposite way of all of others on IFC schema. Also, Core layer represents the conection (intersection) between the two triangles. In Figure 3, is demonstrated the equivalences and suggested the new overview.

Figure 3(a). Demonstration

Figure 3(b). New proposition

Start by locating the source for the current IFC 4.3.x architecture overview shown in Figure 1, then compare its relationships with the proposed two-triangle representation in Figures 3(a) and 3(b). Confirm the diagram accurately communicates the relationship between Core, Interoperability, Domain, and Resource entities; done means the revised overview is incorporated and clearly reflects the schema semantics.

Written by the indexing model from the issue text.