<h1 id="mesh-location">mesh location<a aria-hidden="true" class="anchor-heading icon-link" href="#mesh-location"></a></h1>
A mesh can be represented by a bunch of files and folders in a filesystem. But it is primarily a concept.
Conceptually, a mesh is composed of <a href="/sflo/notes/mesh-resource">mesh resources</a>s. Those resources all have a mesh location: conceptual addresses that may be specified relative to each other (<a href="/sflo/notes/relative-identifier">relative identifier</a>) or from the <a href="/sflo/notes/llzh1jdoieldfpff4v3ealw">root node</a>. 
Mesh locations map cleanly to filesystem paths, and they work 
<hr>
Backlinks
<ul>
<li><a href="/sflo/notes/relative-identifier">relative identifier</a></li>
</ul>

mesh location

sflo


**Dereferenceable, versioned semantic meshes** will be the foundation for a new era of knowledge graphs.

[[now]] | [[todo]] | [[principle]] | [[dev.contributor.djradon.dev-log]]

## What Is Semantic Flow?

**Semantic Flow** is a framework for managing and publishing resource identifiers, knowledge graphs and other semantic data by leveraging GitHub, Gitlab, and other free static hosting services. It enables a **dereferenceable Semantic Web** where every HTTP IRI returns meaningful content.

[[concept.single-mesh-repo]] provide storage, [[concept.mesh]] provide resource management and publishing, and [[concept.semantic-flow-site]] support data discovery and explainability.

## Benefits

- own your own self-describing data and data schemas
- complete version history when you want it
- reliable persistence
- truly FAIR (Findable, Accessible, Interoperable, and Reusable)

## Features

- seamlessly integrate other data sources anywhere in your mesh
- generate and customize mini-sites or single-page applications for nodes in your mesh
- see [[feature]] for a list of planned features
