Schema-Agnostic Data Type Inference and Validation for Exchanging JSON-Encoded Construction Engineering Information

Abstract

Modern construction and infrastructure projects produce large volumes of heterogeneous data, including building information models, JSON sensor streams, and maintenance logs. Ensuring interoperability and data integrity across diverse software platforms requires standardized data exchange methods. However, traditional neutral object models, often constrained by rigid and incompatible schemas, are ill-suited to accommodate the heterogeneity and long-term nature of such data. Addressing this challenge, the study proposes a schema-less data exchange approach that improves flexibility in representing and interpreting infrastructure information. The method uses dynamic JSON-based objects, with infrastructure model definitions serving as semantic guidelines rather than rigid templates. Rule-based reasoning and dictionary-guided term mapping are employed to infer entity types from semi-structured data without enforcing prior schema conformance. Experimental evaluation across four datasets demonstrated exact entity-type match rates ranging from 61.4% to 76.5%, with overall success rates—including supertypes and ties—reaching up to 95.0% when weighted accuracy metrics were applied. Compared to a previous baseline, the method showed a notable improvement in exact matches while maintaining overall performance. These results confirm the feasibility of schema-less inference using domain dictionaries and indicate that incorporating schema-derived constraints could further improve accuracy and applicability in real-world infrastructure data environments.

1. Introduction

1.1. Research Background and Motivation

The construction industry is undergoing a rapid digital transformation driven by advancements in technologies such as building information modeling (BIM), internet of things (IoT), and cloud computing. This transformation has necessitated a shift toward data-driven decision-making, where insights derived by analyzing project data are used in critical decision-making throughout the lifecycle of a built asset. The ability to effectively leverage data is becoming increasingly essential for improving the efficiency, reducing costs, and enhancing the overall project outcomes.

Modern construction projects involve experts from diverse disciplines such as architecture; structural engineering; mechanical, electrical, and plumbing (MEP) engineering; and project management. These disciplines generate and utilize data from different perspectives, requiring data exchange methodologies that can effectively coordinate them [1]. Furthermore, the data evolve throughout the project lifecycle, necessitating mechanisms to manage data versioning and ensure backward compatibility [2,3]. Finally, the data exchange method must incorporate conflict-detection mechanisms to identify and resolve the inconsistencies or contradictions in data originating from different data sources [3].

The existing data exchange methods [1] are characterized by rigidity, complexity, and difficulty in accommodating diverse data sources and evolving requirements. Although several data exchange standards exist within the construction domain, such as industry foundation classes (IFCs), these methods often exhibit significant limitations. Their rigid schema structures struggle to accommodate the diverse and evolving data formats generated by modern construction projects. The inherent complexity of these standards can hinder seamless data exchange, leading to interoperability challenges and impeding the efficient flow of information across project stakeholders.

Schema-less data such as JSON [4] can provide flexibility, as their structure is implicit and not strictly enforced. However, without any agreed-upon data exchange conventions backed by proper management, schema-less data may complicate exchange efforts due to ambiguity of the meanings they carry. Therefore, to take advantage of schema-less data for sharing construction design and engineering information, a measure for sharing the structure and meaning of the data is needed.

1.2. Research Objectives and Scope

This study aimed to develop and present a flexible schema-agnostic data exchange methodology, facilitating data integration of heterogeneous JSON-encoded construction engineering information such as BIM data and construction-phase data such as job progress throughout the lifecycle of a construction project. To identify each data object, various data matching techniques were employed to infer the structure and validate the content without strict schema definitions. This study focuses on information flows across various disciplines such as architecture, structural and MEP engineering, project management, construction management, etc.

1.3. Contributions of This Study

This study introduces a methodology that leverages dynamic data, embraces a schema-agnostic design, and implements a data dictionary-based approach to handle engineering data from a construction project, thus creating a unique and adaptable solution for facilitating data-driven decision-making in construction. It focuses on the interoperability of diverse non-geometric data (cost, schedule, and materials) using standard classifications (dictionaries) and offers a pragmatic approach when full standard compliance is difficult.

Unlike black-box machine learning (ML)/large language model (LLM)-based approaches, this methodology ensures transparency and explainability of the inference, which are critical in construction, where trust and verification are paramount. Also, it demonstrates that semantic interpretation and validation are possible with a relatively lightweight approach without requiring large-scale training data or high-performance computing, as in the case of ML/LLM.

This methodology enables enhanced assessment of the data quality by quantifying the degree of match with the dictionary definitions rather than a binary ‘good-or-bad’ metric. Its data dictionary incorporates additional contexts such as synonyms and importance levels.

2. Theoretical Background and Related Work

2.1. Construction Information Modeling and Data Exchange

The increasing digitization of documents and information in civil infrastructure projects demands seamless data sharing among the project participants. This requires interoperability and compatibility among the diverse data types and formats used in design, engineering, and management software.

Data exchange between various engineering software and hardware systems used for road design and structural analysis was initially addressed in the 1980s and 1990s with the development of neutral data formats for digitizing information in various fields, such as CAD/CAE. In the construction sector, IFC, which defines the various elements comprising the facilities and the relationships between them, is being developed as the standard for data exchange formats based on neutral data models.

Most neutral data models are considered static because the structure and terminology of the models cannot be altered by their user. Table 1 summarizes advantages and disadvantages of static data model-based exchange.

Table 1. Advantages and disadvantages of static data exchange approaches.

	Advantages	Disadvantages
Schema clarity and semantic interoperability	Well-defined schemas clarify structure and semantics, enabling cross-system data exchange, especially geometric shape information.	-
Data integrity and consistency	Static models promote data integrity and consistency; strict rules simplify maintaining structural correctness.	Strictness reduces flexibility when novel or atypical data must be represented.
Standards maturity and tooling	Mature standards (STEP, IFC) and an abundance of software tools.	Standards are slow and complex to update.
Extensibility/adding new types	Predictable schemas ease integration and parsing.	Difficult to add types/attributes not in the predefined schema, hindering rapid response to new needs.
Data conversion fidelity	Neutral formats enable cross-software exchange and reduce ad-hoc translations.	Conversion can lose or distort vendor-unique data when importing/exporting.
Support for unstructured/semi-structured data	-	Neutral models poorly accommodate unstructured or semi-structured data (simulation results, sensor streams, documents).

2.2. Integration of Unstructured Project Information with Structured Object Representations

