A slightly opinionated, common set of 'rules' for creating rdf data using 'rdf-engine':
- Data Rules: for loading tables (csv), hierarchical (json), and rdf (ttl).
- Mapping rule: SPARQL construct
- Ontology rules: Inference and validation using TopQuadrant
These rules come together in the 'engine'.
Development
Develop with uv sync --all-packages --all-extras.
Run python tasks.py stamp_ver before pypi publishing.
Design Choices
These are choices given the common use case of mapping data to an ontology. They are somewhat firm.
- RDF1.2 annotates tripes with metadata as
<<?s ?p ?o>> ?mp ?mowhere?mpand?mocorrespond to simple (key,value) pairs of metadata. - Mappings are in the form of SPARQL constructs
stored as files with a
.mapping.rqextension (can also be.mapping.sparql). - Each (specified) ontology will be processed separately.
- By default, no assumption about data identifier uniqueness is made:
A random unique identifier node,
with the default 'anon.id' prefix 'urn:rdf-rules:anon🆔',
will be created to identify data (table 'rows' or json data).
It is the user's responsibility to make 'nice' named nodes:
This can be by making a 'rule' to SPARQL
constructnodes or by specifyingjson2rdf_options={'subject_id_keys': {'id'}, id_prefix=(..., ...) }argument for Table or JSON data rules. With these options, nodes can be made unique over all data.
Usage
Examine how rules are fed into an engine in the tests. The common workflow is:
-
Specify rules. Each rule is constructed by providing arguments to
mkrule.mkruleprocesses objects such as file paths and data objects. A distinction is made for 'data rules'; These are only triggered once in the beginning. -
Specify engine run parameters. See
runfunction documentation. -
Extract data subsets with queries. 'System' queries are
mapped_and_inferredandvalidation(results). It's best to extract these using thequeryfunction as they slightly depend on configuration.
1 maintainer
Metadata
1 maintainer
Release files for rdf-rules 2026.8.73
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rdf_rules-2026.8.73.tar.gz | 9.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rdf_rules-2026.8.73-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.7 kB
Release files / rdf_rules-2026.8.73.tar.gz
| Download URL | rdf_rules-2026.8.73.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf0ae884911c2ca38ff55b1d018a7c0a2999d58a1ed049caa556efa5772ef3d6
|
|
BLAKE2b-256 checksum How to use checksums |
77247bfec1268a5f1c95f54b760b7e0ad0c26cce1a3a62cdac11851d4a16fd71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 31, 2026.
Transparency logRelease files / rdf_rules-2026.8.73-py3-none-any.whl
| Download URL | rdf_rules-2026.8.73-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c122c34936a4dfb28c9adff41ee41464e7fac08f250302620fcf2b651e03df3
|
|
BLAKE2b-256 checksum How to use checksums |
f88cf6e5b37d3df165697a199acf3fc4c681c860d44412c6c9f38d4537e9bc7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 31, 2026.
Transparency log
