<h1 id="mesh-repo">mesh repo<a aria-hidden="true" class="anchor-heading icon-link" href="#mesh-repo"></a></h1>
<p>A Semantic Flow mesh repository (or mesh repo for short) is a git repository that contains a <a href="/sflo/notes/llzh1jdoieldfpff4v3ealw">root node</a> at the top of the repo, and any number of additional, contained <a href="/sflo/notes/mesh-node">mesh node</a></p>
<h2 id="github-repos">Github Repos<a aria-hidden="true" class="anchor-heading icon-link" href="#github-repos"></a></h2>
<ul>
<li>can either be "username/org pages repository"" (which automatically hosts content at the namesake url, so maybe call it a namesake repository, e.g. djradon.github.io) or 2nd-level (corresponding to an owned repo)</li>
<li>a 'docs' folder that contains the generated sf site
<ul>
<li>within 'docs' there's a folder for each namespace</li>
</ul>
</li>
</ul>
<h2 id="questions">Questions<a aria-hidden="true" class="anchor-heading icon-link" href="#questions"></a></h2>
<ul>
<li>can you include a mesh in an existing repo?
<ul>
<li>Sure!</li>
<li>but for composability (i.e., linking a repo into an existing mesh) you need an unbroken chain, so embedding a root mesh below the top of a repo might make it harder for people to re-use. </li>
</ul>
</li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/">Semantic Flow Documentation</a></li>
<li><a href="/sflo/notes/pqjdlyd8g80x3yr9o3p82mj">node config</a></li>
<li><a href="/sflo/notes/llzh1jdoieldfpff4v3ealw">root node</a></li>
<li><a href="/sflo/notes/ynqxgf8uv2bgbdi81wlz29g">Semantic Site</a></li>
<li><a href="/sflo/notes/concept-summary">Concept Summary</a></li>
<li><a href="/sflo/notes/h4qk30cdxajlrs47toszogm">Fluree Connector</a></li>
<li><a href="/sflo/notes/f2dk7cwbol4o1jsnd0cun1g">namespace base</a></li>
<li><a href="/sflo/notes/fd1whkyvoagggk6ubysjl50">djradon's sflo devlog</a></li>
</ul>

mesh repo

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.mesh-repo]] provide storage, [[concept.mesh]] provide resource management and publishing, and [[concept.semantic-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
