Markup Language Document Preparation via Entity Class Linking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for preparing documents in markup languages for user interfaces in computer information systems are time-consuming and resource-intensive, requiring additional knowledge of programming syntax and involving excessive reconfiguration of templates, which limits the efficiency and flexibility in managing data visualization.

Innovation Solution

A method that forms an entity class with attributes and datasets, creates a template stored separately on a server, and links it with the entity class, allowing for efficient display and management of data in the browser by generating identifiers for template elements and entity class attributes, enabling easier link formation and reducing the need for additional information within documents.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If program code blocks are inserted into markup language documents and processed by a pre-processor, then data can be dynamically generated and displayed, but the process becomes time-consuming and requires additional knowledge of programming syntax

Engineering Contradiction:
Improvedata dynamic generation capabilityVSAvoiddocument preparation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent uses template copying where predefined templates with placeholder elements are copied and automatically instantiated with actual data. Instead of manually inserting program code blocks each time, the system copies templates and replaces placeholders with data, dramatically reducing preparation time while eliminating the need for programming syntax knowledge.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces template processors as intermediaries between data sources and markup language documents. These processors automatically handle the substitution of placeholder elements with actual data, mediating the complex process of dynamic data generation and freeing users from direct programming while maintaining versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If special symbols and variables are inserted into markup language documents and replaced during transmission preparation, then data can be dynamically substituted, but the process requires knowledge of template processor syntax and continuous updating when syntax changes

Engineering Contradiction:
Improvedata substitution capabilityVSAvoiduser operation simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent replaces complex symbol insertion with template copying. Users copy predefined templates that already contain properly formatted placeholder elements, eliminating the need to learn template processor syntax. The copying process automatically handles substitution, making the operation simple while maintaining data substitution capability.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The template system is designed to be self-service, where templates automatically manage their own placeholder elements and substitution processes. The system self-adapts when data formats change, eliminating the need for continuous manual updating of syntax knowledge while maintaining versatile data substitution capabilities.

Inventive Principle:
Principle #25Self-service

3Ease of manufacture

If existing framework widgets are used for data visualization, then implementation is simplified, but the number of available visualization options is limited and reconfiguration requires excessive computer resources

Engineering Contradiction:
Improveimplementation simplicityVSAvoidvisualization template variety
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent segments the visualization system into independent, reusable template components. Each template represents a distinct visualization type that can be independently created, stored, and combined. This segmentation allows users to access diverse visualization options without reconfiguring entire frameworks, maintaining implementation simplicity while dramatically increasing template variety.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary action by pre-defining multiple visualization templates with various data presentation formats before they are needed. These templates are stored and readily available for immediate use, eliminating the need for resource-intensive reconfiguration while providing extensive visualization variety. Users simply select and instantiate pre-prepared templates rather than creating them on-demand.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3358470B1Method of preparing documents in markup languages
Publication Date: 2020.11.04 OBSCHESTVO S OGRANICHENNOY OTVETSTVENNOSTYU INTERSOFT
  • EP3358470B1 patent drawingFigure 1
  • EP3358470B1 patent drawingFigure 2
  • EP3358470B1 patent drawingFigure 3

AI summary

The present technical solution relates to user interfaces in general and specifically to user interfaces intended for working with data of computer information systems. A method for preparing documents written in markup languages while implementing a user interface for working with data of an information system, such that: forming metadata for at least one entity class, entity class attributes, datasets, and dataset elements including at least dataset fields and dataset aggregate functions; forming a template for presenting instances of the entity class, the template includes at least one document written in at least one markup language; forming and storing a link between the template and the entity class; displaying the template, forming and storing links between the template and entity class attributes, datasets, their fields and aggregate functions, furthermore: selecting a template element and displaying information about entity class attributes, their fields and aggregate functions available for link forming; selecting an entity class attribute, or a dataset, or a dataset field, or a dataset aggregate function; forming and storing a link including an identifier of the template element selected earlier and an identifier of the entity class attribute, or the dataset, or the dataset field, or the dataset aggregate function selected previously. A technical effect of embodiments of the present technology allows optimizing a process of preparing documents written in markup languages while implementing a user interface for dealing with data of an information system, optimizing time for preparing the documents and simplifying their further maintenance. The technical effect is based on elimination of the need for inserting additional information into documents written in markup languages, the additional information being intended to manage displaying the data of the information system included in the documents. Further effects are: upgraded convenience of preparing documents written in markup languages for implementing a user interface for dealing with data of an information system and relaxation in the requirements for special knowledge for users forming such documents.