The majority of the information required during the implementation of a construction project is digitized into semi-structured formats, such as text or tables (e.g., Excel). To effectively utilize this semi-structured and unstructured information in construction projects, it must be effectively linked to well-structured object models. The Construction Operations Building Information Exchange (COBie) [5] maintains the building maintenance information in a spreadsheet table format (XML) and assigns IDs to the IFC objects of the target facility to link them with the object model. In contrast, in W3C Linked Building Data (see References), the ontology for the spatial structure of a building is defined using semantic web technologies, enabling the linking of component information based on this ontology in a Linked Data format.

However, the exchange of diverse unstructured and semi-structured information in conjunction with BIM models cannot be adequately addressed by simply expanding neutral models. Sobkhiz and El-Diraby [6] proposed a method for deriving unique models tailored to project-specific situations by combining the semantic networks extracted through natural language analysis of project documents with an analysis of the communication network of a user. However, finding an effective method to ensure that the situational data model derived from the analysis of specific cases can be understood and shared by all project participants remains a challenge for future research.

2.3. Schema Inference and Ontology Matching for Dynamic Data Objects

Dynamic objects are self-describing data structures, often represented in formats such as JSON, XML, or YAML, which enable the modeling of real-world phenomena or abstract concepts through hierarchically structured item-name/content pairs. Unlike traditional schema-bound approaches, dynamic objects are not derived from a fixed data model, which facilitates flexible data representation and adaptation to evolving information requirements.

To ensure the accurate interpretation of the data exchange with dynamic objects, several methodologies have been developed to convey the semantic meaning without relying on rigid, predefined schemas.

2.3.1. Schema Inference

Schema inference techniques aim to derive a data structure or schema from dynamic objects, enabling interpretations based on patterns and relationships within the data.

Inferring the schemas from dynamic data, such as JSON data, involves discovering their implicit structure through frequency analysis of the data element occurrences and tree structure matching, effectively approximating a schema by identifying recurring patterns in the data organization.

By inferring a schema, different systems can understand and process the data, even if they do not have prior knowledge of their structure.

Cánovas Izquierdo and Cabot [7] proposed an iterative schema-merging technique that extracts schemas from individual JSON documents and progressively merges them, thus addressing the need to discover and visualize implicit schemas in schema-free JSON data.

Klettke et al. [8] utilized a structure identification graph to discern hierarchical relationships between JSON nodes. Their approach employed a reverse engineering technique that extracted an explicit schema after data storage and detected structural outliers. This strategy aligns with the scalable implementation of lazy-schema evolution in NoSQL data stores.

Baazizi et al. [9] developed a two-phase inference algorithm that analyzes field occurrence frequencies to identify mandatory/optional fields and union types, allowing users to adjust the precision–conciseness balance of the algorithm by modifying the equivalence relation (E) parameters. The approach addressed the challenges in schema inference from massive, schema-less JSON datasets, where the absence of schema information can negatively affect the query correctness and optimization.

2.3.2. Ontology Matching

Ontology matching addresses the challenge of semantic interoperability by identifying the correspondence between different ontologies or knowledge representations.

When dynamic object reference concepts are defined in different ontologies, ontology matching helps to resolve these differences and ensures that all systems interpret the data consistently.

Ontology matching approaches leverage the existing ontologies and semantic relationships to align dynamic objects with established knowledge domains, thereby facilitating meaning transfer through shared vocabulary and concepts.

Miller et al. [10] proposed an instance-based matching approach that infers schema mappings by analyzing not only the schema structure but also the characteristics of actual data instances (values), such as data types, value distributions, and patterns. For example, they determined that two attributes are likely to correspond if they consistently contain values of a similar format (e.g., date formats), aligning with the schema mapping problem of discovering queries to transform source data into a different but fixed target schema.

Madhavan et al. [11] modeled two schemas internally as schema graphs (representing shared types, referential integrity, and views as nodes and edges) and then automatically generated mappings by calculating the linguistic (name, type) and structural (context, sub-leaf) similarities. Although this approach is intended for translation between two schemas, its similarity-based discovery of the data structure can also be applied to schema-less ontology discovery and matching.

Suchanek et al. [12] identified the correspondence between schemas or ontologies by integrating diverse techniques, including lexical analysis of names, structural analysis using graph-based representations, semantic reasoning leveraging WordNet and background knowledge, and instance-based matching. This multifaceted approach enabled the construction of an extensible ontology by automatically extracting and unifying facts from Wikipedia, thereby achieving a high degree of accuracy in the resulting knowledge base.

2.3.3. Data Mapping

Data-mapping techniques define explicit transformations and correspondences between elements in dynamic objects and those in target systems. They establish clear links to ensure consistent and accurate translation of information between the source and target data models.

For construction data mapping, particularly ontology-based approaches, semantic technologies can be used to refine the matching logic, leveraging rule-based reasoning or semantic descriptions during the dictionary matching phase. Beach et al. [13] proposed a method to flexibly interpret and validate data by transforming the BIM data, such as IFC, into a resource description framework (RDF) and applying semantic web technologies such as SPARQL (SPARQL Protocol and RDF Query Language) and Semantic Web Rule Language (SWRL), thus facilitating automated regulatory compliance within the construction sector.

2.4. Verifying Correctness of Dynamic Data Objects

Because there are no fixed schemas that would normally enforce data integrity, dynamic, schema-less data require verification to ensure their correctness. This verification requires a multifaceted approach, encompassing both the verification of its structural integrity and validation of its semantic meaning against the expected domain knowledge.

2.4.1. Structural Correctness

Verifying the structural correctness of dynamic data involves assessing whether the data adhere to expected patterns, hierarchies, and relationships, ensuring that they are well-formed and consistent in terms of their organization. In the context of the structural correctness of dynamic data, schema inference is often employed, wherein the inferred schema is compared with the dynamic data.

Klettke et al. [14] proposed the “structural outlier” metric, a composite indicator combining attribute (key) omission/addition rates, type mismatch rates, and nested structure inconsistency rates, as a measure of the structural conformity between automatically inferred JSON schemas (using their approach from [8]) and actual documents; this method aimed to capture the degree of heterogeneity of the JSON data and reveal structural outliers.

Afsari et al. [15] verified the correctness of BIM data by first examining the formal validity (structure, data types, etc.) of the JSON documents and then performing schema validation against a defined ifcJSON4 schema, which mirrors the EXPRESS schema matching used with the IFC data (in the SPF format).

2.4.2. Semantic Correctness

Beyond structural integrity, semantic correctness ensures that data accurately represent the intended meaning and comply with domain-specific constraints, requiring methods that validate both content and its correspondence to real-world concepts. Domain rule-based approaches establish semantic correctness by defining explicit rules and constraints that reflect inherent properties and relationships within a specific domain, allowing for validation against these predefined expectations. On the other hand, ontology-based approaches leverage formal ontologies and semantic reasoning to verify the semantic correctness and map the data to well-defined concepts and relationships within an ontology to ensure consistency and adherence to domain knowledge.

