Method and/or system for tagging trees

Information

  • Patent Grant
  • 10380089
  • Patent Number
    10,380,089
  • Date Filed
    Friday, July 2, 2010
    15 years ago
  • Date Issued
    Tuesday, August 13, 2019
    6 years ago
  • CPC
    • G06F16/2246
  • Field of Search
    • US
    • 707 797000
    • CPC
    • G06F17/30961
    • G06F17/30327
    • G06F17/30864
    • G06F17/30595
    • G06F16/2246
    • G06Q10/06
  • International Classifications
    • G06F16/22
Abstract
Embodiments of methods and/or systems for tagging trees are disclosed.
Description
BACKGROUND

This disclosure is related to navigating trees.


In a variety of fields, data or a set of data, may be represented in a hierarchical fashion. This form of representation may, for example, convey information, such as particular relationships or patterns between particular pieces of data or groups of data and the like. However, manipulating and/or even recognizing specific data representations or patterns is not straight-forward, particularly where the data is arranged in a complex hierarchy. Without loss of generality, examples may include a database, and further, without limitation, a relational database. Techniques for performing operations on such databases or recognizing specific patterns, for example, are computationally complex, time consuming, and/or otherwise cumbersome. A need, therefore, continues to exist for improved techniques for performing such operations and/or recognizing such patterns.





BRIEF DESCRIPTION OF THE DRAWINGS

Subject matter is particularly pointed out and distinctly claimed in the concluding portion of the specification. The claimed subject matter, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference of the following detailed description when read with the accompanying drawings in which:



FIG. 1 is a schematic diagram of embodiments of several unordered edge-labeled trees and symbolic expressions mathematically representing the tree embodiments;



FIG. 2 is a schematic diagram of embodiments of several unordered edge-labeled trees and symbolic expressions mathematically representing the tree embodiments;



FIG. 3 is a schematic diagram of embodiments of several unordered edge-labeled trees and symbolic expressions mathematically representing the tree embodiments;



FIG. 4 is a schematic diagram illustrating an embodiment of an unordered edge-labeled tree and a symbolic expression mathematically representing the tree embodiment;



FIG. 5 is a schematic diagram illustrating all N-valued rooted, unordered edge-labeled trees, where N is a natural numeral greater than or equal to 2;



FIG. 6 is a table providing an embodiment of a function that relates natural numerals to composite numerals;



FIG. 7 is a table providing symbolic expressions for an embodiment of rooted, unordered, 2-valued edge-labeled trees;



FIG. 8 is a table providing symbolic expressions for an embodiment of rooted, unordered, 3-valued edge-labeled trees;



FIG. 9 is a table providing symbolic expressions for an embodiment of rooted, unordered, 4-valued edge-labeled trees;



FIG. 10 is a table providing symbolic expressions for an embodiment of rooted, unordered, 5-valued edge-labeled trees;



FIG. 11 is a table providing symbolic expressions for an embodiment of rooted, unordered, 6-valued edge-labeled trees;



FIGS. 12 and 13 provide an embodiment of a table relating the natural numerals and embodiments of different tree views;



FIG. 14 is a schematic diagram of an unordered node labeled tree;



FIG. 15 is a schematic diagram of an unordered edge labeled tree;



FIG. 16 is a table illustrating an embodiment of a relationship between BELTs and natural numerals;



FIG. 17 is a schematic diagram illustrating an embodiment of merging two edge-labeled trees;



FIG. 18 is a table illustrating an embodiment of a set of rules to covert natural numerals to strings;



FIG. 19 is a table illustrating an embodiment of an association between natural numerals and a set of strings;



FIGS. 20-24 are a sequence of operations illustrating a technique to implement one embodiment of a method of tagging a tree; and



FIGS. 25-28 are a sequence of operations illustrating a technique to implement another embodiment of a method of tagging a tree.





DETAILED DESCRIPTION

In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the claimed subject matter. However, it will be understood by those skilled in the art that the claimed subject matter may be practiced without these specific details. In other instances, well-known methods, procedures, components and/or circuits have not been described in detail so as not to obscure the claimed subject matter.


Some portions of the detailed description which follow are presented in terms of algorithms and/or symbolic representations of operations on data bits or binary digital signals stored within a computing system, such as within a computer or computing system memory. These algorithmic descriptions and/or representations are the techniques used by those of ordinary skill in the data processing arts to convey the substance of their work to others skilled in the art. An algorithm is here, and generally, considered to be a self-consistent sequence of operations and/or similar processing leading to a desired result. The operations and/or processing involve physical manipulations of physical quantities. Typically, although not necessarily, these quantities may take the form of electrical and/or magnetic signals capable of being stored, transferred, combined, compared and/or otherwise manipulated. It has proven convenient, at times, principally for reasons of common usage, to refer to these signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals and/or the like. It should be understood, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as apparent from the following discussion, it is appreciated that throughout this specification discussions utilizing terms such as “processing”, “computing”, “calculating”, “determining” and/or the like refer to the actions and/or processes of a computing platform, such as a computer or a similar electronic computing device, that manipulates and/or transforms data represented as physical electronic and/or magnetic quantities and/or other physical quantities within the computing platform's processors, memories, registers, and/or other information storage, transmission, and/or display devices.


In a variety of fields, data or a set of data, may be represented in a hierarchical fashion. This form of representation may, for example, convey information, such as particular relationships or patterns between particular pieces of data or groups of data and the like. However, manipulating and/or even recognizing specific data representations or patterns is not straight-forward, particularly where the data is arranged in a complex hierarchy. Without loss of generality, examples may include a database and further, without limitation, a relational database. Techniques for performing operations on such databases or recognizing specific patterns, for example, are computationally complex, time consuming, and/or otherwise cumbersome. A need, therefore, continues to exist for improved techniques for performing such operations and/or recognizing such patterns.


As previously discussed, in a variety of fields, it is convenient and/or desirable to represent data, a set of data and/or other information in a hierarchical fashion. In this context, such a hierarchy of data shall be referred to as a “tree.” In a particular embodiment, a tree may comprise a finite, rooted, connected, acyclic graph. Likewise, such trees may be either ordered or unordered. Here, ordered refers to the notion that there is an ordering or precedence among nodes attached to a common node corresponding to the order of the attached nodes shown in a graphical illustration. An unordered tree, is illustrated here, for example, in FIG. 15 by embodiment 100. As illustrated, the root of this particular embodiment encompasses node 105. In addition to 105, there are eight other nodes designated 110 to 145, respectively. Likewise, the nodes are connected by branches referred to, in this context, as edges. Thus, the nodes of this tree are connected by eight edges. This embodiment, therefore, illustrates a finite tree that is rooted by node 105. Furthermore, the nodes are connected, meaning, in this context, that a path exists between any two nodes of the tree. The tree is likewise acyclic, meaning here, that no path in the tree forms a complete loop.


As previously suggested, in a variety of contexts, it may be convenient and/or desirable to represent a hierarchy of data and/or other information using a structure, such as the embodiment illustrated in FIG. 15. One particular embodiment, without loss of generality, of a tree may include edges that are labeled with data and/or other values. Likewise, in one particular embodiment, such data and/or values may be limited to a particular set of data. For example, in this context, a binary edge labeled tree refers to a tree in which the data and/or values comprise binary data, that is, in this example, either a binary one or a binary zero. Likewise, alternatively, the edges of a tree may be labeled with three values, such as 0, 1, 2. Continuing, the edges may be labeled with four values, five values, etc. In this context, the class of all trees in which the edges are labeled with a specific number of distinct values, that is, in this context, values chosen from a set having a specific number of distinct elements, shall be referred to as edge-labeled trees (ELTs). It is likewise noted that such trees are not limited to being labeled with the numerals previously described. Any distinctly identifiable labels may be employed; however, in this context, it shall be understood that employing numerals to label the edges is sufficiently general to encompass any sort of data labels that may be desirable, regardless of their form.


To reiterate, in this context, a tree comprises an edge labeled tree if each edge of the string or tree respectively stores a value or single piece of data. Likewise, in this context, two nodes are employed to support an edge holding a single piece of data. At this point, it is worth noting that trees having nodes and edges, such as previously described, may be represented in a computing platform or similar computing device through a data structure or a similar mechanism intended to capture the hierarchical relationship of the data, for example. It is intended that all such embodiments are included within the scope of the claimed subject matter.


It is noted that binary edge labeled trees (BELTs) may be listed or enumerated. See, for example, U.S. provisional patent application Ser. No. 60/543,371, titled “Manipulating Sets of Hierarchical Data,” filed on Feb. 9, 2004, by J. J. LeTourneau, and assigned to the assignee of the current provisional application. This is illustrated, here, for example, in FIG. 16. It is noted that this particular figure also includes the associated natural numerals. The association of such numerals for this particular embodiment should be clear based at least in part on previously cited U.S. provisional patent application Ser. No. 60/543,371. However, it is, of course, again noted that the claimed subject matter is not limited in scope to employing the approach or approaches described in aforementioned U.S. provisional patent application Ser. No. 60/543,371. U.S. provisional patent application Ser. No. 60/543,371 is provided simply as an example of listing or enumerating unordered BELTs.


However, for this particular embodiment, although the claimed subject matter is not limited in scope in this respect, a method of enumerating a set of unordered trees may begin with enumeration of an empty binary edge labeled tree and a one node binary edge labeled tree. Thus, the empty tree is associated with the natural numeral zero and has a symbolic representation as illustrated in FIG. 16 (circle). Likewise, the one node tree, which holds no data, is associated with the natural numeral one and has a graphical representation of a single node. For higher positive natural numbers, ordered trees may be generated by a process described, for example, in “The Lexicographic Generation of Ordered Trees,” by S. Zaks, The Journal of Theoretical Computer Science, Vol. 10(1), pp 63-82, 1980, or, “Enumerating Ordered Trees Lexicographically,” by M. G. Er, Computation Journal, Vol. 28, Issue 5, pp 538-542, 1985. This may be illustrated, for example in FIG. 16, as described in more detail below.


As illustrated, for this particular embodiment, and as previously described, the empty tree has zero nodes and is associated with the natural numeral zero. Likewise, the one node tree root comprises a single node and is associated with the natural numeral one. Thus, to obtain the tree at position two, a root node is attached and connected to the prior root node by an edge. Likewise, here, by convention, the edge is labeled with a binary zero. If, however, the tree formed by the immediately proceeding approach were present in the prior enumeration of trees, then a similar process embodiment is followed, but, instead, the new edge is labeled with a binary one rather than a binary zero. Thus, for example, to obtain the binary edge labeled tree for position three, a new root node is connected to the root node by an edge and that edge is labeled with a binary one.


Continuing with this example, to obtain the binary edge labeled tree for position four, observe that numeral four is the product of numeral two times numeral two. Thus, a union is formed at the root of two trees, where, here, each of those trees is associated with the positive natural numeral two. Likewise, to obtain the binary edge labeled tree for position five, begin with the binary edge labeled tree for position two and follow the previously articulated approach of adding a root and an edge and labeling it with a binary zero.


In this context, adding a root node and an edge and labeling it binary zero is referred to as a “zero-push” operation and adding a root node and an edge and labeling it binary one is referred to as a “one-push” operation. Thus, referring again to FIG. 16, the one-push of the root tree is the tree at position three. This follows from FIG. 9 of previously referenced U.S. provisional patent application Ser. No. 60/543,371, since Q((1*2)−1)=Q(1)=3. Likewise, the tree at position five is the zero-push of the tree at position 2. Again, this follows from FIG. 9 of the previously referenced US provisional patent application, since Q((2*2)−2)=Q(2)=5.


In the embodiment just described, binary edge labeled trees use binary numerals “0” and “1.” However, the claimed subject matter is not limited in scope to binary edge labeled trees. For example, trees may employ any number of numeral combinations as labels, such as triplets, quadruplets, etc. Thus, using a quadruplet example, it is possible to construct trees, such as a zero-push of a particular tree, a one-push of that tree, a two-push of that tree, and a three-push of that tree. Thus, for such trees, edges may be labeled 0, 1, 2 or 3, etc., as previously described and as explained in more detail hereinafter.


The foregoing discussion has begun to characterize an algebra involving trees, in this particular embodiment, an algebra for unordered edge labeled trees or unordered ELTs, such as BELTs. The foregoing discussion defines a value zero, a zero node tree for this particular embodiment, a value one, a one node tree for this particular embodiment, and a monadic operation, previously described as zero-push. For example, alternatively, a “one-push” may be employed. For this embodiment, this is analogous, for example, to the convention that “0” represent “off” and “1” represent “on.” Alternatively and equivalently, “1” may be employed to represent “off,” and “0” may be employed to represent “on,” without loss of generality. For this particular embodiment, an additional operation may be characterized, a “merger” operation. The merger operation with respect to trees refers to merging two trees at their roots. This operation is illustrated, for example, in FIG. 17.


As will now be appreciated, the merger operation comprises a binary operator. Likewise, the constants zero/one, referred to above, may be viewed as an operation having no argument or as a zero valued argument operator or operation. Thus, this operation, in effect, returns the same value whenever applied. Here, for this particular embodiment, the constant value, or zero valued argument operation that returns “c” and is denoted as “c.” The merger operator is denoted as “*”.



FIG. 4 is schematic diagram illustrating an embodiment of an edge labeled tree, here a 4 valued edge labeled tree. In this particular embodiment, four distinct values are employed to label the edges. Here, the labels comprising A, B, C and D, although, of course, the claimed subject matter is not limited to 4 valued edge labeled trees, to edge labeled trees, or to employing these particular edge labels. It is noted that the labels A, B, C, and D in this embodiment are similar to the labels binary 0 and binary 1 for BELTs. Below tree 400 is a symbolic expression mathematically representing tree 400. Performing the operations indicated by the expression shown in FIG. 4 below tree 400 will provide a natural numeral that corresponds, for this particular embodiment, to this particular tree, as described in more detail hereinafter.


To assist in understanding the relationship between the symbolic expression shown in FIG. 4 and tree 400, for this particular embodiment, FIG. 1 provides an embodiment 110 of another tree. As illustrated, tree 110 comprises an edge label D connecting two nodes. For this particular context, this embodiment may be expressed symbolically as follows: D(1). Thus, a technique to describe the embodiment of tree 110 would refer to the “push” of the natural number 1. Here, for this particular embodiment, this particular push operation comprises the “D” push of 1, resulting in D being the label of the edge connecting the two nodes. More specifically, as previously described, a single node comprises the natural numeral 1 in this particular embodiment. To perform a push operation, an edge is attached to that node and labeled. Here, applying a D push, the label provided comprises the label D.


Continuing, the “C” push of “1” is illustrated as two nodes with an edge labeled C connecting the two nodes for tree embodiment 120. Applying similar reasoning provides an edge labeled tree embodiment 130 representing the following expression: B(C(1)). Likewise, for this particular embodiment, the operation of merger may be represented as “*”, as previously suggested. Thus, applying a merger operation provides tree embodiment 140 at the bottom of FIG. 1 corresponding, for this particular embodiment, to the following expression: (D(1)*B(C(1))). Applying similar reasoning to FIGS. 2 and 3 and the tree embodiments shown ultimately produces tree 400 illustrated in FIG. 4, along with the corresponding symbolic expression.


As the previous discussion suggests, here A, B, C and D comprise monadic operators and the merger operation comprises a binary operation. In U.S. provisional patent application No. 60/575,784, titled “Method and/or System for Simplifying Tree Expressions, such as for Pattern Matching,” filed May 28, 2004, by J. J. LeTourneau, assigned to the assignee of the current application, monadic operators similar to those described here were designed as successor operators, using the symbol S(x). Here, these monadic operators comprise multiple successive operators.


Previously, an embodiment for manipulating binary edge labeled trees or BELTs was described in connection with U.S. provisional patent application 60/543,371. In that context, binary edge labeled trees comprise finite rooted, unordered two valued edge labeled trees. Thus, for the particular embodiment of binary edge labeled trees described, the two values comprise “0” and “1,” although alternately they could comprise A and B, for example, or any other two values. Referring now to FIG. 5, a Venn diagram 500 is illustrated providing the set of all edge labeled trees, structured or organized in a particular manner here. In the center of the diagram, binary or two valued edge labeled trees are depicted as a subset. Furthermore, as illustrated, two valued edge labeled trees are also depicted as a subclass or subset of three valued edge labeled trees. Likewise, three valued edge labeled trees are depicted as a subclass or subset of four valued edge labeled trees and so forth. Thus, depending at least in part on the particular set of distinct values employed to label the edges, an edge labeled tree that employs two distinct values may comprise an example of a three valued edge labeled tree in which one of the values is specifically not employed in the particular tree. As shall be explained in more detail hereinafter, this raises a question regarding proper interpretation of the data that the tree may represent or store. More specifically, an identical tree may represent different data depending at least in part on whether the tree is “viewed” as, to continue with this example, a two valued edge labeled tree or a three valued edge labeled tree. Thus, in this embodiment, we refer to this as the “view” of the particular tree. For example, a two valued edge labeled tree is referred to as view 2 and a three valued edge labeled tree is referred to as view 3, although, for example, the particular tree may not contain three different values. The view in this embodiment refers to the set of distinct values from which the labels may be selected, as previously described. FIG. 5 therefore depicts the set of all edge labeled trees as the union of all such edge labeled trees in which the edge values are selected from a set having a specific number of distinct values.


Previously in U.S. provisional application 60/543,371, an embodiment was demonstrated in which an association existed between natural numerals and binary edge labeled trees. For this particular embodiment, similar associations also exist, here between any N valued edge labeled tree and the natural numerals, where N is a numeral. Of course, many different associations are possible and the claimed subject matter is intended to cover all such associations regardless of the particular embodiment. Thus, for example, three valued edge label trees may be converted to numerals, four valued edge labeled trees may be converted to numerals and so forth. Thus, manipulations, such as those previously described, for example, in aforementioned provisional U.S. patent application 60/543,371, as well as additional manipulations, may be applied to N valued edge labeled trees, as described in more detail hereinafter.


As suggested in previously referenced U.S. provisional application 60/543,371, in one particular embodiment, when converting between binary edge labeled trees and numerals, a relationship was found to exist between a “push” operation and non-composite numerals. Thus, in this context, it may be convenient to define an operation indexed by the natural numerals that provides in ascending order the non-composite numerals, although, of course, the claimed subject matter is not limited in scope in this respect. Such an operation is depicted specifically in FIG. 6. As described in more detail hereinafter, this operation is also convenient in this context in connection with edge labeled trees of any number of distinct edge values.


As previously suggested in aforementioned U.S. provisional patent application No. 60/575,784, a set of congruence operations on the set of tree expressions may be isomorphic to the set of finite, rooted, unordered binary edge labeled trees. Thus, or more particularly, under such an isomorphism, in the particular embodiment, a one-to-one relationship between the equivalence classes that satisfy the tree expressions and the finite, rooted, ordered binary edge labeled trees may exist.


Thus, beginning with binary edge labeled trees or finite rooted unordered two valued edge labeled trees, but continuing to edge labeled trees of higher numbers of values, such as, for example, three valued edge labeled trees, four valued edge labeled trees and so forth, for this embodiment, a similar association or relationship between tree expressions and edge labeled trees may be constructed. Thus, for this embodiment, with a set of operations that satisfies a set of tree expressions an isomorphism with a set of finite routed unordered N valued edge labeled trees results in a similar one to one relationship between the equivalence classes that satisfy the tree expressions and the edge labeled trees themselves. Likewise, by demonstrating that these tree expressions are also isomorphic with natural numerals, tree manipulations are able to be constructed for edge labeled trees using natural numerals, as had similarly been done for binary edge labeled trees. Thus, as shall become more clear hereinafter, manipulating tree expressions is isomorphic to manipulating numerals for this particular embodiment.


Previously, binary edge labeled trees have been discussed. For purposes of illustration, it shall instructive to now discuss another type of edge labeled tree, such as four valued edge labeled trees. For example, FIG. 9 corresponds to finite rooted unordered four valued edge labeled trees, which were also discussed previously with respect to FIG. 4. Thus, for this example embodiment, an algebra may be constructed that is isomorphic to the natural numerals for such four valued edge labeled trees. Likewise, similar algebras may be constructed by use a similar set of tree expressions, as shown, for example, by FIGS. 7, 8, 10 and 11. The similarity of these expressions allows us to write a schema or generalized description and thereby cover all such similar algebras.


Thus, similar to an approach previously described, FIG. 9 provides a set of constants and operators here, constants 0 and 1, monadic operators A, B, C, and D and binary operator *. Thus, we designate this algebra with the signature <2,4,1> as a result. The expressions for this particular embodiment are provided in FIG. 9. The first expression, 910, denotes communitivity and the second expression, 920, denotes associativity. Likewise, the next two expressions, 930, define the relationship of the merger of the constants with any other value. The next four expressions, 940, define the monadic operators A, B, C and D.


