In computing, a rose tree is a term for the value of a tree data structure with a variable and unbounded number of branches per node.[1] The term is mostly used in the functional programming community, e.g., in the context of the Bird–Meertens formalism.[2] Apart from the multi-branching property, the most essential characteristic of rose trees is the coincidence of bisimilarity with identity: two distinct rose trees are never bisimilar.
The name "rose tree" was coined by Lambert Meertens to evoke the similarly named, and similarly structured, common rhododendron.[3]
We shall call such trees rose trees, a literal translation of rhododendron (Greek Greek, Ancient (to 1453);: ῥόδον = rose, Greek, Ancient (to 1453);: δένδρον = tree), because of resemblance to the habitus of this shrub, except that the latter does not grow upside-down on the Northern hemisphere.
Well-founded rose trees can be defined by a recursive construction of entities of the following types:
A base entity is an element of a predefined ground set of values (the "tip"-values[3]).
A branching entity (alternatively, a forking entity or a forest entity) is either of the following sub-types:
N
Typically, only some combinations of entity types are used for the construction. The original paper[3] only considers 1+2b ("sequence-forking" rose trees) and 1+2a ("set-forking" rose trees).In later literature, the 1+2b variant is usually introduced by the following definition:
lang="haskell" style="float:left;padding:.1em; margin:.5em;">data Tree a = Leaf a | Node [Tree a]
A rose tree [...] is either aleaf containing a value, or a node that can have an arbitrary list of subtrees
.[4]
The most common definition used in functional programming (particularly in Haskell) combines 3+2b:
lang="haskell" style="float:left;padding:.1em; margin:.5em;">data Rose α = Node α [Rose α]
An element of Rose α consists of a labelled node together with a list of subtrees
.[1] That is, a rose tree is a pairing entity (type 3) whose branching entity is a sequence (thus of type 2b) of rose trees.
Sometimes even the combination 1+3b is considered.[5] [6] The following table provides a summary of the most established combinations of entities.
| Terminology | Entities used | |
|---|---|---|
| Well-founded set | (2a) | |
| Well-founded nested list value | (2b)(1) | |
| Well-founded nested dictionary value | (2c)(1) | |
| Well-founded nested data value | (2b)(2c)(1) | |
| An -name as known from forcing | (2a)(3) | |
| Well-founded rose tree in the most common sense | (3)(2b) |
Notes:
General rose trees can be defined via bisimilarity of accessible pointed multidigraphs with appropriate labelling of nodes and arrows.These structures are generalization of the notion of accessible pointed graph (abbreviated as apg) from non-well-founded set theory.We will use the apq acronym for the below described multidigraph structures. This is meant as an abbreviation of "accessible pointed quiver" where quiver is an established synonym for "multidigraph".
In a correspondence to the types of entities used in the recursive definition, each node of an apq is assigned a type (1), (2a), (2b), (2c) or (3).The apqs are subject to conditions that mimic the properties of recursively constructed entities.
N
N
A bisimilarity between apqs and is a relation between nodes such thatthe roots of and are -related andfor every pair of -related nodes, the following are satisfied:
A symmetric condition is satisfied with and interchanged.
Two apqs and are said to be bisimilar if there exists a bisimilarity relation for them. This establishes an equivalence relation on the class of all apqs.
A rose tree is then some fixed representation of the class of apqs that are bisimilar to some given apq .If the root node of is of type (1) then, thus can be represented by this root node. Otherwise, is a proper class – in this case the representation can be provided by Scott's trick to be the set of those elements of that have the lowest rank.
As a result of the above set-theoretic construction, the class of all rose trees is defined, depending on the sets (ground values), (arrow names) and (node labels) as the definitory constituents.Subsequently, the structure of apqs can be carried over to a labelled multidigraph structure over . That is, elements of can themselves be considered as "nodes" with induced type assignment, node labelling and arrows. The class of arrows is a subclass of, that is, arrows are either source-target couples or source-label-target triples according to the type of the source.
For every element of there is an induced apq such that is the root node of and the respective sets and of nodes and arrows of are formed by those elements of and that are accessible via a path of arrows starting at . The induced apq is bisimilar to apqs used for the construction of .
Rose trees that do not contain set-branching nodes (type 2a) can be represented by pathname maps.A pathname is just a finite sequence of arrow labels. For an arrow path (a finite sequence of consecutive arrows), the pathname of is the corresponding sequence of arrow labels.Here it is assumed that each arrow is labelled (denotes the labelling function). In general, each arrow path needs to be first reduced by removing all its arrows sourced at pairing nodes (type 3).
A pathname is resolvable iff there exists a root-originating arrow path whose pathname is . Such is uniquely given up to a possible unlabelled last arrow (sourced at a pairing node).The target node of a non-empty resolvable path is the target node of the last arrow of the correspondent root-originating arrow path that does not end with an unlabelled arrow.The target of the empty path is the root node.
Given a rose tree that does not contain set-branching nodes, the pathname map of is a map that assigns each resolvable pathname its value according to the following general scheme:
Recall that is the set of arrow labels (
N
| if is of type (1), | |||
| or | if is of respective type (2b) or (2c), | ||
| or | if is of respective type (3b) or (3c) and is the label of . |
It can be shown that different rose trees have different pathname maps. For "homogeneous" rose trees there is no need for type tagging, and their pathname map can be defined as summarized below:
|-|Nested dictionary value||-|Rose tree by Haskell, tree over [7] [8] ||-|-valued tree,[9] tree labelled in [10] ||}
In each case, there is a simple axiomatization in terms of pathnames:
In particular, a rose tree in the most common "Haskell" sense is just a map from a non-empty prefix-closed and left-sibling-closed set of finite sequences of natural numbers to a set .Such a definition is mostly used outside the branch of functional programming, see Tree (automata theory).Typically, documents that use this definition do not mention the term "rose tree" at all.
Notes:
The diagrams below show two examples of rose trees together with the correspondent Haskell code. In both cases, the Data.Tree module[11] is used as it is provided by the Haskell containers package.[12] The module introduces rose trees as pairing entities by the following definition:
Both examples are contrived so as to demonstrate the concept of "sharing of substructures"[13] which is a distinguished feature of rose trees.In both cases, the labelling function is injective (so that the labels 'a', 'b', 'c' or 'd' uniquely identify a subtree / node) which does not need to be satisfied in general.The natural numbers (0,1,2 or 3) along the arrows indicate the zero-based position in which a tree appears in the subForest sequence of a particular "super-tree".As a consequence of possible repetitions in subForest, there can be multiple arrows between nodes.In each of the examples, the rose tree in question is labelled by 'a' and equals the value of the a variable in the code. In both diagrams, the tree is pointed to by a source-less arrow.
Well-founded rose tree
Non-well-founded rose tree
The first example presents a well-founded rose tree a obtained by an incremental construction. First d is constructed, then c then b and finally a. The rose tree can be represented by the pathname map shown on the left.
The second example presents a non-well-founded rose tree a built by a breadth-first constructor unfoldTree. The rose tree is a Moore machine, see notes above. Its pathname map is defined by be respectively equal to or or according to where is the number of occurrences of in .
The general definition provides a connection to tree data structures:
Rose trees are tree structures modulo bisimilarity.
Mapping tree data structures to their values
The "tree structures" are those apqs (labelled multidigraphs from the general definition) in which each node is accessible by a unique arrow path.Every rose tree is bisimilar to such a tree structure (since every apq is bisimilar to its unfolding) and every such tree structure is bisimilar to exactly one rose tree which can therefore be regarded as the value of the tree structure.
The diagram on the right shows an example of such a structure-to-value mapping. In the upper part of the diagram, a node-labelled ordered tree is displayed, containing 23 nodes. In the lower part, a rose tree is shown that is the value of .(In both and, sibling arrows are implicitly ordered from left to right.)There is an induced subtree-to-subvalue mapping which is partially displayed by blue arrows.
Observe that the mapping is many-to-one: distinct tree data structures can have the same value. As a particular consequence, a rose tree in general is not a tree in terms of "subvalue" relationship between its subvalues, see
The value mapping described above can be used to clarify the difference between the terms "tree data structure" and "tree data type":
A tree data type is a set of values of tree data structures.
Note that there are 2 degrees of discrepancy between the terms. This becomes apparent when one compares a single tree data type with a single tree data structure. A single tree data type contains (infinitely) many values each of which is represented by (infinitely) many tree data structures.
For example, given a set of labels, the set of rose trees in the Haskell sense (3b) with labels taken from is a single tree data type. All the above examples of rose trees belong to this data type.
Notes:
As it can be observed in the above text and diagrams, the term "rose tree" is controversial.There are two interrelated issues:
Interestingly, the term "node" does not appear in the original paper[3] except for a single occurrence of "nodes" in an informal paragraph on page 20.In later literature the word is used abundantly.This can already be observed in the quoted comments to the definitions:
A rose tree [...] is either a leaf [...] or a node [...].[4]
An element of Rose α consists of a labelled node [...].[1]
In particular, the definition of rose trees in the most common Haskell sense suggests that (within the context of discourse) "node" and "tree" are synonyms. Does it mean that every rose tree is coincident with its root node? If so, is such a property considered specific to rose trees or does it also apply to other trees? Such questions are left unanswered.
The (B) problem becomes apparent when looking at the diagrams of the above examples. Both diagrams are faithful in the sense that each node is drawn exactly once. One can immediately see that the underlying graphs are not trees. Using a quotation from Tree (graph theory)
The various kinds of data structures referred to as trees in computer science have underlying graphs that are trees in graph theory [...]
one can conclude that rose trees in general are not trees in usual meaning known from computer science.
There is at least one adoption of the term "rose tree" in computer science in which "sharing of substructures" is precluded. The concept of a Bayesian rose tree is based on the following definition of rose trees:
is a rose tree if either for some data point or where 's are rose trees over disjoint sets of data points.[14]