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 allows creating SPARQL endpoints. The endpoint will be able to handle SPARQL select and update queries, and notify about changes in it.

The endpoint is exported via DBus, accessible through the given service_name, either using it in a SERVICE clause, or by creating a dedicated bus-based SPARQL connection.

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

Users should be careful about the --http-port option, consider using it only combined with the --loopback option.

The database itself will be stored according to database_path.

OPTIONS¶

-b, --dbus-service=<service_name>

-d, --database-path=<database_path>

-o, --ontology

-p, --ontology-path

--session

--system

-l, --list

-L, --list-http

--http-port

--loopback

EXAMPLES¶

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

$ 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¶

tracker3-sparql(1),

https://www.w3.org/TR/sparql11-query/