Thus, for this embodiment, these expressions therefore define a set of edge labeled trees with particular properties. Specifically, the properties are isomorphic to the natural numerals. Thus, as shall be demonstrated further, for this embodiment, four valued edge labeled trees, for example, may be manipulated using natural numerals.


At least in part because natural numerals are isomorphic to N valued trees, a way to depict this relationship for this embodiment is illustrated by FIGS. 12 and 13. Previously, a particular view for a particular edge labeled tree, for this embodiment, was discussed. In these figures, each column represents a different potential view for a set of edge labeled trees for this embodiment. Likewise, each row provides the edge labeled tree in the view corresponding to the column for the natural number on the left-hand side of FIG. 12.


For example, column one shows the trees with for two valued edge labeled trees edges, otherwise referred to as binary edge labeled trees. Thus, as previously described, no nodes corresponds to “0”. Continuing, a single node corresponds to “1” or to “root”. Likewise, the numerals two and three in this view turn out to be push operations. In this case, the numeral 2 is the tree corresponding to the A push of one denoted A(1). Likewise, the numeral 3 is the tree corresponding to the B push of one, denoted B(1).


For this embodiment, these relationships may also be confirmed by referring back to FIG. 7. Here, the operations A(x) and B(x) as defined in terms of the function, previously defined in connection with FIG. 6. Thus, using these expressions, to determine the push of 1 denoted A(1), as provided in FIG. 7, this is Q((2*1)−2). This provides Q(0) or the value 2, as demonstrated from FIG. 6. As similar result may be obtained for B(1). Referring to FIG. 7, this corresponds to Q((2*1)−1), or Q(1), again from FIG. 6, the value 3.


A similar relationship may be established for three valued edge labeled trees, described by the expressions provided in FIG. 8, for example. Referring again to FIGS. 12 and 13, the edge labeled trees corresponding to these expressions are depicted in the second column. It is noted that the tree structures using this notation are the same between the first column and the second column for the numerals from zero to four. However, a difference is noted between the first column and the second column at numeral 5. Thus, for view 3, the numeral 5 is the C push of 1. More particularly, again referring to FIG. 8, C(1) equals Q(3*1)−1), or Q(2). From FIG. 6, the corresponding value is 5, as previously suggested. Similarly, looking at column 3 of FIG. 12, for view 5, the D push of 1 is numeral 7.


Thus, for this embodiment, regardless of the “view” of the edge labeled trees, there is a unique one to one correspondence, here, an association embodiment, between the natural numerals and that set of edge labeled trees. This embodiment, therefore, provides the capability to manipulate and combine edge labeled trees of different view. For example, for two edge labeled trees from two different views, one of the edge labeled trees may be converted so that the two edge labeled trees are in the same view. Once in the same view, the trees may be manipulated, such as by a merger, for example. Likewise, in an alternative embodiment, both trees may be converted to numerals, the numerals may be manipulated and then the manipulated numerals may be converted back to edge labeled trees of a particular view. Likewise, the edge labeled trees may be converted to any desirable view.


It is likewise noted that for this particular embodiment one way of manipulation an edge labeled tree is to apply a push operation to the edge labeled tree. Likewise, as previously described, for this embodiment, a push operation comprises adding an edge and labeling it. Assuming for this embodiment that the labels for the edge labeled tree comprise numerals, the label for a particular view will be a numeral that is less than the view itself. For example if the view is 5 than the set of distinct values to label an edge comprises 0, 1, 2, 3 or 4. Of course, this is merely one potential embodiment and the claimed subject matter is not limited in scope in this respect. For example, as previously described, letters may be employed. Likewise, any set of values where each value is distinct may be employed and remain within the scope of the claimed subject matter.


A similar set of manipulations may be applied to node labeled trees rather than edge labeled trees. Thus, node labeled trees may be represented in different views, may be converted to the same view, may be converted to numerals, combined, and converted back to a node labeled tree of a particular view. Likewise, a push operation may be applied to a node labeled tree, as previously described for edge labeled trees.


Although the claimed subject matter is not limited in scope in this respect, one technique for implementing this approach may be to apply a table look up approach. For example, a table providing different embodiments associating different views to natural numerals may be employed. Of course, the claimed subject matter is not limited in scope in this respect. For example, instead, a table look-up may be employed for the operation Q and the expressions previously described may be applied to perform manipulations, such as those previously illustrated, for example.


Techniques for performing table look-ups are well-known and well-understood. Thus, this will not be discussed in detail here. However, it shall be appreciated that any and all of the previously described and/or later described processing, operations, conversions, transformations, manipulations, etc. of strings, trees, numerals, data, etc. may be performed on one or more computing platforms or similar computing devices, such as those that may include a memory to store a table as just described, although, the claimed subject matter is not necessarily limited in scope to this particular approach. Thus, for example, a hierarchy of data, such as a tree as previously described, for example, may be formed. Likewise, operations and/or manipulations, as described, may be performed; however, operations and/or manipulations in addition to those described or instead of those described may also be applied. It is intended that the claimed subject matter cover such embodiments.


As described in prior embodiments, one technique for manipulating edge labeled trees includes converting such trees to natural numerals, performing manipulation of the natural numerals, and converting back to an edge labeled tree of a particular view. Furthermore, as described above, one technique for such conversions may include table look-up, as described above. Likewise, in another embodiment, it may be possible to convert a natural numeral directly to an edge labeled tree using a table look-up for the operation Q, previously described. For example, if it were desirable to convert the natural numeral 61 to an edge labeled tree in view 4, the numeral could be factored and the factors converted to trees. In this example, 61 is a non-composite, so, using a table look-up, Q(17) provides 61. Thus, 61 is a push of 17. Using the expressions provided on FIG. 9, for example, we may determine whether 61 is the A, B, C, or D push of 17, and so forth. Likewise, for this particular embodiment, previously, an example of converting between an edge labeled tree of a particular view and a natural numeral was provided.


As previously described an embodiment in accordance with the claimed subject matter may include edge labeled trees of a distinct number of potential identifying labels N, N being a natural numeral. Likewise, as previously described, an example of an embodiment of such a tree is 400 illustrated in FIG. 4. Likewise, by employing the symbolic expression below tree 400 in FIG. 4, as previously described, for this embodiment, it is possible to convert this particular tree, which we previously described as a tree of view 4, into a natural numeral. By this mechanism, for this particular embodiment, it is possible to perform tree manipulations by manipulating natural numerals. Likewise, for this particular embodiment, edge label trees may be converted to strings and manipulation of such strings may provide tree manipulations as well, as described in more detail hereinafter.


For example, in this embodiment, FIG. 19 provides an embodiment of an association between natural numerals, on the left-hand side, and a set of strings, on the right-hand side. Of course, as has been previously indicated, the claimed subject matter is not limited in scope to this particular association embodiment and many other association embodiments are included within the scope of the claimed subject matter. Nonetheless, there are aspects of this particular embodiment worthy of further discussion. For example, FIG. 18 provides a set of rules that permit conversion between the natural numerals and this particular association embodiment of strings. Again, it is noted that the claimed subject matter is not limited in scope to this particular embodiment. However, as shall be discussed in more detail hereinafter, a feature of this particular embodiment is the ability to represent push operations and merger operations, such as those previously described in connection with edge labeled trees, using strings.



FIG. 18 provides for this embodiment a set of rules for converting natural numerals to strings. As illustrated, and as is similar to the approach previously employed in conjunction with edge labeled trees, the numeral 0 is assigned an empty string, whereas the numeral 1 is assigned a pair of corresponding left-right brackets. This is indicated by expressions 1810. It is likewise noted that in this context we include the numeral zero when referring to the natural numerals. Likewise, as is illustrated by expression 1820 in FIG. 18, a numeral that is two times the numeral X is represented as the string for X plus an extra set of left-right brackets in front of the brackets for the numeral X. Likewise, expression 1830, denoted the odd non-composite rule, is similar in concept to a push operation, previously described in connection with edge labeled trees. If a natural numeral is a non-composite numeral, it is assigned the string for the natural number index of that non-composite, as defined by the operation shown in FIG. 6 but then surrounded by an additional left-hand bracket on the left-hand side and an additional right hand bracket on the right-hand side, as depicted in FIG. 18. Further, expression 1840 comprises the merger rule in which the multiplication of two natural numbers is simply the combination of the strings for those natural numbers represented side by side or adjacent to one another. It is further noted, although the claimed subject matter is not limited in scope in this respect, that a convention may be introduced to ensure that a unique association exists between particular numerals and strings. For example, one such convention may be that the smaller of the two numerals is the string on the left, for example, although, the claimed subject matter is not limited in scope to such a particular approach. From these rules, it is possible to construct the strings shown in FIG. 19 that correspond with the natural numbers. Again, it is noted that this is a particular association embodiment and the claimed subject matter is not limited in scope in this respect. Thus any one of a number of other rules for constructing strings might have been employed and remain within the scope of the claimed subject matter.


A feature of this embodiment, although the claimed subject matter is not limited in scope in this respect, is that the strings shown in FIG. 19 may likewise be associated with unitary edge labeled trees, that is, strings that employ a single unitary label for all of the edges of the tree. To be more specific, the set of distinct values from which labels for edges are chosen is a set of one value only. Alternatively, such trees need not have their edges labeled with any value, similar in respects, to the strings themselves. Thus, as described previously in which an edge labeled tree of a particular view may be converted to a natural numeral for manipulation purposes; likewise, such an edge labeled tree may be converted to, for example, for this particular embodiment, a string corresponding the edge labeled tree and the string may be manipulated in place of manipulating a natural numeral.


Thus, this particular embodiment provides an approach in which edge labeled trees may be manipulated by converting between different views, as previously described. Likewise, edge labeled trees may be manipulated by converting to natural numerals, manipulating the natural numerals, and converting back to edge labeled trees of a particular view. Furthermore, edge labeled trees may be manipulated by converting to corresponding strings, manipulating the strings, and then converting back to edge labeled trees. It is noted that the claimed subject matter is not limited to these particular approaches or to employing any one of these approaches alone. The desirability of the approach will depend at least in part and vary with a variety of factors, including storage capabilities, processing capabilities, the particular application and the like.


A related issue in connection with embodiments of edge labeled trees, such as those previously described, for example, is the ability to traverse or navigate such edge labeled trees. In particular, it may prove desirable to traverse or navigate such trees, for example, without necessarily traversing every edge and/or node of the particular tree. However, techniques known for navigating or traversing trees, as a general principle, involve traversing or navigating all the nodes and/or edges of the tree or at least substantial portions that it might be desirable to avoid due to the limitations of time, resources, processing capability or the like. See, for example, Discrete Mathematics in Computer Science, D. F. Stanat and D. F. McAllister, Prentice-Hall, 1977, Section 3.2, “Tree Traversal Algorithms,” p. 140.


Therefore, as shall become more clear hereinafter, it may be desirable to have a technique for identifying specific edges and/or nodes of an edge labeled tree out of all the edges and/or nodes of the tree. One such approach is referred to in this context as tagging the particular edge and/or nodes. By tagging edges and/or nodes, it may be possible to specify a route or provide a mechanism for navigating around portions of the tree without traversing every node and/or edge. Likewise, as shall become more clear, tagging may also provide the ability to specify the order in which those nodes and/or edges are to be traversed.


Without intending to limit the scope of the claimed subject matter, the desirability of having such capabilities might arise in a number of different situations. For example, in connection with a data base system, for example, it may be desirable to locate specific data quickly without traversing the entire tree structure or nearly the entire structure of the data base. Alternatively, in a commercial process that may structured or represented as a tree and implemented by computing device, for example, it may be desirable to skip a portion of the tree to reach another node or edge at another point in the process, depending, for example, at least in part upon what has occurred in the process to that point in time. Again, these are simply examples and many other examples in which the ability to traverse nodes and/or edges of a tree in a specified order and to traverse only those nodes and/or edges may prove desirable.


In accordance with one embodiment of the claimed subject matter, a method of traversing an edge labeled tree may include locating specific nodes of the tree that are to be traversed. For example, referring to FIG. 4, assuming tree 400 comprise an edge labeled tree in which it is desirable to traverse specific nodes, FIG. 20 provides another representation of tree 400 in which specific nodes are designated to be traversed and, likewise, the desired order of traversal is also provided.


In this particular embodiment, the nodes of the tree that are to be traversed shall each have a corresponding tag. Such tags, in this particular embodiment, for example, are capable of being identified by a computing device that has been suitable programmed. Thus, the tags shall in essence, for this embodiment, become incorporated into the tree structure, as shall be described in more detail hereinafter.


For this specific embodiment, creation of a tag may be illustrated by FIGS. 21 to 24. For example, referring to FIG. 21, for the nodes to be traversed, an edge labeled B is attached and another node is provided supporting that edge labeled B. Again, it is noted that the claimed subject matter is not limited in scope to this particular embodiment. For example, here, the label B was selected due at least in part to the structure of this particular tree, although, alternatively a different label may have been employed. For example, a label that has not been employed in the tree, such as E, for example, might have been employed. Nonetheless, continuing with our example in FIG. 22, sub-trees are attached to the “new” nodes where the sub-trees, in this particular embodiment, are intended to designate the order in which the particular nodes of the initial tree are to be traversed. Thus, for example, from the node designated by the natural numeral 0, an empty sub-tree has been provided. In contrast, a sub-tree corresponding to 1 has been employed to tag the node designated by the natural numeral 1. Likewise, a sub-tree corresponding to the natural numeral 2 has been employed to tag the node having the natural numeral 2 and so forth.


At this point, it is to be noted, for this particular embodiment, that there is a correspondence between the sub-trees employed in FIG. 22 and the strings depicted in FIG. 19, although this is a particular embodiment and the claimed subject matter is not necessarily limited in scope in this respect. More specifically, depending upon the particular embodiment, it may be appropriate to employ tags to designate the particular nodes to be traversed in which the tags comprised strings. Those strings may then be converted to sub-trees. To be more specific, for this particular embodiment, the strings denoted in FIG. 19 may be converted to unitary valued trees, as previously described. Thus, the strings may be converted to trees in which the edges are labeled with a single value. For example, a correspondence exists and is apparent by inspection between the sub-tree for the natural numeral 2 in FIG. 22 and the string for the natural numeral 2 in FIG. 19. Likewise, the correspondence for natural numeral 3 between FIG. 22 and FIG. 19 is likewise apparent by inspection. Thus, the strings provide a mechanism for providing sub-trees that may operate as tags in which the tags may be identified by labeling the edges with a value that either is not employed in the tree elsewhere or a value that is not repeated in the tree so that it is clear which portions of the tree comprise tags and which portions of the tree do not comprise tags.


Comparing FIGS. 22, 23, and 24, it is now apparent how a tree may be constructed in which incorporated into the tree is information specifying the traversal of specific nodes, including the order in which those nodes are to be traversed. More specifically, when the tree illustrated in FIG. 24, for example, is stored, the sub-trees below each node are likewise stored, such as in a table for easy access, although the claimed subject matter is not limited in scope in this respect. Thus, the ability to pick those sub-trees that correspond to tag from those that do not is capable of being implemented based at least in part on the edge labels. To rephrase, the tags that are incorporated into the tree, such as the tree in FIG. 24, in this embodiment operate as pointers to the specific nodes to be traversed and also provide information regarding the order in which the nodes are to be traversed.


Yet another aspect of this particular embodiment, although, again the claimed subject matter is not limited in scope in, this respect is that edge labeled trees that have been tagged in a particular view, such as in the manner previously described, for example, may be converted to natural numerals and/or strings, manipulated, and converted back to trees of the particular view without affecting the tags that have been incorporated into the tree. For example, if two trees in a particular view have tags indicating that the nodes of those trees are to be traversed in a specific order, those trees may be converted to natural numerals or to strings, manipulated, such as by merger, and converted back to a tree of the particular view. Yet, in the resulting tree, the tags and ordering shall remain intact. A reason this is possible relates to the underlying nature of the structure of the views, as previously described. For example, referring to view 4 and FIG. 9, as previously discussed, the edge labeled trees may be related to an algebra involving push and merger operations. From the isomorphism between the edge labeled trees of the particular view, here 4, and the natural numerals, the operations do not result in the particular operand trees from losing their inherent association for this embodiment. Thus, the operand trees that produce the resulting tree may always be recovered in an analogous manner that composite numerals may always be factored, for example.



FIGS. 25-28 illustrate an alternate embodiment to the one just described. Of course, the claimed subject matter is not limited to these embodiments. Many more are possible and are included within the scope of the claimed subject matter. However, for this particular embodiment, rather than employing tags that correspond to a particular natural numeral, here, the tags employed correspond to the index of the non-composite numerals that correspond to the factorization of the particular numeral providing the order to traverse the nodes. For example, in this embodiment, to double the particular numeral, as in going from the numeral 1 to the numeral 2, an additional labeled edge is added from the particular node. Likewise, similarly, a labeled edge is added in going from numeral 2 to numeral 4. For example, the label for the edges may comprise B, as previously, although the claimed subject matter is not limited in scope in this respect. However, for a non-composite numeral, a push operation is applied. Therefore, the numeral 3 is the push of the numeral 1. Of course, this is merely one particular embodiment and the claimed subject matter is not limited in scope in this respect.


