XML Processing Engine Dynamic Workflow and Generic Styling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional Extensible Markup Language (XML) processing systems are inflexible and static, unable to efficiently handle arbitrary XML vocabularies and workflows, often requiring fixed pipelines that stall if one step is delayed, and lack the ability to apply generic stylesheets to documents without appropriate vocabularies.

Innovation Solution

An XML document processing engine that receives document fragments and workflow specifications, allowing dynamic processing, generation of new workflow specifications, and parallel processing, along with a generic document format that enables styling and layout for documents with arbitrary vocabularies by converting them into a format suitable for generic stylesheets.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional fixed processing pipelines are used, then processing sequence is predetermined, but system flexibility and ability to handle arbitrary XML vocabularies deteriorates

Engineering Contradiction:
Improveability to handle arbitrary XML vocabulariesVSAvoidprocessing system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic workflow specifications that can be generated and modified at runtime based on the XML document being processed. Instead of fixed static pipelines, the system creates processing workflows dynamically using workflow specification languages (WSL), allowing the processing sequence to adapt to different XML vocabularies and document structures.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent creates a universal processing framework that can handle arbitrary XML vocabularies through a common intermediate format (PML). The system uses generic style sheets and transformation rules that can be applied to any XML vocabulary by converting it to the intermediate format first, making the processing system versatile across different document types.

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

2Productivity

If fixed processing pipelines are used, then implementation is simpler, but productivity decreases when one step is delayed

Engineering Contradiction:
Improveprocessing throughputVSAvoidpipeline management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the processing pipeline into independent, modular steps that can be executed in parallel. Each processing step operates on document fragments independently, and the system manages multiple processing threads that can run simultaneously without blocking each other, improving productivity when one step is delayed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent ensures continuous processing by implementing a system where multiple document fragments can be processed in parallel through different workflow threads. When one processing step is delayed, other threads continue executing, maintaining overall system productivity and avoiding complete pipeline stalls.

Inventive Principle:
Principle #20Continuity of useful action

3Adaptability or versatility

If specific vocabularies are used, then processing is more efficient, but adaptability to different vocabularies deteriorates

Engineering Contradiction:
Improvecompatibility with different vocabulariesVSAvoidtime to assemble compatible stylesheets
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs preliminary conversion of XML documents to a common intermediate format (PML) before applying style sheets. This pre-processing step creates a standardized representation that can be efficiently styled with generic style sheets, eliminating the need to assemble vocabulary-specific stylesheets for each document type.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediate format (PML - Portable Markup Language) as a mediator between arbitrary XML vocabularies and the styling system. This intermediate format serves as a universal interface that preserves the semantic structure of the original XML while enabling consistent application of generic style sheets across different vocabularies.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If formatting information is embedded in XML vocabularies, then presentation is improved, but versatility for different display devices deteriorates

Engineering Contradiction:
Improveadaptability to different display devicesVSAvoidformatting information requirements
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts formatting and presentation information from the XML content itself and separates it into independent style sheet components. The XML documents contain only semantic and structural information, while all formatting instructions are stored in separate, device-independent style sheets that can be adapted to different display devices without modifying the original content.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS9286272B2Method for transformation of an extensible markup language vocabulary to a generic document structure format
Publication Date: 2016.03.15 XEROX CORP
  • US9286272B2 patent drawing
  • US9286272B2 patent drawing
  • US9286272B2 patent drawing

AI summary

A method determines structures and features of an original document to make style decisions. The extensible markup language of the original document is analyzed to produce instance mapping. The document type definitions of the original document are analyzed to produce document type definitions mapping. Lastly, the instance schema of the original document is analyzed to produce schema mapping. A transform is generated from the produced instance mapping, document type definitions mapping, and schema mapping. The transform is applied to the original document to generate an instance in an intermediate format. A stylesheet is selected and applied to the intermediate format to produce a styled document.