XML Schema Normalization for Object Impedance Mismatch
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is an impedance mismatch between the loose structure of XML documents and the more structured world of object-oriented programming languages, leading to cumbersome and limited bridging mechanisms, such as XML Document Object Model and XML Serialization, which can result in inappropriate nesting and an unreasonable number of object types if not properly managed.
Innovation Solution
A normalization component that evaluates nesting scopes and analyzes subtyping hierarchies to normalize XML schemas at the schema level, facilitating more organized object models and enabling automated transformations to enhance object-oriented programming by normalizing XML expressions and embedded expressions, thereby mitigating impedance mismatch and 'XSD-isms'.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional bridging mechanisms (XML Document Object Model or XML Serialization) are used to map XML to object-oriented programming, then the impedance mismatch between XML's loose structure and structured programming is bridged, but the resulting object models become cumbersome and limited in functionality with inappropriate nesting and unreasonable number of object types
Solution Approach 1:
The patent applies preliminary action by performing schema-level normalization before the actual XML-to-object mapping process. The normalization component analyzes and reorganizes XML schemas in advance, evaluating nesting scopes and analyzing subtyping hierarchies to produce normalized schemas that are more suitable for object-oriented mapping. This preliminary organization prevents the generation of cumbersome object models with inappropriate nesting, as the schema is prepared in an optimal structure before mapping occurs.
Solution Approach 2:
The patent introduces a normalization component as an intermediary between the XML schema and the object-oriented mapping process. This intermediary component transforms the original XML schema into a normalized form that bridges the gap between XML's loose structure and structured programming requirements. The normalization component acts as a mediator that reorganizes the schema to produce more reasonable object models, avoiding the direct mapping problems that occur with conventional approaches.
2Productivity
If naïve mapping is performed without schema-level normalization, then the mapping process is simpler and faster, but unexpected object models result with inappropriate nesting and unreasonable number of object types
Solution Approach 1:
The patent performs schema-level normalization as a preliminary action before mapping, which organizes the XML schema structure in advance. This preliminary organization enables the subsequent mapping process to proceed efficiently while generating high-quality object models. The normalization component evaluates nesting scopes and analyzes subtyping hierarchies beforehand, so that the actual mapping operation can be performed quickly without compromising object model quality.
Solution Approach 2:
The normalization component performs self-service by automatically analyzing and reorganizing the XML schema without requiring manual intervention. It evaluates nesting scopes and analyzes subtyping hierarchies autonomously, transforming the schema into an optimized form that produces reasonable object models. This automated self-service approach maintains mapping productivity while significantly improving object model quality compared to naïve mapping.
Data Source
AI summary
Systems and methods that facilitate mapping from an XML schema to an object model, while mitigating object impedance mismatch. A normalization component can flatten nesting scopes and/or and reduce the number of types in subtyping hierarchies, and a core mapping component can supply the object type. A subsequent object level transformation can typically be performed on the object model, to create the final object model.