Schema Fragment Composition for Custom Object Definition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional ticketing frameworks lack the ability to define custom objects using multiple schema fragments and suffer from naming conflicts when multiple users attempt to add custom fields to the same object class.
Innovation Solution
The proposed solution allows for the definition of custom objects using multiple schema fragments, each containing custom data fields. These fragments can be combined to create a single object, and they are labeled based on the type of custom fields they contain, preventing field name conflicts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple users add custom fields to the same object class in conventional ticketing frameworks, then customization capability is improved, but naming conflicts occur and system reliability deteriorates
Solution Approach 1:
The patent segments the schema definition into multiple independent schema fragments, where each fragment represents a portion of the custom fields. This segmentation allows different users to define fields in different fragments without naming conflicts, while the system composes the complete schema by combining these fragments. The segmentation resolves the contradiction by enabling customization at the fragment level while maintaining system-wide reliability through controlled composition.
Solution Approach 2:
The patent introduces schema fragments as intermediary entities between users and the final object schema. These fragments act as mediators that isolate naming spaces, allowing multiple users to contribute custom fields without direct conflicts. The system serves as an intermediary that composes these fragmented definitions into a unified schema, resolving naming conflicts automatically and maintaining reliability while preserving customization capability.
2Ease of operation
If conventional ticketing frameworks allow custom fields per object class, then user needs are met, but field name conflicts arise when multiple users define fields with the same name
Solution Approach 1:
By segmenting the custom field definitions into separate schema fragments, the patent eliminates naming conflicts that would otherwise require complex management. Each fragment operates in its own namespace, allowing users to define fields with the same name in different fragments without conflict. The system automatically composes these fragments, reducing the complexity of naming conflict management while continuing to meet user needs.
Solution Approach 2:
The patent resolves naming conflicts by adding a new dimension to the field naming space - the schema fragment identifier. Instead of relying solely on unique field names within a single namespace, the system uses the combination of fragment ID and field name to uniquely identify each field. This dimensional change eliminates conflicts while maintaining ease of operation for users.
3Stability of the object's composition
If the system updates all objects when a schema fragment changes, then data consistency is improved, but system performance and productivity deteriorate due to high computational load
Solution Approach 1:
Instead of updating all objects that reference a schema fragment when it changes (excessive action), the patent implements selective updates based on actual usage. The system performs partial updates only for objects that are actively using the changed fragment, determined through lazy evaluation and on-demand composition. This approach maintains data consistency where needed while preserving system performance by avoiding unnecessary updates.
Solution Approach 2:
The patent implements a lazy update mechanism where schema fragment changes do not immediately propagate to all objects. Instead, objects compute their current schema composition on-demand by querying the current state of referenced fragments. This self-service approach allows the system to maintain data consistency through accurate on-demand composition while avoiding the performance penalty of forced immediate updates across all objects.
Data Source
AI summary
Disclosed is a computer implemented method to define schema fragments (also known as fragment(s)) that comprise multiple custom data fields wherein each fragment can be used to add custom data fields to multiple objects. In accordance with the present specification, a single object is defined by multiple custom data fields from multiple schema fragments. Each schema fragment is defined by a set of custom fields representing similar kind of data fields (like tenant data field, custom data filed, application data fields). Each schema fragment can define multiple objects from multiple schemas.