Nodes as encapsulated rich data

The potential of a data point

A simple node

Detached from meaning, the number can still be a simple node. It could absolutely have no greater context.

encap simple.png

A simple node with "3.14" set as an internal label.

(Although it’s rare. Even if it’s your current bank account total, or a bill, or how much length you need to add, it still bubbling up with meaning attached to it.)

A node with supporting metadata

Many people recognize this particular number and it’s underlying meaningfulness, which probably starts along the lines of:

encap meta.png

A simple node with "3.14" set as an internal label, with 4 small nodes set in parenthesis underneath it.

A hierarchy

A node in one architecture could be the indication of a deeper hierarchy – either as the beginning point, or (more complicated) part of the child structure.

encap hierarchy.png

Two hierarchies, both somewhat complex. In the left-hand heirarchy, the parent/largest node is black with a white label "3.14". In the right-hand hierarchy, a node of the same size as its cohort, black, with white text "3.14".

A process

A node in one architecture could signify a relevant part of another process – whether question, answer, or interior piece.

encap process.png

A simple process, three nodes in a straight line, center node black with white text "3.14".

A network

The most complicated, a node could be an encapsulated network.

encap network.png

Relatively simple network with a randomly placed larger node, black with white text "3.14".
encapsulated rich data:
hierarchy, metadata, network, node