Legal claims defining the scope of protection, as filed with the USPTO.
1. A method of processing a query about Extensible Markup Language (XML) data in a processing system, comprising: the first step of representing the XML data in the form of an XML graph; the second step of creating and updating an Adaptive Path indEX (APEX) based on used paths extracted from a previously processed XML queries and the XML graph; and the third step of processing an XML query using the APEX; wherein the APEX has a graph structure, each of nodes of the graph structure having an extent instead of an edge set of required paths; upon the system determining that a set of paths starting from a root are Q XML and a set of required paths each having a support greater than a user-specified minimum support or defined as a path having a length of 1 is R, the extent with respect to a path p is defined as E(p)=∪ r∈Q(p) T(r), where T(r) is an edge set for a path r, Q(P)=Q G (P)−Q A (P) and, with respect to a path p, Q G (p)={1|1∈Q XML and p is a suffix of 1} and Q A (P) ={1|1∈Q XML and every path q (≠p) ∈ R having p as a suffix is a suffix of 1}, where p, q and r are each a path; Q XML , Q(p), Q G (p) and Q A (P) are a set of paths; E(p) is the extent; and, T(r) is an edge set for the path r; and, E(p)=∪ r∈Q(p) T(r) is a union of a plurality of T(r) where r is in Q(p); and displaying the APEX.
2. The method as set forth in claim 1 , wherein the first step is performed by generating the XML graph in such a way that a relationship between an ID of the XML data and an IDREF type attribute is represented by an edge extending from an IDREF type node to a node representing an element having a corresponding ID type attribute, a label of the edge is adapted to have a label of the element, and a label of an edge indicating the IDREF type node is represented to be distinguished from labels of other edges.
3. The method as set forth in claim 1 , wherein the second step is performed in such a way that the APEX is created by creating an initial APEX representing information on a structural summary of the XML graph, extracting paths used more than a user-specified minimum support from a workload that is a path expression set of previously processed XML queries, and updating the initial APEX to include only the used paths, and the APEX is continuously updated.
4. The method as set forth in claim 2 , wherein the second step is performed in such a way that the APEX is created by creating an initial APEX representing information on a structural summary of the XML graph, extracting paths used more than a user-specified minimum support from a workload that is a path expression set of previously processed XML queries and updating the initial APEX to include only the used paths, and the APEX is continuously updated.
5. The method as set forth in any of claims 1 to 4 , wherein the APEX further comprises a hash tree, the hash tree comprising a count field for representing the frequency of use, a new field for representing whether a corresponding node is a newly created node, an xnode field for indicating the node of the graph structure and a next node for indicating a next node, the fields being continuously updated to reflect the variation of the workloads.
6. The method as set forth in claim 5 , wherein the updating of the APEX is performed by eliminating at least some used nodes and adding newly generated nodes to the graph structure while traversing the graph structure of the APEX and examining the entries of the hash tree with respect to each of the nodes.
Unknown
August 21, 2007
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.