XSLT Processor Framework for Application Interface Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of application interface frameworks (AIFs) requires significant effort to configure and customize new interfaces due to their layered architecture and proprietary implementation of application logic, making it difficult for users to define tasks for utilizing structured data from different entities and formats.
Innovation Solution
The implementation of a Fast Integration and Transformation (FIT) framework that uses an XSLT processor to process customer-specific logic, reducing the need for middleware and allowing for easier generation of backend configurations, faster data processing, and support for parallel processing and sequencing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a layered architecture with proprietary implementation is used for AIF, then the system provides structured data processing capabilities, but the device complexity and configuration effort increase significantly
Solution Approach 1:
The patent extracts the proprietary application logic from the complex layered AIF architecture and relocates it to external XSLT transformation files. This separation removes the burden of proprietary implementation details from the core framework, reducing configuration complexity while preserving data processing capabilities. Users can now define transformation logic in standalone XSLT files rather than navigating complex framework layers.
Solution Approach 2:
The patent introduces XSLT processors as intermediary components between the data source and the AIF framework. These processors handle the complex transformation logic externally, acting as a mediator that simplifies the interaction between diverse data formats and the framework's expected input structure, thereby reducing overall system complexity.
2Adaptability or versatility
If proprietary application logic is implemented in AIF, then data transformation functionality is provided, but the ease of operation and customization difficulty increase
Solution Approach 1:
The patent enables users to directly author and customize transformation logic using standard XSLT language without requiring proprietary framework knowledge. Users can independently modify transformation behavior by editing XSLT files, making the system self-serviceable and significantly improving ease of operation while maintaining full transformation functionality.
Solution Approach 2:
The patent changes the parameter representation from proprietary framework-specific parameters to standard XSLT parameters and templates. This parameter transformation allows users to leverage familiar XML transformation concepts rather than learning proprietary parameter systems, thereby improving operational ease while preserving transformation capabilities.
3Adaptability or versatility
If middleware is used for data transformation, then format conversion is achieved, but the processing time and CPU commands increase
Solution Approach 1:
The patent replaces the mechanical middleware processing layer with a more efficient XSLT transformation engine. By substituting the traditional middleware architecture with direct XSLT processing, the system eliminates unnecessary intermediate processing steps and reduces CPU overhead, thereby improving data processing speed while maintaining format conversion capabilities.
Solution Approach 2:
The patent extracts the transformation logic from the middleware layer and places it directly in XSLT processors that execute more efficiently. This extraction removes the performance overhead associated with middleware interpretation and execution, resulting in faster data processing while preserving the essential format conversion functionality.
Data Source
AI summary
A solution is provided that significantly reduces the complexity of existing solutions for creating interfaces in a computer system. More particularly, a middleware common to such solutions is removed and a low-level approach is taken where customer-specific logic is processed on an Extensible Stylesheet Language transformation (XSLT) processor instead. Additional transformations may also then be imported from external XSLT editors making it very easy to generate a backend configuration for interfaces.