.png)
Memo2007Ultra
Discover, Collect, Modify, Create, Share, Inspire,
through Art, Games, and Learning
[ Kikuo ] → [ Kio ] - Tree/Hiearchy
Giving different parts in a structure with a pattern and logic
This is a mechanism, not exactly a word category, instead some word category uses this mechanism
The pronunciation is inspired by "Ki", "Kuo"
TreeNode Identifier Operators
Each glyph is used to identify a node of a tree.
Here are a few ways to understand what does a Tree Identifier Operator does :
- will tell you which path (edge) to take to reach the target node
- can be treated as a nametag that an edge can have
- can be treated as a function to bring you from one node to another
[ Kikuo ] - [ Kio ] : "Start Tree Path"
to declare a tree path
[ ko ] : "Start from Root"
the root Node of the tree, usually this will be omited, unless we are targeting the root node
[ ki<depth> ] : "go Pass <depth> of Edges"
Sometimes a tree may contain a long strand of nodes such that all nodes only has one child. This operator can literally mean "go up/down the strand", to make things shorter, the "travel distance" or "depth" will be a number, however, if the given depth is "ka", it means "keep going down until you are at a branch"
[ kæ<index> ] : "go to the <index>th Child"
selects a branch, attaches the index of the branch to the end of the segment
by default, the index starts from 0. But not all trees uses numbers for indexing, when that happens, the index is prefixed with "klæj" ( Refer to "Klæj" )
[ ka<index> ] : "leaf / a dead end"
optional to use, when a path is a dead end, you can use this to signify it. But it still needs to be indexed if there are other possible but undesired paths.
Examples
​
"Kio - kæNi - kæNæ - kiNæ - kæNo"
"treePath - goto 1st Child - goto 2nd Child - goPass 2 edges - goto 0th Child "
Main Route
Consider the given example :
in order to address Node H, we need
"Kio - kæNi - kæNi - kæNo - kæNi"
Which is a bit mouthful. This is fine for small cases or rare/specific cases
but for Important and Everyday Structures, it is better to have a Main Route
Based on different structures or situation, the Main Route are all different.
the Main Route is not chosen by rule, instead it is chosen by design.
​
In this case, the Main Route for a certain Purpose is decided by a commitee or a team of leaders or experts.
Quick Example would be :
The Main Route for Body Parts is decided by Biology Experts, and it is reviewed, agreed, and approved.
If an Alternative Main Route is suggested, it is possible to update the convention.
​
for our example, we can first rearrange our tree as the following :
(moving nodes around without breaking the edges does not change the tree)
An ideal Main Route is to cover as many Junctions as possible (not always)
since the main route consist of Stems (Ki) and Branches (Kæ)
the glyph and pronunciation for Main Route is :
[ Kiæ<depth> ] : "go Pass <depth> of MainRoute Edges"
a little similar to [ Ki<depth> ], but this is specificaly made for the Main Route
In our example, we will be coloring our MainRoute Orange :
And now we can index them / give them depths :
And we have shrink "Kio - kæNi - kæNi - kæNo - kæNi" down to "Kio - kiæLi"