Solihin et al. [16] highlighted that neutral data models defined with EXPRESS schemas, such as IFC, include definitions of the object relationships and constraints that cannot be expressed with a simple JSON schema alone, necessitating a semantic validation step to ensure the logical consistency of the data; their study aimed to define the requirements for a good-quality IFC model and propose automatable rules for measuring its completeness and correctness.

Lee et al. [17] validated the consistency of the exchanged data by verifying their conformance to the model view definitions (MVDs), which are subsets of the IFC schema, using rule sets that verify whether the information required by the receiver is lost or inconsistent during the data exchange. The study focused on identifying requirements/rules and developing rule-based data validation processes to enhance BIM data interoperability.

The following research cases utilized ifcOWL, which transforms the IFC into an RDF/OWL ontology, to represent the BIM objects as classes and relationships, thus enabling the constraint compliance to be evaluated through logical inference engines:

Venugopal et al. [18] and Terkaj et al. [19] used the ontology to clarify the data elements required for unambiguous information exchange between different project stakeholders [18] or to translate the integrity constraints of the original IFC schema into an OWL class expression [19].

Pauwels et al. [20] checked the compliance of the model data against rulesets defined in the SWRL. A subsequent study [21] proposed enhancing the ifcOWL with optimized geometric semantics to identify incorrect spatial relationships between the building elements. Han et al. [22] defined the physical dependencies among structural components, such as support and containment relationships (e.g., a beam cannot be installed until a column is erected) and developed a construction sequencing ontology based on these relationships. Ontology reasoning was employed to identify incorrect construction sequences by integrating the ontology with the BIM models and construction schedules.

Table 2 summarizes the related research works discussed above, grouped by methodology.

Table 2. Comparison of the research works related to this research.

Method	Input Data	Core Technique	Limitation	Relation to This Study
Integration of Unstructured Information
Dynamic Integration [6]	Project documents, user communication network	Combines semantic networks from NLP with communication network analysis to derive project-specific models.	Ensuring the derived model is understandable and shareable by all project participants is a challenge.	Contrasts their ML method by using a rule-based approach with a shared dictionary to ensure common understanding.
Schema Inference
Iterative Schema Merging [7]	Individual JSON documents	Extracts and progressively merges schemas from separate JSON documents to discover an implicit overall schema.	May result in an overly permissive or complex ‘union schema’ if data sources are highly heterogeneous.	Matches an instance to a dictionary class to infer its type, instead of inferring a schema from multiple documents.
Reverse Engineering [8,14]	JSON data	Uses a structure identification graph to reverse-engineer an explicit schema and detect structural outliers.	The quality of the inferred schema is highly dependent on the initial dataset	This study’s ‘Noise’ score is similar to their ‘outlier’ concept but measures against a predefined dictionary, not an inferred schema.
Parametric Inference [9]	Massive, schema-less JSON datasets	Analyzes field occurrence frequencies to identify mandatory/optional fields.	The absence of a schema can negatively affect query correctness and optimization.	Unlike their method of inferring from data, this study explicitly predefines mandatory attributes in the dictionary.
Ontology Matching
Instance-based Matching [10]	Schema structure and data instances	Infers schema mappings by analyzing data value characteristics, such as types and patterns.	Primarily designed to transform source data into a fixed target schema.	Incorporates their value-based checks into this study’s ‘Accuracy’ score calculation.
Schema-graph Matching [11]	Two schemas	Models schemas as graphs and generates mappings by calculating linguistic and structural similarities.	Intended for translation between two existing schemas.	Addresses instance-to-class matching, a different problem from their schema-to-schema translation.
Hybrid/Extensible Ontology [12]	Wikipedia, WordNet	Integrates diverse techniques to automatically extract facts and build the YAGO knowledge base.	Prone to factual inaccuracies and biases inherited from its source (Wikipedia).	Focuses on using a predefined dictionary for inference, rather than a large knowledge base.
Data Mapping
Rule-Based Semantic Mapping [13]	BIM data (IFC)	Transforms BIM data to RDF and applies semantic web rules (SPARQL, SWRL) for automated compliance checking.	Requires significant expertise to author and maintain complex semantic rules (SWRL).	Also rule-based, but this study first infers the type of schema-less data before applying quantitative validation.
Correctness Verification
Structural Correctness [15]	JSON documents representing BIM data	Performs formal validity checks and then validates against a defined ifcJSON4 schema.	Relies on a rigid, predefined schema (ifcJSON4), offering little flexibility for data variations or project-specific extensions.	Operates in a schema-less context, requiring a type inference step before validation can occur.
Semantic Correctness/Rule-based [16,17]	IFC models, MVDs	Validates data conformance against predefined rules from an EXPRESS schema or Model View Definitions (MVDs).	Tightly coupled to the IFC standard and its MVDs; creating and managing comprehensive rule sets for each MVD is complex.	This study adds a necessary preceding step of type inference for unknown objects.
Semantic Correctness/Ontology-Based [18,19,21]	ifcOWL (IFC as an ontology)	Uses formal ontologies and logical reasoning engines to verify semantic correctness and compliance.	High computational overhead and complexity of semantic reasoners.	This study uses a lightweight data dictionary and a quantitative scoring system instead of formal ontologies.

3. Proposed Methodology: Schema-Agnostic Information Exchange Based on Dynamic Data Objects

3.1. Overview of Methodology

The proposed methodology is founded on dynamic data objects and schema agnosticism, whereby JSON-based dynamic objects are used for data exchange instead of a fixed, neutral model. It is based on schema agnosticism, which allows a data recipient to interpret and utilize the incoming data without knowing the exact schema employed by the data producer. In the context of schema agnosticism, the data dictionary defines classes and members but serves primarily as a reference guide to help recipients understand the semantics of the received data rather than to enforce a rigid structure.

3.1.1. Data Dictionary

Inferring the types and attributes of the data objects from the schema-less JSON data is a significant challenge because of the absence of explicit structural definitions. A data dictionary serves as a reference for semantic interpretation. It offers a primary, yet effective, means of inference by resolving ambiguities in interpretation and assuring data integrity.

