Markup Language Document Update via Hierarchical Graph Merging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual updating of large auto-generated markup language documents, such as API documentation, is time-consuming and error-prone, as users need to navigate through extensive content and repeat edits with frequent changes.

Innovation Solution

The technique involves merging the content of markup language documents with enhancement documents that specify updates, allowing users to override, append, insert, delete, or replace content compactly, and remerging these updates with changes to the original documents.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users manually edit large auto-generated markup language documents directly, then they can update content, but the process becomes extremely time-consuming and error-prone

Engineering Contradiction:
Improveaccuracy of manual updatesVSAvoidtime required for manual updates
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the large markup language document into a hierarchical structure of sections and subsections, allowing users to work with specific portions rather than the entire document. This segmentation enables targeted updates to only the necessary sections, reducing time and errors associated with manual editing of complete large-scale documents.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary processing system that acts as a mediator between the auto-generated markup language document and user edits. This intermediary automatically merges user modifications with the original document structure, eliminating the need for users to manually navigate and edit extensive content while maintaining accuracy through automated reconciliation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If auto-generated markup language documents are frequently rebuilt, then content remains current, but repeated manual edits are required

Engineering Contradiction:
Improvecompleteness of document contentVSAvoidrepetitive editing time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-structuring the markup language document into a hierarchical section framework before user editing occurs. This pre-established structure allows user modifications to be automatically integrated during rebuilds without requiring repeated manual editing, as the framework persists across regeneration cycles.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where user edits are captured and automatically merged back into the markup language document during subsequent rebuilds. This feedback loop ensures that content completeness is maintained while eliminating repetitive manual editing, as the system learns from and incorporates previous user modifications automatically.

Inventive Principle:
Principle #23Feedback

3Manufacturing precision

If users navigate through extensive document content to make updates, then precise edits can be made, but the complexity of the updating process increases

Engineering Contradiction:
Improveprecision of content updatesVSAvoidcomplexity of updating process
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent segments the document into a hierarchical structure with identifiable sections and subsections, allowing users to navigate to and edit specific segments without wading through entire documents. This segmentation maintains editing precision while reducing process complexity by limiting the visible scope to relevant sections only.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent transforms the flat, linear document structure into a hierarchical dimensional structure with multiple levels of sections and subsections. This dimensional change enables users to navigate and edit content through a structured hierarchy rather than linear scrolling, improving precision while simplifying the updating process through organized access points.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS12248749B1Content update by merging of markup language documents
Publication Date: 2025.03.11 BENTLEY SYSTEMS INC
  • US12248749B1 patent drawing
  • US12248749B1 patent drawing
  • US12248749B1 patent drawing

AI summary

In various example embodiments, techniques are provided for updating content of a markup language document. A software process receives a markup language document having one or more sections and a corresponding enhancement document that includes a plurality of commands describing updates to the markup language document. The software process converts the markup language document into a first hierarchical graph in which each section of the markup language document is arranged as a parent of any subsections of the respective section. The software process also converts the enhancement document into a second hierarchical graph including one or more of the commands. The software process merges the first hierarchical graph and the second hierarchical graph, the merging to apply commands of the second hierarchical graph to the first hierarchical graph to produce an updated hierarchical graph. The software process then outputs an updated markup language document based on the updated hierarchical graph.