Embodiments of a method of manipulating tree expressions have a variety of potentially useful applications. As described previously, trees provide a technique for structuring and/or depicting hierarchical data. Thus, for example, trees may be employed to represent language sentence structures, computer programs, algebraic formulae, molecular structures, family relationships and more. For example, one potential application of such a tree reduction technique is in the area of pattern matching See, for example, “A VLSI Architecture for Object Recognition using Tree Matching” K. Sitaraman, N. Ranganathan and A. Ejnioui; Proceedings of the IEEE International Conference on Application-Specific Systems, Architectures, and Processors (ASAP'02) 2000; “Expressive and efficient pattern languages for tree-structured data” by Frank Neven and Thomas Schwentick; Proceedings of the Nineteenth ACM SIGACT-SIGMOD-SIGART Symposium on Principles of Database Systems, May 2000. Thus, in pattern matching, substructures, in the form of a tree, for example, may be located within a larger structure, also in the form of a tree, referred to in this context as the target. This may be accomplished by comparing the structures; however, typically, such a comparison is complex, cumbersome, and/or time consuming.


Of course, the claimed subject matter is not limited to unordered edge labeled trees. For example, as described in previously cited U.S. provisional patent application 60/543,371, binary edge labeled trees and binary node labeled trees may be employed nearly interchangeably to represent substantially the same hierarchy of data. In particular, a binary node labeled tree may be associated with a binary edge labeled tree where the nodes of the binary node labeled tree take the same values as the edges of the binary edge labeled tree, except that the root node of the binary node labeled tree may comprise a node having a zero value or a null value. Thus, rather than employing edge labeled trees (ELTs), the previously described embodiments may alternatively be performed using node labeled trees (NLTs). One example of a NLT is illustrated in the diagram of FIG. 14 by tree 1400. As one example embodiment, operations and/or manipulations may be employed using edge labeled trees and the resulting edge labeled tree may be converted to a node labeled tree. However, in another embodiment, operations and/or manipulations may be performed directly using node labeled trees.


In accordance with the claimed subject matter, therefore, any tree, regardless of whether it is edge labeled, node labeled, non-binary, a feature tree, or otherwise, may be manipulated and/or operated upon in a manner similar to the approach of the previously described embodiments. Typically, different views shall be employed, depending at least in part, for example, upon the particular type of tree. Furthermore or alternatively, as described in the previously referenced U.S. provisional patent application 60/543,371, a node labeled tree in which the nodes are labeled with natural numerals or data values may be converted to an edge labeled tree. Furthermore, this may be accomplished with approximately the same amount of storage. For example, for this particular embodiment, this may involve substantially the same amount of node and/or edge data label values. However, for convenience, without intending to limit the scope of the claimed subject matter in any way, here, operations and/or manipulations and the like have been described primarily in the context of ELTs.


In another embodiment, however, a particular tree may include null types or, more particularly, some node values denoted by the empty set. An advantage of employing null types includes the ability to address a broader array of hierarchical data sets. For example, without loss of generality and not intending to limit the scope of the claimed subject matter in any way, a null type permits representing in a database or a relational database, as two examples, situations where a particular attribute does not exist. As may be appreciated, this is different from a situation, for example, where a particular attribute may take on a numeral value of zero. Again, as described in the previously referenced U.S. provisional patent application 60/543,371, a tree with nulls, as described above, may be converted to a tree without nulls; however, the claimed subject matter is not limited in scope in this respect, of course. Thus, it may be desirable to be able to address both situations when representing, operating upon, manipulating and/or searching for patterns regarding hierarchical sets of data.


Likewise, in an alternative embodiment, a node labeled tree, for example, may comprise fixed length tuples of numerals. For such an embodiment, such multiple numerals may be combined into a single numeral, such as by employing Cantor pairing operations, for example. See, for example, Logical Number Theory, An Introduction, by Craig Smorynski, pp, 14-23, available from Springer-Verlag, 1991. This approach should produce a tree to which the previously described embodiments may then be applied.


Furthermore, a tree in which both the nodes and the edges are labeled may be referred to in this context as a feature tree and may be converted to an edge labeled tree and/or a node labeled tree. For example, without intending to limit the scope of the claimed subject matter, in one approach, a feature tree may be converted by converting any labeled node with its labeled outgoing edge to an ordered pair of labels for the particular node.


In yet another embodiment, for trees in which data labels do not comprise simply natural numerals, such as, as one example, trees that include negative numerals, such data labels may be converted to an ordered pair of numerals. For example, the first numeral may represent a data type. Examples include a data type such as negative, dollars, etc. As described above, such trees may also be converted to edge labeled trees, for example. However, again, this is provided for purposes of explanation and illustration. The claimed subject matter is not limited in scope to employing the approach of the previously referenced provisional patent application.


It will, of course, be understood that, although particular embodiments have just been described, the claimed subject matter is not limited in scope to a particular embodiment or implementation. For example, one embodiment may be in hardware, such as implemented to operate on a device or combination of devices, for example, whereas another embodiment may be in software. Likewise, an embodiment may be implemented in firmware, or as any combination of hardware, software, and/or firmware, for example. Likewise, although the claimed subject matter is not limited in scope in this respect, one embodiment may comprise one or more articles, such as a storage medium or storage media. This storage media, such as, one or more CD-ROMs and/or disks, for example, may have stored thereon instructions, that when executed by a system, such as a computer system, computing platform, or other system, for example, may result in an embodiment of a method in accordance with the claimed subject matter being executed, such as one of the embodiments previously described, for example. As one potential example, a computing platform may include one or more processing units or processors, one or more input/output devices, such as a display, a keyboard and/or a mouse, and/or one or more memories, such as static random access memory, dynamic random access memory, flash memory, and/or a hard drive. For example, a display may be employed to display one or more queries, such as those that may be interrelated, and or one or more tree expressions, although, again, the claimed subject matter is not limited in scope to this example.


In the preceding description, various aspects of the claimed subject matter have been described. For purposes of explanation, specific numbers, systems and/or configurations were set forth to provide a thorough understanding of the claimed subject matter. However, it should be apparent to one skilled in the art having the benefit of this disclosure that the claimed subject matter may be practiced without the specific details. In other instances, well-known features were omitted and/or simplified so as not to obscure the claimed subject matter. While certain features have been illustrated and/or described herein, many modifications, substitutions, changes and/or equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and/or changes as fall within the true spirit of the claimed subject matter.

Claims
  • 1. A method of executing computer instructions on at least one computing device without further human interaction in which the at least one computing device includes at least one processor and at least one memory, the method comprising: executing computer instructions on the at least one processor of the at least one computing device, the computer instructions having been stored on the at least one memory; andstoring in the at least one memory of the at least one computing device any results of having executed the computer instructions on the at least one processor of the at least one computing device;wherein the computer instructions to be executed comprise instructions for identifying and traversing nodes in a complex tree hierarchy;wherein the executing the identifying and traversing node computer instructions further comprises:identifying a selected group of nodes for traversal of the complex tree hierarchyfor the selected group of nodes, attaching respective labeled edges and respective supporting nodes, wherein the labeled edges are to be labeled with specific content to indicate that a selected node of the selected group of nodes is to be traversed; andattaching respective subtrees with edges labeled with the specific content, to the respective supporting nodes,the respective subtrees to indicate a sequential numerical order of traversal for the selected group of nodes.
  • 2. The method of claim 1, wherein the respective subtrees of the complex tree hierarchy represent one or more values.
  • 3. The method of claim 2, wherein the one or more values comprise indices of a Q operation.
  • 4. The method of claim 1 wherein the attached respective subtrees to comprise attached tags.
  • 5. The method of claim 4, wherein the executing the identifying and traversing node computer instructions further comprises: locating the selected group of nodes of a tree substructure of the complex tree hierarchy that correspond to the attached tags.
  • 6. The method of claim 5, wherein the complex tree hierarchy comprises a binary edge labeled tree.
  • 7. The method of claim 6, wherein the complex tree hierarchy comprises an ordered binary edge labeled tree.
  • 8. The method of claim 5, wherein the complex tree hierarchy comprises a binary node labeled tree.
  • 9. The method of claim 8, wherein the complex tree hierarchy comprises an ordered binary node labeled tree.
  • 10. The method of claim 5, wherein the complex tree hierarchy comprises an ordered edge labeled tree.
  • 11. The method of claim 4, wherein the attached tags are incorporated into the structure of the complex tree hierarchy via the computing device.
  • 12. The method of claim 4, wherein the identifying and traversing node computer instructions further comprise instructions for converting the complex tree hierarchy including the attached tags to or from a numerical representation with the attached tags specifying an order of traversal of the nodes selected for traversal.
  • 13. The method of claim 1, wherein the executing the identifying and traversing node computer instructions further comprises: traversing the selected nodes in the sequential numerical order indicated by the attached respective subtrees.
  • 14. The method of claim 13, wherein the executing the identifying and traversing node computer instructions further comprises: locating the edges labeled with the specific content.
  • 15. The method of claim 13, wherein the attached respective subtrees of the complex tree hierarchy represent one or more values; and wherein the executing the identifying and traversing node computer instructions comprises: traversing the selected group of nodes in an order specified by the one or more values of the attached respective subtrees of the complex tree hierarchy.
  • 16. The method of claim 15, wherein the one or more values comprise the indices of a Q operation.
  • 17. The method of claim 1 wherein the respective subtrees attached to the supporting nodes indicate an order of traversal by indicating specific positions in a sequence of nodes to be traversed.
  • 18. An apparatus comprising: at least one computing device;the at least one computing device including at least one processor and at least one memory;the at least one computing device to execute computer instructions on the at least one processor without further human interaction;the computer instructions to be executed to have been stored on the at least one memory for execution on the at least one processor; andthe at least one computing device to store in the at least one memory of the at least one computing device any results to be generated from the execution on the at least one processor of the to be executed computer instructions;the computer instructions to be executed to comprise instructions to identify and traverse a selected group of nodes of a complex tree hierarchy;wherein the computer instructions to identify and traverse the selected group of nodes further comprise instructions to:identify the selected group of nodes for traversal in the complex tree hierarchy;for the selected group of nodes, attach respective labeled edges respective supporting nodes, wherein the labeled edges are labeled with specific content to indicate that a selected node is to be traversed; andattach respective subtrees with edges labeled with the specific content, to the respective supporting nodes, the respective subtrees to indicate a sequential numerical order of traversal for the selected group of nodes.
  • 19. The apparatus of claim 18, wherein the respective subtrees of the complex tree hierarchy to represent one or more values.
  • 20. The apparatus of claim 19, wherein the one or more values to comprise indices of a Q operation.
  • 21. The apparatus of claim 19, wherein the computer instructions to identify and traverse the selected group of nodes further comprise instructions to traverse the selected group of nodes of the complex tree hierarchy in an order to be specified by the one or more values of the attached respective subtrees of the complex tree hierarchy.
  • 22. The apparatus of claim 21, wherein the one or more values to comprise indices of a Q operation.
  • 23. The apparatus of claim 18 wherein the attached respective subtrees comprise attached tags.
  • 24. The apparatus of claim 23, wherein the computer instructions to identify and traverse the selected group of nodes further comprise instructions to locate selected group of nodes of a tree substructure of the complex tree hierarchy that are to correspond to the attached tags.
  • 25. The apparatus of claim 24, wherein the complex tree hierarchy to comprise an ordered edge labeled tree.
  • 26. The apparatus of claim 24, wherein the complex tree hierarchy to comprise a binary edge labeled tree.
  • 27. The apparatus of claim 26, wherein the complex tree hierarchy to comprise an ordered binary edge labeled tree.
  • 28. The apparatus of claim 24, wherein the complex tree hierarchy to comprise a binary node labeled tree.
  • 29. The apparatus of claim 28, wherein the complex tree hierarchy to comprise an ordered binary node labeled tree.
  • 30. The apparatus of claim 23, wherein the computer instructions to identify and traverse the selected group of nodes further comprise instructions to convert the complex tree hierarchy including the attached tags to or convert the complex tree hierarchy including the attached tags from a numerical representation with the attached tags to specify an order of traversal of the selected group of nodes.
  • 31. The apparatus of claim 23, wherein the computer instructions to identify and traverse the selected group of nodes further comprise instructions to incorporate the attached tags into the structure of the complex tree hierarchy.
  • 32. The apparatus of claim 18 wherein the respective subtrees to be attached to the supporting nodes are to indicate an order of traversal by indication of specific positions in a sequence of nodes to be traversed.
  • 33. The apparatus of claim 32, wherein the computer instructions to identify and traverse the selected group of nodes further comprise instructions to locate edges labeled with the specific content.
  • 34. The apparatus of claim 18, wherein the computer instructions to identify and traverse the selected group of nodes further comprise instructions to traverse the selected group of nodes in the sequential numerical order indicated by the attached respective subtrees.
RELATED PATENT APPLICATION(S)

This is a divisional patent application of and a divisional application which claims priority from U.S. patent application Ser. No. 11/006,446, titled “METHOD AND/OR SYSTEM FOR TAGGING TREES,” filed on Dec. 6, 2004, by J. J. LeTourneau, now issued U.S. Pat. No. 7,801,923, which claims priority from U.S. provisional patent application Ser. No. 60/623,352, filed on Oct. 29, 2004, by J. J. LeTourneau, titled, “METHOD AND/OR SYSTEM FOR TAGGING TREES”, assigned to the assignee of the presently claimed subject matter.

US Referenced Citations (292)
Number Name Date Kind
3201701 Maitra Aug 1965 A
3704345 Coker Nov 1972 A
4001951 Fasse Jan 1977 A
4134218 Adams et al. Jan 1979 A
4156910 Barton et al. May 1979 A
4286330 Isaacson Aug 1981 A
4439162 Blaine Mar 1984 A
4677550 Ferguson Jun 1987 A
4737109 Abramson Apr 1988 A
4745561 Hirosawa et al. May 1988 A
4751684 Holt Jun 1988 A
4831525 Saito et al. May 1989 A
4867686 Goldstein Sep 1989 A
4931928 Greenfeld Jun 1990 A
4949388 Bhaskaran Aug 1990 A
4989132 Mellender et al. Jan 1991 A
4991087 Burkowski et al. Feb 1991 A
5021943 Grimes Jun 1991 A
5021992 Kondo Jun 1991 A
5050071 Harris et al. Sep 1991 A
5151697 Bunton Sep 1992 A
5191522 Bosco et al. Mar 1993 A
5235701 Ohler et al. Aug 1993 A
5265245 Nordstrom et al. Nov 1993 A
5295261 Simonetti Mar 1994 A
5325531 McKeeman Jun 1994 A
5335320 Iwata Aug 1994 A
5335345 Frieder et al. Aug 1994 A
5355469 Fant et al. Oct 1994 A
5355496 Fant et al. Oct 1994 A
5463777 Bialkowski et al. Oct 1995 A
5493504 Minato Feb 1996 A
5493678 Arcuri Feb 1996 A
5497500 Rogers et al. Mar 1996 A
5509088 Robson Apr 1996 A
5519627 Mahmood et al. May 1996 A
5522068 Berkowitz May 1996 A
5577253 Blickstein Nov 1996 A
5598350 Kawanishi et al. Jan 1997 A
5606669 Bertin et al. Feb 1997 A
5636155 Kabuo Jun 1997 A
5687362 Bhargava et al. Nov 1997 A
5706406 Pollock Jan 1998 A
5724512 Winterbottom Mar 1998 A
5724576 Letourneau Mar 1998 A
5748975 Van De Vanter May 1998 A
5758152 LeTourneau May 1998 A
5778354 Leslie Jul 1998 A
5778371 Fujihara Jul 1998 A
5781906 Aggarwal et al. Jul 1998 A
5787415 Jacobson et al. Jul 1998 A
5787432 LeTourneau Jul 1998 A
5796356 Okada et al. Aug 1998 A
5802370 Sitbon et al. Sep 1998 A
5822593 Lamping et al. Oct 1998 A
5826262 Bui Oct 1998 A
5848159 Collins et al. Dec 1998 A
5905138 Van Broekhoven May 1999 A
5930805 Marquis Jul 1999 A
5937181 Godefroid Aug 1999 A
5970490 Morgenstern Oct 1999 A
5978790 Buneman et al. Nov 1999 A
5987449 Suciu Nov 1999 A
5999926 Suciu Dec 1999 A
6002879 Radigan et al. Dec 1999 A
6003033 Amano et al. Dec 1999 A
6022879 Crow et al. Feb 2000 A
6028987 Hirairi Feb 2000 A
6055537 LeTourneau Apr 2000 A
6076087 Suciu Jun 2000 A
6088691 Bhargava et al. Jul 2000 A
6141655 Johnson et al. Oct 2000 A
6199103 Sakuguchi et al. Mar 2001 B1
6236410 Politis et al. May 2001 B1
6243859 Chen-Kuang Jun 2001 B1
6279007 Uppala Aug 2001 B1
6289354 Aggarwal et al. Sep 2001 B1
6292938 Sarkar et al. Sep 2001 B1
6314559 Sollich Nov 2001 B1
6336812 Cooper et al. Jan 2002 B1
6341372 Datig Jan 2002 B1
6442584 Kolli et al. Aug 2002 B1
6446256 Hyman et al. Sep 2002 B1
6466240 Maslov Oct 2002 B1
6505205 Kothuri et al. Jan 2003 B1
6542899 Saulpaugh et al. Apr 2003 B1
6550024 Pagurek et al. Apr 2003 B1
6556983 Altschuler et al. Apr 2003 B1
6598052 Saulpaugh et al. Jul 2003 B1
6606632 Saulpaugh et al. Aug 2003 B1
6606741 Kojima et al. Aug 2003 B2
6609130 Saulpaugh et al. Aug 2003 B1
6610106 Jenks Aug 2003 B1
6611844 Saulpaugh et al. Aug 2003 B1
6640218 Golding Oct 2003 B1
6658649 Bates et al. Dec 2003 B1
6691301 Bowen Feb 2004 B2
6714939 Saldanha et al. Mar 2004 B2
6728953 Walster Apr 2004 B1
6745384 Biggerstaff Jun 2004 B1
6748378 Lavender et al. Jun 2004 B1
6763515 Vazquez et al. Jul 2004 B1
6785673 Fernandez et al. Aug 2004 B1
6817865 Charbonneau Nov 2004 B2
6829695 Ross Dec 2004 B1
6847979 Allemang et al. Jan 2005 B2
6854976 Suhr Feb 2005 B1
6874005 Fortenberry et al. Mar 2005 B2
6880148 Raph Apr 2005 B1
6965990 Barsness et al. Nov 2005 B2
6968330 Edwards et al. Nov 2005 B2
6978271 Hoffman Dec 2005 B1
7043555 McCain et al. May 2006 B1
7051033 Agarwal et al. May 2006 B2
7072904 Najork et al. Jul 2006 B2
7103838 Krishnamurthy et al. Sep 2006 B1
7107265 Calvignac et al. Sep 2006 B1
7117196 Gaur et al. Oct 2006 B2
7117479 Van De Vanter Oct 2006 B2
7127704 Van De Vanter et al. Oct 2006 B2
7134075 Hind et al. Nov 2006 B2
7140006 Harrison et al. Nov 2006 B2
7162485 Gottlob et al. Jan 2007 B2
7190376 Tonisson Mar 2007 B1
7191182 Anonsen et al. Mar 2007 B2
7203680 Parida Apr 2007 B2
7203774 Zhou et al. Apr 2007 B1
7287026 Oommen Oct 2007 B2
7313563 Bordawekar et al. Dec 2007 B2
7318215 Krishnan et al. Jan 2008 B1
7337163 Srinivasan Feb 2008 B1
7356802 de Sutter et al. Apr 2008 B2
7360202 Seshadri et al. Apr 2008 B1
7409673 Kuo et al. Aug 2008 B2
7419376 Sarvazyan et al. Sep 2008 B2
7437666 Ramarao Oct 2008 B2
7475070 Fan et al. Jan 2009 B2
7496892 Nuss Feb 2009 B2
7512932 Davidov et al. Mar 2009 B2
7536675 Gallagher May 2009 B2
7536676 Baker May 2009 B2
7544062 Hauschild et al. Jun 2009 B1
7561927 Oyama et al. Jul 2009 B2
7571169 Jones et al. Aug 2009 B2
7574692 Herscu Aug 2009 B2
7575434 Palakodeti Aug 2009 B2
7620632 Andrews Nov 2009 B2
7627591 LeTourneau Dec 2009 B2
7630995 LeTourneau Dec 2009 B2
7636727 Schiffmann et al. Dec 2009 B2
7650592 Eckels et al. Jan 2010 B2
7669183 Bowman et al. Feb 2010 B2
7681177 LeTourneau Mar 2010 B2
7761847 Kornerup et al. Jul 2010 B2
7761858 Chang et al. Jul 2010 B2
7765183 Williams, Jr. Jul 2010 B2
7779396 Meijer et al. Aug 2010 B2
7801923 LeTourneau Sep 2010 B2
7861304 Nachenberg Dec 2010 B1
7882147 LeTourneau Feb 2011 B2
7890928 Patrudu Feb 2011 B2
7899821 Schiffmann Mar 2011 B1
8020145 Fant Sep 2011 B2
8032860 Piehler et al. Oct 2011 B2
8037102 LeTourneau Oct 2011 B2
8060868 Meijer et al. Nov 2011 B2
8112740 Meijer et al. Feb 2012 B2
8151276 Grechanik Apr 2012 B2
8181155 Pinto et al. May 2012 B2
8230526 Holland et al. Jul 2012 B2
8250526 Anderson et al. Aug 2012 B2
8316059 Schiffmann Nov 2012 B1
8356040 LeTourneau Jan 2013 B2
8365137 Fant Jan 2013 B2
8438534 Thomson May 2013 B2
8443339 LeTourneau May 2013 B2
8484236 Andrews Jul 2013 B1
8626777 LeTourneau Jan 2014 B2
8650201 Letourneau Feb 2014 B2
8683431 Thomson et al. Mar 2014 B2
8762942 Langworthy et al. Jun 2014 B2
8869106 Jazdzewski Oct 2014 B2
8990769 LeTourneau Mar 2015 B2
9002862 Schiffmann Apr 2015 B2
9020961 LeTourneau Apr 2015 B2
9043347 LeTourneau May 2015 B2
9077515 LeTourneau Jul 2015 B2
9330128 Schiffmann May 2016 B2
9411841 Schiffmann Aug 2016 B2
9425951 LeTourneau Aug 2016 B2
9430512 LeTourneau Aug 2016 B2
9563653 LeTourneau Feb 2017 B2
9646034 Schiffmann May 2017 B2
9646107 LeTourneau May 2017 B2
9842130 Schiffmann Dec 2017 B2
10055438 Schiffmann Aug 2018 B2
10068003 Schiffmann Sep 2018 B2
10255311 LeTourneau Apr 2019 B2
20010003211 Bera Jun 2001 A1
20010037496 Simonyi Nov 2001 A1
20020040292 Marcu Apr 2002 A1
20020059281 Watanabe et al. May 2002 A1
20020062259 Katz et al. May 2002 A1
20020091676 Agrawal Jul 2002 A1
20020107860 Gobeille et al. Aug 2002 A1
20020129129 Bloch et al. Sep 2002 A1
20020130796 Tsuchido et al. Sep 2002 A1
20020130907 Chi Sep 2002 A1
20020133347 Schoneburg Sep 2002 A1
20020133497 Draper et al. Sep 2002 A1
20020149604 Wilkinson Oct 2002 A1
20020169563 de Carvalho Ferreira Nov 2002 A1
20020194163 Hopeman Dec 2002 A1
20030041088 Wilson et al. Feb 2003 A1
20030065659 Agarwal et al. Apr 2003 A1
20030074436 Gieseke Apr 2003 A1
20030115559 Sawada Jun 2003 A1
20030130977 Oommen Jul 2003 A1
20030158854 Yoshida et al. Aug 2003 A1
20030167445 Su et al. Sep 2003 A1
20030195885 Emmick et al. Oct 2003 A1
20030195890 Oommen Oct 2003 A1
20030236794 Hostetter et al. Dec 2003 A1
20040010752 Chan et al. Jan 2004 A1
20040019599 Trappen Jan 2004 A1
20040024724 Rubin Feb 2004 A1
20040024790 Everett Feb 2004 A1
20040044659 Judd et al. Mar 2004 A1
20040054692 Seyrat et al. Mar 2004 A1
20040060006 Lindblad Mar 2004 A1
20040060007 Gottlob et al. Mar 2004 A1
20040068498 Patchet et al. Apr 2004 A1
20040075677 Loyall Apr 2004 A1
20040103105 Lindblad May 2004 A1
20040122844 Malloy Jun 2004 A1
20040125124 Kim Jul 2004 A1
20040160464 Reyna Aug 2004 A1
20040205047 Carpenter Oct 2004 A1
20040215642 Cameron et al. Oct 2004 A1
20040239674 Ewald et al. Dec 2004 A1
20040254909 Testa Dec 2004 A1
20040260683 Chan et al. Dec 2004 A1
20040260684 Agrawal et al. Dec 2004 A1
20040267958 Reed Dec 2004 A1
20040268236 Chidlovskii et al. Dec 2004 A1
20050021548 Bohannon et al. Jan 2005 A1
20050023524 Beatty Feb 2005 A1
20050027495 Matichuk Feb 2005 A1
20050027743 O'Neil et al. Feb 2005 A1
20050028091 Bordawekar Feb 2005 A1
20050050016 Stanoi et al. Mar 2005 A1
20050050066 Hughes Mar 2005 A1
20050058976 Vernon Mar 2005 A1
20050060332 Bernstein et al. Mar 2005 A1
20050065964 Ziemann et al. Mar 2005 A1
20050097084 Balmin May 2005 A1
20050125432 Lin et al. Jun 2005 A1
20050138073 Zhou et al. Jun 2005 A1
20050149471 Lassalle Jul 2005 A1
20050154265 Miro et al. Jul 2005 A1
20050154979 Chidlovskii et al. Jul 2005 A1
20050156761 Oh Jul 2005 A1
20050165732 Burges Jul 2005 A1
20050171962 Martin Aug 2005 A1
20050187900 LeTourneau Aug 2005 A1
20050214727 Stoianovici et al. Sep 2005 A1
20050216445 Rao Sep 2005 A1
20050267908 LeTourneau Dec 2005 A1
20050286788 Orr Dec 2005 A1
20060004817 Andrews Jan 2006 A1
20060005122 Lemoine Jan 2006 A1
20060015538 LeTourneau Jan 2006 A1
20060053122 Korn et al. Mar 2006 A1
20060074838 Srivastava Apr 2006 A1
20060095442 LeTourneau May 2006 A1
20060095455 LeTourneau May 2006 A1
20060123029 LeTourneau Jun 2006 A1
20060129582 Schiffmann et al. Jun 2006 A1
20060209351 Saito et al. Sep 2006 A1
20060259533 LeTourneau Nov 2006 A1
20060271573 LeTourneau Nov 2006 A1
20070003917 Kitching et al. Jan 2007 A1
20070198538 Palacios Aug 2007 A1
20080270435 Furusho Oct 2008 A1
20080313196 Furusho Dec 2008 A1
20100094885 LeTourneau Apr 2010 A1
20100094908 LeTourneau Apr 2010 A1
20100114969 LeTourneau Apr 2010 A1
20100191775 Schiffmann et al. Jul 2010 A1
20100205581 LeTourneau Aug 2010 A1
20120144388 Schiffmann Jun 2012 A1
20160162528 LeTourneau Jun 2016 A1
Non-Patent Literature Citations (860)
Entry
U.S. Appl. No. 11/005,859: Advisory Action dated Dec. 22, 2009, 2 pages.
U.S. Appl. No. 11/005,859: RCE with Amendment filed Jan. 7, 2010, 87 pages.
U.S. Appl. No. 11/005,859: Non-Final Office Action dated Jan. 21, 2010, 17 pages.
U.S. Appl. No. 11/005,859: Response to Non-Final Office Action filed Feb. 25, 2010, 85 pages.
U.S. Appl. No. 11/005,859: Final Office Action dated Jun. 8, 2010, 9 pages.
U.S. Appl. No. 11/007,139: RCE with amendment filed Jan. 4, 2010, 27 pages.
U.S. Appl. No. 11/007,139: Non-Final Office Action dated Jan. 27, 2010, 31 pages.
U.S. Appl. No. 11/007,139: Response to Non-Final Office Action filed Apr. 27, 2010, 30 pages.
U.S. Appl. No. 11/006,320: Response to Non-Final Office Action filed Feb. 23, 2010, 11 pages.
U.S. Appl. No. 11/006,320: Final Office Action dated May 24, 2010, 11 pages.
U.S. Appl. No. 12/573,829: Notice of Publication dated Apr. 15, 2010, 1 page.
U.S. Appl. No. 12/573,829: Examiner's Search Strategy and Results dated Jun. 11, 2010, 1 page.
U.S. Appl. No. 12/578,411: Notice of Missing Parts dated Oct. 28, 2009, 2 pages.
U.S. Appl. No. 12/578,411: Response to Missing Parts filed Dec. 28, 2009, 25 pages.
U.S. Appl. No. 12/578,411: Notice of Publication dated Apr. 15, 2010, 1 page.
U.S. Appl. No. 12/627,816: Notice of Missing Parts dated Dec. 15, 2009, 2 pages.
U.S. Appl. No. 12/627,816: Response to Missing Parts filed Apr. 12, 2010, 21 pages.
U.S. Appl. No. 11/006,446: Examiner Interview Summary dated Mar. 19, 2010, 4 pages.
U.S. Appl. No. 11/006,446: Notice of Allowance/Allowability dated Mar. 19, 2010, 29 pages.
U.S. Appl. No. 11/006,446: Issue Fee Payment and 312 Amendment filed Jun. 21, 2010, 23 pages.
U.S. Appl. No. 11/385,257: Response to Non-Final Office Action dated Jan. 13, 2010, 34 pages.
U.S. Appl. No. 11/385,257: Final Office Action dated Apr. 12, 2010, 47 pages.
U.S. Appl. No. 11/319,758: RCE filed Jan. 4, 2010, 45 pages.
U.S. Appl. No. 11/319,758: Non-Final Office Action dated Mar. 30, 2010, 39 pages.
U.S. Appl. No. 12/613,450: Notice of Missing Parts dated Nov. 18, 2009, 2 pages.
U.S. Appl. No. 12/613,450: Preliminary Amendment and Response to Missing Parts filed Jan. 19, 2010, 16 pages.
U.S. Appl. No. 11/320,538: Response to Final Office Action filed Jan. 4, 2010, 23 pages.
U.S. Appl. No. 11/320,538: Advisory Action dated Jan. 19, 2010, 3 pages.
U.S. Appl. No. 11/320,538: RCE and Amendment filed Apr. 2, 2010, 26 pages.
U.S. Appl. No. 12/702,243: Continuation Application with Preliminary Amendment filed Feb. 8, 2010, 83 pages.
U.S. Appl. No. 12/702,243: Notice of Missing Parts dated Feb. 25, 2010, 2 pages.
U.S. Appl. No. 12/702,243: Response to Missing Parts filed Apr. 26, 2010, 8 pages.
U.S. Appl. No. 11/412,417: Final Office Action dated Jan. 4, 2010, 37 pages.
U.S. Appl. No. 11/412,417: RCE with Amendment filed May 4, 2010, 27 pages.
U.S. Appl. No. 11/319,758, filed Dec. 27, 2005, Schiffmann.
U.S. Appl. No. 11/320,538, filed Dec 27, 2005, LeTourneau, J.J.
U.S. Appl. No. 11/412,417, filed Apr. 26, 2006, Schiffmann.
U.S. Appl. No. 11/480,094, filed Apr. 26, 2006, LeTourneau, J.J.
U.S. Appl. No. 12/627,816, filed Nov. 30, 2009, Schiffmann.
U.S. Appl. No. 12/702,243, filed Feb. 8, 2010, LeTourneau, J.J.
“Core Technology Benchmarks A White Paper”, Jul. 2002, downloaded from the internet Mar. 2, 2004.
“Origin Data, Inc. White Paper”, © 1999, pp. 1-13.
“The Associative Model of Data White Paper”, Lazy Software, Ltd., 2000.
ACM Portal Search Results (Kleene and prime and enumeration and operation and natural and numerals and sequences and “enumeration operation”) conducted by Examiner on Jul. 18, 2009, 6 pages.
ACM Portal Search Results (Kleene and prime and enumeration and operation and natural and numerals and sequences and enumeration and operation) conducted by Examiner on Jul. 18, 2009, 1 page.
Apostol, “A Centennial History of the Prime Number Theorem”, Engineering and Science, No. 4, 1996.
Cano et al., “Lazy Evaluation in Penniless Propagation over Join Trees”, Networks, vol. 39(4), 2002 Wiley Periodicals, Inc., 175-185, 2002.
Cooper et al., “Oh! Pascal!”, 1982, W.W. Norton & Company, Inc., Chapter 12, Arrays for Random Access, pp. 295-327.
Er, M.C., “Enumerating Ordered Trees Lexicographically”, The Computation Journal, vol. 28, Issue 5, pp. 538-542, 1985.
Google search (Kleene prime enumeration operation natural numerals sequences “Kleene prime”) conducted by Examiner on Jul. 18, 2009, 2 pages.
Google Search (Kleene prime enumeration operation natural numerals sequences “enumeration operation”) conducted by Examiner on Jul. 18, 2009, 2 pages.
Google Search (Kleene prime enumeration operation) conducted by Examiner on Jul. 18, 2009, 2 pages.
Hoffman et al., “Pattern Matching in Trees”, Purdue University, Jan. 1982, Journal for the Association for Computing Machinery, vol. 29, Issue 1, pp. 68-95.
Iacob et al., “XPath Extension for Querying Concurrent XML Markup”, Technical Report #TR 394-04, Department of Computer Science, University of Kentucky, Lexington, KY 40506, Mar. 6, 2004, 15 pages.
IEEE Explore Digital Library Search Result conducted by Examiner on Jul. 18, 2009, 1 page.
Johnston et al. Advances in Dataflow Programming Languages, ACM Computing Surveys, vol. 36, No. 1, pp. 1-34, 2004.
Kharbutli et al., “Using Prime Numbers For Cache Indexing to Eliminate Conflict Misses”, Dept. of Electrical and Computer Engineering, North Carolina State University, Feb. 2004, 24 pages.
Kilpelainen, “Tree Matching Problems with Applications to Structured Text Databases”, Ph.D. Dissertation, Department of Computer Science, University of Helsinki, Report A-1992-6, Helsinki, Finland, pp. 1-109, Nov. 1992.
Knuth, “The Art of Computer Programming”, vol. 1 Fundamental Algorithms, Second edition, Addison-Wesley Series in Computer Science and Information Processing, ISBN 0-201-03809-9, Reading, Massachusetts, Copyright 1973.
Leinonen et al., “Automation of Document Structure Transformations”, Auditorium, Microteknia Building, University of Kuopio, Nov. 5, 2004, 68 pages.
Lerman et al., “Learning the Common Structure of Data”, American Association for Artificial Intelligence, AAAI-00 Proceedings, www.aaai.org, Apr. 13, 2000, 6 pages.
LeTourneau, “The Elementary Theory of Object Oriented Arithmetic”, pp. 1-9, Apr. 1990.
Navarro, “A Guided Tour to Approximate String Matching”, ACM Computing Surveys, vol. 33, No. 1, pp. 31-88, 2001.
Neven, Frank and Thomas Schwentick, “Expressive and efficient pattern languages for tree-structured data” Proceedings of the Nineteenth ACM SIGACT-SIGMOD-SIGART Symposium on Principles of Database Systems, May 2000.
Reiss, “Semantics-Based Code Search”, IEEE ICSE, pp. 243-253, 2009.
Sechrest et al., “Blending Hierarchical and Attribute-Based File Naming”, Distributed Computing System, 1992, Proceedings of the 12th International Conference on Jun. 9-12, 1992, pp. 572-580.
Shanmugasundaram et al., “Querying SML Views of Relational Data”, Proceedings of the 27th VLDB Conference, Roma, Italy, 2001, 9 pages.
Sitaraman, Krishna, Ranganathan, N., and Ejnioui, Abdel, “A VLSI Architecture for Object Recognition using Tree Matching” Proceedings of the IEEE International Conference on Application-Specific Systems, Architectures, and Processors (ASAP'02) Dec. 2001, pp. 1-71.
Smorynski, Craig, “Logical Number Theory I: An Introduction”, Springer-Verlag Berlin Heidelberg, © 1991, Arithmetic Encoding, The Cantor Pairing Function, pp. 14-23, and 305.
Somani et al., “Phased-Mission System Analysis Using Boolean Algebraic Methods”, May 1994, ACM Press, vol. 22, Issue 1.
Stanat, D.F., and McAllister, D.F., “Discrete Mathematics in Computer Science”, Prentice-Hall, 1977, Binary Relations, Ch. 3, Sec. 3.2, Trees, p. 131-145.
Talukdar, “Learning to Create Data-Integrating Queries”, ACM PVLDB, pp. 785-796, 2008.
Valiente, “Algorithms on Trees and Graphs”, Tree Isomorphism, pp. 151-251, Springer 2002.
Valiente, Gabriel, “Tree Isomorphism,” of Algorithms on Trees and Graphs, Chapter 4, published by Springer, 2002, 51 pages.
Wu, “A Prime Number Labeling Scheme for Dynamic Ordered XML Trees”, IEEE, 2004, 13 pages.
Zaks, S., “Lexicographic Generation of Ordered Trees”, Dept. of Computer Science, University of Illinois, The Journal of Theoretical Computer Science, vol. 10(1), pp. 63-82, Revised 1978.
Dubiner, M., Galil, Z., and Magen, E. “Faster Tree Pattern Matching.”, Journal of the Association for Computing Machinery, vol. 41, No. 2, Mar. 1994, pp. 205-213.
Ramesh, R. and Ramakrishnan, I.V., “Nonlinear Pattern Matching in Trees.” Journal of the Association for Computer Machinery, vol. 39, No. 2. Apr. 1992, pp. 295-316.
Durango Bill's Enumeration of Trees. http://web.archive.org/web/20021028184112/http://www.durangobill.com/Trees.html, 1998.
Cole, Richard, Hariharan, Ramesh, and Indyk, Piotr. “Tree pattern matching and subset matching in deterministic O(n log 3 n)-time”, Proceedings of the Tenth Annual ACM-SIAM Symposium on Discrete Algorithms, p. 1-10, Jan. 2, 1999, Baltimore, Maryland, United States.
U.S. Appl. No. 11/005,859, filed Dec. 6, 2004, 120 pages.
U.S. Appl. No. 11/005,859: Notice to File Missing parts dated Jan. 10, 2005, 2 pages.
U.S. Appl. No. 11/005,859: Response to Notice to File Missing parts dated Apr. 1, 2005, 9 pages.
U.S. Appl. No. 11/005,859: Preliminary Amendment filed Apr. 28, 2005, 193 pages.
U.S. Appl. No. 11/005,859: Office Action—Restriction Requirement dated Dec. 12, 2007, 7 pages.
U.S. Appl. No. 11/005,859: Response to Office Action—Restriction Requirement filed Jan. 14, 2008, 82 pages.
U.S. Appl. No. 11/005,859: Non-final Office Action dated Mar. 21, 2008, 10 pages.
U.S. Appl. No. 11/005,859: Amendment filed Jul. 21, 2008, 86 pages.
U.S. Appl. No. 11/005,859: Final Office Action dated Oct. 30, 2008, 14 pages.
U.S. Appl. No. 11/005,859: Amendment filed Dec. 30, 2008, 83 pages.
U.S. Appl. No. 11/005,859: Advisory Action dated Jan. 13, 2009, 4 pages.
U.S. Appl. No. 11/005,859: RCE with amendment filed Apr. 30, 2009, 86 pages.
U.S. Appl. No. 11/005,859: Final Office Action dated Jul. 8, 2009, 9 pages.
U.S. Appl. No. 11/005,859: Examiner Interview Summary received Oct. 27, 2009, 3 pages.
U.S. Appl. No. 11/005,859: Amendment filed Dec. 8, 2009, 83 pages.
U.S. Appl. No. 11/005,859: Office Action Response dated Sep. 1, 2010, 89 pages.
U.S. Appl. No. 11/005,859: Advisory Action dated Sep. 14, 2010, 3 pages.
U.S. Appl. No. 11/005,859: Notice of Appeal mailed Sep. 29, 2010, 1 page.
U.S. Appl. No. 11/005,859: Office Action dated Oct. 15, 2010, 5 pages.
U.S. Appl. No. 11/005,859: Office Action Response dated Jan. 18, 2011, 95 pages.
U.S. Appl. No. 11/005,859: Final Office Action dated Mar. 30, 2011, 7 pages.
U.S. Appl. No. 11/007,139, filed Dec. 7, 2004, 90 pages.
U.S. Appl. No. 11/007,139: Notice to File Missing Parts dated Jan. 19, 2005, 2 pages.
U.S. Appl. No. 11/007,139: Response to Notice to File Missing Parts dated Apr. 1, 2005, 9 pages.
U.S. Appl. No. 11/007,139: Preliminary Amendment filed Apr. 28, 2005, 146 pages.
U.S. Appl. No. 11/007,139: Non-final Office Action dated May 14, 2007, 58 pages.
U.S. Appl. No. 11/007,139: Amendment filed Oct. 15, 2007, 32 pages.
U.S. Appl. No. 11/007,139: Supplemental Response filed Oct. 17, 2007, 7 pages.
U.S. Appl. No. 11/007,139: Non-final Office Action dated Jan. 2, 2008 with Examiner's search results, 21 pages.
U.S. Appl. No. 11/007,139: Amendment filed Apr. 2, 2008, 30 pages.
U.S. Appl. No. 11/007,139: Final Office Action dated Aug. 15, 2008, 30 pages.
U.S. Appl. No. 11/007,139: Amendment filed Oct. 15, 2008, 26 pages.
U.S. Appl. No. 11/007,139: Advisory Action dated Oct. 22, 2008, 26 pages.
U.S. Appl. No. 11/007,139: RCE with Amendment filed Nov. 14, 2008, 32 pages.
U.S. Appl. No. 11/007,139: Non-final Office Action dated Dec. 8, 2008, 24 pages.
U.S. Appl. No. 11/007,139: Amendment filed May 8, 2009, 31 pages.
U.S. Appl. No. 11/007,139: Final Office Action dated Aug. 4, 2009, 26 pages.
U.S. Appl. No. 11/007,139: Amendment filed Dec. 4, 2009, 28 pages.
U.S. Appl. No. 11/007,139: Advisory Action dated Dec. 14, 2009, 4 pages.
U.S. Appl. No. 11/007,139: Office Action dated Jul. 20, 2010, 20 pages.
U.S. Appl. No. 11/007,139: Office Action response dated Oct. 20, 2010, 33 pages.
U.S. Appl. No. 11/007,139: Advisory Action dated Oct. 25, 2010, 2 pages.
U.S. Appl. No. 11/007,139: Office Action response dated Nov. 18, 2010, 24 pages.
U.S. Appl. No. 11/007,139: Advisory Action dated Dec. 1, 2010, 4 pages.
U.S. Appl. No. 11/007,139: Office Action response and Notice of Appeal dated Dec. 20, 2010, 29 pages.
U.S. Appl. No. 11/007,139: Office Action dated Jan. 3, 2011, 24 pages.
U.S. Appl. No. 11/007,139: Office Action response, dated May 3, 2011, 27 pages.
U.S. Appl. No. 11/006,320, filed Dec. 6, 2004, 75 pages.
U.S. Appl. No. 11/006,320: Response to Missing Parts and Preliminary Amendment filed May 9, 2005, 135 pages.
U.S. Appl. No. 11/006,320: Office Action—Restriction Requirement dated Mar. 26, 2007, 7 pages.
U.S. Appl. No. 11/006,320: Response to Restriction Requirement filed Apr. 27, 2007, 34 pages.
U.S. Appl. No. 11/006,320: Notice of Non-Compliant Amendment dated Jul. 6, 2007, 3 pages.
U.S. Appl. No. 11/006,320: Response to Non-Compliant Amendment filed Jul. 25, 2007, 33 pages.
U.S. Appl. No. 11/006,320: Non-final Office Action dated Oct. 1, 2007, 24 pages.
U.S. Appl. No. 11/006,320: Amendment filed Jan. 29, 2008, 45 pages.
U.S. Appl. No. 11/006,320: Notice of Non-Compliant Amendment dated Apr. 8, 2008, 4 pages.
U.S. Appl. No. 11/006,320: Amendment filed May 5, 2008, 44 pages.
U.S. Appl. No. 11/006,320: Non-final Office Action dated Aug. 15, 2008, 33 pages.
U.S. Appl. No. 11/006,320: Amendment filed Nov. 14, 2008, 40 pages.
U.S. Appl. No. 11/006,320: Office Action—Shortened Statutory Period dated Jan. 27, 2009, 2 pages.
U.S. Appl. No. 11/006,320: Amendment filed Apr. 27, 2009, 44 pages.
U.S. Appl. No. 11/006,320: Final Office Action dated Jul. 29, 2009, 13 pages.
U.S. Appl. No. 11/006,320: Amendment filed Nov. 30, 2009, 10 pages.
U.S. Appl. No. 11/006,320: Non-final Office Action dated Dec. 4, 2009, 25 pages.
U.S. Appl. No. 11/006,320: Office Action response dated Aug. 24, 2010, 15 pages.
U.S. Appl. No. 11/006,320: Notice of Allowance dated Sep. 17, 2010, 8 pages.
U.S. Appl. No. 11/006,320: Examiner Interview Summary and supplemental Notice of Allowance dated Dec. 17, 2010, 9 pages.
U.S. Appl. No. 11/006,320: Rule 312 Amendment and Issue Fee payment dated Dec. 17, 2010, 10 pages.
U.S. Appl. No. 11/006,320: Issue Notification dated Jan. 12, 2011, 1 page.
U.S. Appl. No. 12/972,326, filed Dec. 17, 2010, 74 pages.
U.S. Appl. No. 12/972,326: Filing receipt and Notice to File Missing Parts dated Jan. 6, 2011, 5 pages.
U.S. Appl. No. 12/972,326: Response to Notice to File Missing parts dated Jan. 26, 2011, 14 pages.
U.S. Appl. No. 12/972,326: Filing Receipt, mailed Feb. 18, 2011, 3 pages.
U.S. Appl. No. 12/972,326: Preliminary amendment dated May 20, 2011, 15 pages.
U.S. Appl. No. 12/972,326: Notice of publication and non-compliant amendment dated Jun. 2, 2011, 3 pages.
U.S. Appl. No. 13/014,677, filed Jan. 26, 2011, 90 pages.
U.S. Appl. No. 13/014,677: Notice to file missing parts and filing receipt, dated Mar. 23, 2011, 5 pages.
U.S. Appl. No. 11/006,848, filed Dec. 7, 2004, 59 pages.
U.S. Appl. No. 11/006,848: Notice to File Missing Parts dated Mar. 18. 2005, 2 pages.
U.S. Appl. No. 11/006,848: Response to Notice to File Missing Parts dated May 3, 2005, 101 pages.
U.S. Appl. No. 11/006,848: Non-Final Office Action dated Apr. 4, 2007, 11 pages.
U.S. Appl. No. 11/006,848: Response to Non-Final Office Action dated Oct. 3, 2007, 20 pages.
U.S. Appl. No. 11/006,848: Supplemental Amendment dated Nov. 13, 2007, 4 pages.
U.S. Appl. No. 11/006,848: Non-Final Office Action dated Feb. 5, 2008, 16 pages.
U.S. Appl. No. 11/006,848: Response to Non-Final Office Action filed Aug. 4, 2008, 27 pages.
U.S. Appl. No. 11/006,848: Final Office Action dated Dec. 2, 2008, 30 pages.
U.S. Appl. No. 11/006,848: RCE filed May 4, 2009, 24 pages.
U.S. Appl. No. 11/006,848: Notice of Allowance dated Jun. 11, 2009, 8 pages.
U.S. Appl. No. 11/006,848: Issue fee mailed Sep. 11, 2009, 10 pages.
U.S. Appl. No. 11/006,848: Issue Notification dated Oct. 28, 2009, 1 page.
U.S. Appl. No. 12/573,829, filed Oct. 5, 2009, 64 pages.
U.S. Appl. No. 12/573,829: Notice to File Missing Parts and Filing Receipt dated Oct. 20, 2009, 5 pages.
U.S. Appl. No. 12/573,829: Preliminary Amendment dated Dec. 21, 2009, 17 pages.
U.S. Appl. No. 12/573,829: Filing receipt mailed Jan. 4, 2010, 5 pages.
U.S. Appl. No. 12/573,829: Office Action dated Jun. 28, 2010, 35 pages.
U.S. Appl. No. 12/573,829: Office Action Response dated Sep. 28, 2010, 22 pages.
U.S. Appl. No. 12/573,829: Office Action dated Nov. 1, 2010, 29 pages.
U.S. Appl. No. 12/573,829: Office Action Response dated Jan. 3, 2011, 29 pages.
U.S. Appl. No. 12/573,829: Advisory Action dated Jan. 7, 2011, 3 pages.
U.S. Appl. No. 12/573,829: Notice of Appeal dated Jan. 11, 2011, 1 page.
U.S. Appl. No. 12/573,829: Appeal Brief, mailed May 4, 2011, 68 pages.
U.S. Appl. No. 11/006,841, filed Dec. 7, 2004, 63 pages.
U.S. Appl. No. 11/006,841: Notice to file missing parts dated Jan. 10, 2005, 2 pages.
U.S. Appl. No. 11/006,841: Response to Notice to file missing parts and preliminary amendment dated Apr. 14, 2005, 105 pages.
U.S. Appl. No. 11/006,841: Non-Final OA dated Apr. 6, 2007, 16 pages.
U.S. Appl. No. 11/006,841: Response to Non-Final OA dated Sep. 6, 2007, 63 pages.
U.S. Appl. No. 11/006,841: Restriction Requirement dated Nov. 27, 2007, 5 pages.
U.S. Appl. No. 11/006,841: Restriction Requirement response dated Dec. 27, 2007, 36 pages.
U.S. Appl. No. 11/006,841: Restriction Requirement dated Mar. 17, 2008, 9 pages.
U.S. Appl. No. 11/006,841: Response to Restriction Requirement dated Jul. 17, 2008, 33 pages.
U.S. Appl. No. 11/006,841: Final Office Action dated Oct. 29, 2008, 54 pages.
U.S. Appl. No. 11/006,841: Response to Final Office Action dated Dec. 29, 2008, 45 pages.
U.S. Appl. No. 11/006,841: Advisory Action dated Jan. 6, 2009, 3 pages.
U.S. Appl. No. 11/006,841: RCE mailed Apr. 23, 2009, 48 pages.
U.S. Appl. No. 11/006,841: Supplemental Response dated Jun. 26, 2009, 34 pages.
U.S. Appl. No. 11/006,841: Notice of Allowance dated Jun. 29, 2009, 40 pages.
U.S. Appl. No. 11/006,841: Issue Fee mailed Sep. 29, 2009, 4 pages.
U.S. Appl. No. 11/006,841: Issue Notification dated Nov. 11, 2009, 1 page.
U.S. Appl. No. 12/578,411: Continuation application filed Oct. 13, 2009, 75 pages.
U.S. Appl. No. 12/578,411: Filing Receipt mailed Jan. 7, 2010, 3 pages.
U.S. Appl. No. 11/006,440, filed Dec. 6, 2004, 85 pages.
U.S. Appl. No. 11/006,440: Notice to file missing parts Jan. 11, 2005, 2 pages.
U.S. Appl. No. 11/006,440: Response to Notice to file missing parts, dated Mar. 15, 2005, 8 pages.
U.S. Appl. No. 11/006,440: Preliminary Amendment dated Apr. 28, 2005, 140 pages.
U.S. Appl. No. 11/006,440: Preliminary Amendment and Substitute Specification dated Oct. 10, 2006, 139 pages.
U.S. Appl. No. 11/006,440: Restriction Requirement dated Mar. 29, 2007, 5 pages.
U.S. Appl. No. 11/006,440: Response to Restriction Requirement dated Apr. 30, 2007, 42 pages.
U.S. Appl. No. 11/006,440: Non-Final Office Action dated Jun. 21, 2007, 15 pages.
U.S. Appl. No. 11/006,440: Response to Non-Final Office Action dated Nov. 20, 2007, 42 pages.
U.S. Appl. No. 11/006,440: Final Office Action dated Feb. 6, 2008, 13 pages.
U.S. Appl. No. 11/006,440: Response to Final Office Action dated Apr. 7, 2008, 34 pages.
U.S. Appl. No. 11/006,440: Advisory Action dated May 9, 2008, 3 pages.
U.S. Appl. No. 11/006,440: Notice of appeal mailed Aug. 4, 2008, 1 page.
U.S. Appl. No. 11/006,440: RCE mailed Nov. 4, 2008, 39 pages.
U.S. Appl. No. 11/006,440: Final Office Action dated Jan. 23, 2009, 22 pages.
U.S. Appl. No. 11/006,440: Amendment after Final dated Apr. 23, 2009, 34 pages.
U.S. Appl. No. 11/006,440: Supplemental Amendment dated Jul. 17, 2009, 29 pages.
U.S. Appl. No. 11/006,440: Notice of Allowance dated Jul. 31, 2009, 15 pages.
U.S. Appl. No. 11/006,440: Examiner's Amendment and Reasons for Allowance dated Sep. 3, 2009, 9 pages.
U.S. Appl. No. 11/006,440: Issue Fee mailed Nov. 2, 2009, 12 pages.
U.S. Appl. No. 11/006,440: Issue Notification dated Dec. 2, 2009, 1 page.
U.S. Appl. No. 12/627,816: Continuation application filed Nov. 30, 2009, 95 pages.
U.S. Appl. No. 12/627,816: Filing Receipt mailed Apr. 20, 2010, 3 pages.
U.S. Appl. No. 12/627,816: Notice of Publication dated Jul. 29, 2010, 1 page.
U.S. Appl. No. 12/627,816: Non-Final OA, dated May 5, 2011, 19 pages.
U.S. Appl. No. 11/006,446, filed Dec. 6, 2004, 91 pages.
U.S. Appl. No. 11/006,446: Notice of Missing Parts dated Jan. 24, 2005, 3 pages.
U.S. Appl. No. 11/006,446: Response to Notice to File Missing Parts dated Mar. 29, 2005, 8 pages.
U.S. Appl. No. 11/006,446: Preliminary Amendment filed Apr. 28, 2005, 118 pages.
U.S. Appl. No. 11/006,446: Office Action—Restriction Requirement dated Apr. 4, 2007, 5 pages.
U.S. Appl. No. 11/006,446: Response to Office Action—Restriction Requirement filed May 3, 2007, 6 pages.
U.S. Appl. No. 11/006,446: Non-final Office Action dated Jul. 26, 2007, 45 pages.
U.S. Appl. No. 11/006,446: Amendment filed Nov. 26, 2007, 38 pages.
U.S. Appl. No. 11/006,446: Non-Final Office Action dated Feb. 20, 2008, 67 pages.
U.S. Appl. No. 11/006,446: Amendment filed Jul. 21, 2008, 33 pages.
U.S. Appl. No. 11/006,446: Final Office Action dated Oct. 28, 2008, 49 pages.
U.S. Appl. No. 11/006,446: Amendment filed Dec. 29, 2008, 33 pages.
U.S. Appl. No. 11/006,446: Advisory Action dated Jan. 7, 2009, 4 pages.
U.S. Appl. No. 11/006,446: RCE with Amendment filed Apr. 28, 2009, 38 pages.
U.S. Appl. No. 11/006,446: Non-final Office Action dated Jul. 7, 2009, 41 pages.
U.S. Appl. No. 11/006,446: Examiner interview Summary and Search Results dated Oct. 26, 2009, 6 pages.
U.S. Appl. No. 11/006,446: Amendment dated Dec. 7, 2009, 33 pages.
U.S. Appl. No. 11/006,446: Rule 312 Amendment dated Aug. 19, 2010, 2 pages.
U.S. Appl. No. 11/006,446: Formal drawings mailed Aug. 25, 2010, 29 pages.
U.S. Appl. No. 11/006,446: Issue Notification dated Sep. 1, 2010, 1 page.
U.S. Appl. No. 11/385,257, filed Mar. 20, 2006, 118 pages.
U.S. Appl. No. 11/385,257: Notice of Missing Parts dated May 3, 2006, 2 pages.
U.S. Appl. No. 11/385,257: Response to Missing Parts filed Aug. 3, 2006, 46 pages.
U.S. Appl. No. 11/385,257: Notice of Publication dated Nov. 30, 2006, 1 page.
U.S. Appl. No. 11/385,257: Non-final Office Action dated Apr. 29, 2008, 44 pages.
U.S. Appl. No. 11/385,257: Amendment filed Jul. 29, 2008, 29 pages.
U.S. Appl. No. 11/385,257: Final Office Action dated Dec. 9, 2008, 47 pages.
U.S. Appl. No. 11/385,257: RCE with Amendment filed May 11, 2009, 38 pages.
U.S. Appl. No. 11/385,257: Supplemental Amendment filed May 26, 2009, 32 pages.
U.S. Appl. No. 11/385,257: Notice of Non-Compliant Amendment dated Jun. 1, 2009, 3 pages.
U.S. Appl. No. 11/385,257: Amendment filed Jun. 30, 2009, 34 pages.
U.S. Appl. No. 11/385,257: Non-final Office Action dated Sep. 14, 2009, 60 pages.
U.S. Appl. No. 11/385,257: RCE mailed Aug. 12, 2010, 35 pages.
U.S. Appl. No. 11/385,257: Office Action dated Sep. 30, 2010, 39 pages.
U.S. Appl. No. 11/385,257: Office Action response, dated Mar 29, 2011, 31 pages.
U.S. Appl. No. 11/319,758, filed Dec. 27, 2005, 79 pages.
U.S. Appl. No. 11/319,758: Notice of Missing Parts dated Feb. 1, 2006, 2 pages.
U.S. Appl. No. 11/319,758: Response to Missing Parts filed Jul. 3, 2006, 15 pages.
U.S. Appl. No. 11/319,758: Non-final Office Action dated Nov. 12, 2008, 46 pages.
U.S. Appl. No. 11/319,758: Amendment filed May 12, 2009, 40 pages.
U.S. Appl. No. 11/319,758: Final Office Action dated Aug. 3, 2009, 39 pages.
U.S. Appl. No. 11/319,758: Office Action response dated Jul. 29, 2010, 30 pages.
U.S. Appl. No. 11/319,758: Final Office Action dated Oct. 28, 2010, 31 pages.
U.S. Appl. No. 11/319,758: Request for Continued Examination, dated Mar. 28, 2011, 32 pages.
U.S. Appl. No. 11/006,842, filed Dec. 27, 2004, 58 pages.
U.S. Appl. No. 11/006,842: Notice to file missing parts dated Jan. 10, 2005, 2 pages.
U.S. Appl. No. 11/006,842: Response to Notice to file missing parts dated Apr. 1, 2005, 7 pages.
U.S. Appl. No. 11/006,842: Preliminary Amendment dated May 2, 2005, 93 pages.
U.S. Appl. No. 11/006,842: Restriction Requirement dated Jan. 23, 2008, 5 pages.
U.S. Appl. No. 11/006,842: Response to Restriction Requirement dated Feb. 25, 2008, 25 pages.
U.S. Appl. No. 11/006,842: Restriction Requirement dated May 13, 2008, 5 pages.
U.S. Appl. No. 11/006,842: Response to Restriction Requirement dated Aug. 13, 2008, 24 pages.
U.S. Appl. No. 11/006,842: Non-Final Office Action dated Nov. 3, 2008.
U.S. Appl. No. 11/006,842: Response to Non-Final Office Action dated May 4, 2009, 35 pages.
U.S. Appl. No. 11/006,842: Supplemental Response dated Jul. 17, 2009, 23 pages.
U.S. Appl. No. 11/006,842: Notice of Allowance dated Jul. 27, 2009, 13 pages.
U.S. Appl. No. 11/006,842: Issue Fee filed Oct. 27, 2009, 1 page.
U.S. Appl. No. 11/006,842: Issue notification dated Nov. 18, 2009, 1 page.
U.S. Appl. No. 12/613,450: Continuation application filed Nov. 5, 2009, 63 pages.
U.S. Appl. No. 12/613,450: Filing receipt mailed Jan. 27, 2010, 3 pages.
U.S. Appl. No. 12/613,450: Notice of Publication dated May 6, 2010, 1 page.
U.S. Appl. No. 11/320,538, filed Dec. 27, 2005, 76 pages.
U.S. Appl. No. 11/320,538: Notice of Missing Parts dated Feb. 2, 2006, 2 pages.
U.S. Appl. No. 11/320,538: Response to Missing Parts filed Aug. 2, 2006, 36 pages.
U.S. Appl. No. 11/320,538: Non-final Office Action dated Apr. 1, 2009, 27 pages.
U.S. Appl. No. 11/320,538: Amendment filed Jul. 1, 2009, 54 pages.
U.S. Appl. No. 11/320,538: Final Office Action dated Nov. 2, 2009, 29 pages.
U.S. Appl. No. 11/320,538: Office action dated Dec. 22, 2010, 10 pages.
U.S. Appl. No. 11/320,538: Notice of Appeal, dated May 23, 2011, 6 pages.
U.S. Appl. No. 11/320,538: Pre-brief appeal conference decision mailed Jun. 30, 2011, 2 pages.
U.S. Appl. No. 11/361,500, filed Feb. 23, 2006, 72 pages.
U.S. Appl. No. 11/361,500: Notice to file missing parts dated Mar. 23, 2006, 2 pages.
U.S. Appl. No. 11/361,500: Response to Notice to File Missing Parts dated Jul. 19, 2006, 27 pages.
U.S. Appl. No. 11/361,500: Notice of Publication dated Nov. 16, 2006, 1 page.
U.S. Appl. No. 11/361,500: Office Action dated May 27, 2009, 18 pages.
U.S. Appl. No. 11/361,500: Response to Office Action dated Aug. 27, 2009, 34 pages.
U.S. Appl. No. 11/361,500: Notice of Allowance dated Dec. 11, 2009, 8 pages.
U.S. Appl. No. 11/361,500: Issue Fee Payment and Rule 312 Amendment dated Jan. 6, 2010, 28 pages.
U.S. Appl. No. 11/361,500: Response to Rule 312 Amendment dated Jan. 25, 2010, 4 pages.
U.S. Appl. No. 11/361,500: Issue Notification dated Feb. 24, 2010, 1 page.
U.S. Appl. No. 12/702,243: Filing receipt mailed May 4, 2010, 3 pages.
U.S. Appl. No. 11/412,417, filed Apr. 26, 2006, 96 pages.
U.S. Appl. No. 11/412,417: Notice of Missing Parts dated May 19, 2006, 2 pages.
U.S. Appl. No. 11/412,417: Response to Notice of Missing Parts filed Jul. 19, 2006, 14 pages.
U.S. Appl. No. 11/412,417: Non-final Office Action dated Apr. 1, 2008, 53 pages.
U.S. Appl. No. 11/412,417: Amendment filed Aug. 1, 2008, 34 pages.
U.S. Appl. No. 11/412,417: Final Office Action dated Nov. 13, 2008, 40 pages.
U.S. Appl. No. 11/412,417: RCE and Amendment filed May 12, 2009, 36 pages.
U.S. Appl. No. 11/412,417: Non-final Office Action dated Jun. 30, 2009, 141 pages.
U.S. Appl. No. 11/412,417: Examiner Interview Summary dated Oct. 30, 2009, 3 pages.
U.S. Appl. No. 11/412,417: Amendment filed Oct. 30, 2009, 33 pages.
U.S. Appl. No. 11/412,417: Supplemental Office Action Response dated Jun. 22, 2010, 22 pages.
U.S. Appl. No. 11/412,417: Notice of Allowance and bibliographic data sheet dated Jul. 6, 2010, 9 pages.
U.S. Appl. No. 11/412,417: RCE mailed Oct. 5, 2010, 4 pages.
U.S. Appl. No. 11/412,417: Notice of Allowance and bibliographic data sheet dated Oct. 26, 2010, 4 pages.
U.S. Appl. No. 13/030,084, filed Feb. 17, 2011, 103 pages.
U.S. Appl. No. 13/030,084: Filing receipt and Notice to File Missing parts dated Mar. 3, 2011, 6 pages.
U.S. Appl. No. 11/480,094, filed Jun. 29, 2006, 125 pages.
U.S. Appl. No. 11/480,094: Notice to File Corrected Application Papers dated Aug. 2, 2006, 2 pages.
U.S. Appl. No. 11/480,094: Response to Notice to File Corrected Application Papers filed Nov. 2, 2006, 32 pages.
U.S. Appl. No. 11/480,094: Filing Receipt mailed Dec. 7, 2006, 3 pages.
U.S. Appl. No. 11/480,094: Non-final Office Action dated Nov. 7, 2008, 28 pages.
U.S. Appl. No. 11/480,094: Amendment filed May 7, 2009, 37 pages.
U.S. Appl. No. 11/480,094: Final Office Action dated Jul. 28, 2009, 16 pages.
U.S. Appl. No. 11/480,094: RCE with Amendment filed Dec. 28, 2009, 39 pages.
U.S. Appl. No. 11/480,094: Office Action dated Dec. 15, 2010, 15 pages.
U.S. Appl. No. 11/480,094: Office Action response, dated May 16, 2011, 29 pages.
U.S. Appl. No. 11/005,859: Notice of Allowance and Fees Due, dated Jun. 9, 2011, 11 pages.
U.S. Appl. No. 11/005,859: Amendment after Notice of Allowance and Issue Fee Payment, dated Sep. 9, 2011, 2 pages.
U.S. Appl. No. 11/005,859: Issue Notification, dated Sep. 21, 2011, 1 page.
U.S. Appl. No. 13/229,624, filed Sep. 9, 2011, 139 pages.
U.S. Appl. No. 13/229,624: Filing receipt, mailed Sep. 21, 2011, 4 pages.
U.S. Appl. No. 13/229,624: Non-Final Office Action, dated Nov. 23, 2011, 8 pages.
U.S. Appl. No. 13/229,624: Notice of Publication, dated Dec. 30, 2011, 1 page.
U.S. Appl. No. 13/229,624: Amendment, dated Feb. 23, 2012, 22 pages.
U.S. Appl. No. 13/229,624: Final Office Action, dated Mar. 20, 2012, 10 pages.
U.S. Appl. No. 13/229,624: Amendment after final, dated Jun. 13, 2012, 25 pages.
U.S. Appl. No. 13/229,624: Advisory Action, dated Jun. 20, 2012, 4 pages.
U.S. Appl. No. 13/229,624: RCE, mailed Jul. 20, 2012, 26 pages.
U.S. Appl. No. 11/007,139: Final Office Action, dated Jul. 18, 2011, 23 pages.
U.S. Appl. No. 11/007,139: Amendment after final dated Oct. 18, 2011, 30 pages.
U.S. Appl. No. 11/007,139: Advisory Action and rule 312 amendment, dated Nov. 3, 2011, 4 pages.
U.S. Appl. No. 11/007,139: Notice of Appeal filed Nov. 16, 2011, 1 page.
U.S. Appl. No. 11/007,139: Appeal Brief filed May 1, 2012, 93 pages.
U.S. Appl. No. 11/007,139: Notice of defective appeal brief, dated May 7, 2012, 3 pages.
U.S. Appl. No. 11/007,139: Appeal Brief filed May 15, 2012, 9 pages.
U.S. Appl. No. 11/007,139: Examiner's answer to appeal brief, dated Aug. 20, 2012, 35 pages.
U.S. Appl. No. 12/972,326: Notice of additional fee due, dated Jul. 12, 2011, 2 pages.
U.S. Appl. No. 12/972,326: Preliminary Amendment dated Aug. 10, 2011, 7 pages.
U.S. Appl. No. 12/972,326: Non-Final Office Action, dated Feb. 23, 2012, 9 pages.
U.S. Appl. No. 12/972,326: Abandonment, mailed Sep. 18, 2012, 2 pages.
U.S. Appl. No. 13/014,677: Notice of Abandonment dated Nov. 29, 2011, 2 pages.
U.S. Appl. No. 12/573,829: Examiner's Answer to Appeal Brief, dated Jul. 21, 2011, 31 pages.
U.S. Appl. No. 12/573,829: Reply brief filed Sep. 21, 2011, 17 pages.
U.S. Appl. No. 12/573,829: Reply brief noted Oct. 5, 2011, 2 pages.
U.S. Appl. No. 12/573,829: Appeal Docketing notice Oct. 11, 2011, 2 pages.
U.S. Appl. No. 12/578,411: Non-Final Office Action, dated Aug. 23, 2011, 19 pages.
U.S. Appl. No. 12/578,411: Non-Final Office Action response dated Dec. 22, 2011, 38 pages.
U.S. Appl. No. 12/578,411: Final Rejection dated Jan. 20, 2012, 16 pages.
U.S. Appl. No. 12/578,411: Amendment, dated May 21, 2012, 23 pages.
U.S. Appl. No. 12/578,411: Advisory Action, dated May 31, 2012, 4 pages.
U.S. Appl. No. 12/578,411: RCE, mailed Jun. 12, 2012, 38 pages.
U.S. Appl. No. 12/627,816: Non-Final OA response, dated Nov. 7, 2011, 12 pages.
U.S. Appl. No. 12/627,816: Final Rejection dated Nov. 17, 2011, 18 pages.
U.S. Appl. No. 12/627,816: RCE mailed Feb. 17, 2012, 20 pages.
U.S. Appl. No. 12/627,816: Terminal disclaimer review, dated Mar. 7, 2012, 1 page.
U.S. Appl. No. 11/385,257: Request for continued Examination dated Nov. 1, 2011, 30 pages.
U.S. Appl. No. 11/385,257: Non-Final Office Action, dated Jan. 9, 2012, 40 pages.
U.S. Appl. No. 11/385,257: Amendment, dated Apr. 6, 2012, 30 pages.
U.S. Appl. No. 11/385,257: Notice of allowance and Examiner interview summary, dated Jun. 22, 2012, 36 pages.
U.S. Appl. No. 13/625,812, filed Sep. 24, 2012, 123 pages.
U.S. Appl. No. 11/319,758: Non-Final Office Action Response dated Nov. 3, 2011, 29 pages.
U.S. Appl. No. 11/319,758: Final Office Action, dated Jan. 17, 2012, 22 pages.
U.S. Appl. No. 11/319,758: Amendment after final, dated May 17, 2012, 34 pages.
U.S. Appl. No. 11/319,758: Advisory Action, dated Jun. 20, 2012, 3 pages.
U.S. Appl. No. 11/319,758: Amendment after final, dated Jun. 28, 2012, 29 pages.
U.S. Appl. No. 11/319,758: Notice of Allowance and examiner's interview summary, dated Jul. 17, 2012, 10 pages.
U.S. Appl. No. 12/613,450: Non-Final Office Action, dated Aug. 25, 2011, 15 pages.
U.S. Appl. No. 12/613,450: Non-Final OA response dated Dec. 27, 2011, 28 pages.
U.S. Appl. No. 12/613,450: Final rejection, dated Feb. 14, 2012, 14 pages.
U.S. Appl. No. 12/613,450: Amendment after final, dated Jun. 8, 2012, 23 pages.
U.S. Appl. No. 12/613,450: Advisory Action, dated Jun. 20, 2012, 4 pages.
U.S. Appl. No. 12/613,450: RCE, mailed Jul. 12, 2012, 25 pages.
U.S. Appl. No. 11/320,538: Request for Continued Examination dated Dec. 23, 2011, 21 pages.
U.S. Appl. No. 12/702,243: Non-Final rejection, dated Aug. 30, 2012, 8 pages.
U.S. Appl. No. 13/030,084: Response to Notice to File Missing Parts, dated Aug. 3, 2011, 23 pages.
U.S. Appl. No. 13/030,084: Updated filing receipt, mailed Aug. 11, 2011, 3 pages.
U.S. Appl. No. 13/030,084: Non-Final Rejection dated Oct. 26, 2011, 34 pages.
U.S. Appl. No. 13/030,084: Notice of Publication dated Nov. 17, 2011, 1 page.
U.S. Appl. No. 13/030,084: Amendment, dated Jan. 26, 2012, 35 pages.
U.S. Appl. No. 13/030,084: Notice regarding non-compliant amendment, dated Jan. 31, 2012, 4 pages.
U.S. Appl. No. 13/030,084: Amendment, dated Feb. 9, 2012, 35 pages.
U.S. Appl. No. 13/030,084: Final Rejection, dated Mar. 28, 2012, 62 pages.
U.S. Appl. No. 13/030,084: Amendment after final, dated Jun. 14, 2012, 88 pages.
U.S. Appl. No. 13/030,084: Advisory Action, dated Jun. 26, 2012, 4 pages.
U.S. Appl. No. 13/030,084: RCE, mailed Jul. 23, 2012, 89 pages.
U.S. Appl. No. 13/030,084: Notice regarding non-compliant amendment, dated Jul. 25, 2012, 2 pages.
U.S. Appl. No. 11/480,094: Final Office Action, dated Aug. 1, 2011, 13 pages.
U.S. Appl. No. 11/480,094: Amendment after final dated Nov. 1, 2011, 32 pages.
U.S. Appl. No. 11/480,094: Advisory Action dated Nov. 14, 2011, 3 pages.
U.S. Appl. No. 11/480,094: Notice of Appeal dated Nov. 28, 2011, 1 page.
U.S. Appl. No. 11/480,094: Abandonment, mailed Jul. 31, 2012, 2 pages.
Alderson et al., “Toward an Optimization Driven Framework for Designing and Generating Realistic Internet Topologies” ACM SIGCOMM Computer Communications Review 41, vol. 33, No. 1, pp. 41-46, 2003.
Sproat et al., “Compilation of Weighted Finite-State Tranducers from Decision Trees” ACM, pp. 215-222, 1996.
Benedikt et al., “Definable Relations and First-Order Query Languages over Strings” Journal of the ACM, vol. 50, No. 5, pp. 694-751, 2003.
Malhotra et al, “A Methodology for Formal Expression of Hierarchy in Model Solution”, IEEE, pp. 258-267,1983.
U.S. Appl. No. 13/229,624: Non-Final Office Action Response, dated Aug. 1, 2014, 9 Pages.
U.S. Appl. No. 13/229,624: Final Rejection. dated Oct. 30, 2014, 6 pages.
U.S. Appl. No. 14/086,837, filed Nov. 21, 2013, 68 Pages.
U.S. Appl. No. 14/086,837: Notice to File Missing Parts, dated Dec. 12, 2013, 5 Pages.
U.S. Appl. No. 14/086,837: Applicant Response to Pre-Exam Formalities Notice, dated Jun. 11, 2014, 26 Pages.
U.S. Appl. No. 14/086,837: Notice of Publication, dated Sep. 25, 2014, 4 Pages.
U.S. Appl. No. 14/086,837: Terminal Disclaimer, Filed Nov. 14, 2014, 1 page.
U.S. Appl. No. 14/086,808, filed Nov. 21, 2013, 87 Pages.
U.S. Appl. No. 14/086,808: Notice to File Missing Parts and Filing Receipt, dated Dec. 11, 2013, 5 Pages.
U.S. Appl. No. 14/086,808: Applicant Reponse to Pre-Exam Formalities Notice, dated Jun. 11, 2014, 53 Pages.
U.S. Appl. No. 14/086,808: Filing receipt, Mailed Jun. 17, 2014, 3 Pages.
U.S. Appl. No. 14/086,808: Notice of Publication, dated Sep. 25, 2014, 1 Page.
U.S. Appl. No. 14/086,808: Terminal Disclaimer, Filed Oct. 24, 2014, 2 pages.
U.S. Appl. No. 14/086,808: Terminal Disclaimer Review Decision, Mailed Oct. 29, 2014, 1 page.
U.S. Appl. No. 14/086,808: Terminal Disclaimer, Filed Nov. 4, 2014, 2 pages.
U.S. Appl. No. 14/086,808: Terminal Disclaimer Review Decision, Mailed Nov. 13, 2014, 1 page.
U.S. Appl. No. 13/625,812: Notice of Appeal, filed May 5, 2014, 1 Page.
U.S. Appl. No. 13/625,812: Request for Continued Examination, dated Aug. 4, 2014, 18 Pages.
U.S. Appl. No. 13/625,812: Request for Corrected Filing Receipt, dated Aug. 21, 2014, 6 Pages.
U.S. Appl. No. 13/625,812: Filing Receipt, Mailed Aug. 27, 2014, 3 Pages.
U.S. Appl. No. 13/632,581, filed Oct. 1, 2012, 88 Pages.
U.S. Appl. No. 13/632,581: Notice to File Missing Parts and Filing Receipt, dated Oct. 22, 2012, 27 Pages.
U.S. Appl. No. 13/632,581: Filing Receipt, Mailed Mar. 5, 2004, 3 Pages.
U.S. Appl. No. 13/632,581: Notice of Publication, dated Jun. 13, 2013, 1 Page.
U.S. Appl. No. 13/632,581: Non-final Office Action, dated Jul. 3, 2013, 22 Pages.
U.S. Appl. No. 13/632,581: Non-Final Office Action Response, dated Sep. 11, 2013, 23 Pages.
U.S. Appl. No. 13/632,581: Final Office Action, dated Dec. 18, 2013, 27 Pages.
U.S. Appl. No. 13/632,581: Response After Final Action, dated Mar. 18, 2014, 37 Pages.
U.S. Appl. No. 13/632,581: Advisory Action (PTOL-303), dated Apr. 3, 2014, 4 Pages.
U.S. Appl. No. 13/632,581: Notice of Appeal Filed Jul. 17, 2014, 2 Pages.
U.S. Appl. No. 13/632,581: Request for Continued Examination, dated Jul. 16, 2014, 23 Pages.
U.S. Appl. No. 13/632,581: Notice Non-Compliant Amendment, dated Oct. 20, 2014, 5 pages.
U.S. Appl. No. 13/632,581: Amendment/Req Reconsideration after Non-Final Reject, Filed Nov. 4, 2014, 16 pages.
U.S. Appl. No. 12/613,450: Amendment After Final or Under 37CFR 1.312, initialed by the Examiner, dated Jan. 14, 2014, 2 Pages.
U.S. Appl. No. 12/613,450: Issue Notification, dated Jan. 22, 2014, 1 Page.
U.S. Appl. No. 14/149,749, filed Jan. 7, 2014, 59 Pages.
U.S. Appl. No. 14/149,749: Notice to File Missing Parts and Filing Receipt, dated Jan. 23, 2014, 6 Pages.
U.S. Appl. No. 14/149,749: Applicant Response to Pre-exam Formalities Notice, dated May 23, 2014 12 Pages.
U.S. Appl. No. 14/149,749: Applicant Response to Pre-Exam Formalities Notice, dated Aug. 25, 2014, 103 Pages.
U.S. Appl. No. 14/149,749: Filing Receipt, Mailed Sep. 4, 2014, 3 Pages.
U.S. Appl. No. 14/086,741, filed Dec. 12, 2013, 77 Pages.
U.S. Appl. No. 14/086,741: Filing Receipt and Notice to File Missing Parts, dated Dec. 12, 2013, 6 Pages.
U.S. Appl. No. 14/086,741: Applicant Response to Pre-Exam Formalities Notice, dated Jun. 12, 2014, 60 Pages.
U.S. Appl. No. 14/086,741: Filing Receipt, Mailed Jun. 17, 2014, 3 Pages.
U.S. Appl. No. 14/086,741: Notice of Publication, dated Sep. 25, 2014, 1 Page.
U.S. Appl. No. 14/086,741: Terminal Disclaimer as Filed Sep. 29, 2014, 1 Page.
U.S. Appl. No. 14/086,741: Terminal Disclaimer Review Decision, Mailed Sep. 30, 2014, 1 Page.
U.S. Appl. No. 14/086,741: Notice of Allowance and Fees Due, Filed Oct. 3, 2014, 22 pages.
U.S. Appl. No. 13/860,482, filed Apr. 10, 2013, 98 Pages.
U.S. Appl. No. 13/860,482: Notice to File Missing Parts and Filing Receipt, dated May 21, 2013, 5 Pages.
U.S. Appl. No. 13/860,482: Applicant Response to Pre-Exam Formalities Notice, dated Oct. 22, 2013, 3 Pages.
U.S. Appl. No. 13/860,482: Notice of Publication, dated Feb. 6, 2014, 1 Page.
U.S. Appl. No. 13/860,482: Non-Final Office Action, dated Jun. 9, 2014, 11 Pages.
U.S. Appl. No. 13/860,482: Non-Final Office Action Response, dated Sep. 8, 2014, 19 Pages.
U.S. Appl. No. 13/860,482: Terminal Disclaimer Review Decision, Sep. 9, 2014, 1 page.
U.S. Appl. No. 13/860,482: Terminal Disclaimer Filed, Oct. 8, 2014, 1 page.
U.S. Appl. No. 13/860,482: Terminal Disclaimer Review Decision, Oct. 9, 2014, 1 page.
U.S. Appl. No. 13/860,482: Notice of Allowance and Fees Due, dated Nov. 5, 2014, 8 Pages.
U.S. Appl. No. 13/030,084: Amendment Submitted/Entered with Filing of CPA/RCE, dated May 19, 2014, 38 Pages.
U.S. Appl. No. 13/030,084: Advisory Action (PTOL-303), dated Jun. 6, 2014, 4 Pages.
U.S. Appl. No. 13/030,084: Applicant Initiated Interview Summary (PTOL-413), dated Jul. 1, 2014, 3 Pages.
U.S. Appl. No. 13/030,084: Request for Continued Examination, dated Aug. 15, 2015, 26 Pages.
U.S. Appl. No. 13/229,624: Non-Final Rejection, dated Oct. 2, 2013, 9 pages.
U.S. Appl. No. 13/229,624: Response to non-final office action, dated Dec. 27, 2013, 11 pages.
U.S. Appl. No. 13/229,624: Non-Final Office Action, dated Apr. 4, 2014, 5 Pages.
U.S. Appl. No. 11/007,139: Reply Brief, mailed Oct. 22, 2012, 29 pages.
U.S. Appl. No. 11/007,139: Appeal Docketing Notice, dated Nov. 6, 2012, 2 pages.
U.S. Appl. No. 12/972,326: Preliminary amendment dated Jul. 5, 2011, 21 pages.
U.S. Appl. No. 12/578,411: Restriction requirement dated Jun. 8, 2011, 6 pages.
U.S. Appl. No. 12/578,411: Response to restriction requirement dated Jul. 6, 2011, 19 pages.
U.S. Appl. No. 12/578,411: Notice of Allowance, dated Aug. 19, 2013, 19 pages.
U.S. Appl. No. 12/578,411: Issue fee payment and Rule 312 amendment, dated Nov. 14, 2013, 14 pages.
U.S. Appl. No. 12/578,411: Examiner response to rule 312 amendment, dated Nov. 19, 2013, 2 pages.
U.S. Appl. No. 12/578,411: Response to Amendment under rule 312, dated Dec. 3, 2013, 3 pages.
U.S. Appl. No. 12/578,411: Issue notification, dated Dec. 18, 2013, 1 page.
U.S. Appl. No. 12/627,816: Notice of Allowance, dated Aug. 1, 2013, 16 pages.
U.S. Appl. No. 12/627,816: Issue fee payment and Rule 312 amendment, dated Nov. 1, 2013, 14 pages.
U.S. Appl. No. 12/627,816: Examiner response to rule 312 amendment, dated Nov. 13, 2013, 2 pages.
U.S. Appl. No. 12/627,816: Issue Notification, dated Nov. 26, 2013, 1 page.
U.S. Appl. No. 11/385,257: Final Rejection dated Jun. 1, 2011, 40 pages.
U.S. Appl. No. 11/385,257: Office communication concerning previous IDS filing, dated Oct. 4, 2012, 4 pages.
U.S. Appl. No. 11/385,257: Miscellaneous Communication to Applicant, dated Oct. 15, 2012, 3 pages.
U.S. Appl. No. 11/385,257: Rule 312 Amendment, dated Dec. 12, 2012, 10 pages.
U.S. Appl. No. 11/385,257: Issue Notification, dated Dec. 22, 2012, 1 page.
U.S. Appl. No. 13/625,812: Notice to file missing parts, dated Oct. 15, 2012, 6 pages.
U.S. Appl. No. 13/625,812: Response to Notice to file missing parts and preliminary amendment, dated Mar. 8, 2013, 47 pages.
U.S. Appl. No. 13/625,812: Notice of incomplete reply, dated Mar. 15, 2013, 3 pages.
U.S. Appl. No. 13/625,812: Response to incomplete reply notice, dated Apr. 2, 2013, 5 pages.
U.S. Appl. No. 13/625,812: Non-Final office action, dated Jul. 26, 2013, 29 pages.
U.S. Appl. No. 13/625,812: Publication notice, dated Aug. 1, 2013, 1 page.
U.S. Appl. No. 13/625,812: Response to non-final office action, dated Oct. 9, 2013, 15 pages.
U.S. Appl. No. 13/625,812: Final rejection, dated Dec. 3, 2013, 28 pages.
U.S. Appl. No. 13/625,812: Response After Final Action, dated Apr. 1, 2014, 1 Page.
U.S. Appl. No. 13/625,812: Advisory Action (PTOL-303), dated Apr. 9, 2014, 3 Pages.
U.S. Appl. No. 11/319,758: Non-Final office action dated Jun. 3, 2011, 31 pages.
U.S. Appl. No. 11/319,758: Issue Fee payment, Rule 312 and Miscellaneous Communication, dated Oct. 12, 2012, 12 pages.
U.S. Appl. No. 11/319,758: Issue Notification, dated Oct. 31, 2012, 1 page.
U.S. Appl. No. 12/613,450: Restriction requirement dated Jun. 10, 2011, 5 pages.
U.S. Appl. No. 12/613,450: Response to restriction requirement dated Jul. 6, 2011, 17 pages.
U.S. Appl. No. 12/613,450: Notice of Allowance, dated Oct. 7, 2013, 20 pages.
U.S. Appl. No. 12/613,450: Electronic Terminal Disclaimer filed and approved, Jan. 2, 2014, 2 pages.
U.S. Appl. No. 11/320,538: Non-Final Office Action dated Jun. 9, 2010, 24 pages.
U.S. Appl. No. 11/320,538: Non-Final Office Action, dated Dec. 19, 2012, 12 pages.
U.S. Appl. No. 11/320,538: Response to Non-final office action, dated Apr. 17, 2013, 20 pages.
U.S. Appl. No. 11/320,538: Notice of allowance, dated Aug. 1, 2013, 25 pages.
U.S. Appl. No. 11/320,538: Issue fee payment, mailed Nov. 1, 2013, 7 pages.
U.S. Appl. No. 11/320,538: Rule 312 amendment, dated Nov. 19, 2013, 20 pages.
U.S. Appl. No. 11/320,538: Issue Notification, dated Dec. 4, 2013, 1 page.
U.S. Appl. No. 12/702,243: Notice of Publication dated Aug. 12, 2010, 1 page.
U.S. Appl. No. 12/702,243: Amendment, dated Nov. 20, 2012, 14 pages.
U.S. Appl. No. 12/702,243: Terminal Disclaimer, mailed Jan. 2, 2013, 5 pages.
U.S. Appl. No. 12/702,243: Terminal Disclaimer decision, mailed Jan. 4, 2013, 1 page1.
U.S. Appl. No. 12/702,243: Notice of allowance and fees due and examiner interview summary, dated Jan. 10, 2013, pages.
U.S. Appl. No. 12/702,243: Issue notification, dated Apr. 24, 2013, 1 page.
U.S. Appl. No. 11/412,417: Issue Fee Payment and Comments on Reasons for Allowance dated Jan. 26, 2011, 6 pages.
U.S. Appl. No. 11/412,417: Issue Notification dated Feb. 9, 2011, 1 page.
U.S. Appl. No. 13/030,084: Amendment, dated Jan. 2, 2013, 40 pages.
U.S. Appl. No. 13/030,084: Refund request, dated Jan. 23, 2013 17 pages.
U.S. Appl. No. 13/030,084: Non-Final office action, dated Apr. 30, 2013, 39 pages.
U.S. Appl. No. 13/030,084: Response to non-final office action, dated Jul. 30, 2013, 28 pages.
U.S. Appl. No. 13/030,084: Non-final office action, dated Oct. 10, 2013, 44 pages.
U.S. Appl. No. 13/030,084: Response after Non-Final Reject, dated Jan. 2, 2014, 1 Page.
U.S. Appl. No. 13/030,084: Final Rejection, dated Mar. 19, 2014, 41 Pages.
Coenen, Frans; Leng, Paul and Ahmed, Shakil; “T-Trees, Vertical Partitioning and Distributed Association Rule Mining”, IEEE, 2003.
Borodin et al., “A Tradeoff Between Search and Update Time for the Implicit Dictionary Problem”, Theoretical Computer Science vol. 1 No. 4 (1990), 425-447.
Ferragina et al., “The String B-Tree: A New Data Structure for String Search in External Memory and Its Applications”, Journal of the ACM, vol. 46, No. 2, pp. 236-280, 1999.
Katajainen et al., “Tree Compression and Optimization with Applications”, International Journal of Foundations of Computer Science, vol. 1 No. 4 (1990), 425-447.
Prasad et al., “Efficient Bit-Parallel Multi-Patterns String Matching Algorithms for Limited Expression”, ACM, pp. 1-6, 2010.
Schmidt et al., “Comparision of Tree and Graph Encodings as Function of Problem Complexity”, ACM, pp. 1674-1679, 2007.
Sinha et al, “Efficient Trie Based Sorting of Large Sets of Strings,” ACM, pp. 1-8, 2003.
Spinells “Declarative Peephole Optimization Using String Pattern Matching”, ACM, pp. 47-51, 1999.
Thiemann, “Grammar-Based Analysis of String Expressions”, ACM, pp. 59-70, 2005.
Wagner et al., “The String-to-String Correction Problem”, Journal of the Association for Computing Machinery, vol. 21, No. 1, pp. 168-173, 1974.
Xie et al., “S-Looper: Automatice Summarization for Multipath String Loops”, ACM, pp. 188-198, 2015.
Yates et al, “A New Approach to Text Searchin”, Communications of the ACM, vol. 35, No. 1, pp. 74-82, 1992.
U.S. Appl. No. 13/229,624: Response and Amendments after Final, filed Jan. 30, 2015, 11 pages.
U.S. Appl. No. 13/229,624: Advisory Action, dated Mar. 11, 2015, 3 pages.
U.S. Appl. No. 13/229,624: Applicant Initiated Interview Summary, dated Mar. 19, 2015, 3 pages.
U.S. Appl. No. 13/229,624: Response After Final Action and Interview Summary, filed Mar. 27, 2015, 20 pages.
U.S. Appl. No. 13/229,624: RCE and Amendments, filed Apr. 27, 2015, 17 pages.
U.S. Appl. No. 13/229,624: Notice of Allowance and Fees, dated Jul. 6, 2015, 21 pages.
U.S. Appl. No. 13/229,624: Issue Fee Payment, dated Sep. 28, 2015, 1 page.
U.S. Appl. No. 13/229,624: Issue Notification, dated Oct. 14, 2015, 1 page.
U.S. Appl. No. 14/870,744, filed Sep. 30, 2015, 127 pages.
U.S. Appl. No. 14/870,744: Preliminary Amendments, dated Oct. 6, 2015, 10 pages.
U.S. Appl. No. 14/870,744: Notice to File Missing Parts, dated Oct. 16, 2015, 2 pages.
U.S. Appl. No. 14/870,744: Filing Receipt, Oct. 16, 2015, 3 pages.
U.S. Appl. No. 14/870,744: Applicant Response to Pre-Exam Formalities Notice, dated Feb. 19, 2016, 2 pages.
U.S. Appl. No. 14/870,744: Filing Receipt, Mar. 2, 2016, 3 pages.
U.S. Appl. No. 14/870,744: Notice of Publication, dated Jun. 9, 2016, 1 page.
U.S. Appl. No. 14/870,744: Non-Final Rejection, dated Aug. 24, 2017, 11 pages.
U.S. Appl. No. 11/007,139: Patent Board Decision, mailed Jul. 24, 2015, 8 pages.
U.S. Appl. No. 11/007,139: RCE, Sep. 18, 2015, 19 pages.
U.S. Appl. No. 11/007,139: Non-Final Rejection, dated Dec. 31, 2015, 10 pages.
U.S. Appl. No. 11/007,139: Amendment/Req. Reconsideration—After Non-Final Rejection, dated Mar. 28, 2016, 19 pages.
U.S. Appl. No. 11/007,139: Final Rejection, dated Jun. 20, 2016, 12 pages.
U.S. Appl. No. 11/007,139: Response After Final Action, dated Jul. 29, 2016, 17 pages.
U.S. Appl. No. 11/007,139: Notice of Allowance and Fees, dated Aug. 23, 2016, 10 pages.
U.S. Appl. No. 11/007,139: Filing Receipt, Sep. 2, 2016, 3 pages.
U.S. Appl. No. 11/007,139: RCE, Nov. 10, 2016, 3 pages.
U.S. Appl. No. 11/007,139: Notice of Allowance and Fees, dated Dec. 29, 2016, 8 pages.
U.S. Appl. No. 11/007,139: Issue Notification, dated Apr. 19, 2017, 1 page.
U.S. Appl. No. 15/043,267, filed Feb. 12, 2016, 92 pages.
U.S. Appl. No. 15/043,267: Preliminary Amendment, filed Feb. 12, 2016, 7 pages.
U.S. Appl. No. 15/043,267: Filing Receipt, Mar. 7, 2016, 3 pages.
U.S. Appl. No. 15/043,267: Preliminary Amendment, dated Jun. 10, 2016, 9 pages.
U.S. Appl. No. 15/043,267: Filing Receipt, Oct. 25, 2016, 3 pages.
U.S. Appl. No. 15/043,267: Notice of Publication, dated Feb. 2, 2017, 1 page.
U.S. Appl. No. 12/573,829 Non-Final Rejection and Examiner's Search, dated Apr. 28, 2015, 22 pages.
U.S. Appl. No. 12/573,829 Amendment/Req. Reconsideration After Non-Final Rejection, filed Jul. 27, 2015, 21 pages.
U.S. Appl. No. 12/573,829 Final Rejection and Examiner search, dated Sep. 15, 2015, 17 pages.
U.S. Appl. No. 12/573,829 Response After Final Action, dated Nov. 16, 2015, 17 pages.
U.S. Appl. No. 12/573,829 Advisory Action, dated Dec. 2, 2015, 4 pages.
U.S. Appl. No. 12/573,829 Request for Continued Examination and Amendments, dated Dec. 14, 2015, 17 pages.
U.S. Appl. No. 12/573,829: Non-Final Rejection, dated Jun. 13, 2016, 18 pages.
U.S. Appl. No. 12/573,829: Amendment/Req. Reconsideration-After Non-Final Reject, dated Sep. 13, 2016, 24 pages.
U.S. Appl. No. 12/573,829: Filing Receipt, Sep. 15, 2016, 3 pages.
U.S. Appl. No. 12/573,829: Non-Final Rejection, dated Dec. 16, 2016, 10 pages.
U.S. Appl. No. 12/573,829: Amendment/Req. Reconsideration-After Non-Final Reject, dated Mar. 16, 2017, 18 pages.
U.S. Appl. No. 12/573,829: Final Rejection, dated May 2, 2017, 20 pages.
U.S. Appl. No. 12/573,829: After Final Consideration Program Request, dated Jul. 5, 2017, 13 pages.
U.S. Appl. No. 12/573,829: Advisory Action/After Final Consideration Program Decision, dated Aug. 29, 2017, 5 pages.
U.S. Appl. No. 12/573,829: RCE and Amendments, dated Sep. 5, 2017, 24 pages.
U.S. Appl. No. 14/086,837: Examiner's search strategy and results, dated Dec. 2, 2014, 9 pages.
U.S. Appl. No. 14/086,837: Notice of Allowance and Fees, dated Dec. 2, 2014, 17 pages.
U.S. Appl. No. 14/086,837: Amendment After Notice of Allowance, filed Feb. 27, 2015, 9 pages.
U.S. Appl. No. 14/086,837: Issue Fee Payment, filed Feb. 27, 2015, 1 page.
U.S. Appl. No. 14/086,837: Issue Notification, dated May 6, 2015, 1 page.
U.S. Appl. No. 14/635,836, filed Mar. 2, 2015, 70 pages.
U.S. Appl. No. 14/635,836: Filing Receipt, mailed Mar. 12, 2015, 3 pages.
U.S. Appl. No. 14/635,836: Notice to File Missing Parts, dated Mar. 12, 2015, 2 pages.
U.S. Appl. No. 14/635,836: Applicant Response to Pre-Exam Formalities Notice, filed May 12, 2015, 40 pages.
U.S. Appl. No. 14/635,836: Filing Receipt, mailed May 19, 2015, 3 pages.
U.S. Appl. No. 14/635,836: Notice of Publication, dated Aug. 27, 2015, 1 page.
U.S. Appl. No. 14/635,836: Electronic Terminal Disclaimer Approved and Filed, Nov. 13, 2015, 3 pages.
U.S. Appl. No. 14/635,836: Notice of Allowance and Fees Due, dated Apr. 18, 2016, 25 pages.
U.S. Appl. No. 14/635,836: Issue Fee Payment and Amendment after NOA, dated Jul. 15, 2016, 15 pages.
U.S. Appl. No. 14/635,836: Response to Amendment under Rule 312, dated Jul. 21, 2016, 1 page.
U.S. Appl. No. 14/635,836: Response to Amendment under Rule 312, dated Jul. 22, 2016, 2 page.
U.S. Appl. No. 14/635,836: Issue Notification, dated Aug. 10, 2016, 1 page.
U.S. Appl. No. 15/250,118, filed Aug. 29, 2016, 71 pages.
U.S. Appl. No. 15/250,118: Preliminary Amendment, dated Aug. 29, 2016, 20 pages.
U.S. Appl. No. 15/250,118: Filing Receipt, Sep. 9, 2016, 3 pages.
U.S. Appl. No. 15/250,118: Applicant Response to Pre-Exam Formalities Notice, dated Nov. 8, 2016, 21 pages.
U.S. Appl. No. 15/250,118: Filing Receipt, Nov. 15, 2016, 3 pages.
U.S. Appl. No. 15/250,118: Notice of Publication, dated Feb. 23, 2017, 1 page.
U.S. Appl. No. 15/250,118: Non-Final Rejection, dated Jun. 15, 2017, 22 pages.
U.S. Appl. No. 15/250,118: Amendmet/Req. Reconsideration-After Non-Final Reject, dated Sep. 14, 2017, 44 pages.
U.S. Appl. No. 14/086,808: Examiner's search strategy and results, dated Nov. 17, 2014, 5 pages.
U.S. Appl. No. 14/086,808: Notice of Allowance and fees, dated Nov. 17, 2014, 16 pages.
U.S. Appl. No. 14/086,808: Issue Fee Payment and Rule 312 amendment, filed Feb. 17, 2015, 1 page.
U.S. Appl. No. 14/086,808: Amendment After Notice of Allowance, dated Feb. 17, 2015, 17 pages.
U.S. Appl. No. 14/086,808: Response to Amendment under Rule 312, dated Feb. 20, 2015, 2 pages.
U.S. Appl. No. 14/086,808: Response to Amendment under Rule 312, dated Feb. 25, 2015, 3 pages.
U.S. Appl. No. 14/086,808: Issue Notification, dated Mar. 18, 2015, 1 page.
U.S. Appl. No. 14/625,473, filed Feb. 18, 2015, 92 pages.
U.S. Appl. No. 14/625,473: Filing Receipt, mailed Mar. 18, 2015, 3 pages.
U.S. Appl. No. 14/625,473: Notice to File Missing Parts, dated Mar. 18, 2015.
U.S. Appl. No. 14/625,473: Response to Pre-Exam Formalities Notice and Preliminary Amendment, filed May 18, 2015, 28 pages.
U.S. Appl. No. 14/625,473: Filing Receipt, mailed May 20, 2015, 3 pages.
U.S. Appl. No. 14/625,473: Notice of Publication, dated Aug. 27, 2015, 1 page.
U.S. Appl. No. 14/625,473: Electronic Terminal Disclaimer Filed and Approved, Nov. 13, 2015, 3 pages.
U.S. Appl. No. 14/625,473: Notice of Allowance, dated Mar. 28, 2016, 19 pages.
U.S. Appl. No. 14/625,473: Issue Fee Payment and Amendments after Notice of Allowance, dated Jun. 28, 2016, 24 pages.
U.S. Appl. No. 14/625,473: Response to Amendment under Rule 312, dated Jun. 30, 2016, 1 page.
U.S. Appl. No. 14/625,473: Issue Notification, dated Jul. 20, 2016, 1 page.
U.S. Appl. No. 15/214,168: Application as filed with preliminary amendments, dated Jul. 19, 2016, 116 pages.
U.S. Appl. No. 15/214,168: Filing Receipt, Aug. 3, 2016, 4 pages.
U.S. Appl. No. 15/214,168: Corrected Filing Receipt, Oct. 12, 2016, 4 pages.
U.S. Appl. No. 15/214,168: Notice of Publication, dated Nov. 10, 2016, 1 page.
U.S. Appl. No. 15/214,168: Non-Final Rejection, dated Mar. 2, 2017, 20 pages.
U.S. Appl. No. 15/214,168: Amendment/Req. Reconsideration-After Non-Final Reject, dated Jun. 2, 2017, 39 pages.
U.S. Appl. No. 15/214,168: Terminal Disclaimer, Jul. 17, 2017, 4 pages.
U.S. Appl. No. 15/214,168: Notice of Allowance and Fees Due, dated Aug. 1, 2017, 26 pages.
U.S. Appl. No. 13/625,812: Notice of Allowance and Fees, dated Dec. 9, 2014, 20 pages.
U.S. Appl. No. 13/625,812: Filing Receipt, mailed Feb. 2, 2015, 3 pages.
U.S. Appl. No. 13/625,812: Filing Receipt, mailed Feb. 6, 2015, 3 pages.
U.S. Appl. No. 13/625,812: Terminal Disclaimer Filed Mar. 2, 2015, 1 page.
U.S. Appl. No. 13/625,812: Post Allowance Arguments/Amendments, filed Mar. 6, 2015, 6 pages.
U.S. Appl. No. 13/625,812: Amendment After Notice of Allowance, filed Mar. 9, 2015, 3 pages.
U.S. Appl. No. 13/625,812: Issue Fee Payment, filed Mar. 9, 2015, 1 page.
U.S. Appl. No. 13/625,812: Terminal Disclaimer Review Decision, mailed Mar. 12, 2015.
U.S. Appl. No. 14/641,735, filed Mar. 9, 2015, 126 pages.
U.S. Appl. No. 14/641,735: Filing Receipt, mailed Mar. 20, 2015, 3 pages.
U.S. Appl. No. 14/641,735: Notice to File Missing Parts, dated Mar. 20, 2015, 2 pages.
U.S. Appl. No. 14/641,735: Notice of Incomplete Reply, dated Jun. 26, 2015, 2 pages.
U.S. Appl. No. 14/641,735: Applicant Response to Pre-Exam Formalities Notice and Amendments, filed Jul. 8, 2015, 32 pages.
U.S. Appl. No. 14/641,735: Electronic Terminal Disclaimer, filed Aug. 27, 2015, 3 pages.
U.S. Appl. No. 14/641,735: Notice of Publication, dated Oct. 29, 2015, 1 page.
U.S. Appl. No. 14/641,735: Preliminary Amendment, dated Jan. 14, 2016, 8 pages.
U.S. Appl. No. 14/641,735: Non-Final Rejection, dated Jul. 14, 2017, 14 pages.
U.S. Appl. No. 14/641,735: Letter Restarting Period for Response, dated Aug. 24, 2017, 22 pages.
U.S. Appl. No. 13/632,581: Non-Final Rejection, dated Jan. 27, 2015, 16 pages.
U.S. Appl. No. 13/632,581: Amendment/Req Reconsideration Non-Final Rejection and Amendments, filed Apr. 20, 2015, 24 pages.
U.S. Appl. No. 13/632,581: Final Rejection, dated Jul. 20, 2015, 21 pages.
U.S. Appl. No. 13/632,581: After Final Consideration Request and Response, dated Sep. 21, 2015, 28 pages.
U.S. Appl. No. 13/632,581: Advisory Action and After Final Decision, dated Oct. 2, 2015, 18 pages.
U.S. Appl. No. 13/632,581: RCE and Amendments, dated Nov. 30, 2015, 55 pages.
U.S. Appl. No. 13/632,581: Notice of Allowance and Fees, dated Dec. 17, 2015, 5 pages.
U.S. Appl. No. 13/632,581: Filing Receipt, Jan. 22, 2016, 4 pages.
U.S. Appl. No. 13/632,581: Electronic Terminal Disclaimer, Mar. 7, 2016, 3 pages.
U.S. Appl. No. 13/632,581: Issue Fee Payment, Mar. 16, 2016, 1 page.
U.S. Appl. No. 13/632,581: Amendment after Notice of Allowance, dated Mar. 16, 2016 19 pages.
U.S. Appl. No. 13/632,581: Response to Amendment under Rule 312, dated Mar. 22, 2016, 2 pages.
U.S. Appl. No. 13/632,581: Issue Notification, dated Apr. 13, 2016, 1 page.
U.S. Appl. No. 15/081,612, filed Mar. 25, 2016, 87 Pages.
U.S. Appl. No. 15/081,612: Notice to File Missing Parts and Filing Receipt, dated Apr. 11, 2016, 4 Pages.
U.S. Appl. No. 15/081,612: Filing Receipt, Apr. 11, 2016, 3 Pages.
U.S. Appl. No. 15/081,612: Applicant Response to Pre-Exam Formalities Notice and Preliminary Amendments, dated Jun. 13, 2016, 34 pages.
U.S. Appl. No. 15/081,612: Preliminary Amendment, dated Jun. 14, 2016, 4 pages.
U.S. Appl. No. 15/081,612: Filing Receipt, Jun. 21, 2016, 3 pages.
U.S. Appl. No. 15/081,612: Non-Final Rejection, dated Jul. 27, 2016, 9 pages.
U.S. Appl. No. 15/081,612: Electronic Terminal Disclaimer, Sep. 23, 2016, 3 pages.
U.S. Appl. No. 15/081,612: Notice of Publication, dated Sep. 29, 2016, 1 page.
U.S. Appl. No. 15/081,612: Amendment/Req. Reconsideration-After Non-Final Reject, dated Oct. 17, 2016, 10 pages.
U.S. Appl. No. 15/081,612: Notice of Allowance and Fees, dated Oct. 27, 2016, 5 pages.
U.S. Appl. No. 15/081,612: RCE, Jan. 30, 2017, 2 pages.
U.S. Appl. No. 15/081,612: Issue Fee Payment, Jan. 30, 2017, 1 page.
U.S. Appl. No. 15/081,612: Notice of Allowance and Fees Due, dated Jan. 30, 2017, 2 pages.
U.S. Appl. No. 15/081,612: Notice of Allowance and Fees Due, dated Feb. 13, 2017, 7 pages.
U.S. Appl. No. 15/081,612: Amendment After Notice of Allowance, dated Mar. 20, 2017, 4 pages.
U.S. Appl. No. 15/081,612: Issue Fee Payment, Mar. 20, 2017, 1 page.
U.S. Appl. No. 15/081,612: Issue Notification, dated Apr. 20, 2017, 1 page.
U.S. Appl. No. 14/149,749: Notice of Publication, dated Dec. 11, 2014, 1 page.
U.S. Appl. No. 14/149,749: Electronic Terminal Disclaimer Filed and Approved Feb. 23, 2015.
U.S. Appl. No. 14/149,749: Examiner Initiated Interview Summary, dated Feb. 24, 2015, 2 pages.
U.S. Appl. No. 14/149,749: Notice of Allowance and Fees and Examiner Search, dated Apr. 17, 2015, 30 pages.
U.S. Appl. No. 14/149,749: Amendment after Notice of Allowance, filed May 27, 2015, 10 pages.
U.S. Appl. No. 14/149,749: Issue Fee Payment, filed May 27, 2015, 1 page.
U.S. Appl. No. 14/149,749: Electronic Terminal Disclaimer Filed and Approved, May 27, 2015, 3 pages.
U.S. Appl. No. 14/149,749: Response to Amendment under Rule 312, dated May 29, 2015, 1 page.
U.S. Appl. No. 14/149,749: Response to Amendment under Rule 312, dated Jun. 1, 2015, 3 pages.
U.S. Appl. No. 14/149,749: Issue Notification, dated Jun. 17, 2015, 1 page.
U.S. Appl. No. 14/726,192, filed May 29, 2015, 39 pages.
U.S. Appl. No. 14/726,192: Filing Receipt, mailed Jun. 9, 2015, 3 pages.
U.S. Appl. No. 14/726,192: Notice to File Missing Parts, dated Jun. 9, 2015, 2 pages.
U.S. Appl. No. 14/726,192: Applicant Response to Pre-Exam Formalities Notice and Amendments, filed Aug. 12, 2015, 114 pages.
U.S. Appl. No. 14/726,192: Filing Receipt, mailed Aug. 20, 2015, 3 pages.
U.S. Appl. No. 14/726,192: Electronic Terminal Disclaimer Filed and Approved, Nov. 20, 2015, 3 pages.
U.S. Appl. No. 14/726,192: Notice of Publication, dated Nov. 27, 2015, 1 page.
U.S. Appl. No. 14/726,192: Issue Fee Payment and Amendment after Notice of Allowance, dated Jul. 18, 2016, 13 pages.
U.S. Appl. No. 14/726,192: Response to Amendment under Rule 312, dated Jul. 21, 2016, 1 page.
U.S. Appl. No. 14/726,192: Response to Amendment under Rule 312, dated Jul. 22, 2016, 2 pages.
U.S. Appl. No. 14/726,192: Issue Notification, dated Aug. 3, 2016, 1 page.
U.S. Appl. No. 15/240,964: Application and Preliminary Amendments as filed Aug. 18, 2016, 70 pages.
U.S. Appl. No. 15/240,964: Filing Receipt, Aug. 31, 2016, 3 pages.
U.S. Appl. No. 15/240,964: Notice of Publication, dated Dec. 8, 2016.
U.S. Appl. No. 15/240,964: Non-Final Rejection, dated Mar. 14, 2017, 23 pages.
U.S. Appl. No. 15/240,964: Amendment/Req. Reconsideration-After Non-Final Reject, dated Jun. 14, 2017, 27 pages.
U.S. Appl. No. 15/240,964: Final Rejection, dated Aug. 9, 2017, 25 pages.
U.S. Appl. No. 15/240,964: After Final Consideration Program Request, Oct. 10, 2017, 30 pages.
U.S. Appl. No. 15/240,964: Advisory Action, dated Oct. 30, 2017, 3 pages.
U.S. Appl. No. 14/086,741: Amendment after Notice of Allowance, filed Jan. 5, 2015, 14 pages.
U.S. Appl. No. 14/086,741: Issue Fee Payment, filed Jan. 5, 2015, 1 page.
U.S. Appl. No. 14/086,741: Response to Amendment under Rule 312, dated Jan. 22, 2015, 2 pages.
U.S. Appl. No. 14/086,741: Notice of Allowance and Fees and Examiner Search strategy, dated Mar. 16, 2015, 40 pages.
U.S. Appl. No. 14/086,741: Issue Notification, dated Apr. 1, 2015, 1 page.
U.S. Appl. No. 14/596,154, filed Jan. 13, 2015, 60 pages.
U.S. Appl. No. 14/596,154: Filing Receipt, mailed Jan. 27, 2015, 3 pages.
U.S. Appl. No. 14/596,154: Notice to File Missing Parts, dated Jan. 27, 2015, 3 pages.
U.S. Appl. No. 14/596,154: Applicant Response to Pre Exam Formalities Notice with Preliminary Amendments, filed Mar. 27, 2015, 85 pages.
U.S. Appl. No. 14/596,154: Filing Receipt, mailed Apr. 2, 2015, 3 pages.
U.S. Appl. No. 14/596,154: Notice of Publication, dated Jul. 9, 2015, 1 page.
U.S. Appl. No. 14/596,154: Electronic Terminal Disclaimer Filed and Approved, Nov. 20, 2015, 3 pages.
U.S. Appl. No. 14/596,154: Non-Final Rejection, dated Sep. 21, 2017, 19 pages.
U.S. Appl. No. 13/860,482: Issue Fee Payment and Rule 312 Amendments, filed Feb. 4, 2015, 4 pages.
U.S. Appl. No. 13/860,482: Issue Notification, dated Mar. 4, 2015, 1 page.
U.S. Appl. No. 14/614,292, filed Feb. 4, 2015, 76 pages.
U.S. Appl. No. 14/614,292: Notice to File Missing Parts and Filing Receipt, dated Feb. 20, 2015, 5 pages.
U.S. Appl. No. 14/614,292: Applicant Response to Pre-Exam Formalities Notice and Amendments, filed Apr. 17, 2015, 30 pages.
U.S. Appl. No. 14/614,292: Filing Receipt, mailed Apr. 24, 2015, 3 pages.
U.S. Appl. No. 14/614,292: Notice of Publication, dated Aug. 6, 2015, 1 page.
U.S. Appl. No. 14/614,292: Electronic Terminal Disclaimer Filed and Approved, Nov. 20, 2015, 3 pages.
U.S. Appl. No. 14/614,292: Non-Final Rejection, dated May 19, 2016, 10 pages.
U.S. Appl. No. 14/614,292: Amendment/Req. Reconsideration-After Non-Final Rejection, dated Aug. 18, 2016, 20 pages.
U.S. Appl. No. 14/614,292: Notice of Allowance and Fees, dated Sep. 21, 2016, 8 pages.
U.S. Appl. No. 14/614,292: Issue Fee Payment and Amendment after Notice of Allowance, dated Dec. 21, 2014, 4 pages.
U.S. Appl. No. 14/614,292: Issue Notification, dated Jan. 18, 2017, 1 page.
U.S. Appl. No. 15/411,823, filed Jan. 20, 2017, 77 pages.
U.S. Appl. No. 15/411,823: Preliminary Amendment, dated Jan. 20, 2017, 25 pages.
U.S. Appl. No. 15/411,823: Filing Receipt, Jan. 31, 2017, 3 pages.
U.S. Appl. No. 15/411,823: Notice of Publication, dated May 11, 2017, 1 page.
U.S. Appl. No. 13/030,084: Non-Final Rejection and Examiner's Search, dated Mar. 24, 2015, 24 pages.
U.S. Appl. No. 13/030,084: Amendment/Req. Reconsideration After Non-Final Rejection, filed Jun. 24, 2015, 28 pages.
U.S. Appl. No. 13/030,084: Terminal Disclaimer filed and Approved, Sep. 10, 2015, 3 pages.
U.S. Appl. No. 13/030,084: Notice of Allowance and Fees, dated Sep. 17, 2015, 24 pages.
U.S. Appl. No. 13/030,084: Issue Fee Payment and Amendment, dated Dec. 10, 2015, 4 pages.
U.S. Appl. No. 14/968,429, filed Dec. 14, 2015.
U.S. Appl. No. 14/968,429: Filing Receipt, Jan. 4, 2016, 3 pages.
U.S. Appl. No. 14/968,429: Applicant Response to Pre-Exam Formalities Notice, dated Jan. 14, 2016, 35 pages.
U.S. Appl. No. 14/968,429: Filing Receipt, Jan. 21, 2016, 3 pages.
U.S. Appl. No. 14/968,429: Notice of Publication, dated Apr. 28, 2016, 1 page.
U.S. Appl. No. 14/968,429: Non-Final Rejection, dated May 15, 2017, 8 pages.
U.S. Appl. No. 14/968,429: Amendment/Req. Reconsideration-After Non-Final Reject, dated Aug. 9, 2017, 19 pages.
U.S. Appl. No. 14/968,429: Final Rejection, dated Oct. 24, 2017, 10 pages.
Boppana et al., “Full Fault Dictionary Storage Based on Labeled Tree Encoding”, Proceedings of 14th VLSI Test Symposium, 1996, pp. 174-179.
U.S. Appl. No. 14/870,744: Final Rejection, dated Mar. 30, 2018, 20 pages.
U.S. Appl. No. 12/573,829: Amendment/Req. Reconsideration-After Non-Final Reject, dated Mar. 27, 2018, 22 pages.
U.S. Appl. No. 15/250,118: RCE and Amendments, dated Apr. 16, 2018, 44 pages.
U.S. Appl. No. 15/802,348: Notice of Publication, dated Apr. 19, 2018, 1 page.
U.S. Appl. No. 14/641,735: Final Rejection, dated Mar. 15, 2018, 25 pages.
U.S. Appl. No. 14/641,735: Response After Final Action, dated May 15, 2018, 28 pages.
U.S. Appl. No. 14/596,154: Notice of Allowance and Fees Due, dated May 2, 2018, 8 pages.
U.S. Appl. No. 15/411,823: Amendment/Req. Reconsideration-After Non-Final Rejection, dated Apr. 24, 2018, 18 pages.
U.S. Appl. No. 15/411,823: Terminal Disclaimer-Filed and Approved, Apr. 24, 2018, 3 pages.
U.S. Appl. No. 14/968,429: Terminal Disclaimer-Filed and Approved, Feb. 7, 2018, 3 pages.
U.S. Appl. No. 14/968,429: Response After Final Action, dated Feb. 7, 2018, 13 pages.
U.S. Appl. No. 14/968,429: Notice of Allowance and Fees Due, dated Feb. 26, 2018, 8 pages.
U.S. Appl. No. 14/968,429: Notice of Allowance and Fees Due, dated Mar. 19, 2018, 6 pages.
Caviness et al, “Simplification of Radical Expressions”, ACM, pp. 329-338, 1976.
Hirschberg, “Algorithm for Computing Maximal Common Sebsequences”, Communicatoin of the ACM, vol. 18, No. 6, pp. 341-343, 1975.
Siegel, “All Searches Are Divided into Three Parts String Searches Using Ternary Trees”, ACM, pp. 57-68, 1988.
U.S. Appl. No. 14/870,744: Amendment/Req. Reconsideration-After Non-Final Reject, dated Nov. 24, 2017, 30 pages.
U.S. Appl. No. 12/573,829: Non-Final Rejection, dated Dec. 27, 2017, 13 pages.
U.S. Appl. No. 15/250,118: Final Rejection, dated Dec. 15, 2017, 25 pages.
U.S. Appl. No. 15/214,168: Amendment after Notice of Allowance, dated Nov. 1, 2017, 22 pages.
U.S. Appl. No. 15/214,168: Issue Notification, dated Nov. 21, 2017, 1 page.
U.S. Appl. No. 15/802,348: Applicant Response to Pre-Exam Formalities Notice, dated Jan. 9, 2018, 17 pages.
U.S. Appl. No. 15/802,348: Filing Receipt, Jan. 11, 2018, 4 pages.
U.S. Appl. No. 14/641,735: Amendment/Req. Reconsideration-After Non-Final Reject, dated Nov. 24, 2017, 28 pages.
U.S. Appl. No. 15/240,964: RCE and Amendments, dated Nov. 9, 2017, 31 pages.
U.S. Appl. No. 14/596,154: Amendment/Req. Reconsideration-After Non-Final Reject, dated Dec. 21, 2017, 37 pages.
U.S. Appl. No. 15/411,823: Non-Final Rejection, dated Jan. 25, 2018, 10 pages.
U.S. Appl. No. 14/968,429: Response After Final Action, dated Dec. 26, 2017, 28 pages.
U.S. Appl. No. 14/968,429: Advisory Action, dated Jan. 11, 2018, 5 pages.
U.S. Appl. No. 14/870,744: Advisory Action, dated Jul. 3, 2018, 5 pages.
U.S. Appl. No. 14/870,744: RCE and Amendments, dated Jul. 27, 2018, 33 pages.
U.S. Appl. No. 14/870,744: Notice of Allowance and Fees Due, dated Sep. 6, 2018, 11 pages.
U.S. Appl. No. 12/573,829: Final Rejection, dated Jul. 11, 2018, 15 pages.
U.S. Appl. No. 12/573,829: After Final Consideration Program Request, Sep. 7, 2018, 23 pages.
U.S. Appl. No. 14/641,735: Internet Communications Authorized, dated Jun. 23, 2018, 2 pages.
U.S. Appl. No. 14/641,735: RCE and Amendments, dated Jul. 16, 2018, 34 pages.
U.S. Appl. No. 15/240,964: Non-Final Rejection, dated Jul. 30, 2018, 32 pages.
U.S. Appl. No. 14/596,154: Issue Notification, dated Aug. 21, 2018, 1 page.
U.S. Appl. No. 16/048,119, filed Jul. 27, 2018, 81 pages.
U.S. Appl. No. 16/048,119: Filing Receipt, Aug. 24, 2018, 3 pages.
U.S. Appl. No. 16/048,119: Notice to File Missing Parts, dated Aug. 24, 2018, 2 pages.
U.S. Appl. No. 15/411,823: Notice of Allowance and Fees Due, dated Jul. 13, 2018, 8 pages.
U.S. Appl. No. 14/968,429: Response to Amendment under Rule 312, dated Jul. 10, 2018, 2 pages.
U.S. Appl. No. 14/968,429: Response to Amendment under Rule 312, dated Jul. 23, 2018, 2 pages.
U.S. Appl. No. 14/968,429: Issue Notification, dated Aug. 1, 2018, 1 page.
U.S. Appl. No. 16/048,061, filed Jul. 27, 2018, 101 pages.
U.S. Appl. No. 16/048,061: Notice to File Missing Parts, dated Aug. 13, 2018, 2 pages.
U.S. Appl. No. 16/048,061: Filing Receipt, Aug. 13, 2018, 4 pages.
U.S. Appl. No. 16/209,872, filed Dec. 4, 2018, 129 pages.
U.S. Appl. No. 16/209,872: Notice to File Missing Parts, dated Dec. 28, 2018, 2 pages.
U.S. Appl. No. 16/209,872: Filing Receipt, Dec. 28, 2018, 3 pages.
U.S. Appl. No. 12/573,829: Advisory Action, dated Sep. 24, 2018, 4 pages.
U.S. Appl. No. 12/573,829: RCE and Amendments, dated Oct. 9, 2018, 20 pages.
U.S. Appl. No. 15/250,118: Terminal Disclaimer, Dec. 11, 2018, 4 pages.
U.S. Appl. No. 15/250,118: Notice of Allowance and Fees Due, dated Jan. 8, 2019, 32 pages.
U.S. Appl. No. 15/250,118: Amendment after Notice of Allowance, dated Jan. 23, 2019, 18 pages.
U.S. Appl. No. 15/802,348: Preliminary Amendment, dated Oct. 26, 2018, 24 pages.
U.S. Appl. No. 14/641,735: Preliminary Amendment, dated Oct. 26, 2018, 10 pages.
U.S. Appl. No. 14/641,735: Non-Final Rejection, dated Nov. 2, 2018, 28 pages.
U.S. Appl. No. 15/240,964: Amendment/Req. Reconsideration-After Non-Final Reject, dated Oct. 30, 2018, 43 pages.
U.S. Appl. No. 16/048,113: Applicant Response to Pre-Exam Formalities Notice and Amendment, dated Oct. 22, 2018, 38 pages.
U.S. Appl. No. 16/048,113: Filing Receipt, Oct. 24, 2018, 3 pages.
U.S. Appl. No. 15/411,823: Issue Notification, dated Nov. 7, 2018, 1 page.
U.S. Appl. No. 16/164,430, filed Oct. 18, 2018, 79 pages.
U.S. Appl. No. 16/164,430: Notice to File Missing Parts, dated Nov. 6, 2018, 2 pages.
U.S. Appl. No. 16/164,430: Filing Receipt, Nov. 6, 2018, 4 pages.
U.S. Appl. No. 16/164,430: Applicant Response to Pre-Exam Formalities Notice, dated Jan. 18, 2019, 29 pages.
U.S. Appl. No. 16/164,430: Filing Receipt, Jan. 23, 2019, 4 pages.
U.S. Appl. No. 16/048,061: Applicant Response to Pre-Exam Formalities Notice, dated Oct. 12, 2018, 13 pages.
U.S. Appl. No. 16/048,061: Filing Receipt, Oct. 16, 2018, 4 pages.
U.S. Appl. No. 16/048,061: Request for Corrected Filing Receipt, Oct. 31, 2018, 6 pages.
U.S. Appl. No. 16/048,061: Filing Receipt, Nov. 5, 2018, 4 pages.
U.S. Appl. No. 16/164,535, filed Oct. 18, 2018, 115 pages.
U.S. Appl. No. 16/164,535: Filing Receipt, Nov. 7, 2018, 4 pages.
U.S. Appl. No. 16/164,535: Notice to File Corrected Application Papers, dated Nov. 7, 2018, 2 pages.
U.S. Appl. No. 16/164,535: Applicant Response to Pre-Exam Formalities Notice, dated Jan. 7, 2019, 23 pages.
U.S. Appl. No. 16/164,535: Filing Receipt, Jan. 11, 2019, 4 pages.
U.S. Appl. No. 14/870,744, Corrected Notice of Allowability, dated Mar. 12, 2019, 7 pages.
U.S. Appl. No. 14/870,744, Issue Notification, dated Mar. 20, 2019, 1 page.
U.S. Appl. No. 15/043,267, Non-Final Rejection, dated Apr. 2, 2019, 21 pages.
U.S. Appl. No. 15/250,118, Issue Fee Payment, dated Apr. 5, 2019, 20 pages.
U.S. Appl. No. 16/379,674, Application as filed Apr. 9, 2019, 85 pages.
U.S. Appl. No. 16/379,674, Filing Receipt Apr. 24, 2019, 4 pages.
U.S. Appl. No. 15/802,348, Amendment/Req. Reconsideration-After Non-Final Reject, dated May 13, 2019, 22 pages.
U.S. Appl. No. 14/641,735, Notice of Allowance and Fees Due, dated Apr. 15, 2019, 23 pages.
U.S. Appl. No. 16/164,430, Notice of Publication, May 2, 2019, 1 page.
U.S. Appl. No. 16/209,872, Applicant Response to Pre-Exam Formalities Notice, dated Feb. 21, 2019, 17 pages.
U.S. Appl. No. 16/209,872, Filing Receipt Feb. 26, 2019, 3 pages.
U.S. Appl. No. 15/802,348, Non-Final Rejection, Feb. 11, 2019, 18 pages.
U.S. Appl. No. 14/641,735, Amendment/Req. Reconsideration-After Non-Final Reject, dated Feb. 4, 2019, 27 pages.
U.S. Appl. No. 15/464,205, Preliminary Amendment, dated Feb. 22, 2019, 11 pages.
U.S. Appl. No. 15/240,964, Notice of Allowance and Fees Due, dated Feb. 21, 2019, 29 pages.
U.S. Appl. No. 16/048,113, Notice of Publication, dated Jan. 31, 2019, 1 page.
Related Publications (1)
Number Date Country
20100318521 A1 Dec 2010 US
Provisional Applications (1)
Number Date Country
60623352 Oct 2004 US
Divisions (1)
Number Date Country
Parent 11006446 Dec 2004 US
Child 12830236 US