The Eyeron Playground

Run eyeron in your browser — Notation3 (N3), SPARQL 1.2 RL, and Prolog — with the same native reasoner core, compiled to WebAssembly.

Version …

Program and data

Choose a format, load a bundled example or write your own, and (for N3) optionally add RDF/TriG data.
Engine: eyeron

Rules / program

Inline data / RDF Message log

Advanced options

These mirror the Eyeling playground workflow: keep reusable knowledge in the background, reason over the editor, and optionally provide RDF Message logs separately.

SPARQL-RL: a body pattern ({ ?x :descendedFrom :C }) to match against the closure instead of printing every derived fact. Prolog: a goal (ancestor(alice, Who)) appended as an extra ?- directive.
Render a JSON representation instead of Prolog result-format-3 syntax.
Enables the browser Eyeling engine for log:query output, log:outputString rendering, and Eyeling-compatible proof/RDF execution.
Emit proof output instead of only inferred conclusions.
Parse RDF syntax and use the selected RDF format.
The next Program URL load is kept separate and merged only when reasoning runs.
No background knowledge loaded.
Uses the inline data or Message log URL as message input. Eyeling mode can use message-oriented examples; eyeron receives the log as RDF/TriG data.
Passed to Eyeling when selected, matching its browser mixed-content-safe dereferencing option.
Loading wasm module…

Build the browser module with wasm-pack build --target web --out-dir pkg, then serve this directory over HTTP.

Two Prolog examples expect companion input the playground does not wire up standalone: proof-audit.pl (needs examples/proof/socrates.pl prepended) and rdf12-interoperability.pl (needs --rdf-input examples/rdf12-interoperability.nq) — run those from the command line instead.

import-main.srl's IMPORTS directive and rdf-messages.srl's examples/rdf-messages.trig base data are both fetched and wired in automatically when you load either example. rdf-messages.srl itself derives nothing either way: its rule expects the eymsg:payloadTriple <<...>> RDF-star encoding eyeleng's own message-log parser produces, while Eyeron's parses message logs into a different internal replay view — a known encoding gap, not a playground limitation.

Output