This approach involves semantically aligning the keys (fields) found within the schema-less JSON data against formally defined terms and concepts residing in authoritative domain dictionaries or industry classification systems, such as OmniClass, UniClass, buildingSMART Data Dictionary (bSDD), or relevant national standards. These curated resources provide controlled vocabularies and standardized definitions for various types of facilities, components, and their associated attributes or properties within the architecture, engineering, and construction (AEC) domain. By matching the JSON keys to these standard definitions, the intended meaning and type of the data object can be reliably inferred. Because this logic is fixed and explicitly defined, the inference process remains consistent, transparent, and explainable when compared with less interpretable ML approaches.

3.1.2. Object Class Inference Mechanism

The inference techniques discussed above (key name pattern matching, value heuristics, and semantic dictionary matching) are used to align a given data object to a class. The data object properties are defined in the data dictionary derived from a domain-specific classification system such as OmniClass.

These mechanisms operate on a predefined set of criteria that maps the observed features within the JSON data (such as specific key names, value patterns, or successful matches to dictionary/ontology terms) to a specific object category or semantic interpretation.

A key advantage of this approach is its inherent transparency and explainability; the reasoning of the system for classifying an object is directly traceable through the applied explicit logic.

The practical implementation of this inference logic frequently involves the utilization of rule engines or custom-developed scripts designed to evaluate these conditions against the incoming JSON objects. For example, developers can encode deterministic checks that reflect the domain knowledge, such as: “IF the object contains a key named ‘pier_count’ OR a key named ‘deck_type’ THEN classify the object as ‘Bridge’.”

Rule-based classifiers have demonstrated high accuracy in specific controlled scenarios within the AEC domain, such as classifying BIM elements based on geometric and topological clues using IF–THEN rules [23] or mapping textual requirements to BIM elements via predefined correspondence rules [24].

Although a potentially large number of patterns and rules must be enumerated in advance to effectively handle diverse data sources and variations in terminology, the explicit rule-based logic derived from domain knowledge and dictionary definitions remains a viable and transparent method for interpreting the intended meaning of schema-less JSON data in dynamic exchange scenarios.

3.2. Core Components

There are two fundamental components underpinning the proposed schema-agnostic exchange methodology: the data dictionary/ontology establishing the semantic context and the dynamic data object acting as a flexible information carrier.

3.2.1. Data Dictionary/Ontology

In this study, the data dictionary serves as a lightweight domain ontology and is the semantic cornerstone of the proposed schema-agnostic methodology. Derived from an established classification (similar to OmniClass; for further details on the classification system, see [25]), it provides the ground-truth definitions for classes (representing concepts) and their attributes (properties).

It provides a structured knowledge base necessary for interpreting dynamic data objects reliably in a distributed and heterogeneous environment rather than enforcing structural conformance, as in the case of a rigid schema. It acts as a shared, unambiguous reference point, enabling consistent interpretation of the meaning embedded within incoming, potentially schema-less, dynamic data objects.

To fulfill this role effectively, the data dictionary performs several critical functions:

• Semantic Definition: It disambiguates the meaning of keys or attribute names used in the dynamic data; for instance, it clarifies whether a “length” attribute refers to a physical dimension (e.g., of a beam) or a time duration (e.g., of a task).
• Concept Identification: It formally identifies and describes the core entities pertinent to the construction project domain, such as physical elements, spaces, activities, and resources.
• Relationship Indication: It explicitly defines the key relationships between concepts, including inheritance (is-a), composition/decomposition (part-of), and association (refers-to). This helps the receiving systems to understand the intended structure and context (e.g., “Column” is-a “StructuralMember”; “ReinforcementBar” part-of “Beam”).
• Data Type and Unit Guidance: It specifies the expected data types (e.g., string, number, Boolean, object reference, and list) and the associated units of measure (e.g., m, mm, kg, and MPa) for the attributes. Although not strictly enforced at the schema level, this guidance is crucial for ensuring consistency during data generation and subsequent validation.

3.2.2. Dynamic Data Object

A dynamic data object, typically represented using a lightweight hierarchical format such as JSON, serves as a flexible container for exchanging information fragments related to specific physical or conceptual entities within a project. Unlike the data conforming to rigid schemas, these dynamic objects primarily consist of attribute–value pairs, where the structure and included attributes can vary based on the data source and the specific information being conveyed at that time.

A critical characteristic of each dynamic data object intended to represent a persistent project entity (e.g., a specific column, beam, activity, or requirement) is the inclusion of a unique, immutable identifier such as a global unique identifier (GUID) or a project-specific URN. The identifier ensures that disparate data objects, potentially generated by different systems or at different times, can be reliably associated with the same real-world or conceptual entity that they describe (e.g., urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6). Persistent identification is fundamental for integrating information from various sources and tracking the evolution of entities throughout the lifecycle of a project.

Beyond the identifier, the object contains various key–value pairs representing the properties of the entities, where the keys usually correspond semantically to the member names defined in the data dictionary, and the values are specific data (e.g., “elementLength”: 12.5, “concreteGrade”: “C24”). Optionally, objects might also contain metadata fields (e.g., @type, _classId) that explicitly link them to their corresponding class definitions in the data dictionary, although this is not strictly required in a truly schema-agnostic approach where the type is inferred.

3.3. Mitigating Uncertainty in Class Inference Using a Data Dictionary

The core methodology proposed in this study focuses on implicitly inferring the object types based on their content and structure against a data dictionary. Alternatively, explicit methods can also achieve this association; they provide direct linkage information, simplifying the type identification process but potentially sacrificing some of the flexibility inherent in a purely schema-agnostic approach. Table 3 summarizes several explicit identification methods with advantages and disadvantages of each method.

Table 3. Advantages and disadvantages of object type identification methodologies.

	Advantages	Disadvantages
Explicit Identification via Embedded Metadata	Provides a direct and clear identification of the object’s type; allows receiving systems to quickly find the class definition by checking a single known field.	All parties must agree on the specific metadata keys to be used (e.g., @type); can reintroduce a degree of structural rigidity, reducing the flexibility of schema-less data.
Contextual Identification via Wrapping Structures	Structures data by logically grouping objects of the same type; keeps individual objects free from explicit metadata fields, focusing purely on their properties.	Imposes a stricter overall data structure, which limits flexibility; becomes difficult to use when objects of diverse types must be intermingled in the same list.
External Identification via Manifest Files	Keeps the primary data files clean and lean, containing only property data; clearly separates instance data from their classification metadata.	Adds the complexity of managing and linking multiple files (data and manifest); requires systems to correlate information from separate files to determine object types.
Implicit Identification via Member Matching	Allows for processing data even when they lack any explicit type information; aligns well with the dynamic and unpredictable nature of data from distributed sources.	High potential for misclassification, especially when different classes share similar member names; accuracy is degraded by inconsistent naming, missing members, or unexpected “noise” keys; accurate matching logic often requires incorporating domain-specific knowledge.

