XML Schema Conversion to Extensible RNC and RNG Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current commerce eXtensible Markup Language (cXML) schemas, particularly nonextensible Document Type Definitions (DTDs), often lack necessary information for transactions and lead to redundancy and misinterpretation of custom extrinsics, making them difficult to manage and document.
Innovation Solution
A method and system that convert nonextensible schemas to compact syntax regular language for XML next generation (RNC) and regular language for XML next generation (RNG) files, allowing for the explicit enumeration of semantics and generation of extensible schemas, enabling the inclusion of custom information and facilitating communication between senders, commerce hubs, and recipients.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If nonextensible schemas (DTDs) are used to establish fixed templates for cXML documents, then document format validation is achieved, but the schemas cannot include all necessary information for transactions and require custom extrinsics that lead to redundancy and misinterpretation
Solution Approach 1:
The patent segments the schema into a structured hierarchy with a base schema containing common elements and extension schemas containing custom extrinsics. This segmentation allows the base schema to maintain validation while extension schemas add necessary transaction-specific information without causing redundancy or misinterpretation.
Solution Approach 2:
The patent introduces a new dimension to schema organization by creating an extensible schema framework that operates alongside the traditional nonextensible DTD. This multi-layered schema architecture enables both fixed validation rules and flexible custom information inclusion in a structured manner.
2Loss of information
If senders create custom extrinsics for additional information, then transaction-specific data can be included, but redundancy occurs when multiple senders create similar custom extrinsics and the commerce hub cannot understand their values
Solution Approach 1:
The patent creates a universal extension schema framework that can accommodate custom extrinsics from multiple senders in a standardized format. This universal structure allows the commerce hub to understand and process custom information consistently, eliminating the need for each sender to create entirely custom schemas while preserving the ability to include transaction-specific data.
Solution Approach 2:
The patent introduces an intermediary extension schema layer between the base schema and custom extrinsics. This intermediary structure standardizes how custom information is formatted and organized, allowing the commerce hub to interpret custom data consistently while reducing redundancy across multiple senders.
3Reliability
If nonextensible schemas are used, then document validation is performed, but schema updates are slow and difficult to manage
Solution Approach 1:
The patent segments the schema system into a stable base schema that maintains validation reliability and flexible extension schemas that enable rapid updates. This segmentation allows the base schema to remain unchanged for continued validation while extension schemas can be quickly modified to accommodate new transaction requirements.
Solution Approach 2:
The patent introduces dynamic extensibility to the previously static nonextensible schema system. The extension schemas can be dynamically added, modified, or removed without affecting the core validation framework, enabling rapid schema updates while maintaining document validation reliability.
Data Source
AI summary
A nonextensible schema is obtained including a first content model of ANY. Based on the nonextensible schema, a compact syntax regular language for XML next generation (RNC) file is generated that includes a second content model of ANY. The second content model of ANY can correspond to the first content model of ANY. The RNC file is modified, based upon the RNC file including the second content model of ANY, so as to explicitly enumerate all semantics of the second content model of ANY as elements in the RNC file. A regular language for XML next generation (RNG) file is later generated based on the modified RNC file. Related apparatus, systems, techniques and articles are also described.