<h1 id="what-is-the-referential-difference-between-a-payload-nodes-iri-and-its-payload-flows-iri">What Is the referential difference between a payload node's IRI and its payload flow's IRI<a aria-hidden="true" class="anchor-heading icon-link" href="#what-is-the-referential-difference-between-a-payload-nodes-iri-and-its-payload-flows-iri"></a></h1>
<p>A <strong>payload node IRI</strong> (e.g. <code>ns/djradon/bio/</code>) identifies the <strong>abstract dataset itself</strong> — it's a dereferenceable identifier for an RDF dataset
A <strong>payload flow IRI</strong> (e.g. <code>ns/djradon/bio/_payload</code>) identifies the <strong>semantic flow that captures the evolution of that dataset</strong> — metadata about <em>how</em> the payload is produced, validated, versioned, or transformed.</p>
<div class="table-responsive">







































<table><thead><tr><th>Aspect</th><th>Payload Node (<code>ns/djradon/bio/</code>)</th><th>Payload Flow (<code>ns/djradon/bio/_payload</code>)</th></tr></thead><tbody><tr><td><strong>Referential role</strong></td><td>Refers to the dataset <em>as content</em></td><td>Refers to the dataset’s <em>production process</em></td></tr><tr><td><strong>Ontological category</strong></td><td><code>sflo:PayloadNode</code> (or equivalent)</td><td><code>sflo:PayloadFlow</code> (a subclass of <code>sflo:Flow</code>)</td></tr><tr><td><strong>Nature</strong></td><td>Public, stable identifier for consumers</td><td>Internal, operational metadata for publishers</td></tr><tr><td><strong>Dereferencing expectation</strong></td><td>Returns the default dataset or its default distribution (<code>index.trig</code>, etc.)</td><td>Returns RDF describing the flow’s inputs, transformations, outputs</td></tr><tr><td><strong>Persistence</strong></td><td>Semi-permanent, versioned through dataset series (<code>_series/_main/v1/...</code>)</td><td>May change across builds, describing how payload evolves</td></tr><tr><td><strong>Relations</strong></td><td><code>sflo:hasPayloadFlow &#x3C;_payload></code></td><td><code>sflo:producesPayload &#x3C;bio/></code> (inverse)</td></tr></tbody></table></div>
<p>In short:</p>
<ul>
<li><strong><code>/bio/</code></strong> = “the data about Bio.”</li>
<li><strong><code>/bio/_payload</code></strong> = “the process that emits <code>/bio/</code>.”</li>
</ul>
<p>The node is the <em>what</em>; the flow is the <em>how</em>.</p>

What Is the referential difference between a payload node's IRI and its payload flow's IRI

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


Aspect	Payload Node (`ns/djradon/bio/`)	Payload Flow (`ns/djradon/bio/_payload`)
Referential role	Refers to the dataset as content	Refers to the dataset’s production process
Ontological category	`sflo:PayloadNode` (or equivalent)	`sflo:PayloadFlow` (a subclass of `sflo:Flow`)
Nature	Public, stable identifier for consumers	Internal, operational metadata for publishers
Dereferencing expectation	Returns the default dataset or its default distribution (`index.trig`, etc.)	Returns RDF describing the flow’s inputs, transformations, outputs
Persistence	Semi-permanent, versioned through dataset series (`_series/_main/v1/...`)	May change across builds, describing how payload evolves
Relations	`sflo:hasPayloadFlow <_payload>`	`sflo:producesPayload <bio/>` (inverse)