RDF-Engine
Why?
Motivation: This was developed as part of BIM2RDF where the conversion from BIM to RDF is framed as 'mapping rules'.
How?
Rules are processes that generate triples. They are simply applied until no new triples are produced. Oxigraph is used to store data.
A rule is defined as a function that takes an Oxigraph instance and returns quads.
Features
- Handling of anonymous/blank nodes: They can be deanonimized.
- Oxigraph can handle RDF-star data and querying. However, if
Usage
A 'program' is defined as a sequence of engine runs initialized by a `db'. Each engine run takes:
- (engine)
params - and a list of
rules. Each rule needs amodule,maker, andparams. See program example in test script.
Development Philosophy
- KISS: It should only address executing rules. Therefore, the code is expected to be feature complete (without need for adding more 'features').
- Minimal dependencies: follows from above.
- Explicit > Implicit: Parameters should be specificed (explicitly).
3 maintainers
Metadata
3 maintainers
Release files for rdf-engine 191
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_engine-191.tar.gz | 6.7 kB | With provenance | Details for rdf_engine-191.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rdf_engine-191-py3-none-any.whl | Python 3 | none | any | Details for rdf_engine-191-py3-none-any.whl |
Total release size: 15.4 kB
Release files / rdf_engine-191.tar.gz
| Download URL | rdf_engine-191.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11892dee1bc7ddd27d59a9424e9391a87ba8167bcc242de057de52ab056146bd
|
|
BLAKE2b-256 checksum How to use checksums |
833537cb89200cfaf8ee7a17464299c5daf6cd252cee1e8c837cbbde9fd8cac7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Jan 2, 2025.
Transparency logRelease files / rdf_engine-191-py3-none-any.whl
| Download URL | rdf_engine-191-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9713cb5ab9a34543acc63ee373eec1fa67d0e48684d12b156922df0bb5b18df
|
|
BLAKE2b-256 checksum How to use checksums |
78a48e445207a66df8cbba98ac4de3c068a2171ba630b60ad7015eec495f1a0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
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 Jan 2, 2025.
Transparency logSecurity for rdf-engine 191
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_engine-191.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 Jan 2, 2025.
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.
