XML Document Repository with Automatic Schema Parsing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for storing XML documents in repositories require significant development and maintenance efforts, including specific program code and relational database table design, which is burdensome and limits flexibility when XML schemas change.

Innovation Solution

A system that uses an interface processor to store and process XML documents, automatically parsing and identifying internal structure and external relationships, allowing for dynamic referential integrity and indexing without requiring additional programming or administration, enabling seamless handling of XML data within a relational database management system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If specific program code and relational database table design are used to handle XML documents, then data management features can be provided, but development and maintenance burden increases substantially

Engineering Contradiction:
Improvedata management featuresVSAvoidprogram code and table design
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system automatically extracts relationships and indexing information from XML documents without requiring manual program code or table design. The database self-generates the necessary structure by parsing XML schemas and creating corresponding relational tables, eliminating the need for developers to manually configure data management features.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary extraction and classification of XML document structures, relationships, and indexing information before data storage. By pre-processing the XML schemas to identify patterns and relationships, the system prepares the relational database structure in advance, eliminating the need for subsequent manual configuration.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If relational database tables and program code are designed for XML documents, then data storage and retrieval can be achieved, but flexibility to handle XML schema changes is reduced

Engineering Contradiction:
Improvedata storage and retrievalVSAvoidflexibility to schema changes
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically adapts the relational database structure to match XML schema changes. When XML schemas are modified, the system automatically detects the changes and updates the corresponding database tables, indexes, and relationships, maintaining flexibility without requiring manual intervention or rigid pre-defined structures.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes database parameters such as table structures, column definitions, and indexing strategies based on the actual XML schema content. By adjusting these parameters dynamically according to the extracted XML characteristics, the system maintains optimal performance and flexibility despite schema variations.

Inventive Principle:
Principle #35Parameter changes

3Ease of manufacture

If manual coding and testing are performed for each XML document instance, then specific features can be implemented, but development time increases substantially

Engineering Contradiction:
Improvefeature implementationVSAvoiddevelopment and testing time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The system automatically generates program code and database structures based on extracted XML schema patterns. Instead of manually coding each feature, the system self-generates the necessary SQL statements, table definitions, and indexing strategies, dramatically reducing development and testing time while maintaining ease of implementation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system creates template-based database structures and program code that can be copied and applied to different XML document types. By extracting common patterns from XML schemas and generating standardized templates, the system eliminates repetitive manual coding and testing efforts across multiple document instances.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7941395B2System for storing documents in a repository
Publication Date: 2011.05.10 CERNER INNOVATION INC
  • US7941395B2 patent drawing
  • US7941395B2 patent drawing
  • US7941395B2 patent drawing

AI summary

A system stores documents in a repository and includes a repository for storing data representing a document. An interface processor receives and stores document data representing a first document and an associated document identifier. A document processor automatically parses and processes the received document data to identify and store data indicating: (a) internal document structure and characteristics, and (b) external document relationships. The internal document structure and characteristics include a compilation of searchable keywords and key values. The external document relationships include an association or hierarchical relationship between the first document and one or more different documents.