Metadata Schema for XML-Hierarchical Database Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies lack a method for seamlessly passing XML data between XML documents and hierarchical databases, such as IBM's Information Management System (IMS), due to the absence of proprietary schema information that can accommodate user-defined database views and changes, leading to a steep learning curve and limited flexibility.

Innovation Solution

A metadata schema is defined using a database accessor, document accessor, and association module to map XML documents to hierarchical databases, utilizing an XML schema that is text-based and industry-standard compliant, allowing for the passing of valid XML documents and accommodating user-defined views, with directive metadata elements to modify data passing behavior.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If proprietary schema information is used to pass XML data between XML documents and relational databases, then data passing functionality is achieved, but the learning curve becomes steep and flexibility is limited

Engineering Contradiction:
Improvelearning curveVSAvoidflexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary mechanism that automatically generates mapping information between XML schemas and hierarchical database schemas. This intermediary layer eliminates the need for users to manually learn and configure proprietary schema information, thereby reducing the learning curve while maintaining flexibility through automated adaptation to different database structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system dynamically adjusts mapping parameters based on the detected XML schema and hierarchical database schema. By automatically changing mapping parameters such as data type conversions, attribute mappings, and hierarchical structure transformations, the system achieves both ease of operation and flexibility without requiring manual configuration.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If proprietary schema information is used for data passing, then data exchange functionality is provided, but adaptability to user-defined database views and changes is limited

Engineering Contradiction:
Improveaccommodation of user-defined viewsVSAvoidschema information complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by automatically detecting and analyzing XML schemas and hierarchical database schemas before data passing occurs. This preliminary schema analysis enables the system to pre-generate appropriate mapping information, accommodating user-defined database views and changes without increasing operational complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the system continuously monitors and adapts to changes in user-defined database views. By receiving feedback about schema modifications and automatically updating mapping information, the system maintains adaptability while keeping the complexity management automated rather than manual.

Inventive Principle:
Principle #23Feedback

3Reliability

If XML documents are validated against a predefined XML schema, then data integrity is ensured, but the ability to accommodate flexible XML element organization is reduced

Engineering Contradiction:
Improvedata integrityVSAvoidXML element organization flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically adapts the validation process by automatically generating XML schemas from the hierarchical database schema structure. This dynamic schema generation allows the system to maintain data integrity through validation while accommodating flexible XML element organization, as the validation rules are automatically adjusted to match the actual database structure requirements.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7418456B2Method for defining a metadata schema to facilitate passing data between an extensible markup language document and a hierarchical database
Publication Date: 2008.08.26 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US7418456B2 patent drawing
  • US7418456B2 patent drawing
  • US7418456B2 patent drawing

AI summary

A method is provided for defining a metadata schema to facilitate passing data between an XML document and a hierarchical database. The invention includes a database accessor, a document accessor, and an association module. The database accessor accesses a database schema indicative of database field names and a hierarchical structure for a hierarchical database. The document accessor accesses a document schema that defines the hierarchical structure, content data syntax, and semantics of valid, well-formed, XML documents that can be passed into and out of the hierarchical database. The document schema also includes at least one XML element name that maps to a corresponding database field name in the database schema. The association module associates the database schema and the document schema to provide a metadata schema that enables data to be passed between an XML document and the hierarchical database.