RNG Schema Conversion for cXML Extensibility and Stability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current commerce eXtensible Markup Language (cXML) schemas, such as nonextensible Document Type Definitions (DTDs), often lack necessary information fields and lead to redundancy and misinterpretation of custom extrinsics, making it difficult for senders and receivers to communicate effectively, especially when custom fields are used.

Innovation Solution

A method and system for generating and distributing regular language for XML next generation (RNG) files, which allow for the creation of both extensible and nonextensible schemas, enabling the inclusion of custom fields and facilitating communication by converting nonextensible schemas into RNG files, and subsequently into XML Schema Definition (XSD) and DTD formats, thereby supporting both schema formats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If nonextensible schemas (DTDs) are used to maintain schema stability and prevent arbitrary modifications, then schema reliability is improved, but adaptability deteriorates because custom fields and extrinsics cannot be easily added

Engineering Contradiction:

Improveschema stabilityVSAvoidcustom field inclusion

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The schema is segmented into a core nonextensible DTD portion and an extensible RNG portion. The core DTD maintains stability and reliability for standard cXML elements, while the RNG schema provides extensibility for custom fields and extrinsics. This segmentation allows each part to fulfill its specific function without compromising the other.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The RNG schema acts as an intermediary between the stable DTD and the need for extensibility. It references the DTD for core structure validation while adding its own grammar rules for custom fields, effectively mediating between the conflicting requirements of stability and adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If senders create custom extrinsics to include additional information, then adaptability is improved, but device complexity worsens due to redundancy and lack of standardization

Engineering Contradiction:

Improvecustom information inclusionVSAvoidschema management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The RNG schema provides a universal framework that can accommodate both standard cXML elements and custom fields through a unified grammar structure. Instead of each sender creating isolated custom extrinsics, the RNG schema offers standardized mechanisms (such as datatypes, constraints, and inheritance) that serve multiple purposes and reduce redundancy.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The schema system transitions from fixed DTD parameters to flexible RNG parameters. RNG allows parameterized definitions of custom fields with configurable datatypes, constraints, and relationships, enabling adaptability without proportionally increasing complexity through systematic parameter management.

Inventive Principle:

Principle #35Parameter changes

3Adaptability or versatility

If the schema is updated to include new fields, then adaptability is improved, but loss of time increases due to schema validation and conversion processes

Engineering Contradiction:

Improveschema extensibilityVSAvoidschema processing time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The RNG schema is prepared in advance with predefined grammar rules, datatypes, and constraints for both standard and custom fields. This preliminary structuring allows for faster validation during document processing, as the validation logic is pre-compiled and organized rather than constructed on-demand.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses schema templates and references that can be copied and reused. Once an RNG schema is created with custom field definitions, it can be referenced by multiple cXML documents and updated centrally, avoiding repeated validation overhead and enabling efficient schema propagation.

Inventive Principle:

Principle #26Copying

4Adaptability or versatility

If a centralized schema repository is implemented to manage schemas, then adaptability is improved through standardization, but device complexity worsens due to file directory structure management

Engineering Contradiction:

Improveschema standardizationVSAvoidfile management complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The schema repository is organized in a hierarchical file directory structure that mirrors the logical schema relationships. This dimensional organization (files, directories, namespaces) provides a natural mapping between physical storage and logical schema structure, making the complexity manageable through familiar file system concepts rather than abstract data structures.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS20180181547A1Converting RNG Files to Extensible and Nonextensible XML Schemas

Publication Date: 2018.06.28 SAP SE

AI summary

A regular language for XML, next generation (RNG) file referencing an RNG schema file is obtained. Subsequently, the referenced RNG schema file is stored in a file directory structure matching a reference definition of the schema in the RNG file. Based on the RNG file, a first nonextensible schema and a first extensible schema are generated each corresponding to the referenced RNG schema file. Related apparatus, systems, techniques and articles are also described.