Skip to content

Implement live file-backed SPARQL access with sparqld

Decided · 7 August 2026

Context

Linked Data files need direct SPARQL access for human users and agents; files remain authoritative and edits become available live. This decision compares solutions that do not require operating a separately loaded triple store.

flowchart LR LinkedDataFiles["Linked Data files"] --> LiveSparqlAccess["Live SPARQL access"] LiveSparqlAccess --> HumanUsers["Human users"] LiveSparqlAccess --> Agents["Agents"]

Decision

Alternative Direct file access Live reload SPARQL endpoint YAML-LD Markdown-LD GitHub stars Latest release
iolanta-tech/sparqld ✅ ✅ ✅ ✅ ✅ 0 0.1.1
2026-08-07
SPARQL Anything ✅ ⚠ ✅ ❌ ❌ 302 v1.2.0
2026-07-24
Apache Jena Fuseki ❌ ❌ ✅ ❌ ❌ 1,398 6.1.0
2026-05-03
Oxigraph server ❌ ❌ ✅ ❌ ❌ 1,801 v0.5.9
2026-06-18
RDF4J Server ❌ ❌ ✅ ❌ ❌ 409 5.3.2
2026-06-29
Comunica over local RDF files ✅ ⚠ ✅ ❌ ❌ 577 v5.3.0
2026-07-10
Apache Jena ARQ ✅ ⚠ ❌ ❌ ❌ 1,398 6.1.0
2026-05-03
fabio-rovai/open-ontologies ❌ ❌ ❌ ❌ ❌ 353 v1.1.1
2026-08-05

Green row: chosen, meets every requirement. Red row: excluded, fails one or more required capabilities; stronger-red cells are the disqualifying capability. ⚠ re-querying reflects a changed file but there is no watcher.

Consequences

  • Work proceeds on sparqld as the selected live file-backed SPARQL access product.