Dynamic Metadata Adaptation for Native Encoding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing metadata systems face inefficiencies in retrieving and applying the correct metadata files due to the need for multiple metadata files to accommodate different metadata types, leading to complexities in metadata management and retrieval.
Innovation Solution
A system that dynamically adapts metadata for native data encoding by instantiating a metadata reader to detect and modify non-native metadata encodings into native formats, using a type reference table to substitute types and provide appropriate metadata definitions based on consumer requests, allowing for efficient translation and presentation of metadata to different consumers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple metadata files are stored to provide different metadata types for different users, then the system can accommodate diverse user expectations and metadata requirements, but the complexity of retrieving and applying the correct metadata file increases
Solution Approach 1:
The patent implements a universal metadata file that can serve multiple different metadata types through dynamic adaptation. Instead of maintaining separate metadata files for different users and metadata types, a single metadata file is designed to be adaptable to various consumers' expectations through runtime type substitution and dynamic content generation, making one file perform the function of multiple specialized files
Solution Approach 2:
The system employs dynamic metadata adaptation where the metadata file can change its presentation and structure at runtime based on the consumer's type expectations. The metadata reader dynamically substitutes types and adapts the metadata content according to which consumer is accessing it, allowing the same underlying metadata to serve multiple purposes without requiring static pre-processing into multiple files
2Loss of information
If multiple metadata files are maintained for different metadata types, then comprehensive metadata coverage is achieved, but the time and resources required to retrieve and apply the correct metadata file increase
Solution Approach 1:
The patent merges multiple metadata types into a single unified metadata file structure. Instead of storing separate files for different metadata types, all metadata information is consolidated into one file that can be retrieved in a single operation. The system then dynamically adapts this unified metadata to present appropriate views to different consumers, eliminating the need to retrieve and switch between multiple separate files
Solution Approach 2:
The system performs preliminary organization of all metadata types within a single file structure during the metadata definition phase. By pre-organizing the unified metadata file to contain all necessary type information and relationships, the system enables rapid retrieval without requiring subsequent complex file switching or concatenation operations when serving different consumers
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Embodiments are directed to dynamically adapting metadata for use with a native data encoding and to efficiently modifying object model type references. In one scenario, a computer system instantiates a metadata reader over an object model description to access various portions of metadata in the object model description. The metadata reader is configured to read native metadata, where native metadata is metadata represented in an encoding that is expected by the metadata reader. The metadata reader determines that the accessed metadata is encoded in a non-native encoding and then determines which metadata modifications are to be performed to transform the non-native encoding into a native encoding. The computer system then dynamically adapts the metadata of the object model from a non-native encoding to a native encoding according to the determined modifications. As such, the object model is readable by a native runtime.