Building upon the previously discussed implicit identification techniques, this section introduces enhancements designed to mitigate uncertainties and improve the accuracy and reliability of inferring the class types from schema-less data by refining both the underlying knowledge base and the matching logic. The approaches proposed here focus on improving the inference accuracy without resorting to ML, instead relying on enriching the explicit, human-curated data dictionary and refining rule-based inference mechanisms.

Refining the logic used to infer the object types and matching them with the dictionary definitions is crucial for improving the accuracy. This involves moving beyond simple comparisons and incorporating sophisticated evaluation techniques.

To provide an objective measure of how well a given JSON object aligns with a specific dictionary class definition, the match between them is quantified using several metrics and combined into a final score, typically ranging from 0 to 1 (or 0% to 100%). The definitions of the mathematical notations used to express the scoring procedure are as follows:

-

J is the input JSON object.

-

C is a candidate class definition from the data dictionary.

-

Keys(J) is the set of keys present in the JSON object J.

-

Members(C) is the set of all the members (attributes) defined for class C in the dictionary.

-

MatchedMembers(J, C) is the subset of Members(C) for which a corresponding key exists in Keys(J) (considering synonym mapping).

MatchedMembers(J, C) = {m ∈ Members(C)|∃ k ∈ Keys(J) such that k maps to m}.

-

ConformingMembers(J, C) is the subset of MatchedMembers(J, C), where the value associated with the corresponding key in J conforms to the constraints (type, format, range, unit, etc.) specified for the member m in the dictionary definition C.

-

NoiseKeys(J, C) is the subset of Keys(J) that does not map to any member in Members(C).

NoiseKeys(J, C) = {k ∈ Keys(J)|¬∃ m ∈ Members(C) such that k maps to m}.

-

|S| denotes the cardinality (number of elements) of a set S.

-

Coverage (Score_Cov): Calculate the percentage of members defined in the dictionary (especially mandatory members) that are present in the JSON object.

$$Scor{e}_{Cov}\left(J,C\right)={\displaystyle \frac{\left|MatchedMembers\left(J,C\right)\right|}{\left|Members\left(C\right)\right|}}if\left|Members\left(C\right)\right|>0,else0$$

(1)

Weights can be applied based on member importance.

-

Accuracy/Conformance (Score_Acc): Measure how well the values of the members present in the JSON object conform to the specifications (type, format, unit, range, enum, etc.) in the dictionary.

$$Scor{e}_{Acc}\left(J,C\right)={\displaystyle \frac{\left|ConformingMembers\left(J,C\right)\right|}{\left|MatchedMembers\left(J,C\right)\right|}}if\left|MatchedMembers\left(C\right)\right|>0,else1$$

(2)

Penalties can be adjusted for mismatches.

-

Redundancy/Noise (Score_Noise): Quantify the proportion of members present in the JSON object that are not defined in the dictionary class definition. A higher noise score generally indicates a poorer match.

$$Scor{e}_{Noise}\left(J,C\right)={\displaystyle \frac{\left|NoiseKeys\left(J,C\right)\right|}{\left|Keys\left(J,C\right)\right|}}if\left|Keys\left(J\right)\right|>0,else1$$

(3)

This score typically acts as a penalty in the final calculation.

-

(Optional) Semantic Fit: Incorporate a score reflecting the semantic similarity between key names, even if they do not exactly match. Inferred meanings that align well can contribute positively to the score.

The final match score (Score_Final) is calculated by combining the individual metric scores using weights that reflect their relative importance.

$${Score}_{Final}\left(J,C\right)=w_{Cov}·{Score}_{Cov}\left(J,C\right)+w_{Acc}·{Score}_{Acc}\left(J,C\right)-w_{Noise}·{Score}_{Noise}\left(J,C\right),$$

(4)

where w_Cov, w_Acc, and w_Noise are non-negative weighting factors (≥0) assigned to the Coverage, Accuracy, and Noise scores, respectively.

These weights represent the emphasis placed on each aspect of the match. They are configured based on the specific priorities of the application. For example:

-

If the primary objective is to ensure that all the expected data fields are present (completeness), then w_Cov is assigned a relatively high value.

-

If the correctness of the values for the present fields (precision) is more critical, w_Acc has a higher weight.

-

w_Noise determines the penalty applied for extraneous keys present in the JSON object but not defined in the dictionary class.

The calculated final score provides an objective measure of how well a JSON object satisfies the requirements of a specific dictionary definition, even in the absence of explicit type information.

During score calculation, weights can be added to differentiate more critical members (e.g., higher weights for mandatory members or key indicators). Weights can also be used to indicate missing non-mandatory members or the presence of significant “noise” (undefined members). Additionally, a “confidence score” can be derived along with the inferred type to quantify the certainty of the inference.

3.4. Validation Framework for Dynamic Data

Effective validation of dynamic data, particularly in a schema-agnostic context, necessitates the definition of specific metrics to quantitatively assess their structural integrity, completeness, and accuracy against the expectations set by the data dictionary and domain knowledge. Section 3.3 explained the calculation of match scores based on various comparison factors. The present section outlines a framework for evaluating the quality and conformity of dynamic data objects during the validation process described later in Section 3.4.3.

The methodology presented in the previous sections is described in the following sequential steps. Broadly speaking, the process involves establishing and managing a data dictionary, which serves as an authoritative semantic reference. Subsequently, dynamic data objects are generated by the source systems, wherein the metadata are potentially embedded or packaged according to agreed-upon conventions and then shared or aggregated. Upon reception, the core validation and inference engine utilizes the prepared dictionary to interpret the intended meaning of an object, assess its quality against the defined metrics, and determine its suitability for downstream use. Figure 1 illustrates the data exchange process.

Figure 1. Overall process flow of the dynamic data exchange framework.

3.4.1. Preparation Phase: Data Dictionary Construction and Management

The first step involves the construction and management of a data dictionary. Based on a selected standard classification system (such as OmniClass, UniClass, KCCS, or a project-specific adaptation), precise definitions must be established for each relevant class (representing concepts or object types) and its associated members (attributes or properties). Table 4 describes the information fields required for each entry in the dictionary.

Table 4. Structure of the data dictionary.

