Declarative Data Transformation Architecture for Incompatible Interfaces
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for data exchange between computer systems with mutually incompatible interfaces and proprietary data formats require adapters or complex standardization, limiting flexibility and efficiency.
Innovation Solution
A declarative data transformation architecture using semantic data information models, interface annotations, and data information model mapping, facilitated by technologies like RDF, JSON-LD, OWL, and SHACL/SPARQL, enables flexible data processing across incompatible interfaces without the need for dedicated adapters.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If adapters are used to translate between incompatible interfaces, then data exchange between computer systems is enabled, but device complexity and maintenance effort increase
Solution Approach 1:
The patent implements a universal data exchange format that can be used across multiple incompatible interfaces without requiring separate adapters for each interface combination. The format defines a common structure with fields for data type identification, units, and values that can represent various physical quantities (temperature, pressure, flow rate, etc.), enabling one format to serve multiple translation purposes that would otherwise require multiple specialized adapters
Solution Approach 2:
The patent introduces a standardized data format as an intermediary representation layer between incompatible interfaces. Instead of directly translating from interface A to interface B through complex adapters, data is first converted to the standardized format which serves as a common mediator, then converted to the target interface format. This intermediary approach simplifies the translation process and reduces overall system complexity
2Adaptability or versatility
If proprietary data formats are used at each interface, then interface flexibility is maintained, but interoperability between systems deteriorates
Solution Approach 1:
The patent applies local quality by allowing each interface to maintain its proprietary characteristics and data representation methods locally, while introducing a standardized format that captures the essential semantic information (data type, units, values) in a universally interpretable way. This enables each interface to preserve its local flexibility while the standardized format ensures reliable interoperability through common semantic understanding
3Reliability
If standardization is implemented for data exchange formats, then interoperability improves, but implementation effort and time increase
Solution Approach 1:
The patent establishes a predefined standardized data exchange format with clearly defined structures for different data types (temperature, pressure, flow rate, etc.), including field definitions, data type identifiers, and unit specifications. This preliminary standardization work is done once and can be reused across multiple interface integrations, significantly reducing the time and effort required for subsequent implementations compared to creating custom translation solutions for each case
Data Source
Figure 1
Figure 2
Figure 3
AI summary
To transmit data (DT) between a sending computer system (CSs) and a receiving computer system (CSE) via mutually incompatible interfaces, a transmit interface (SS) of the sending computer system for transporting the data in a transmit data format (SDTF) and a receive interface (ES) of the receiving computer system for transporting the data in a receive data format (EDTF), so that the exchanged data can be further processed on the receiving side even when using proprietary, non-standardized interfaces of the computer systems involved in the data exchange, it is proposed that to create a declarative data transformation architecture (DTTA) for processing data information to be recognized and transported with the data transmission (DTI, DTISDTF) (ezg) by Data information models (DTIMSS, DTIMES) of the interfaces are semantically described (bsc) and interface-related data information semantics are defined in the "Resource Description Framework". <rdf>"-Formats (F1, F2) are documented (dkm)," <ii>Interface annotation (SSA, ESA) for rule-based description of a mapping of the data information to be transported onto the interface-related, semantic data information model is implemented (ipl). <iii>a data information model mapping (DTIM-M) is implemented for rule-based "DIMSS to DTIMES" mapping of the data information models, and The data transformation architecture-based processing of data information (DTISDTF) in the sending data format up to recognized, equivalent data information (DTIEDTF) in the receiving data format is carried out using the data information models and the integration of the RDF formats, the interface annotation and the data information model mapping. </iii> </ii> </rdf>