Ontology-Based Workflow for Multi-Language Component Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data analysis platforms are limited to single programming languages, restricting users to specific tools and lacking standardized definition and management of components, preventing optimal data mining and analysis, and failing to support customization and flexible assembly of multi-programming language components.

Innovation Solution

An ontology-based multi-programming language component specifications and workflow system, including a multi-language programming component manager, design modeler, transformation engine, and core workflow engine, enabling flexible assembly and conversion across different programming languages, with support for no-code/low-code components and online code development.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a data analysis platform supports only a single programming language, then the system complexity is reduced and ease of operation is improved, but the adaptability and versatility of the platform deteriorate

Engineering Contradiction:
Improveease of operationVSAvoidadaptability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent implements a unified workflow management system that can execute components from multiple programming languages (Python, Java, R, etc.) through a common interface. The system provides universal support for different programming languages by establishing standardized component definitions and a translation layer that maps various language-specific components to a unified execution model, enabling the platform to handle diverse data analysis tasks while maintaining ease of operation.

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

Solution Approach 2:

The patent introduces a workflow engine as an intermediary layer between the user interface and the diverse programming language components. This mediator translates high-level workflow definitions into language-specific executions, managing the complexity of multi-language support internally while presenting a simplified interface to users. The workflow engine acts as a buffer that handles language translation and coordination, allowing users to benefit from multiple languages without directly dealing with their complexities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If the platform enables flexible assembly of multi-programming language components, then the adaptability and productivity are improved, but the device complexity and difficulty of managing components increase

Engineering Contradiction:
ImproveproductivityVSAvoidcomplexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the complex multi-language component management system into distinct modular layers: a component definition layer that handles language-specific component specifications, a workflow design layer for assembling components, and an execution layer that manages runtime coordination. This segmentation allows each layer to handle specific aspects of complexity independently, enabling flexible component assembly while maintaining manageable system structure through clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent employs parameterized component definitions that allow the same component interface to work across multiple programming languages by changing language-specific parameters. The system uses configurable parameters to adapt component behavior to different programming languages while maintaining a unified workflow model. This parameter-based approach enables flexible assembly of multi-language components without requiring separate management mechanisms for each language.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If standardized definition and management of components is implemented across multiple programming languages, then the adaptability is improved, but the device complexity increases

Engineering Contradiction:
ImproveadaptabilityVSAvoidcomplexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent establishes a universal component definition framework that provides standardized interfaces for components across multiple programming languages. The system defines language-agnostic component contracts while allowing language-specific implementations, enabling adaptability through consistent standardized definitions. This universal framework manages complexity by providing a common vocabulary and interface structure that works across Python, Java, R and other languages without requiring separate management systems for each.

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

Data Source

PatentUS12405779B2Ontology-based multi-programming language component specifications and workflow system and use method
Publication Date: 2025.09.02 INST OF MEDICAL INFORMATION CHINESE ACAD OF MEDICAL SCI
  • US12405779B2 patent drawing
  • US12405779B2 patent drawing
  • US12405779B2 patent drawing

AI summary

Disclosed are an ontology-based multi-programming language component specifications and workflow system and a use method. A multi-language programming component manager is connected with a multi-language programming component workflow design modeler and a multi-programming language transformation engine. A core workflow engine is connected with the multi-language programming component workflow design modeler and the multi-programming language transformation engine. An ontology that supports normalized management of multi-programming language transformation and components is designed to standardize the definition of core components, support multi-programming language data conversion communication and component management, support custom design creation, flexible expansion and result interaction of multi-class workflow components, make full use of advantages of various programming languages, and reduce technical difficulties in the applicability of components developed in various programming languages; while achieving the maximum use of multi-programming languages to achieve the effect of “1+1>2”.