Dynamic XSD Enumeration for Database Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In XML-based software that interfaces with databases, manually updating database values and corresponding XML Schema Definition (XSD) files is time-consuming and prone to inconsistencies, as changes need to be made in two places.

Innovation Solution

A dynamic XSD enumeration software module that retrieves values from a database and generates an XSD file dynamically, caching the data for future use and updating it when changes occur, thereby minimizing manual updates and ensuring data consistency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual updates are performed in both database and XSD files, then data consistency can be maintained, but the time and effort required for updates increases significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service by automatically generating XSD files from database values without requiring manual intervention. The software module queries the database, extracts relevant values, and dynamically generates the corresponding XSD enumeration, eliminating the need for developers to manually update both database and XSD files while maintaining consistency

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary software module that acts as a mediator between the database and XSD files. This module automatically queries database values and generates corresponding XSD enumerations, serving as an automated bridge that eliminates manual synchronization efforts and ensures consistency between database data and XML schema definitions

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual updates are performed in both database and XSD files, then data consistency can be maintained, but the complexity of the update process increases

Engineering Contradiction:
Improvedata consistencyVSAvoidupdate process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system enables self-service by automatically generating XSD files from database values without requiring manual intervention. The software module queries the database, extracts relevant values, and dynamically generates the corresponding XSD enumeration, eliminating the need for developers to manually update both database and XSD files while maintaining consistency

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary software module that acts as a mediator between the database and XSD files. This module automatically queries database values and generates corresponding XSD enumerations, serving as an automated bridge that eliminates manual synchronization efforts and ensures consistency between database data and XML schema definitions

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If manual updates are performed in both database and XSD files, then data consistency can be maintained, but the risk of inconsistencies increases

Engineering Contradiction:
Improvedata consistencyVSAvoidinconsistency risk
Core Design Contradiction:
ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The system enables self-service by automatically generating XSD files from database values without requiring manual intervention. The software module queries the database, extracts relevant values, and dynamically generates the corresponding XSD enumeration, eliminating the need for developers to manually update both database and XSD files while maintaining consistency

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary software module that acts as a mediator between the database and XSD files. This module automatically queries database values and generates corresponding XSD enumerations, serving as an automated bridge that eliminates manual synchronization efforts and ensures consistency between database data and XML schema definitions

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of time

If dynamic generation from database is implemented, then manual update time is reduced, but the complexity of the system increases

Engineering Contradiction:
Improveupdate timeVSAvoidsystem complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The software module performs multiple functions: it queries the database, processes the results, generates XSD enumerations, and handles caching. This multi-functional approach consolidates what would otherwise require separate tools and processes, reducing overall system complexity despite the dynamic generation capability

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

Solution Approach 2:

The system enables self-service by automatically generating XSD files from database values without requiring manual intervention. The software module queries the database, extracts relevant values, and dynamically generates the corresponding XSD enumeration, eliminating the need for developers to manually update both database and XSD files while maintaining consistency

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7711755B2Dynamic XSD enumeration
Publication Date: 2010.05.04 TOPCODER
  • US7711755B2 patent drawing
  • US7711755B2 patent drawing
  • US7711755B2 patent drawing

AI summary

In general, in one aspect, a method for dynamic markup language schema enumeration includes receiving a request for schema file data, the schema file data for validating markup language data, using a database query to retrieve from a database values in a database table that are valid values for the markup language data, and dynamically generating schema file data comprising markup language data structures generated in response to the retrieved database table values, the markup language data structures comprising the results of the database query.