Overview: pyirk
Pyirk is a Python framework for imperative representation of knowledge.
- Designed to formally represent knowledge (including meta levels)
- Implementation-status: "early alpha"
- Inspired by OWL, but much more expressive
- ... at the cost of guarantied computability
- Inspired by Wikidata, but much simpler
- Inspired by SUO-KIF, but with less brackets
- Represented directly in python: → imperative instead of declarative knowledge representation
While pyirk aims to be applicable to a wide range of knowledge domains, its origin an its current (2023) main focus is the representation of knowledge from the domain of control theory as part of the Automatic Control Knowledge Repository (ACKREP). Thus, a subset of the Ontology of Control Systems Engineering is used as test data for pyirk. In fact, both projects are practically co-developed.
Not that, originally pyirk (imperative representation of knowledge) was called pyerk (emergent representation of knowledge), in case you come across some old version.
Recommended Directory Structure
<irk-root>/
├── pyirk-core/ ← repo with the code of the core package
│ ├── .git/
│ ├── README.md ← the currently displayed file (README.md)
│ ├── setup.py ← deployment script
│ ├── src/pyirk/auxiliary.py ← module containing function get_irk_root_dir()
│ └── ...
│
├── django-irk-gui/ ← repo with the code for the django gui (project and! app)
│ │ (this package is optional)
│ ├── .git/
│ ├── manage.py
│ └── ...
└──...
Documentation
Rudimentary documentation is available at https://pyirk-core.readthedocs.io (generated from the /docs directory). To get an overview of the most important features you might also want to have a look at the source code, especially at the files builtin_entities.py and the test cases, e.g., test_core.py.
Coding style
We use black -l 120 ./ to ensure coding style consistency.
Metadata
Release files for pyirk 0.12.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 |
|---|---|---|---|---|
| pyirk-0.12.0.tar.gz | 205.9 kB | Without provenance | Details for pyirk-0.12.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyirk-0.12.0-py3-none-any.whl | Python 3 | none | any | Details for pyirk-0.12.0-py3-none-any.whl |
Total release size: 318.6 kB
Release files / pyirk-0.12.0.tar.gz
| Download URL | pyirk-0.12.0.tar.gz |
|---|---|
| Size | 205.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9fb5798b43f442260c203eec0b9826462807ebfa019c0f556aafdc2e34b26921
|
|
BLAKE2b-256 checksum How to use checksums |
55db8fb89073b6512e1297f37afcf6d1151975b9a3d00d4dd1ee352dd80c2639
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / pyirk-0.12.0-py3-none-any.whl
| Download URL | pyirk-0.12.0-py3-none-any.whl |
|---|---|
| Size | 112.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
707be0a5a97d7a43c3f1a5580edb88278e58f065d67b26c62c96f0b84b39d7c2
|
|
BLAKE2b-256 checksum How to use checksums |
6873216e2fea6bc459a440a2734f2df8888531376efe03c306725ea39887c890
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for pyirk 0.12.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.