RDF fingerprinter
Understand the structure of your RDF data at a glance using automatically built application profiles and spot differences between dataset structures.
An application profile, in this context, is the set of data shapes designed for a particular purpose acting as constraints on how the data are instantiated and so can be used to validate the data.
Fingerprinting is the action of generating, or rather, guessing, the application profile applied to a particular dataset. This is an inductive process of reconstructing the data shape for each class instantiated in the dataset.
Documentation: https://meaningfy-ws.github.io/rdf-fingerprinter/
Installation
RDF fingerprinter may be installed with pip as follows.
pip install rdf-fingerprinter
Python 3.12 or later is required (tested on 3.12, 3.13 and 3.14).
Upgrading from 0.3? 1.0 needs Python 3.12+, runs on eds4jinja2 2 (pandas 3 / numpy 2) and no longer configures logging when imported: configure it in your application. See the CHANGELOG.
Usage
The easiest way to build a fingerprint of a SPARQL endpoint is by calling the fingeprinting CLI command and write the report in an output folder.
fingerprint -e http://my.sparql.endpoint.com -o my/output/folder
To use the fingerprinter programmatically, see the API Reference.
Development
Requires Poetry, Docker and (for make check-spec) Node.js.
make install # Poetry env with the test and lint groups
make check-all # lint, types, layers, OpenSpec, unit tests — the gate CI runs
make oxigraph-load-test-data # in-memory Oxigraph on :7878 with the test graphs
make test-e2e # end-to-end tests against it (local only)
See Development.
Contributing
You are more than welcome to help expand and mature this project. We adhere to Apache code of conduct, please follow it in all your interactions on the project.
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the maintainers of this repository before making a change.
Licence
This project is licensed under Apache License 2.0.
1 maintainer
Metadata
1 maintainer
Release files for rdf-fingerprinter 3.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rdf_fingerprinter-3.1.0.tar.gz | 125.9 kB | With provenance | Details for rdf_fingerprinter-3.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rdf_fingerprinter-3.1.0-py3-none-any.whl | Python 3 | none | any | Details for rdf_fingerprinter-3.1.0-py3-none-any.whl |
Total release size: 293.8 kB
Release files / rdf_fingerprinter-3.1.0.tar.gz
| Download URL | rdf_fingerprinter-3.1.0.tar.gz |
|---|---|
| Size | 125.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
23fc935d3557eedfba115b767744b871a09c060e020be08035d3e26e08f72dce
|
|
BLAKE2b-256 checksum How to use checksums |
7ea71f010899c5fd722fa6daa7ef39cc4e686d942eea0607be7c4f501f566c0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 1, 2026.
Transparency logRelease files / rdf_fingerprinter-3.1.0-py3-none-any.whl
| Download URL | rdf_fingerprinter-3.1.0-py3-none-any.whl |
|---|---|
| Size | 167.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7848d03d72257798c5cefc511e30d8ff7b665f36ba350a6dcb58a535ad86e5b5
|
|
BLAKE2b-256 checksum How to use checksums |
b6a43fabfe173b367a1e51df8f4a1fd20dfb24c0417990f4ec431528d9ebee72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 1, 2026.
Transparency logSecurity for rdf-fingerprinter 3.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for rdf_fingerprinter-3.1.0.tar.gz
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 Nov 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
