Dynamic XML Default Value Configuration via Code Execution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing XML validation technologies, such as DTDs and XML schemas, cannot dynamically set default values for XML elements based on the content of other elements or semantically validate text content, limiting their ability to adapt to changing data structures.

Innovation Solution

A system that generates and configures default data values for XML data trees by parsing consumer input data XML files and executing default data generation code specified in data preprocessing instructions XML files, allowing for dynamic default setting and validation of node content.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If DTDs or XML schemas are used to specify default values for XML elements, then default values can be provided for elements and attributes, but these default values are hardwired and cannot be automatically calculated or adjusted based on other element content

Engineering Contradiction:
Improveadaptability of default valuesVSAvoidcomplexity of validation system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent transforms static, hardwired default values in DTDs/XML schemas into dynamic defaults that are automatically calculated at runtime. The system uses code execution engines to compute default values based on current document content, other element values, and contextual information, making the default value assignment adaptive rather than fixed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent introduces intermediary components including a default value calculation engine, code execution environment, and configuration files that mediate between the XML document and the validation system. These intermediaries enable complex default value generation while keeping the core XML parsing and validation systems relatively simple and unchanged.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If DTDs or XML schemas are used for validation, then structural validation can be performed, but semantic validation of text content cannot be achieved

Engineering Contradiction:
Improvedata integrityVSAvoidcomplexity of validation system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal validation framework that can perform both structural validation (inherited from DTD/XML schema) and semantic validation (new capability). The system uses a configurable validation engine that executes custom code to perform semantic checks on text content, making the validation system multi-functional without requiring separate systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent changes the validation approach from fixed structural rules to flexible, parameter-driven validation. By allowing validation rules to be specified through configuration files and executable code with adjustable parameters, the system can adapt validation criteria to semantic requirements while maintaining the underlying structural validation capabilities.

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If configurable default values are implemented through code execution, then dynamic default setting is enabled, but processing time and system complexity increase

Engineering Contradiction:
Improveflexibility of default configurationVSAvoidprocessing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by allowing default value calculation logic to be pre-configured in configuration files and compiled or prepared in advance. The system caches validation rules and default value generation logic, so that during actual document processing, the execution involves calling pre-prepared functions rather than interpreting raw configuration from scratch, reducing processing time.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS8200714B2Apparatus, systems and methods for configurable defaults for XML data
Publication Date: 2012.06.12 ORACLE AMERICAN INC
  • US8200714B2 patent drawing
  • US8200714B2 patent drawing
  • US8200714B2 patent drawing

AI summary

A data tree is generated in memory by parsing a first XML file. Default setting requests and validation requests are read from a second XML file. Default data values for nodes in the data tree are generated by executing default data generation code from locations specified in the default setting requests and recorded in the data tree. The content of data stored in nodes of the data tree is then validated by executing validation code from locations specified in the validation requests. The data tree is then searched by getting a nodepath, parsing the nodepath into a plurality of path pieces, searching the data tree based on each of the path pieces, and returning one or more nodes of the data tree based on the search that satisfy the path pieces. A data value of one or more nodes or child nodes may be specified to narrow the search.