Skip to main content
Tripper logo

PyPI Documentation CI Tests DOI

Triplestore wrapper for Python providing a simple and consistent interface to a range of triplestore backends

Tripper

Getting started

Basic concepts

Tripper provides a simple and consistent interface to a range of triplestore backends. It strives for simplicity and is modelled after rdflib (with a few simplifications).

In Tripper:

  • All IRIs are represented by Python strings. Example: https://w3id.org/emmo#Metre

  • Blank nodes are strings starting with _:. Example: _:bnode1

  • Literals are constructed with tripper.Literal. Example: tripper.Literal(3.14, datatype=XSD.float)

To make it easy to work with IRIs, provide Tripper a set of pre-defined namespaces, like XSD.float. New namespaces can be defined with the tripper.Namespace class.

A triplestore wrapper is created with the tripper.Triplestore class.

Sub-packages

Additional functionality beyond interfacing triplestore backends is provided by specialised sub-package:

Available backends

The following backends are currently available, either in Tripper or other packages.

Backend name Provided by Requirements Comment
rdflib tripper rdflib In-memory rdflib triplestore supporting all features.
ontopy tripper EMMOntoPy Backend for EMMOntoPy. In-memory.
sparqlwrapper tripper sparqlwrapper Generic backend for all triplestores supported by sparqlwrapper.
collection tripper DLite-Python Backend to a DLite collection.
graphdb tripper sparqlwrapper Backend to GraphDB.
fuseki PyBackTrip sparqlwrapper Backend to fuseki.
stardog PyBackTrip sparqlwrapper,pystardog Backend to StarDog.

Installation

Tripper has by itself no dependencies outside the standard library, but the triplestore backends may have specific dependencies.

The package can be installed from PyPI using pip. A minimal installation can be done with

pip install tripper

but typically, you would also like to install the requirements needed by the backends, the tripper sub-packages and extra features. The requirements for the backends are listed in the table above, while sub-packages and extra features are enabled by specifying one or more of the "extras" listed in the table below when installing Tripper.

For example, the following command will install Tripper with the tripper.datadoc sub-package and the rdflib backend enabled:

pip install tripper[datadoc] rdflib

Developers should install Tripper with the dev extras and enable pre-commit:

pip install tripper[dev]
pre-commit install  # Enable pre-commit and installing hooks
Extras Description of dependencies Implies
units Required by the tripper.units sub-package.
mappings Required by the tripper.mappings sub-package. units
datadoc Required by the tripper.datadoc sub-package. mappings
backends Installs dependencies for all backends
testing For testing. datadoc,backends
docs For generation of documentation testing
dev For developers. Installs all dependencies, including pre-commit. dev

License and copyright

All files in this repository are licensed under the MIT license. If not stated otherwise in the top of the files, they have copyright © 2022 SINTEF.

Acknowledgements

We gratefully acknowledge the following projects for supporting the development of Tripper:

  • OntoTrans (2020-2024) that receives funding from the European Union's Horizon 2020 Research and Innovation Programme, under Grant Agreement n. 862136.
  • OpenModel (2021-2025) that receives funding from the European Union's Horizon 2020 Research and Innovation Programme, under Grant Agreement n. 953167.
  • SFI PhysMet (2020-2028) funded by Forskningsrådet and Norwegian industry partners.
  • DOME 4.0 (2021-2025) that receives funding from the European Union's Horizon 2020 Research and Innovation Programme, under Grant Agreement n. 953163.
  • VIPCOAT (2021-2025) that receives funding from the European Union's Horizon 2020 Research and Innovation Programme, under Grant Agreement n. 952903.
  • MEDIATE (2022-2025) that receives funding from the RCN, Norway; FNR, Luxenburg; SMWK Germany via the M-era.net programme, project 9557,
  • MatCHMaker (2022-2026) that receives funding from the European Union's Horizon 2020 Research and Innovation Programme, under Grant Agreement n. 101091687.
  • PINK (2024-2027) that receives funding from the European Union's Horizon 2020 Research and Innovation Programme, under Grant Agreement n. 101137809.

Release files for tripper 0.5.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tripper 0.5.3
File Size Uploaded
tripper-0.5.3.tar.gz 1.4 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for tripper 0.5.3
File Interpreter ABI Platform
tripper-0.5.3-py3-none-any.whl Python 3 none any Details

Total release size: 1.5 MB

Release files / tripper-0.5.3.tar.gz

Download URL tripper-0.5.3.tar.gz
Size 1.4 MB
Tags Source
SHA-256 checksum
How to use checksums
9904444ff933edc8f644ba8dcbebe19d1e24779507deab8a3ecf85f5e4743226
BLAKE2b-256 checksum
How to use checksums
d25e74bedb6b189e603287448bb2dbf0ab29d48e4be3b0bbd4b8031f5e55f660
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 13, 2026.

Transparency log

Release files / tripper-0.5.3-py3-none-any.whl

Download URL tripper-0.5.3-py3-none-any.whl
Size 159.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9b239409bfcb352db04766c240401caf00fd656d85346acc3a9e3ab3f0f7b643
BLAKE2b-256 checksum
How to use checksums
40a0660f8e275505766e7f936bee3a3d5f32598d797fe831d5ff4db1fcc2523a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 13, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.5.3 This release

2 release files

0.5.2

2 release files

0.4.3

2 release files

0.4.2

2 release files

0.4.0

2 release files

0.3.4

2 release files

0.3.3

2 release files

0.3.0

2 release files

0.2.16

2 release files

0.2.15

2 release files

0.2.14

2 release files

0.2.13

2 release files

0.2.11

2 release files

0.2.10

2 release files

0.2.9

2 release files

0.2.7

2 release files

0.2.6

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page