Markup Language Hierarchical Table Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Transmitting and parsing markup language files with complex hierarchical data structures are cumbersome and time-consuming due to the need to store and manage intricate parent-child relationships, which complicates the process of data transmission and parsing.

Innovation Solution

A method for storing hierarchical data as a markup language file by using markup tags and attributes to represent the position of cells within the table, allowing for efficient parsing without requiring knowledge of user-defined tags or hierarchical information, thereby simplifying the extraction of hierarchical data from the file.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hierarchical data is stored in a traditional markup language file structure, then the data structure and relationships are preserved, but the parsing process becomes cumbersome and time-consuming

Engineering Contradiction:
Improvedata structure preservationVSAvoidparsing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the hierarchical data into a flat table structure with explicit row and column index markers. Each cell is represented as a separate row with markers indicating its position in the hierarchical structure, allowing the parser to reconstruct the hierarchy by processing rows in sequence rather than parsing complex nested structures.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of storing hierarchical data in a nested structure that requires complex parsing, the patent inverts the approach by using a flat structure with positional markers. The hierarchy is implied through the order and positioning of rows rather than through explicit nested containers, making the parsing process simpler and faster.

Inventive Principle:
Principle #13The other way round (Inversion)

2Loss of information

If complex hierarchical structures are stored in markup language files, then complete data relationships are maintained, but the ease of operation and parsing is reduced

Engineering Contradiction:
Improvehierarchical relationship informationVSAvoidparsing ease
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The patent introduces intermediary markers (row index markers and column index markers) that act as mediators between the flat data structure and the hierarchical relationships. These markers carry the necessary positional information to reconstruct the hierarchy during parsing, eliminating the need for complex nested structures while preserving complete relationship information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the representation parameters of hierarchical data from nested structural elements to flat rows with positional markers. By encoding hierarchy information as attributes of individual cells (through row and column indices) rather than through structural nesting, the data becomes easier to parse while maintaining all hierarchical relationships.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If user-defined tags and hierarchical information are used in markup files, then data structure is accurately represented, but the complexity of device operation increases

Engineering Contradiction:
Improvedata structure representation accuracyVSAvoidparsing complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent uses a universal flat row structure that can represent any hierarchical data regardless of the specific user-defined tags or hierarchy levels. The standardized row-based format with row index markers and column index markers provides a multi-functional representation that works for various hierarchical structures without requiring parser complexity to handle different tag types or hierarchy depths.

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

Data Source

PatentUS8706783B2Storing hierarchical table as a markup language file
Publication Date: 2014.04.22 SAP SE
  • US8706783B2 patent drawing
  • US8706783B2 patent drawing
  • US8706783B2 patent drawing

AI summary

Various embodiments of systems and methods for storing a hierarchical table as a markup language file are described herein. Initially the position of the cells included in the hierarchical table may be identified. The position of the plurality of cells includes a first dimension coordinate and a second dimension coordinate. The first dimension coordinate is inserted as a markup tag in the markup language file. The second dimension coordinate is inserted as a markup attribute corresponding to the markup language file. One or more cells, corresponding to a first dimension of the hierarchical table is selected. Data included in the selected cells is identified and stored in the markup attribute inserted in the markup language file.