XML-Based Translation Service for Dynamic Language Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for internationalizing computer applications require a priori knowledge of supported languages, leading to wasteful storage of duplicate translations, difficulty in updating, and a lack of transparency, as well as dependency on relational database tables that are cumbersome to manage.
Innovation Solution
The use of XML-based translation services that store translations in schema-based XML documents within an XML-enabled database, allowing for dynamic customization based on user language preferences, leveraging XML and XPath/XQuery standards to provide virtual views and transparent language management without the need for pre-defined relational database tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If conventional relational database tables are used to store translations, then structured storage is achieved, but storage waste occurs due to duplicate translations for unsupported languages and the tables become difficult to update
Solution Approach 1:
The patent extracts the translation storage function from conventional relational database tables and implements it through XML documents. This allows the system to store only actual translations rather than pre-defined tables with duplicate entries, eliminating storage waste while enabling flexible updates through XML manipulation without requiring database schema changes.
Solution Approach 2:
The patent introduces dynamic language support through XML documents that can be updated without pre-defined table structures. The system dynamically determines supported languages by querying XML content rather than relying on static database schemas, enabling easy addition or removal of languages without affecting the entire system.
2Adaptability or versatility
If pre-defined relational database tables are used for internationalization, then language support is structured, but the application becomes dependent on a priori knowledge of supported languages
Solution Approach 1:
The patent introduces XML documents as an intermediary between the application and language storage. This intermediary layer decouples the application from direct database dependencies, allowing the system to dynamically determine supported languages through XML queries rather than relying on pre-defined table structures. The XML documents serve as a flexible mediator that can adapt to any language configuration without requiring application-level changes.
3Reliability
If conventional database tables store all supported languages, then complete language coverage is achieved, but meaningless translations and default translations are stored unnecessarily
Solution Approach 1:
The patent applies local quality by storing translations only where they actually exist in the XML document, rather than forcing entries for all supported languages. The system queries XML documents to retrieve translations only for languages that have actual content, eliminating the storage of meaningless default translations while maintaining reliable translation availability for supported languages.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems, methods, and other embodiments associated with providing an XML-based translation service are described. One method embodiment includes accessing a translation-aware XML document that may comply with a translation-enabling XML schema. The document may store a first XML element that stores translatable data and a second XML element that stores a translation of the translatable data. The schema may describe that the first XML element includes a first identifier that identifies the first element as storing translatable data. The schema may also describe that the second XML element includes a second identifier that identifies the second element as storing a translation for translatable data. The method may also include establishing a session language identifier and providing a virtual view of the translation-aware XML document, the virtual view being determined, at least in part, by the session language identifier.