Format Translator Using Intermediary Common Format

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing solutions for converting electronic content data between different formats are inefficient, requiring two conversion steps and often losing information due to inconsistent semantic levels, and struggle to adapt to rapidly evolving software technologies.

Innovation Solution

A method for generating translators based on format translation patterns, using a meta-language like XML to represent features and translations, which allows for the automatic creation of parser, mapper, and serializer translators to directly convert between source and target formats, optimizing the conversion process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a common format is used as an intermediate step for format conversion, then the number of converters needed is reduced from N2 to 2N, but the conversion process requires two separate conversion steps instead of one

Engineering Contradiction:
Improvenumber of convertersVSAvoidconversion time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent applies the intermediary principle by introducing a common format as a mediator between source and target formats. The format translator includes a parser that converts source format to the common format, and a serializer that converts the common format to target format. This intermediary approach reduces the total number of converters needed from N2 to 2N, though it does require two conversion steps.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the format conversion process into two distinct components: parsing (source format to common format) and serialization (common format to target format). This segmentation allows the system to reuse the common format across multiple conversions, reducing overall system complexity while maintaining efficient conversion capabilities.

Inventive Principle:
Principle #1Segmentation

2Productivity

If standard tools are used for conversion to the common format, then conversion can be performed, but information may be lost due to inconsistent or inappropriate semantic levels

Engineering Contradiction:
Improveconversion capabilityVSAvoidinformation loss
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent addresses information loss by carefully controlling the semantic level parameters of the common format. The format translator is designed to operate at a specific semantic level that preserves all necessary information for both content management and electronic publishing functions. This parameter control ensures that no information is lost during the conversion process while still achieving efficient format translation.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If existing translation solutions are used, then format conversion can be performed, but they are difficult to adapt to rapidly advancing software technology and new file formats

Engineering Contradiction:
Improveconversion functionalityVSAvoidadaptability to new formats
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent achieves adaptability through universality by designing a format translator based on a common format that can serve multiple purposes and accommodate various source and target formats. The parser and serializer components are designed to be flexible and can be extended to handle new formats as they emerge, making the system universally applicable across different format requirements and adaptable to advancing software technology.

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

Data Source

PatentUS7774746B2Generating a format translator
Publication Date: 2010.08.10 APPLE INC
  • US7774746B2 patent drawing
  • US7774746B2 patent drawing
  • US7774746B2 patent drawing

AI summary

Generating code is disclosed. A specification of one or more translation patterns is received. The one or more translation patterns are used to generate at least a portion of code associated with a translator. Using the one or more translation patterns to generate at least a portion of code associated with the translator results in the translator being configured to create a target object model. Creating the target object model includes populating one or more elements of the target object model in a processing order at least in part associated with an order of elements in the one or more translation patterns.