XMLType Type Tree for Uniform Data Typing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Object-relational database systems face challenges in efficiently executing XML queries due to the lack of a uniform mechanism for representing the type structure of XMLType instances from diverse data sources, leading to complex data typing and optimization issues.

Innovation Solution

The introduction of an XMLType type tree, which provides a universal format for representing the type structure of XMLType instances as a hierarchy of nodes, allowing for a single abstraction that simplifies data typing and query rewriting, regardless of the source or generation method of the XMLType instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple type representations are used for XMLType instances from diverse data sources, then the system can accommodate various XML generation methods, but the complexity of data typing and query optimization increases significantly

Engineering Contradiction:
Improveaccommodation of various XML generation methodsVSAvoidcomplexity of data typing and query optimization
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a universal XMLType type tree representation that can serve all XMLType instances regardless of their source or generation method. This single unified structure replaces the need for multiple specialized type representations, thereby maintaining adaptability while reducing the complexity of data typing and query optimization operations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent merges diverse type representations from different XML generation methods into a single unified XMLType type tree structure. By combining multiple representation approaches into one standardized format, the system simplifies data typing operations and query optimization while preserving the ability to handle various XML sources.

Inventive Principle:
Principle #5Merging (Combining)

2Device complexity

If a uniform type representation mechanism is introduced for all XMLType instances, then data typing and query optimization complexity is reduced, but the system loses flexibility in handling diverse XML generation methods

Engineering Contradiction:
Improvesimplicity of data typing and query optimizationVSAvoidflexibility in handling diverse XML generation methods
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The XMLType type tree is designed as a universal representation that can accommodate multiple XML generation methods through its flexible node structure. The tree can represent scalar elements, complex elements, attributes, and collections in a unified manner, maintaining both simplicity and adaptability simultaneously.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The XMLType type tree employs dynamic node types that can adapt to different XML structures. Each node can represent different XML constructs (elements, attributes, text, comments) depending on the specific XML generation method, allowing the uniform structure to flexibly handle diverse XML sources without losing adaptability.

Inventive Principle:
Principle #15Dynamics

3Measurement precision

If multiple type representations are maintained for different XML sources, then accurate type information is preserved, but query execution performance decreases due to handling complexity

Engineering Contradiction:
Improveaccuracy of type informationVSAvoidquery execution performance
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent combines type information from diverse XML sources into a single XMLType type tree representation. This merging process preserves the accuracy of type information through the detailed node structure while improving query execution performance by eliminating the overhead of handling multiple separate type representations.

Inventive Principle:
Principle #5Merging (Combining)

4Device complexity

If a single XMLType type tree representation is used for all XMLType instances, then handling complexity is reduced, but detailed type information from specific sources may be lost

Engineering Contradiction:
Improvehandling complexity of type representationsVSAvoidloss of source-specific type information
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The XMLType type tree employs a nested structure where parent nodes represent XML constructs and child nodes contain detailed type information. This nesting allows the unified representation to maintain detailed source-specific type information within the hierarchical structure while presenting a simplified interface for handling operations.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The type information is segmented into hierarchical nodes within the XMLType type tree, with each node representing a specific XML construct. This segmentation preserves detailed type information from specific sources in discrete units while allowing the overall structure to be handled as a single unified representation, reducing handling complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7685137B2Technique of using XMLType tree as the type infrastructure for XML
Publication Date: 2010.03.23 ORACLE INT CORP
  • US7685137B2 patent drawing
  • US7685137B2 patent drawing
  • US7685137B2 patent drawing

AI summary

A universal format is used to create a type representation of XMLType instances that are generated in various ways from various sources. An XMLType Type Tree is represented as a hierarchy of nodes, including leaf item node, composite item node, operator node, aggregate node, referred to herein as an XMLType Type Tree. An XMLType Type Tree serves as a digest of the type structure of XMLType, no matter the source of the XMLType instance or its manner of its generation and it creates one uniform abstraction of the type structure of XMLType for the data-typing analysis of XPath and XQuery during query compile time.