Dynamic Schema Semantic Exposure via Intermediary Views
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current master data management systems do not provide semantic exposure of data stored in dynamic schemas, limiting external applications' ability to access and understand data using standard query languages like SQL, as they require schema awareness and do not support dynamic schema changes.
Innovation Solution
A system and method that determines the schema from metadata, generates database views, and updates them upon schema changes, allowing external applications to access data in a semantically accurate format through standard SQL queries while maintaining read-only access and client-specific views.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a master data management system uses a dynamic schema that is fully extensible and customizable, then the system's adaptability and versatility are improved, but external applications using standard query languages cannot access the data because they require schema awareness and do not support dynamic schema changes
Solution Approach 1:
The patent introduces an intermediary layer (view generation mechanism) between the dynamic schema and external applications. This intermediary automatically generates database views that translate dynamic schema structures into standardized access patterns, allowing external applications to query data using standard SQL without needing to understand or adapt to schema changes. The intermediary resolves the contradiction by decoupling the flexibility of the dynamic schema from the rigidity requirements of standard query languages.
Solution Approach 2:
The patent segments the data access interface into two distinct layers: the dynamic schema layer (internal flexibility) and the standardized view layer (external accessibility). By dividing the access path into these segments, the system maintains schema extensibility internally while presenting a stable, standardized interface externally through generated views, thus resolving the contradiction between adaptability and ease of operation.
2Reliability
If the system exposes data through an API to maintain complete control and handle data in a proprietary schema, then data consistency and control are improved, but semantic exposure of data in a standard protocol understood by external applications is lost
Solution Approach 1:
The patent uses database views as an intermediary that preserves the proprietary schema internally while exposing semantic meaning externally. The views act as a translation layer that maintains data consistency through controlled access patterns while simultaneously providing semantic exposure in standard SQL format that external applications can understand and utilize, thus resolving the contradiction between control and semantic exposure.
3Productivity
If hard-coded queries relying on a schema are used to access data, then query performance is improved, but the queries become inadequate when schema changes occur because applications must be aware of any schema changes
Solution Approach 1:
The patent implements dynamic view generation that automatically adapts to schema changes. Instead of static hard-coded queries, the system dynamically generates views based on the current schema state, allowing queries to maintain optimal performance while automatically adapting to schema evolutions without requiring application modifications.
Solution Approach 2:
The system incorporates feedback mechanisms that monitor schema changes and automatically trigger view regeneration. This feedback loop ensures that queries continue to perform efficiently while adapting to schema changes, resolving the contradiction between query performance and schema adaptability.
Data Source
AI summary
A system and method for providing semantic access of data in a master data management system. Data stored in a dynamic repository schema is exposed in a semantically accurate format. The schema is determined from information received from the master data management system describing the schema. A set of database views is generated based on said schema. A query from an external application in a standard query language is received and the query is performed using at least one database view. The database views are updated when a schema change is detected.