Graphical User Interface for Complex Data Object Hierarchy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Structured data schema, such as JSON and XML, can be complex and difficult for non-technical users to understand and interact with, due to their intricate nature and deep nesting of elements, which prevents them from effectively designing and managing workflows in software applications.
Innovation Solution
The development of graphical user interfaces (GUIs) that allow users to visually specify and configure complex data objects, including adding, removing, and configuring elements, with clear explanations of their names, types, and positions in the hierarchy, enabling non-technical users to design actions and incorporate them into workflows.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If structured data schema (JSON/XML) is used to represent complex data objects, then the data can be encoded and stored in a standardized format, but the schema becomes intricate and difficult for non-technical users to understand and interact with
Solution Approach 1:
The patent introduces a visual schema editor as an intermediary layer between users and the underlying JSON/XML data formats. This editor provides a graphical interface where users can define and manipulate data schemas through visual elements rather than directly editing text-based code, thereby maintaining data encoding reliability while dramatically improving ease of operation for non-technical users
Solution Approach 2:
The patent replaces the mechanical system of text-based code editing with a graphical user interface system. Instead of requiring users to manually write and parse JSON/XML syntax, the system provides visual controls, drag-and-drop interfaces, and automated code generation, substituting the manual mechanical process with an automated graphical system that preserves data integrity while reducing complexity
2Ease of manufacture
If JSON or XML formats are used for machine-to-machine communication, then data can be stored in a human-readable form, but reading and understanding the organization of data becomes a painstaking task even for experienced users
Solution Approach 1:
The patent adds a visual dimension to data schema representation. Instead of relying solely on the textual hierarchy of JSON/XML, the system creates a parallel visual representation that displays data organization through graphical elements, icons, and spatial arrangement, allowing users to comprehend data structure instantly without having to parse through lines of code
3Adaptability or versatility
If complex data objects with arbitrary nesting and multiple elements are supported, then the schema can represent intricate data structures, but the complexity becomes a barrier that prevents non-technical users from interacting with software applications
Solution Approach 1:
The patent segments the complex data object schema into manageable visual components. Each element, property, and nested structure is represented as a separate graphical element that can be independently configured. This segmentation allows non-technical users to interact with one small portion of the data structure at a time rather than being overwhelmed by the entire complex schema at once
Solution Approach 2:
The patent implements dynamic behavior in the schema editor where the interface adapts to the complexity of the data structure. As users add nested elements or arrays, the visual editor automatically adjusts its layout and provides context-aware controls, making the interaction experience remain simple and intuitive regardless of how complex the underlying data structure becomes
Data Source
AI summary
A system may involve persistent storage defining primitive data types and compound data types, where the compound data types include objects and arrays, where the objects contain sets of elements that have various primitive data types, compound data types, or both, and where the arrays contain sets of elements that all have one particular primitive data type or compound data type. The system may also involve one or more processors configured to provide a representation of a graphical user interface for designing a hierarchy of elements, each of the elements therein having a data type that is either a primitive data type or a compound data type, where elements in the hierarchy are associated with data type change controls, and where object elements in the hierarchy are: (i) associated with child element controls, and (ii) represented as collapsible menu items that can either display or hide their child elements.