XML Structural Condition Rewriting for High-Speed Search
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing structured document management systems face inefficiencies in searching XML data due to difficulties in processing ancestor, sibling, and order structural conditions, which hinder high-speed structure matching and increase complexity, especially when dealing with external resources or temporarily generated documents.
Innovation Solution
A structured document management device with a query data receiving unit, structural condition dividing unit, and structural condition rewriting unit that rewrites non-descendant structural conditions into join operations with descendant conditions, allowing for efficient processing and simplifying the configuration by applying rewritten conditions only to refined document sets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If ancestor structural condition, sibling structural condition, or order structural condition is used in structure matching, then the structural condition can express complex hierarchical relationships, but the structure matching process cannot be performed at high speed
Solution Approach 1:
The patent segments the structure matching process into two distinct phases: a preprocessing phase that transforms ancestor, sibling, and order structural conditions into descendant structural conditions with position information, and an execution phase that performs high-speed matching using only descendant conditions. This segmentation allows complex structural expressions to be converted into simpler, faster-to-process forms.
Solution Approach 2:
The patent applies preliminary transformation of structural conditions before the actual matching process. By converting ancestor, sibling, and order conditions into descendant conditions with position metadata in advance, the system prepares the query in a form that enables high-speed execution without sacrificing structural expression capability.
2Speed
If structure guide ID is allocated to accelerate structure matching, then matching speed improves, but the configuration becomes complex and structure guide cannot be determined for external resources
Solution Approach 1:
The patent extracts the structure guide ID mechanism from the query processing system and replaces it with position information that is inherently available in XML documents. Instead of requiring external structure guides, the system uses position metadata (such as document position, element position) that can be determined for any XML document including external resources and temporarily generated documents.
Solution Approach 2:
The patent enables the XML document itself to provide the necessary structural information through its inherent position metadata, eliminating the need for external structure guide IDs. The document's own structural properties (position information) are used to enable high-speed matching, making the system self-sufficient.
3Adaptability or versatility
If XQuery transformation process is applied to convert structural conditions, then structure matching can be performed, but the process overhead is heavy and performance deteriorates when applied to entire document sets
Solution Approach 1:
The patent extracts only the essential position information from the XML document structure, rather than performing comprehensive XQuery transformations. This selective extraction of position metadata (document position, element position) significantly reduces processing overhead while maintaining the ability to handle complex structural conditions.
Solution Approach 2:
The patent changes the representation parameters of structural conditions from complex XQuery expressions to simplified position-based parameters. By transforming structural conditions into forms that use position information (document position, element position, appearance order), the system achieves faster processing without losing structural expression capability.
Data Source
AI summary
According to an embodiment, a structured document management device includes a query data receiving unit; a structural condition dividing unit; a structural condition rewriting unit; and a query execution unit. The query data receiving unit is configured to receive query data for searching a structured document. The structural condition dividing unit is configured to divide the query data into elements including a structural condition. The structural condition rewriting unit is configured to rewrite the structural condition into a rewritten query when a type of the structural condition is other than a descendant structural condition. The rewritten query is predetermined to include a joining process with a descendant structural condition so as not to affect structural conditions appearing before and after the structural condition. The query execution unit is configured to output a search result in response to query data that includes the structural condition and the rewritten query.