mesh resource

Overview

A mesh resource is any addressable component within a semantic mesh. Every mesh resource has a unique Intramesh based on its path and locally unique name, making it dereferenceable via URL.

In RDF terms, a resource is any node in an RDF graph that can be represented with an IRI (the other kinds of RDF graph nodes are literals and blank nodes). So theoretically, files and folders in assets tree could be considered RDF resources. But they are not considered mesh resources

Types of Mesh Resources

The structure of a semantic mesh is built on a fundamental distinction between extensible and terminal resources:

• Mesh nodes are extensible namespace containers:
• Mesh node components are terminal mesh resources:
  • Can be physically represented as folders or files
    • Folder intramesh identifier are part of the namespace but cannot be extended beyond their own internal structure
  • All files and folders within a component folder are considered to be part of the parent node

Folder-based components:

• metadata flows: Administrative metadata (in _meta-flow/ folders)
• Asset trees: File collections (in _assets/ folders)
• Version datasets: Versioned snapshots
• next snapshots: Draft workspaces

File-based components:

• Documentation files:
  • Resource pages are index.html files that provide de-referencability for their containing intramesh identifier folder resource facet
  • README.md and CHANGELOG.md: unstructured documentation
• snapshot distribution files: Data files in RDF formats

Physical vs Logical Structure

Physical Representation:

• Mesh nodes and components are represented as folders in the filesystem
• File resources are represented as individual files
• Folder names become namespace segments and URL path components

Logical Function:

• All mesh resources are addressable via their URL path
• URLs must return meaningful content when dereferenced
• Resources maintain semantic relationships through containment and cross-references

Asset Tree Special Case

Asset trees represent a special category where:

• The asset tree itself (with its metadata flow) is part of the mesh structure
• The files and folders contained within asset trees are "attached to" but not "contained in" the mesh
• Asset tree contents are addressable but are not considered semantic flow resources

This distinction maintains clean separation between semantic mesh structure and arbitrary file attachments while preserving addressability.

---

Children

1. mesh node
2. node component

---

Backlinks

• semantic mesh
• root node
• Dereferencability for Humans
• assets tree