Column Name	Description	Applies To 1	Notes
Entry ID 2	A globally unique identifier for this specific dictionary entry (row). Could be a URI, UUID, or another unique scheme.	Both	Primary key for the dictionary table.
Entry Type 3	Specifies whether this row defines a “Class” or a “Member.”	Both	Determines the interpretation of other columns in this row.
Parent Class ID 4	If Entry Type is “Member,” this contains the Entry ID of the Parent Class this member belongs to.	Member	Null/empty if Entry Type is “Class.” Links Member to its Class.
Key Name 5	If Entry Type is “Member,” this is the standardized key/name used in data instances (e.g., JSON key).	Member	Null/empty if Entry Type is “Class.”
Human-Readable Name	A user-friendly name for the Class or Member (potentially multilingual).	Both	E.g., “Reinforced Concrete Beam”, “Element Length.”
Description	Detailed explanation of the Class concept or the purpose and meaning of the Member.	Both	Provides semantic context.
Semantic Synonyms	If Entry Type is “Member,” lists alternative names/abbreviations mapping to the Key Name.	Member	Null/empty if Entry Type is “Class.” Aids in robust key matching.
Data Type 5	If Entry Type is “Member,” specifies the expected data type (e.g., string, number, Boolean, object, array).	Member	Null/empty if Entry Type is “Class.”
Mandatory Status 5	If Entry Type is “Member,” indicates if this member is mandatory (“True”) or optional (“False”) for its Parent Class.	Member	Null/empty if Entry Type is “Class.”
Format Constraint	If Entry Type is “Member,” defines specific format rules (e.g., regex, ISO date).	Member	Null/empty if Entry Type is “Class.”
Unit of Measure	If Entry Type is “Member” and Data Type is numeric, specifies the expected unit (e.g., m, kg, MPa).	Member	Null/empty otherwise.
Enumerated Values	If Entry Type is “Member,” lists permissible values if it is an enumerated type.	Member	Null/empty otherwise.
Nested Structure	If Entry Type is “Member” and Data Type is object/array, defines the expected structure/cardinality of the nested element(s).	Member	Null/empty otherwise.
Discriminative Wt.	If Entry Type is “Member,” indicates its importance weight for class inference.	Member	Null/empty if Entry Type is “Class.”
Coverage Wt.	If Entry Type is “Member,” indicates its weight for quality score calculation (esp. if mandatory).	Member	Null/empty if Entry Type is “Class.”
Version Info	Information about the version of this dictionary entry (e.g., creation date, modification date, version number).	Both	Important for dictionary management.

¹ Indicates whether the column is applied to class items, member items, or both. ² Member can also have unique identifiers; if multiple members share the same name, their unique identifiers must be differentiated. ³ Explicitly distinguishes whether the entry is a class or a member. ⁴ Only used in rows of type “Member.” For rows of type “Class,” this value is empty. ⁵ Attributes that apply only to members are treated as null or empty values in rows where Entry Type is “Class.”.

The data dictionary must provide version information to allow for the tracking of changes and ensure that the consuming systems can reference the correct version. Furthermore, mechanisms must be established to ensure the accessibility of the dictionary to all participating systems involved in data sharing and validation. This typically involves providing access via API endpoints, shared libraries, or dedicated registry services.

3.4.2. Data Generation and Sharing Phase

Following the preparation of the Data Dictionary, the next phase involves the generation and subsequent sharing of dynamic data objects. Schema-less JSON data objects are generated that typically reflect the specific viewpoints or requirements of different project domains or disciplines. This process often involves exporting information from the existing specialized software systems or capturing data from sensors and other sources.

To facilitate interpretation by the recipient, the data originator can choose to perform its own preliminary type inference and calculate the match scores for the generated data against the relevant dictionary definitions before transmission. The results of this pre-validation, such as the inferred type and its confidence level, can be captured as metadata accompanying the data.

The generated JSON data objects, along with any accompanying metadata, are then prepared for transmission. Although various transmission methods can be employed, the core JSON data can be packaged with the associated metadata that provide the essential context. These metadata may include the following:

• Dictionary Context Information: Details specifying the classification system(s) and version(s) of the Data Dictionary that were used as the basis for generating the data or are intended to be used for its interpretation (e.g., {“dictionaryRefs”: [“KCCS_v2.1”, “UniClass2015_v1.8”]}). This ensures that the recipient uses the correct semantic reference framework.
• Inference Results of the Sender (Optional): The outcome of any preliminary type inference performed by the sender, potentially including the most likely class type and an associated confidence score (e.g., {“senderInferredType”: {“type”: “KCCS:11-22-33”, “confidence”: 0.92}}). If provided, this information can serve as a suggestion or starting point for the independent inference process of the receiver but does not replace it.
• Match Score of the Sender (Optional): The match score calculated by the sender, quantifying the conformance of the data to the dictionary definition from the perspective of the originator (e.g., {“senderMatchScore”: 0.88}). When available, this score offers the receiver an initial indication of the data quality as assessed by the sender, although the receiver must perform its own comprehensive validation to make a definitive quality judgment.

3.4.3. Data Validation Phase—Reception and Evaluation

Upon receiving the data package, validation and interpretation commence, leveraging the previously established Data Dictionary to assess the incoming information. This evaluation process is central to ensuring the reliability and utility of schema-agnostic data exchange.

• Data Reception and Context Verification:
  The receiving system first ingests the data package, which includes dynamic JSON objects and the accompanying metadata. A critical initial action involves parsing the metadata to identify the specified data dictionary version(s) referenced by the sender. The system must ensure that it has the correct version of the dictionary, as this provides the essential semantic framework for all subsequent interpretation and validation tasks.
• Execution of Type Inference:
  For each received JSON object, the core-type inference algorithm, detailed in Section 3.3, is executed. By utilizing the loaded data dictionary, the algorithm analyzes the structure keys and potentially the values of the object to identify the most probable class definition(s) that it represents. Although the sender-provided indications may be available in the metadata, the receiving system performs this inference independently to arrive at an objective classification. This process typically yields one or more candidate class types, each associated with a calculated confidence or similarity score that reflects the strength of the match based on the inference logic.
• Initial Screening via Inference Results:
  The outcome of the type inference is subjected to a preliminary assessment. If the highest calculated confidence score for an object fails to meet a predefined minimum threshold (e.g., 0.7), or if the scores for the top two candidate classes are too close to distinguish reliably, the object may be flagged as “Type Ambiguous” or “Unclassifiable.” Such objects may be excluded from further automated processing or routed for manual inspection, thereby preventing erroneous interpretations downstream. The objects that pass this initial screening proceed with a provisionally assigned inferred type.
