Turtle Is Not JSON

Back to Devoured - October 08, 2026

DEVOURED

Turtle Is Not JSON

Time-series data requires more than simple timestamps; using a graph layer for metadata helps manage provenance and exceptions that raw tables ignore.

What: The article advocates for separating time-series storage (for bulk measurement data) from a graph-based semantic layer (JSON-LD/RDF) that manages units, derivations, and anomaly context.

Why it matters: Standard time-series databases treat data as isolated points, but context-aware systems need semantic links to ensure data interoperability and validation across different domains.

Takeaway: If your time-series pipeline is struggling with complex anomaly detection or data provenance, introduce a graph metadata layer (RDF/JSON-LD) to house the context rather than bloating the time-series schema.

Deep dive

Time-series data often misses units, provenance, and exceptions.
Use tabular storage for raw measurements and graph stores for metadata context.
JSON-LD/RDF allows for explicit, queryable semantic relationships.
Semantic modeling improves automated validation and cross-system interoperability.
Anomaly handling is more efficient when related metadata is explicitly linked in a graph.

Decoder

Provenance: The chronological documentation of the source and history of a data point.
JSON-LD: A lightweight Linked Data format that allows for embedding contextual metadata in JSON objects.

Original article

Time-series data often needs more than values and timestamps: units, provenance, derivations, and exceptions matter too. JSON-LD and RDF make that context explicit and queryable, which improves validation and interoperability. Keep bulk measurements in efficient tabular or time-series storage, and use a graph layer for metadata, semantics, and anomaly handling.

Explore all 59 articles in today's digest