Context-Aware Schema Layout for Business Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current electronic business systems lack a unified method for representing the structure and semantics of business data, leading to varied document representations and the inability to exchange business documents electronically without manual coordination and mapping.

Innovation Solution

A computer-implemented method that assigns context values to layout information for data elements, allowing for the configuration and storage of this information within a schema definition, enabling improved handling and visualization of data elements in graphical user interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If external script files are used to describe layout information, then layout properties can be separately defined, but there is no tight conjunction between reusable building blocks and layout information, requiring complete new layout information to be developed for each new document

Engineering Contradiction:
Improvereusability of layout informationVSAvoidintegration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges layout information with schema definitions by embedding layout information directly within the schema definition files. This integration allows layout information to be automatically associated with reusable building blocks (XML schema components), eliminating the need for separate external script files and manual mapping processes.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal schema definition structure that simultaneously handles both data structure validation and layout information storage. This multi-functional approach allows a single schema definition to serve both structural validation purposes and layout specification purposes, enabling reuse across different documents and contexts.

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

2Adaptability or versatility

If context-specific layout information is provided for different business scenarios, then layout flexibility is improved, but the complexity of managing multiple layout definitions increases

Engineering Contradiction:
Improvelayout flexibilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic layout information selection based on context parameters. The system automatically selects appropriate layout information from the schema definition based on the specific business context, document type, or other contextual factors, providing layout flexibility without requiring manual intervention to manage multiple layout definitions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent allows different parts of the schema definition to contain context-specific layout information tailored to specific business scenarios. Each data element or component can have its own context-specific layout properties, enabling localized adaptation while maintaining overall system consistency through the unified schema definition structure.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS7937408B2Layout information for data element
Publication Date: 2011.05.03 SAP SE
  • US7937408B2 patent drawing
  • US7937408B2 patent drawing
  • US7937408B2 patent drawing

AI summary

Providing layout information includes assigning at least a first context value to layout information for a data element. The layout information is configured for use in displaying an instance of the data element in a graphical user interface. The method includes storing the layout information and the first context value in a schema definition for the data element. Providing display of data using layout information includes receiving a context definition. A data element is identified using the received context definition. A schema definition for the data element includes layout information with at least a first context value assigned thereto. The method further includes providing, using the layout information, an instance of the identified data element for display in a graphical user interface.