Opportunity
The proliferation of internet applications and e-commerce has intensified the need for seamless data exchange and integration across diverse systems. A significant challenge arises from the coexistence of two dominant data formats: relational databases, which are optimized for traditional data processing and internal operations, and XML (eXtensible Markup Language), which has emerged as the standard for data interchange over the web. Conventional methods for translating between these formats are often limited. Many existing XML-enabled database systems can only translate a few relations into an XML document and cannot transform an entire relational database or synchronize a replicate XML database. Furthermore, these methods frequently fail to preserve the underlying data semantics and constraints (such as functional dependencies, cardinalities, and participation) during conversion. This results in laborious, error-prone processes that hinder the realization of a truly integrated information highway. There is a pressing need for a robust, automated system that enables efficient, bidirectional conversion while maintaining data integrity, improving internet computing performance, and facilitating applications like B2B data transmission and legacy system interoperability.
Technology
This patent presents a comprehensive system and method for bidirectional translation between relational databases and XML documents. The core innovation lies in a schema translation process that preserves data semantics. The method involves reverse-engineering the relational schema into an Extended Entity Relationship (EER) model to recover data dependencies and constraints. This EER model is then mapped into an XML schema, specifically a Document Type Definition (DTD). Crucially, the invention introduces an XML Tree Model as a conceptual schema that diagrammatically represents the DTD and preserves the original relational constraints (e.g., weak entities, participation, cardinality, aggregation, generalization) within the hierarchical structure of the XML document. For data conversion, relational tuples are loaded into XML element instances according to these mapped constraints. The process also supports the creation of replicate, information-capacity-equivalent databases. It includes mechanisms for synchronized or asynchronous updates between the relational and XML databases by translating SQL update transactions (INSERT, UPDATE, DELETE) into Document Object Model (DOM) operations, ensuring data consistency across both formats.
Advantages
- Preserves the data semantics and constraints (e.g., functional dependencies, cardinalities) of the original relational database in the translated XML document.
- Enables complete translation of an entire relational database into an XML document and vice versa, unlike limited conventional methods.Improves internet computing performance by allowing parallel processing of relational data internally and XML data for external transmission.
- Facilitates automated recovery of an XML database from its counterpart relational database in case of system failure.
- Allows users to employ familiar query languages (e.g., SQL) while working with the underlying system.
- Supports synchronized or asynchronous updates between replicate relational and XML databases, maintaining data consistency.
- Provides a user-friendly conceptual model (XML Tree Model) for understanding the XML database structure.
Applications
- Enterprise Data Integration: Sharing business data and enabling interoperability between incompatible systems that use different data formats.
- E-Commerce and B2B Applications: Transmitting relational data as standardized XML documents over the internet for transactions and data exchange.
- Legacy System Modernization: Exposing legacy relational data to modern applications and web services that utilize XML.
- Content Management and Syndication: Publishing relational data as XML documents for content distribution and aggregation.
- Database Migration and Replication: Creating and maintaining synchronized, equivalent databases in both relational and XML formats for different operational needs.
- Web Services and Data Exchange Middleware: Serving as a core component in middleware for converting data formats in service-oriented architectures.
