mesh node

Overview

The primary constituents of a semantic mesh are mesh nodes. A node's IRI refers to the its referent, i.e. the real-world or imaginary "thing" which the IRI names.

Nodes are represented "on disk" as mesh folders.

Mesh nodes establish conceptual namespace segments and can be holonic containers of other mesh nodes. They may also contain node components, which are supporting files and conceptual structures.

Node Types

• bare node : containers
• reference node : refering containers
• payload node : dataset containers that refer to their datasets

Filesystem Structure

When stored on disk, all mesh nodes:

• are physically represented as folders in the filesystem
• extend the identifier namespace with their folder name
• contain any of their own mesh resources
• may contain other nodes

Mandatory Components

Every mesh node has these components:

• metadata flow (_meta flow folder): Centralized metadata for the node
• node handle (_node-handle/): Universal marker folder that refers to the parent "as a mesh node", as opposed to "as the name, dataset, or other thing" to which it normally refers; a handle resource page should explain this distinction

---

Children

1. bare node
2. paylod node
3. reference node

---

Backlinks

• mesh resources
• semantic mesh
• root node
• mesh repo
• Concept Summary
• Why are there components at the top of a repo?
• node folder
• Project Brief
• node component
• assets tree
• node flow
• bare node
• reference node
• metadata flow
• handle resource page