Ontology-Driven Inter-Program Communication System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional applications face rigidity and inflexibility when adapting to new data types, requiring extensive changes to database schemas, storage procedures, and user interfaces, leading to resource-intensive revisions and challenges in handling disparate data representations.
Innovation Solution
An ontology-driven system that updates business semantics and rules for storing and displaying new data types, automatically generating new columns in databases and communicating data through browsers, eliminating the need for manual code changes and multiple databases.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional database schemas and storage procedures are used, then data storage and retrieval are straightforward, but the system becomes rigid and requires extensive manual changes when adapting to new data types
Solution Approach 1:
The patent introduces an ontology as an intermediary layer between the database schema and the application logic. This ontology serves as a mediator that captures business semantics, data relationships, and display rules, allowing the system to adapt to new data types by updating the ontology rather than directly modifying complex database schemas and storage procedures.
Solution Approach 2:
The patent segments the data management system into distinct components: the ontology layer (containing business semantics and rules), the database layer (for data storage), and the application layer (for data processing). This segmentation allows independent updates to the ontology without requiring comprehensive changes to the entire system architecture.
2Adaptability or versatility
If manual code changes are made to accommodate new data types, then the database can store new information, but significant resources are spent on maintaining databases and applications
Solution Approach 1:
The patent implements a self-service mechanism where the ontology automatically generates and updates the necessary database schemas, storage procedures, and application logic based on the defined business semantics and data relationships. This automation eliminates the need for manual code changes and reduces the resources required for maintaining databases and applications when integrating new data types.
Solution Approach 2:
The patent performs preliminary action by pre-defining the ontology structure, business semantics, and transformation rules before actual data integration occurs. This advance preparation enables the system to automatically handle new data types without requiring reactive manual interventions, thereby improving resource efficiency.
3Adaptability or versatility
If multiple databases are used to handle disparate data representations, then data flexibility is improved, but memory requirements increase and processor efficiency decreases
Solution Approach 1:
The patent creates a universal ontology layer that can represent and manage multiple disparate data types and formats within a single unified framework. This ontology serves multiple functions: it defines business semantics, establishes data relationships, generates storage procedures, and controls data display. By using this single multi-functional ontology instead of multiple specialized databases, the system reduces memory requirements while maintaining the ability to handle diverse data representations.
Data Source
AI summary
In one embodiment, a method for providing secure and flexible inter-program communication includes storing an ontology in a first data store, the ontology includes a plurality of business semantics for an application, a plurality of rules for storing data in a database, and a plurality of rules for displaying the data in a browser. The method further includes receiving a new data type to add to the database and updating the ontology to describe the new data type. Updating the ontology includes updating the plurality of rules for storing the new data type in the database and updating the plurality of rules for displaying the new data type in the browser. In response to updating the ontology, generating a new column for the new data type in the database and communicating the new data type for presentation in the browser.