XSLT Mapping Tool Single-View Interface for Node Transformation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mapping tools for XML source and target documents using XSLT transformations are limited in displaying node mappings due to the presence of templates, making it difficult for users to understand how source nodes are transformed into target nodes without delving into the specifics of the XSLT code.

Innovation Solution

An XSLT mapping tool is developed that presents an interface showing direct mappings between source and target nodes, hiding the XSLT template code, and allowing users to view the source and target structures, with the option to see the specific template code for each mapping, using a web-based graphical user interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If XSLT templates are displayed in mapping tools, then users can see the transformation code, but users cannot efficiently determine node mappings without delving into code specifics

Engineering Contradiction:
Improveease of determining node mappingsVSAvoidcomplexity of displaying templates
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the mapping relationship information from the XSLT template code and presents it separately in a graphical interface. The mapping tool displays source nodes, target nodes, and their connections without requiring users to read or parse the underlying XSLT templates, thus separating the mapping visualization from the transformation code.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary graphical user interface that mediates between the XSLT templates and the user. This interface layer translates the template-based transformation logic into visual node mappings, allowing users to understand the transformation without interacting with the complex template code directly.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If XSLT template code is hidden in mapping tools, then users can view mappings more simply, but users cannot see the specific template code for each mapping

Engineering Contradiction:
Improvesimplicity of viewing mappingsVSAvoidloss of template code information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent segments the information display into different levels: a primary graphical view showing node mappings, and a secondary detailed view showing the corresponding XSLT template code. Users can navigate between these levels through expandable/collapsible elements or separate panels, allowing them to access template information only when needed without cluttering the main mapping view.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a dynamic interface where the level of detail can be adjusted. The mapping display can transition between a simplified node connection view and a detailed template code view, allowing users to adapt the information density according to their needs. This dynamic reconfiguration enables both simplicity and comprehensive information access.

Inventive Principle:
Principle #15Dynamics

3Loss of information

If mapping tools display both source and target structures, then users can understand transformation context, but the interface becomes more complex

Engineering Contradiction:
Improvecompleteness of transformation contextVSAvoidcomplexity of interface structure
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent employs a nested structure where source nodes, target nodes, and their mappings are organized in a hierarchical manner. The graphical interface can display the source document structure, target document structure, and the mapping relationships between them in a nested arrangement, allowing users to understand the transformation context without requiring a completely separate complex interface for each element.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS9372837B2Single view representation of an XLS transformation
Publication Date: 2016.06.21 ORACLE INT CORP
  • US9372837B2 patent drawing
  • US9372837B2 patent drawing
  • US9372837B2 patent drawing

AI summary

In various embodiments, arrangements for presenting an XSLT mapping tool is presented. A computer system may receive XML source code that includes a plurality of source nodes. The computer system may also receive XSLT code configured to transform the XML source code into XML target code. The XSLT code may include multiple templates. The computer system may use the multiple templates of the XSLT code and the XML source code to create XML target code. The XML target code may include a plurality of target nodes. An interface of the XSLT mapping tool that displays mappings between the plurality of source nodes of the XML source code and the plurality of target nodes of the XML target code resulting from the multiple XSLT templates may be presented.