XML Schema View Generation for Recursive Type Transformation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

XML schemas with recursive data types complicate transformations between XML datasets and non-hierarchical formats due to ambiguity in mapping levels of recursive structure, making simple mappings unclear and difficult to implement.

Innovation Solution

A method and system for generating a view of a schema that allows users to control the level of recursion by chunking instances of recursive elements, transforming recursive types into non-recursive structures, and encoding hierarchical information in attributes, enabling clear and efficient data transformation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If recursive type definitions are used in XML schemas to represent hierarchical data structures, then the ability to model complex nested relationships is improved, but the complexity of specifying transformations between XML datasets and non-hierarchical formats increases significantly

Engineering Contradiction:

Improveability to model nested relationshipsVSAvoidcomplexity of specifying transformations

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the recursive type definition into multiple non-recursive type definitions, each representing a specific level or aspect of the hierarchical structure. Instead of using a single recursive type that references itself, the schema breaks down the hierarchy into distinct type levels that can be transformed independently, eliminating the ambiguity of recursive mapping while preserving the hierarchical relationship through structured composition.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of a wrapper element or intermediate data structure that mediates between the hierarchical XML structure and the non-hierarchical target format. This intermediary captures the hierarchical relationships in a way that can be systematically transformed, acting as a bridge that resolves the complexity of direct recursive transformation while maintaining data integrity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If recursive elements are allowed in XML schemas to represent self-referential data structures, then the expressiveness of the schema is improved, but simple mappings become inherently ambiguous since it can be unclear which levels of recursive structure are being mapped

Engineering Contradiction:

Improveexpressiveness of schemaVSAvoidclarity of mappings

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent divides the recursive structure into discrete, non-recursive segments where each segment represents a specific level of the hierarchy. By segmenting the recursive type into multiple distinct type definitions with clear boundaries, the mapping process becomes unambiguous as each segment can be mapped independently without confusion about which recursive level is being addressed.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary action by pre-structuring the hierarchical data into a standardized intermediate format before transformation. This preliminary structuring establishes clear mapping rules in advance, so that when transformation occurs, there is no ambiguity about which levels are being mapped because the structure has already been organized to reflect the intended mapping relationships.

Inventive Principle:

Principle #10Preliminary action

3Extent of automation

If transformations are specified as mappings to and from types defined in XML schemas with recursive types, then automated transformation tools can be created, but the presence of recursive types makes it unclear which and how many levels of recursive structure are being mapped

Engineering Contradiction:

Improveautomated transformation toolsVSAvoidambiguity in mapping levels

Core Design Contradiction:

Extent of automationVSDevice complexity

Solution Approach 1:

The patent segments the recursive type hierarchy into multiple non-recursive type definitions, each with a clear and finite structure. This segmentation enables automated transformation tools to work effectively because each segment can be processed independently with deterministic mapping rules, eliminating the ambiguity that would otherwise prevent automation while preserving the hierarchical relationships through structured composition.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS10635646B2Generating a view for a schema including information on indication to transform recursive types to non-recursive structure in the schema

Publication Date: 2020.04.28 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

Provided are a computer program product, system, and method for generating a view for a schema. A schema provides a definition of elements, wherein at least one of the elements comprises a recursive element of a recursive data type, wherein the recursive data type allows for instances of the recursive element to include instances of that same recursive data type at different levels in a hierarchy. Indication is received to transform the recursive types to non-recursive structures. A view for the schema is generated including information on the indication to transform the recursive types to non-recursive structure, wherein the processing of the data defined by the view causes a parser to generate a structured element for each instance of the recursive element in schema data being parsed, wherein the generated structured element includes a unique identifier of the instance of the recursive element.