mesh node

Overview

The primary constituents of a semantic mesh are mesh nodes. They are physically represented as mesh folders and establish a namespace segments.

Mesh nodes are holonic containers that can contain other mesh nodes node components, distinguishing them from components which are terminal within their own scope.

Physical Structure

When stored on disk, all mesh nodes:

• Are physically represented as folders in the filesystem
• Extend the identifier namespace with their folder name
• Can be further extended by containing other mesh resources

Mandatory Components

Every mesh node has these components:

• metadata flow (_node-metadata-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

Optional Components

Node Types

1. bare node

Components: _meta-flow/ + _node-handle/

• Functions as organizational containers
• Contains essential identity, metadata, and handle information
• Node IRI refers to the namespace itself
• Base level for all mesh nodes

2. data node

Components: _meta-flow/ + _node-handle/ + _data-flow/

• Contains data distributions and versioning capabilities
• Node URL refers to the node’s referent (real-world entity or dataset concept) represented by the data flow
• Adds dataset storage to the namespace foundation
• Can be configured as dataset series
• Evolved from bare nodes by adding the _data-flow/ component
• Maintains single referent principle

---

Children

1. bare node
2. reference node

---

Backlinks

• mesh resource
• mesh repo
• semantic mesh
• Namespace
• root node
• Concept Summary
• Why are there components at the top of a repo?
• namespace folder
• node folder
• node component
• node flow facet
• assets tree
• node flow
• bare node
• reference node
• metadata flow