• Quantification of Match Degree:
  Following a successful type inference, the system performs a detailed quantification of the match degree between the actual JSON object and the specific definition of its inferred class within the data dictionary. This involves applying the comprehensive scoring mechanism described in Section 3.3, which calculates metrics, such as Coverage, Accuracy/Conformance, and Noise/Redundancy (as defined conceptually in Section 3.4.1). The system meticulously compares the object keys, conformance of its values (type, format, range, and unit), and structural characteristics against the dictionary requirements for the inferred class. This calculation yields individual scores for each metric and culminates in a single, comprehensive final match score (e.g., a value between 0 and 1 or 0–100%), objectively representing the overall conformance of the object to its inferred semantic definition.
• Final Validation Verdict:
  The calculated final match score is then compared against a predefined acceptance threshold (e.g., 0.8 or 80%) to determine the final validation outcome.

  -

  Validation Passed: If the score meets or exceeds the threshold, the object is considered successfully validated. It is typically marked as “Verified” or “Passed,” confirming its inferred type and deeming it sufficiently reliable for integration into downstream applications, analyses, or data stores.

  -

  Validation Failed/Review Required: If the score falls below the threshold, the object is flagged as “Validation Failed” or “Requires Review.” Critically, the individual metric scores (Coverage, Accuracy, Noise) calculated during the quantification of the degree of match provide valuable diagnostic information. By examining these sub-scores, users or automated systems can identify the specific reasons for the low overall score, such as missing mandatory attributes (low coverage), incorrect data value formats (low accuracy), and the presence of many unexpected fields (high noise). This allows for targeted troubleshooting or data cleansing.

• Utilization of Results:
  All results from the validation process, including the inferred class type, confidence score, final match score, individual metric scores, and final validation status (Passed/Failed/Review), are recorded for each data object. This information serves multiple purposes: generating data quality reports, enabling filtering or querying of data based on the validation status or quality scores, prioritizing data remediation tasks, and potentially providing insights to improve the upstream data generation processes.

3.5. Expected Benefits

The adoption of the proposed schema-agnostic methodology, grounded in dynamic data objects and semantic interpretation using a data dictionary, is expected to yield significant benefits for the exchange of construction information.

By moving beyond the constraints of rigid, predefined schemas, this approach enhances the semantic understanding of diverse data fragments originating from various sources, thus enabling a more flexible and adaptive integration environment.

Furthermore, the ability to quantitatively assess the data quality through objective match scoring promotes increased reliability and trust in shared information, facilitating early detection and remediation of errors or inconsistencies.

Ultimately, these improvements in data interoperability, semantic clarity, and verifiable quality are expected to contribute to a higher standard of data-driven decision-making throughout the project lifecycle.

4. Experimentation and Evaluation

4.1. Experiment Design

The experiment aims to validate the core components of the proposed methodology, specifically (1) the ability to accurately infer the class type of schema-less JSON objects representing construction components using dictionary-based member matching and (2) the effectiveness of the calculated degree of match (Coverage, Accuracy, Noise, Final Score) in reflecting the conformance of the object to its inferred dictionary definition.

For the experimental algorithms, software scripts were developed in C# to implement the core methodology:

• Loading and parsing the Data Dictionary.
• Ingesting and iterating through the objects in both JSON datasets.
• Executing the type inference algorithm (detailed in Section 3.3) based on member matching against the dictionary.
• Calculating the degree of match metrics (Coverage, Accuracy) and the final match score for each object against its inferred class definition (as per Section 3.3 and Section 3.4.3).

4.1.1. Datasets Used

The datasets used for the experiment were derived from the IFC sample datasets representing various facility types (buildings, bridges, and road sections). These are available online from the official GitHub websites of buildingSMART International [26,27].

Four JSON datasets were prepared from these sample datasets encoded in the STEP Physical File format (ISO-10303-21 [28]). They were converted to the JSON format, which generally conforms to ifcJSON, while maintaining the local object identifiers and references rather than embedding them explicitly. Although the datasets included explicit entity-type identifiers, they were not used in the type inference process. Table 5 provides a brief description of each dataset and Figure 2 shows screenshots of the rendered IFC model.

Table 5. Descriptions of the datasets.

Number	Original IFC File Name	IFC Schema Version	Number of Objects	Description
1	Duplex_A_20110907.ifc	2 × 3 TC1	33,510	A duplex house with MEP assemblies
2	construction-scheduling-task.ifc	4	246	Building walls and a slab; each element is assigned with scheduled construction tasks
3	Infra-Road.ifc	4.3 Addendum 2	887	Road parts; each part consists of multiple layers
4	Infra-Bridge.ifc	4.3 Addendum 2	883	Two generic road bridges

Figure 2. Rendered images of four sample IFC models from which JSON datasets were derived. Numbers shown in each subfigure correspond to the description items listed in Table 5.

4.1.2. Data Dictionary Construction

A data dictionary was constructed based on the principles outlined in Section 3.2.1. The dictionary was constructed by parsing the IFC schema and generating a subset of the items listed in Table 4. Through this process, the dictionary was populated with information on each entity type, supertype, and names and data types of its constituent members. Additionally, by exploiting the semantic information provided by the IFC schema, we extracted and converted it into the dictionary entry details of the required status of individual members, correctness of enumeration values, relationships and cardinalities among the entities, and accuracy of both the references and inverse references between the related entities.

Items not defined within the IFC schema, such as semantic synonyms and format constraints, were omitted from the dictionary. Furthermore, although the IFC schema explicitly specifies constraints for certain entity member values, these constraints were not applied in our experiments.

4.1.3. Experimental Procedure

The experiments were conducted on each sample dataset according to the following procedure:

• Convert the IFC file to JSON (ifcJSON-style type annotations included for result validation only).
• Run a software script to transform the EXPRESS schema (matching the IFC version of the dataset) into a dictionary.
• For each object of the dataset:
  • Compare the attribute names of the dynamic object against the data dictionary to extract the candidate entity types.
  • Eliminate any entity whose required properties are not present in the object from the candidate set.
  • Sort the remaining candidates in descending order by the number of attributes they share with the object (i.e., entities with a higher Score_Acc are ranked first). The inverse references are also counted as attributes.
  • Apply a higher weight (W_Acc) to attributes defined in the higher-level supertypes. The datasets used in these experiments contain no noise, and the weighted scores are not adjusted.
  • Report both the entity with the highest raw Score_Acc and that with the highest W_Acc-adjusted score as the inferred types and compare them against the true IFC entity type of the objects.

4.1.4. Evaluation Metrics

The performance of the methodology was assessed using the following metrics (Table 6):

Table 6. List of evaluation metrics used in the experiment.

