For full text search please use the '?' prefix. e.g. ? Onboarding

paylod node

Payload nodes are nodes with datasets conained in them via payload flow. They denote their contained payload dataset, and must have a reference flow to describe that dataset.

Overview

payload nodes are reference nodes that represent and contain an evolvable "payload" dataset in the form of a payload flow.

The payload dataset is kept in the payload node's payload flow.

Like all node flows, because it is evolvable it gets typed as a DatasetSeries. Its snapshots are datasets (Private).

Unlike flow snapshots which contain concrete data distributions, payload nodes serve as conceptual containers that organize and provide identity for datasets without containing the data directly. I.e., payload nodes only contain concrete datasets by virtue of containing a payload flow (also abstract) and its snapshots, which have concrete distributions.

If a node has a PayloadFlow (i.e., it’s a “payload node”), then in its ReferenceFlow the node’s IRI MUST have rdf:type dcat:Dataset.

Abstract vs Concrete Datasets

payload node (highly abstract)

A payload node represents a dataset as a concept, e.g.:

  • /ns/djradon/bio/ = a biographical dataset about the person djradon
  • /ns/census/ = the results of a census
  • /ns/weather-stations/ = a weather stations dataset

The payload node provides stable identity: The dataset persists conceptually even as concrete data changes.

payload flow (abstract)

payload flow is the single user payload flow for a node, realized by snapshots:

  • /ns/monsters/_payload/_default/ = the default dataset snapshot
  • /ns/weather-stations/_payload/2025-11-24_0142_07_v3/ = version 3 dataset snapshot

Snapshots contain distribution files: the actual data in various formats (e.g., .trig, .jsonld)

payload flow Snapshot (slightly concrete)

Flow snapshots are still not actual data, but they denote a specific version of an evolving dataset

payload flow Snapshot Distributions (concrete)

These are "concrete information resources", i.e. files.

Required Components

Every payload node must contain:

Optional Components

Key Characteristics

Not a Dataset

Important: A payload node is not itself a (concrete) dataset. It represents the abstract concept of a dataset that may evolve over time:

  • payload nodes are never versioned (only their component flows are)
  • payload nodes serve as stable conceptual anchors

Extensible Container

Like all mesh nodes, payload nodes can contain other mesh nodes and components, making them extensible namespace containers.

Examples

Unversioned payload node

ns/monsters/
├── _meta/                 # metadata about the "monsters" payload node
├── _node-handle/               # handle for the payload node
└── _payload/                 # single payload flow
    └── _default/               # default dataset snapshot
        ├── monsters.jsonld     # concrete distribution of the default snapshot
        └── monsters.trig
Backlinks