XML Schema Namespace Segmentation for Coding Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for binary representation of XML-based documents, such as those based on the MPEG-7 standard, face compatibility issues due to unknown schemas at the start of transmission, leading to inefficient coding and decoding processes.

Innovation Solution

A method that generates independent codes for schemas and namespaces, allowing for separate coding and decoding without modifying existing code tables, even when many namespaces are involved, by using separate codes for elements, data types, and SubstitutionGroups, which can be loaded during transmission and reduce the number of bits required for addressing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If codes are generated based on all schemas and namespaces at the start of transmission, then complete coding coverage is achieved, but compatibility issues arise when schemas are unknown and code table regeneration is required

Engineering Contradiction:
Improvecoding compatibilityVSAvoidcode table management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the code space into separate namespaces, each with its own independent code table. This segmentation allows each namespace to be coded independently without requiring knowledge of other namespaces, eliminating the need for complete schema knowledge at transmission start and avoiding code table regeneration while maintaining coding compatibility.

Inventive Principle:
Principle #1Segmentation

2Measurement precision

If all schemas and namespaces are processed together, then comprehensive validation is achieved, but the number of bits required for addressing increases

Engineering Contradiction:
Improvevalidation accuracyVSAvoidbit usage efficiency
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

By segmenting the code space into separate namespaces with independent code tables, each namespace requires fewer addressing bits compared to a unified code table. This segmentation maintains validation accuracy within each namespace while significantly reducing the total bit usage efficiency, especially when dealing with large or numerous namespaces.

Inventive Principle:
Principle #1Segmentation

3Reliability

If code tables are regenerated when schemas change, then up-to-date coding is achieved, but transmission efficiency decreases due to modifications

Engineering Contradiction:
Improveschema conformanceVSAvoidtransmission efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent creates independent code tables for each namespace, allowing schemas within a namespace to evolve without affecting other namespaces. This segmentation enables localized schema updates without requiring global code table regeneration, maintaining schema conformance while preserving transmission efficiency by avoiding unnecessary modifications to the entire code structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables dynamic schema evolution within each namespace independently. Schemas can be added, modified, or removed in one namespace without triggering changes in other namespaces, allowing the system to adapt to changing requirements while maintaining stable, efficient transmission of existing namespaces.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7607080B2Method for coding structured documents
Publication Date: 2009.10.20 CALLAHAN CELLULAR LLC
  • US7607080B2 patent drawing
  • US7607080B2 patent drawing
  • US7607080B2 patent drawing

AI summary

The invention present disclosure relates to a method and device for coding a structured document, particularly such as a XML-based document, wherein a plurality of codes are generated by one or more schemas or namespaces, wherein independent codes are assigned for a schema and/or a namespace separately from other schemas and namespaces, for the elements defined or declared in the schemas or namespaces or in groups of schemas or namespaces.