Schema Information Document for XML Namespace Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing multiple XML schemas associated with a large number of XML documents is challenging, as users and components find it difficult to identify the correct schema for processing, especially when namespaces are shared among multiple schemas and URIs do not provide the physical location, leading to inefficient schema management in conventional systems.

Innovation Solution

A method and system for managing schemas involve registering schemas and associated schema documents, generating a schema information document, and processing requests using a schema manager and schema document manager to identify and manage schemas, including versioning and access control, with a three-part composite key for unique identification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple XML schemas are associated with a large number of XML documents using shared namespaces and URIs, then the system can support diverse document types and validation requirements, but users and components find it difficult to identify the correct schema for processing

Engineering Contradiction:
Improvesupport for diverse document typesVSAvoidschema identification
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent segments the schema identification process by introducing a schema information document that separates schema metadata (namespace, URI, version) from the actual schema content. This segmentation allows users to query schema information without needing to examine multiple schemas, thereby improving ease of operation while maintaining support for diverse document types through the structured information document that references multiple schemas.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The schema information document acts as an intermediary between the XML documents and the multiple XML schemas. It contains structured information including namespace, URI, and version details that mediate the identification process, allowing components to efficiently determine the correct schema without directly navigating through multiple schema files, thus resolving the contradiction between versatility and ease of operation.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If a namespace is used to identify XML schemas, then schemas can be organized and shared across multiple documents, but a namespace may imply multiple XML schemas making it insufficient for identifying a desired schema

Engineering Contradiction:
Improveschema sharingVSAvoidschema identification precision
Core Design Contradiction:
Adaptability or versatilityVSMeasurement precision

Solution Approach 1:

The patent segments the identification process into two parts: namespace for broad categorization and schema information document for precise identification. The information document breaks down the identification into structured fields (namespace, URI, version), allowing namespace to maintain its versatile schema-sharing function while the segmented information provides precise identification of the desired schema among multiple possibilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds another dimension to schema identification by introducing version information and structured metadata in the schema information document. This transforms the one-dimensional namespace identification into a multi-dimensional identification system that includes namespace, URI, and version, thereby maintaining namespace versatility while achieving precise schema identification.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Device complexity

If conventional systems manage XML schemas without dedicated management mechanisms, then implementation is simple, but it is difficult to identify a particular XML schema and manage schema versions

Engineering Contradiction:
Improvemanagement system complexityVSAvoidschema identification and management
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent applies preliminary action by generating and storing schema information documents that contain all necessary identification metadata (namespace, URI, version) before schemas are actually needed for processing. This preliminary organization of schema information allows for simple implementation while enabling easy identification and management, as the information is prepared in advance rather than requiring complex search mechanisms when needed.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a copy of essential schema information in the form of structured information documents that replicate key identification details (namespace, URI, version) without requiring access to the full schema content. This copying approach maintains simple system implementation while dramatically improving ease of operation for schema identification and version management.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS7433940B2Schema management
Publication Date: 2008.10.07 SAP SE
  • US7433940B2 patent drawing
  • US7433940B2 patent drawing
  • US7433940B2 patent drawing

AI summary

Disclosed is a method, system, and program for managing schemas. A schema and one or more associated schema documents are registered. A schema information document is automatically generated based on the schema and the one or more associated schema documents. A request to be performed on at least one of the schema, an associated schema document, and the schema information document is processed.