Object Type to XML Document Mapping via Configuration Templates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computer systems face challenges in interpreting data objects created based on non-XML object schemas, as these objects do not conform to XML schema structures, leading to compatibility issues with systems designed for XML documents.

Innovation Solution

A computer-implemented method for mapping object types to markup language document types, allowing users to select configuration templates, modify attribute associations, and generate markup language documents, enabling the transformation of objects into compatible XML formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If objects are stored based on non-XML object schemas, then the objects can maintain their original structure and semantics, but systems configured to interpret XML documents cannot interpret these objects

Engineering Contradiction:
Improvedata integrityVSAvoidsystem compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces configuration templates as an intermediary layer between non-XML object schemas and XML document schemas. These templates define mapping relationships that translate object attributes to XML elements/attributes without altering the original object structure, enabling XML-based systems to interpret non-XML objects while preserving data integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the parameter representation by transforming attribute names and data structures through configurable mapping templates. The mapping templates allow dynamic parameter transformation where object attributes are mapped to corresponding XML elements or attributes, enabling flexible adaptation between different schema representations.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If XML documents are generated based on specific XML schemas, then XML systems can interpret the documents correctly, but objects with different schema structures cannot be mapped to these documents

Engineering Contradiction:
Improveschema conformanceVSAvoidschema flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The mapping configuration is made dynamic and adjustable through the graphical user interface, allowing users to modify attribute associations between object types and XML elements. This dynamic configuration enables the system to adapt to different schema requirements while maintaining proper XML schema conformance through structured mapping templates.

Inventive Principle:
Principle #15Dynamics

3Productivity

If automatic mapping is implemented between object schemas and XML schemas, then productivity increases, but mapping precision decreases due to schema structure differences

Engineering Contradiction:
Improvemapping speedVSAvoidmapping accuracy
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The system performs preliminary actions by providing pre-configured mapping templates that establish initial attribute associations between object types and XML elements. These templates serve as a starting point that accelerates the mapping process while allowing subsequent refinement to maintain accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The graphical user interface provides feedback mechanisms that allow users to review, modify, and refine automatic mapping configurations. Users can visualize the mapping relationships and make adjustments to ensure mapping accuracy, creating a feedback loop that balances automation efficiency with precision requirements.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8661336B2Mapping an object type to a document type
Publication Date: 2014.02.25 SAP SE
  • US8661336B2 patent drawing
  • US8661336B2 patent drawing
  • US8661336B2 patent drawing

AI summary

In general, the subject matter described in this specification can be embodied in methods, systems, and program products for mapping an object type to a document type. A computer system stores configuration templates that each identify a mapping of an object type to a markup language document type. The computer system displays a graphical user interface that permits a user of the computing system to select a configuration template. The computer system displays a list of the at least some attributes and, for each of the attributes, the associated markup language attribute or element that is identified by the selected configuration template. The computer system receives second user input that changes an association of one of the attributes so that the attribute is instead associated with a different markup language attribute or element. The computer system stores an updated mapping of the object type to the markup language document type.