TINYSPARQL-ENDPOINT(1)

📦
version 3.12.0 · 12 versions
, in arch rolling

💅 TINYSPARQL-ENDPOINT 💅

okay so bestie, welcome to tinysparql-endpoint(1) from the TinySPARQL manual — this is the one that spins up SPARQL endpoints for you, and honestly? it's giving main character energy ✨

🎀 NAME 🎀

tinysparql-endpoint — literally just. create a SPARQL endpoint. that's the whole vibe 🦋

🌸 SYNOPSIS 🌸

tinysparql endpoint [--dbus-service | -b] <service_name>
                  [--database-path | -d] <database_path>
                  [[--ontology | -o] <ontology_name> |
                   [--ontology-path | -p] <ontology_path>]
                  [--http-port] <port>
                  [--loopback]
                  [[--system | --session]]

like yeah it's a lot of brackets but we love a flexible queen 💅

✨ DESCRIPTION ✨

So this command lets you create SPARQL endpoints, periodt. The endpoint you make is gonna be able to handle SPARQL select and update queries, and it'll also notify you about changes in it — iconic behaviour tbh 🔥

The endpoint gets exported via DBus, and you reach it through the service_name you gave it — either by using it in a SERVICE clause, or by creating a dedicated bus-based SPARQL connection. iykyk 🫶

When you're creating a database, you must provide the ontology_name (or alternatively an ontology_path) in order to generate the database. no ontology, no database, no cap. If you go with ontology_name, the ontology has to already exist in $datadir/tracker/ontologies 💖

⚠️ bestie be careful with the --http-port option — consider using it only combined with the --loopback option. like fr fr, safety first 🙈

The database itself will be stored according to database_path 🍓

🌈 OPTIONS 🌈

  • -b, --dbus-service=<service_name> — the service name to use on the endpoint. this is the name you'll be calling it by 💫
  • -d, --database-path=<database_path> — the path where the database will be stored. your database lives here now, congrats 🏠
  • -o, --ontology — the name of an ontology in $datadir/tracker/ontologies to use on the constructed database 🎀
  • -p, --ontology-path — full path to an ontology to use on the constructed database. like, the whole entire path 🔍
  • --session — use the session bus. this is the default, so if you don't say anything, this is what you get 💜
  • -l, --list — list all SPARQL endpoints available in DBus 👑
  • -L, --list-http — list network-local HTTP SPARQL endpoints 🌐
  • --http-port — creates a HTTP endpoint that listens in the specified port. (careful with this one, remember the warning above!! 😭)
  • --loopback — allows only HTTP connections in the loopback device. only effective with HTTP endpoints, so don't expect it to do anything otherwise 💀

⭐ EXAMPLES ⭐

Export a Nepomuk endpoint with the org.example.Example1 bus name:

$ tinysparql endpoint -b org.example.Example1 -o nepomuk -d /tmp/example1

Access this endpoint with the tinysparql-sparql(1) subcommand:

$ tinysparql sparql --dbus-service org.example.Example1 -q "
  SELECT ?s ?o
  WHERE {
    ?u a ?o
  }"

Export a Nepomuk endpoint via HTTP:

$ tinysparql endpoint --http-port 8080 -o nepomuk --loopback

Access this endpoint via HTTP:

$ tinysparql sparql --remote-service http://127.0.0.1:8080/sparql -q "
  SELECT ?u {
    ?u a rdfs:Resource
  }"

🦋 SEE ALSO 🦋

and that's the whole page!! this lil doc is from TinySPARQL version 3.12.0, dated 09/15/2026 — ty for reading, ily, go make some endpoints 💖✨🎀

📦 where this page comes from