Extensible XML Schema Generation via RNC and RNG Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current commerce eXtensible Markup Language (cXML) schemas, particularly nonextensible Document Type Definitions (DTDs), often lack necessary information fields, leading to redundancy and manageability issues due to custom extrinsics, which can be misunderstood by commerce hubs and result in inefficient document processing.
Innovation Solution
A method and system for generating compact syntax regular language for XML next generation (RNC) files from nonextensible schemas, then converting these to regular language for XML next generation (RNG) files, and subsequently creating both extensible and nonextensible schemas, allowing for the inclusion of custom extensions and plugins to enhance information exchange between senders, commerce hubs, and recipients.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If custom extrinsics are added to cXML documents to include additional information fields, then the information completeness is improved, but the schema manageability and processing efficiency deteriorate due to redundancy and lack of standardization
Solution Approach 1:
The patent segments the schema into a core nonextensible schema (defining standard fields) and separate extensible schema files (defining custom extrinsics). This segmentation allows custom information fields to be added without modifying or managing the core schema, thus maintaining information completeness while improving schema manageability by isolating customizations into independent, versioned files.
Solution Approach 2:
The patent introduces an intermediary schema layer that sits between the core nonextensible schema and the cXML documents. This intermediary extensible schema acts as a mediator that standardizes custom extrinsics, allowing senders to include additional information fields while enabling the commerce hub to process them efficiently through predefined schemas, thus resolving the manageability issue.
2Adaptability or versatility
If senders create their own custom extrinsics for specific functional uses, then the adaptability to specific needs is improved, but the system complexity increases due to redundancy and the need for mapping
Solution Approach 1:
The patent creates a universal extensible schema framework that can accommodate multiple custom extrinsics for the same functional use through a standardized structure. Instead of each sender creating entirely separate custom schemas, the universal framework provides a common namespace and structure that multiple senders can utilize, reducing redundancy while maintaining adaptability to specific functional needs.
Solution Approach 2:
The patent enables adaptability through parameter changes in the extensible schema definitions, where custom extrinsics are defined with configurable parameters such as namespaces, data types, and validation rules. This allows the schema to adapt to specific functional needs by modifying parameters in the extensible schema files without changing the core schema or creating entirely new custom extrinsics for each use case.
3Loss of information
If the nonextensible schema is updated to include all desired information fields, then the information completeness is improved, but the schema modification complexity and risk of breaking existing documents increases
Solution Approach 1:
The patent segments the schema into core nonextensible and extensible components, allowing information completeness to be improved by adding fields only to the extensible schema portion. This segmentation enables schema updates to be made locally in the extensible schema files without risking breaks to existing documents that rely on the stable core schema, thus improving update ease while maintaining information completeness.
Solution Approach 2:
The patent performs preliminary action by pre-defining extensible schema files that contain templates for custom extrinsics. This preliminary setup allows senders to include additional information fields using predefined schemas before any document exchange occurs, eliminating the need to modify the core schema later and reducing the risk of breaking existing documents while achieving information completeness.
Data Source
AI summary
A first nonextensible schema is obtained, based on the first nonextensible schema, a compact syntax regular language for XML next generation (RNC) file. A regular language for XML next generation (RNG) file can be generated based on the RNC file. Based on the RNG file, a second (core) nonextensible schema and a first (core) extensible schema can be generated. An extensible (extension) schema and a nonextensible (extension) schema can also be generated. The extensible (extension) schema and the nonextensible (extension) schema can be plugged into the RNG file. The RNG file can be regenerated with the plugins, and a third nonextensible schema and a second extensible schema can be generated based on the regenerated RNG file. Related apparatus, systems, techniques and articles are also described.