<h1 id="fragment-identifiers">Fragment Identifiers<a aria-hidden="true" class="anchor-heading icon-link" href="#fragment-identifiers"></a></h1>
<h2 id="uses">Uses<a aria-hidden="true" class="anchor-heading icon-link" href="#uses"></a></h2>
<ul>
<li><a href="/sflo/notes/4v2b7t8nbzkmtyvnayye3vj">Provenance</a> data and similar "too small to be a node" use cases
<ul>
<li>e.g., things need a name, but you don't want to cause an infinitie cascade of naming pieces of metadata that need their own metadata</li>
</ul>
</li>
<li><a href="/sflo/notes/34to8s18168griy8qbgs6o5">Named Graphs</a></li>
<li>handle-as-mesh-resource references</li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/sflo/notes/tn4fb1v558dd7sh1r5ubh7n">Do payload nodes support DatasetSeries?</a></li>
<li><a href="/sflo/notes/4v2b7t8nbzkmtyvnayye3vj">Provenance</a></li>
</ul>

Fragment Identifiers

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
