Tools

Start by inspecting a feed in your browser, or use a client and publishing pipeline to integrate LDES into your applications.

LDFetch

LDFetch is a browser tool for exploring Linked Data. Paste an LDES entry point into the URL field and fetch it, then open the Hypermedia pane to inspect the stream’s links and navigate its pages. This is a useful way to understand a feed before setting up a harvesting pipeline.

Try one of the built-in LDES examples or copy an entry point from our LDES examples.

RDF-Connect JavaScript / TypeScript

RDF-Connect is an initiative that lets you declaratively define RDF processing pipelines in RDF itself, executed by runners for different languages and environments (JavaScript being the most mature today). It hosts the reference LDES tooling used throughout the community:

• ldes-client — the TREE/LDES client to replicate and synchronise an LDES from JavaScript or TypeScript, either as a library or as an RDF-Connect processor.
• ldes-server — an LDES server implementation built within the Community Solid Server, for publishing one or more event streams.
• ldes2sparql — materialises an LDES into a SPARQL graph store, keeping it incrementally up to date.

OpenLDES Java

OpenLDES is the open-source ecosystem that grew out of the Flemish government's Vlaamse Smart Data Space (VSDS) programme. It provides a Java-based toolchain to publish and consume both open and closed data as LDES, structured around three pipeline archetypes: a publishing pipeline (turning sources into an LDES), a consuming pipeline (harvesting an LDES into a database, file store or message queue), and an intermediary pipeline (republishing an enriched or restructured LDES).

• LDES Server — a configurable server for ingesting and publishing LDES views.
• Linked Data Interactions (LDIO) — a pipeline framework of input/transform/output components for LDES.
• Onboarding example — a hands-on tutorial to get a first pipeline running.

Building your own client

The LDES specification is intentionally implementable from any RDF library, so several other clients and servers exist beyond the two ecosystems above — see the specification repository and the community chat for pointers to the latest ones.

Writing your own? Check it against the LDES 1.0 client conformance test suite, a black-box suite that turns the consumer requirements of the LDES 1.0 specification into reproducible HTTP scenarios and machine-readable EARL reports. Its baseline already maps 77 of the 100 reviewed LDES 1.0 requirements to 18 executable scenarios, covering unordered and ordered traversal, member extraction, and context information as separately reportable compliance groups. View the conformance report →