Structural Context for Fixed Layout Documents

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Fixed layout markup documents, such as those in the XPS format, lack structural context, leading to issues like improper reading order when content is copied and pasted into different document formats, as they do not inherently define structural information like paragraphs, tables, or headers, which affects functionalities like accessibility and copy-paste operations.

Innovation Solution

Introducing a structural context for fixed layout markup documents by maintaining separate structural markup that references content markup, allowing for the definition of reading order, organizational structure, and inter-relationships between markup elements, enabling functionalities like maintaining the intended reading order and recreating table structures during copy-paste operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate structural markup is introduced for fixed layout documents, then structural context and reading order are preserved, but document complexity increases

Engineering Contradiction:
Improvestructural context preservationVSAvoiddocument markup complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The document markup is segmented into two distinct parts: content markup that defines visual rendering, and structural markup that defines organizational structure and reading order. This segmentation allows each part to serve its specific function without interference, preserving structural context while maintaining clear separation of concerns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A story fragment structure acts as an intermediary layer between content markup and structural markup. The story fragment references both the visual content and its structural context, enabling document consumers to access structural information without directly processing the entire markup system, thus managing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If structural markup is maintained separately from content markup, then accessibility and copy-paste operations improve, but information access complexity increases

Engineering Contradiction:
Improvecopy-paste operation accuracyVSAvoidmarkup access complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The structural markup is nested within the existing document structure through story fragments that are themselves nested within the content markup. This nested organization allows structural information to be accessed through the existing content markup pathways, improving ease of operation while managing access complexity through hierarchical organization.

Inventive Principle:
Principle #7Nested doll (Nesting)

3Manufacturing precision

If reading order is defined through separate structural markup, then copy-paste operations maintain intended order, but processing overhead increases

Engineering Contradiction:
Improvereading order accuracyVSAvoiddocument processing speed
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The reading order is predetermined and defined in advance through the structural markup during document creation. This preliminary definition of reading order allows document consumers to directly access the intended sequence without performing complex analysis during copy-paste operations, maintaining precision while reducing processing overhead.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7676741B2Structural context for fixed layout markup documents
Publication Date: 2010.03.09 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7676741B2 patent drawing
  • US7676741B2 patent drawing
  • US7676741B2 patent drawing

AI summary

Techniques relating to structural context for fixed layout markup documents are described. In one instance, a process defines content and associated positional information of a document with a set of content markup. The process also specifies a structural configuration for the document relative to at least some of the content markup, such that the structural configuration is separate from the content markup.