Use Case: Radio Show Websiste

Suppose DJ Radon wants to publish a website about himself, his musical activities, and maybe some album reviews. Call it a wiki, call it a knowledgebase, call it a show site.

To get started, he wants to publish his top-5 most-played tracks of the week.

Publishing them as plain-text might be adequate for this situation, but say he eventually wanted to make his site linked: you can click from a playlist, to an album, to a track, to an artist.

But to get started:

A namespace /ns/
A thing /ns/djradon/
A dataset /ns/djradon/picks/

See Example Mesh for a mapping of resources types

Mesh Node Directory Structure

test-ns                    # bare node
   djradon                 # ref node (refering to a human dj)
      bio                  # payload node
      picks                # payload node 
      underbrush           # ref node
         playlists         # data (series) node
            1996-11-10     # payload node
            1996-11-17     # payload node

Sample RDF (Turtle)

Namespace metadata

# /ns/_id/ns_id.trig
<> a sflo:BareNode ;
   dct:title "Namespace Root" ;
   sf:contains <https://example.org/ns/djradon/> .

Thing metadata

# /ns/djradon/_id/djradon_id.trig
<> a sf:Thing ;
   rdfs:label "djradon" ;
   sf:backlink <https://example.org/ns/> .

Dataset metadata

# /ns/djradon/picks/_id/picks_id.trig
<> a sf:VersionedDataset ;
   dct:title "djradon picks" ;
   sf:backlink <https://example.org/ns/djradon/> .

Current distribution

# /ns/djradon/picks/picks.trig
<> dct:issued "2025-06-22"^^xsd:date ;
   dct:creator <https://example.org/agents/bot> .

Historical version

# /ns/djradon/picks/_v-series/v1/picks.jsonld
<> dct:issued "2025-06-01"^^xsd:date .

With these few rules and a tiny folder-walking parser your Semantic Mesh is unambiguously self-describing, easy to validate, and ready for any RDF-aware tooling.

Mesh Node Directory Structure

Sample RDF (Turtle)