RDF-JS inference playground

Align RDF input from a documented source contract towards the RDF contract your application accepts.

Editor fields use rdf-parser-ts for Turtle, TriG, N-Triples, N-Quads, and RDF Message Logs; URL sources are dereferenced with ldfetch for JSON-LD, RDF/XML, RDFa, Microdata, SHACL Compact, Jelly-RDF, and negotiated RDF serializations.

SPARQL CONSTRUCT playground · NPM package · GitHub repository

Example

Each example combines source and target contracts, background knowledge, and an RDF Message log.

Advanced settings

N3 rule profiles

Disable a profile to inspect its contribution to the alignment.

Execution

Retain facts across message boundaries. Enable only when earlier messages remain universally true.

Alignment contract

Trusted SHACL contracts guide rule pruning and select the inferred representation retained for the application.

SHACL IN

What each incoming message may contain.

SHACL OUT

What the receiving application can handle.

Ontology and background knowledge

Stable vocabulary, mappings, and context loaded before the messages are processed.

RDF Input

RDF Message Logs preserve message boundaries; ordinary RDF input is processed as one batch.

MESSAGES IN

Editable Turtle, TriG, N-Triples, N-Quads, or RDF Message Log supplied by the source.

MESSAGES OUT

Newly inferred RDF, preserving input message boundaries when present.