Mashup Web Application Authoring via Metadata Templates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current mashup web application development requires programming knowledge and is complex for general users, as it involves analyzing and integrating different open APIs, making it difficult for non-technical users to create and update mashup services.

Innovation Solution

An apparatus and method that includes a web application authoring unit generating metadata from block resources and web application resources, a workflow management unit verifying the workflow, and a block authoring unit generating metadata and source code from open APIs, allowing general users to create mashup web applications without programming knowledge.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a mashup developer manually analyzes and integrates open APIs to create a mashup web application, then the application can be customized according to specific requirements, but the development process becomes complex and requires programming knowledge

Engineering Contradiction:
Improvecustomization capabilityVSAvoiddevelopment process complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a mashup template as an intermediary component that pre-defines the integration logic between open APIs and web application frameworks. The template includes predefined metadata schemas, workflow definitions, and code generation templates that mediate between API specifications and final applications, eliminating the need for developers to manually handle complex integration details while preserving customization capability through template parameters and configurations

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies preliminary action by pre-generating standardized code templates, metadata schemas, and workflow definitions before actual mashup development. The system prepares integration frameworks, API connection templates, and data mapping schemas in advance, allowing developers to simply configure parameters rather than write integration code from scratch, thereby reducing development complexity while maintaining adaptability

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If open API codes and scripts are arbitrarily produced by developers, then the mashup can be customized, but it becomes difficult to update open APIs or add new APIs to existing mashups

Engineering Contradiction:
Improvemashup customizationVSAvoidAPI update and maintenance
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent segments the mashup system into independent, modular components: open API adapters, metadata schemas, workflow definitions, and web application frameworks. Each open API is integrated through a standardized adapter interface that separates API-specific logic from the core mashup template. This segmentation allows individual API adapters to be updated or replaced without affecting the overall mashup structure, enabling easy maintenance while preserving customization

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates universal metadata schemas and workflow templates that can accommodate multiple open APIs through standardized interfaces. The mashup template uses generic data binding mechanisms and configuration parameters that work across different API types, allowing the same template framework to support various APIs. This universality enables new APIs to be added by creating new adapters that conform to the standard interface, without requiring changes to existing mashup logic

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

3Manufacturing precision

If a mashup developer learns various API service methods and techniques, then the quality of mashup development improves, but the learning curve and time required increase significantly

Engineering Contradiction:
Improvemashup development qualityVSAvoidlearning time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent uses copying by providing pre-written, standardized code templates, metadata schemas, and workflow definitions that can be reused across different mashup projects. Instead of requiring developers to learn and write integration code from scratch for each API, the system provides copyable templates that follow best practices and proven patterns. Developers can copy and adapt these templates for different APIs, maintaining high development quality while minimizing learning time through template-based reuse

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9069873B2Apparatus and method for creating mashup web application
Publication Date: 2015.06.30 ELECTRONICS & TELECOMM RES INST
  • US9069873B2 patent drawing
  • US9069873B2 patent drawing
  • US9069873B2 patent drawing

AI summary

An apparatus for creating a mashup web application includes: a web application authoring unit configured to generate a web application initial page from previously stored block resources and web application resources during web application authoring login, receive UI-based web application authoring information through the web application initial page, and generate web application metadata; and a workflow management unit configured to generate a final web application by verifying a workflow of the web application metadata.