Web Extension Management via XML Manifest Files

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Legacy applications often lack standardized interfaces for integrating external tools, leading to custom, costly, and non-portable solutions that are difficult to maintain due to rapid depreciation of knowledge bases with new technology cycles.

Innovation Solution

Managing a web extension through a manifest file formatted in XML, which stores attributes such as metadata and a pointer to the extension, enabling standardized interaction and management of the extension's functionality between the host application and the web extension.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If custom developed third party tool solutions are used to integrate external tools with legacy applications, then the integration can be achieved, but the solutions lack flexibility and are difficult to maintain

Engineering Contradiction:

Improveflexibility of integration solutionVSAvoidcomplexity of custom integration solution

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal integration framework using standardized interfaces and protocols that enable multiple external tools to connect with legacy applications through a common architecture. The manifest file system provides a universal configuration mechanism that works across different tool types, eliminating the need for custom integration code for each tool and enabling flexible, maintainable solutions.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If custom integration solutions are developed for each legacy application, then the specific integration needs can be met, but the solutions are rarely portable or upgradeable

Engineering Contradiction:

Improveportability and upgradeability of integration solutionVSAvoidcost and effort of developing integration solution

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The patent segments the integration architecture into independent components: a standardized interface layer, a manifest file configuration layer, and the legacy application layer. This segmentation allows the integration solution to be decoupled from specific applications, making it portable and upgradeable. The manifest files can be independently modified without affecting the core integration framework, enabling easy upgrades and reusability across different applications.

Inventive Principle:

Principle #1Segmentation

3Productivity

If vendors develop custom solutions to integrate external tools, then the legacy application can be enhanced, but resources are spent maintaining in house legacy knowledge base that depreciates rapidly

Engineering Contradiction:

Improvefunctionality of legacy applicationVSAvoidtime and resources for maintaining legacy knowledge base

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The patent uses manifest files as standardized templates that capture integration configurations in a portable format. Instead of maintaining proprietary knowledge bases, the system copies integration definitions into standardized manifest files that can be shared, archived, and reused. This allows organizations to preserve integration knowledge without investing in maintaining internal expertise, as the manifest files serve as self-contained documentation and configuration templates.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS9239817B2Managing web extension through manifest file

Publication Date: 2016.01.19 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A web extension is managed through a manifest file. An application managing the web extension receives attributes of the extension from a developer or metadata of the extension. A pointer to the web extension is inserted into the attributes. The pointer can be used as a link to activate the web extension. The attributes are stored in a manifest file formatted in extensible markup language (XML). The functionality of the web extension is managed based on the manifest file.