Hierarchical names in workcraft

Implement hierarchical naming for nodes that provide their own name space. VisualPage is one example of name space providers, which affects unique naming constraints. For instance, there may be several pages: p1, p2, p3. One page contains several nodes n1, n2, n3... Equally, page p2 may have the same nodes: n1, n2 (those are local to p2 and there is no naming conflict). The delimiter '.' can be used to separate nodes from the namespace provider, hence: p1.n1 and p2.n1 identify both nodes from the root perspective.

The root of the model is the main name space and it does not have a name(?).

Important: connecting two nodes is done from a perspective of the connection owner. If a connection is made from n1 to n2 inside p1, then its first and second component references are written with local names only. If a connection is between p1 and p2, then it belongs to the container that includes these pages. Therefore, its reference would be written as a connection between "p1.n1" and "p2.n2"