TRACKER3-ENDPOINT(1)

📦
version 3.7.3 · 5 versions
, in centos-stream 10

💅 tracker3-endpoint(1) 💅

okay bestie, welcome to the Tracker manual page for this absolute icon: tracker3-endpoint. It’s giving “make me a SPARQL endpoint” energy, and we’re gonna walk through it together 💖

🌸 NAME 🌸

tracker3-endpoint — create a SPARQL endpoint ✨

✨ SYNOPSIS ✨

tracker3 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]]

💖 DESCRIPTION 💖

This command is your lil factory for creating SPARQL endpoints, no cap. The endpoint can handle SPARQL select and update queries, and it can notify about changes in it. Slay.

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

When you’re creating a database, the ontology_name (or alternatively, an ontology_path) must be provided in order to generate the database. If ontology_name is used, the ontology must exist in $datadir/tracker/ontologies.

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

The database itself will be stored according to database_path. That’s where it lives, periodt 💅

🎀 OPTIONS 🎀

  • -b, --dbus-service=<service_name> — the service name to use on the endpoint 💖
  • -d, --database-path=<database_path> — the path where the database will be stored 🍓
  • -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 🦋
  • --session — use the session bus. This is the default 👑
  • --system — use the system bus 🌈
  • -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 🌸
  • --loopback — allows only HTTP connections in the loopback device. Only effective with HTTP endpoints 🧚

🦋 EXAMPLES 🦋

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

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

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

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

Export a Nepomuk endpoint via HTTP 🎀:

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

Access this endpoint via HTTP:

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

👑 SEE ALSO 👑

this page is from Tracker 3.7.3, dated 10/29/2024 — bye bestie, go make some endpoints and slay 💜🫶

📦 where this page comes from