Data Schema Inference for Error-Resistant ECS Configuration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Developing data schema in a data oriented architecture for entity component systems is tedious, repetitive, and error-prone, requiring front-end coding knowledge and leading to potential runtime errors and performance issues due to non-compliance with the framework.

Innovation Solution

Implementing a system that controls data schema through conditional type inference, providing suggestions and error indications to enforce property definition schema, allowing users to add or configure components without manual coding, and ensuring data objects conform to the data schema.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If manual code development is used for configuring and customizing data schema, then user interface can be generated, but the process becomes tedious, error-prone, and requires coding knowledge

Engineering Contradiction:

Improveease of configuring data schemaVSAvoidcoding complexity

Core Design Contradiction:

Ease of manufactureVSDevice complexity

Solution Approach 1:

The system automatically generates user interface code based on the data schema definition. When a user defines a component with properties, the system self-generates the necessary front-end code, UI components, and state management without requiring manual coding, thus eliminating the need for coding knowledge while maintaining functionality

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical code writing with an automated system that generates code from data schema definitions. The mechanical process of writing, formatting, and validating code manually is substituted by an automated code generation mechanism that derives all necessary code from the high-level data schema specification

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If manual code development is used for user interface generation, then custom components can be created, but the process is time-consuming and repetitive

Engineering Contradiction:

Improvespeed of component configurationVSAvoidtime for code development

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary action by automatically generating the complete user interface code structure before the user needs to interact with the component. The code generation happens in advance based on the data schema definition, eliminating the need for real-time manual coding during the configuration process and significantly reducing development time

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system creates copies of standardized UI component patterns and code templates automatically. Instead of manually writing unique code for each component, the system copies and adapts pre-defined UI patterns based on the data schema, rapidly generating consistent, reusable interface code without repetitive manual effort

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If data schema is not enforced, then flexible component definition is allowed, but runtime errors occur due to lack of data layout enforcement

Engineering Contradiction:

Improveflexibility in component definitionVSAvoidruntime error prevention

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements feedback by providing real-time validation of data schema definitions against the enforced data layout. When users define component properties, the system immediately checks for compliance and provides feedback in the form of errors or warnings, preventing invalid definitions from causing runtime errors while maintaining the flexibility to define custom components

Inventive Principle:

Principle #23Feedback

4Manufacturing precision

If coding knowledge is required for user interface configuration, then precise control is achieved, but the barrier to entry increases and development becomes error-prone

Engineering Contradiction:

Improveprecision of data schema configurationVSAvoidease of component configuration

Core Design Contradiction:

Manufacturing precisionVSEase of operation

Solution Approach 1:

The system introduces an intermediary layer between the user's high-level data schema definitions and the low-level implementation code. This intermediary is the automated code generation system that translates user-friendly schema definitions into precise, error-free code, eliminating the need for users to directly manipulate code while maintaining configuration precision through the enforced data layout

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12613680B2Controlling data schema for data oriented architecture

Publication Date: 2026.04.28 LEMON INC(GB)

AI summary

Controlling data schema is provided for data object(s) in a data oriented architecture. Suggestions are provided for received data objects, including determining whether the received data object maps to one of multiple data types, and performing a conditional type inference to provide the one or more suggestions based on a result of the determining of whether the one of the data object maps to one of the multiple data types.