JSON Data Validation via XML Schema Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

JSON data validation methods are inefficient in systems with limited memory or storage capacity, as they often rely on large, human-readable formats similar to XML, which are not compatible with devices with restricted resources.

Innovation Solution

A method is introduced that generates a JSON schema (JSchema) to define JSON data structures, converts it to an XML schema, and then validates the JSON data based on the XML schema, reducing memory footprint by leveraging existing XML validation processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If JSON data is stored in human-readable text format, then readability and ease of processing are improved, but memory and storage capacity requirements increase

Engineering Contradiction:
ImprovereadabilityVSAvoidmemory capacity
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent creates a compact binary representation (copy) of the JSON data that preserves all essential information while reducing storage requirements. The system validates the binary format against the original schema without requiring the full human-readable text to be stored in memory simultaneously.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent transforms JSON data from one parameter state (human-readable text format with high memory usage) to another parameter state (compact binary format with reduced memory usage). This parameter change maintains data integrity and validity while optimizing for memory-constrained environments.

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If JSON validation is performed directly on JSON format, then validation accuracy is improved, but compatibility with memory-constrained devices deteriorates

Engineering Contradiction:
Improvevalidation accuracyVSAvoidmemory capacity
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The patent introduces an intermediary compact binary format that serves as a bridge between the original JSON data and the validation process. This intermediary representation reduces memory requirements while maintaining sufficient information for accurate schema validation, enabling deployment on memory-constrained devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If XML schema validation is used for JSON data, then validation reliability is improved, but format compatibility deteriorates

Engineering Contradiction:
Improvevalidation reliabilityVSAvoidformat compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a transformed copy of the JSON schema in XML Schema format, enabling the use of reliable XML validation tools and processes for JSON data. This copying approach leverages existing mature validation infrastructure while maintaining JSON data format compatibility through the transformation layer.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10606891B2JSON data validation
Publication Date: 2020.03.31 FUJITSU LTD
  • US10606891B2 patent drawing
  • US10606891B2 patent drawing
  • US10606891B2 patent drawing

AI summary

A JavaScript Object Notation (JSON) data validation method may include generating a description schema for defining JSON data using one or more JSON constructs. The method may further include converting the description schema to an Extensible Markup Language (XML) schema. The method may also include converting the JSON data to XML data, and validating the JSON data based on the XML Schema and the XML data.