Metric	Description
Exact Match Rate	The percentage of objects where the inferred class precisely matches the ground-truth class
Superclass Match Rate	The percentage of objects where the inferred class is a direct superclass of the ground-truth class in the dictionary hierarchy
Overall Success Rate	The sum of Exact Match Rate and Superclass Match Rate

4.2. Experimental Results

The outcomes of inferring the entity types for the individual objects in the sample JSON dataset using the data dictionary can be categorized as follows:

• The top-scoring candidate entity type exactly matches the actual entity type of the object (exact match).
• The top-scoring candidate corresponds to a supertype of the actual entity (e.g., the inferred candidate is IfcWall, where the true type is IfcWallStandardCase).
• There are multiple top-scoring (tied) candidates, one of which matches the actual entity type of the object (i.e., match among ties).
• Among multiple top-scoring ties, one candidate corresponds to a supertype of the actual entity (match with the supertype among the ties).
• None of the candidates match the actual entity type of the object (no match).

Table 7 and Figure 3 summarize the inference results for the JSON sample dataset. The dataset indices follow those presented in Table 4 and Figure 1. Each outcome simultaneously presents the inference results based solely on the unweighted Score_Acc (i.e., without any adjustment by W_Acc) and inference results based on the scores adjusted by W_Acc (i.e., weighted).

Table 7. IFC entity inference results for the sample JSON datasets.

JSON Dataset	Inference Method	Exact Match	Among Ties	Supertype Match	Supertype Among Ties	No. Match
Data 1 (Duplex, 33,510 objects)	Unweighted	26,358 (76.5%)	122 (0.4%)	0 (0%)	5393 (16.1%)	2357 (7.0%)
	Weighted	25,625 (76.5%)	532 (1.6%)	0 (0%)	4853 (14.5%)	2500 (7.5%)
Data 2 (Construction Schedule, 246 objects)	Unweighted	151 (61.4%)	10 (4.1%)	0 (0%)	5 (2.0%)	80 (32.5%)
	Weighted	151 (61.4%)	24 (9.8%)	0 (0%)	4 (1.6%)	67 (27.2%)
Data 3 (Infra-Road, 887 objects)	Unweighted	672 (75.8%)	117 (13.2%)	0 (0%)	17 (1.9%)	81 (9.1%)
	Weighted	662 (74.6%)	181 (20.4%)	0 (0%)	0 (0%)	44 (5.0%)
Data 4 (Infra-Bridge, 883 objects)	Unweighted	665 (75.3%)	102 (11.6%)	0 (0%)	40 (4.5%)	76 (8.6%)
	Weighted	682 (77.2%)	149 (16.9%)	0 (0%)	0 (0%)	52 (5.9%)

Figure 3. Graphical representation of the entity inference results.

4.3. Analysis and Discussion of the Results

The experimental evaluation yielded exact match success rates ranging from 61.4% (Dataset 2) to 76.5% (Dataset 1) across the four sample datasets. When considering the presence of the inferred entity type among multiple top-scoring candidates and allowing for matches to any supertype of that entity, the success rates increased to between 67.5% (Dataset 2, unweighted) and 95.0% (Dataset 3, weighted). In comparison with the methodology in a prior study by the authors [29], this represents an overall improvement: although the total matching rate (including supertypes) on Dataset 2 decreased slightly from 75.2% to 72.8%, the exact match rate improved substantially from 46.5% to 61.4%.

This performance gain appears to be attributable to the incorporation of accuracy measures semantically derived from the data model in addition to the leveraging of object-property coverage, as in the previous approach. When accuracy weights were applied to the hierarchical levels of the entity attributes, the exact match differences remained within 0.04–1.9%. However, under a more relaxed criterion that the correct type appears among the highest-scoring candidates, accuracy weighting yielded discriminative improvements of approximately 1.2–6.0% depending on the dataset.

We also observed that multiple top-scoring entity-type candidates occurred in many cases (from 0.4% in the unweighted analysis of Dataset 1 to 20.4% in the weighted analysis of Dataset 3). This tendency increased when hierarchical accuracy weights were applied, reflecting the highly structured nature of the IFC data model, where many entities share the same level in the hierarchy. However, this may likewise arise in any classification-based definition of dynamic objects. Notably, our experimental methodology does not apply the additional constraints defined in the IFC schema for entity selection. Incorporating such constraints into the matching process can further improve the inference accuracy by increasing the match probabilities and reducing the number of tied candidates.

In scenarios where dynamic objects are generated from classification schemes and their formats are inferred, additional constraints, such as those on the data scope presented in this paper, and reasoning based on the data labels (e.g., attribute names) may further enhance the discriminative power.

Overall, these results substantiate the core hypothesis of this study that for dynamic data adhering to the standard classification schemes, explicit schema information is not strictly necessary to infer the content by matching against a data dictionary. Nevertheless, applying this approach to practical environments requires supplementary constraints and refinement to ensure a robust performance.

5. Conclusions

This study presented a schema-agnostic methodology for exchanging digital construction engineering information, thereby addressing the limitations of traditional schema-bound approaches for handling the diversity and dynamism of data in modern projects. The following sections summarize the key findings and contributions of the study.

The practical value of this methodology stems from its potential to enhance the reliability of data sharing and integration in complex multidisciplinary construction projects. Collaboration among stakeholders is facilitated using diverse software tools and data formats by enabling the interpretation and validation of data without rigid schema enforcement. The objective quality assessment allows recipients to make informed decisions about data trustworthiness and to identify potential issues early. The expected advantages include improved semantic understanding of the shared data, increased confidence in data quality through quantitative metrics, and easier integration of data from various sources, potentially leading to improved project efficiency and outcomes. The systematic use of a dictionary also promotes explicit domain knowledge formalization and reuse.

Achieving and maintaining stakeholder consensus on the shared Data Dictionary and implementing robust governance for its versioning and evolution throughout a project represent significant practical and organizational hurdles. In addition, the reliance of the methodology on predefined dictionary rules limits its ability to accurately interpret or validate data patterns that are entirely novel or deviate significantly from established definitions, potentially requiring manual interventions or dictionary updates.

Future research should explore enhancing the inference accuracy by incorporating Natural Language Processing or word embedding models to better handle ambiguous terminology and subtle data variations. Interdisciplinary data sharing services such as Common Data Environment (CDE) is another area this study fits in; future research will provide mechanisms to ensure integrity of the data in such environments. Rigorous validations through large-scale case studies using diverse real-world construction project datasets with standardized data dictionaries are essential to assess the scalability of the methodology, its robustness against practical data imperfections, and its overall effectiveness in industry settings.