Markup Language Element Inheritance for Platform-Specific GUI Customization

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current markup languages lack the ability to effectively represent object-oriented derived classes, specifically in extending or overriding attributes of base classes across multiple platforms for graphical user interface (GUI) screens in wireless communication devices.

Innovation Solution

The use of XML to create a markup language document that includes platform-independent and platform-specific attributes, with indicators to override or extend these attributes, allowing for the generation of a single instance of a markup language element tailored to specific deployment platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If markup language represents multiple platform-specific instances separately, then platform-specific customization is achieved, but device complexity and maintenance difficulty increase

Engineering Contradiction:

Improveplatform-specific customizationVSAvoidmarkup language structure

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The markup language is segmented into hierarchical levels: a base instance containing platform-independent attributes, and derived instances containing platform-specific attributes. This segmentation allows each level to handle appropriate customization without duplicating entire markup structures, resolving the contradiction between adaptability and complexity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements a nested structure where derived markup instances are embedded within or reference base instances. The derived instances contain only the platform-specific overrides, while inheriting the base instance's platform-independent attributes. This nesting eliminates the need for separate complete markup files for each platform, reducing overall system complexity while maintaining customization capability.

Inventive Principle:

Principle #7Nested doll (Nesting)

2Stability of the object's composition

If markup language includes platform-independent attributes only, then consistency across platforms is maintained, but platform-specific requirements cannot be met

Engineering Contradiction:

Improvecross-platform consistencyVSAvoidplatform-specific customization

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by allowing different portions of the markup language to have different levels of specificity. Base instances provide platform-independent quality for common attributes, while derived instances provide platform-specific quality for customized attributes. This localized differentiation enables both consistency and adaptability within the same markup structure.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The base markup instance serves as a universal template that can be inherited by multiple platform-specific derived instances. This multi-functionality allows a single base definition to serve all platforms while derived instances customize only what is necessary, maintaining consistency for common elements while enabling platform-specific adaptations.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If separate markup files are created for each platform, then platform-specific attributes are fully supported, but information redundancy and file management complexity increase

Engineering Contradiction:

Improveplatform-specific attribute supportVSAvoidinformation redundancy

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent performs preliminary action by defining platform-independent base attributes once in a base instance, before they are needed for specific platforms. This preliminary definition eliminates the need to repeatedly specify the same attributes in each platform-specific file, preventing information redundancy while maintaining full platform-specific support through inheritance.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS7890853B2Apparatus and machine-readable medium for generating markup language representing a derived entity which extends or overrides attributes of a base entity

Publication Date: 2011.02.15 MALIKIE INNOVATIONS LTD

AI summary

A markup language document (e.g. an XML document) may contain a first instance of a markup language element having an attribute with a first, platform-independent value, a second instance of the element having the attribute with a second, platform-specific value, and an indicator that the second value overrides the first. Executable code may replace both of the first and second instances with a single instance having the attribute with the second value. Alternatively the markup language document may contain a first instance of a markup language element having a first, platform-independent attribute, a second instance of the element having a second, platform-specific attribute different from the first attribute, and an indicator that the second instance extends the first. In this case executable code may replace both instances of the markup language element with a single instance having the first attribute and the second attribute.