Overview: pyerk
Pyerk is the python implementation of the emergent representation of knowledge framework.
- 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 instaead of declarative knowledge representation
Pyerk originated and is currently (2022) mainly developed with focus on representing knowledge from the domain of control theory as part of the Automatic Control Knowledge Repository (ACKREP). However, in principle, it aims to be applicable wo a wide range of domains.
Assumed Directory Structure
<erk-root>/
├── pyerk/ ← repo with the code of the core package
│ ├── .git/
│ ├── README.md ← the currently displayed file (README.md)
│ ├── setup.py ← deployment script
│ ├── src/pyerk/auxiliary.py ← module containing function get_erk_root_dir()
│ └── ...
│
├── django-erk-gui/ ← repo with the code for the django gui (project and! app)
│ │ (this package is optional)
│ ├── .git/
│ ├── manage.py
│ └── ...
│
├── erk-data/ ← directory that contains erk-knowledge packages (for actual usage)
│ ├── ocse/ ← a knowledge package (ontology of control systems engineering)
│ │ ├── .git/
│ │ ├── README.md
│ │ ├── ocse.py ← a knowledge module
│ │ │ (this one is currently used for unit testing)
│ │ └── ...
│ ├── xyz123/ ← another knowledge package
│ │ └── ...
│ └── ...
├── erk-data-for-unittests/ ← directory that contains erk-knowledge packages
│ └── ... (unittest version, probably older and different from
│ production data.)
└──...
Documentation
Rudimentary documentation is available at https://pyerk-core.readthedocs.io (generated from the /docs directory). To get an overview of the most importent features you might also want to have a look at the source code, especially at the files builtin_entities.py and the test_core.py.
Coding style
We use black -l 120 ./ to ensure coding style consistency.
Metadata
Release files for pyerk 0.9.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 |
|---|---|---|---|---|
| pyerk-0.9.0.tar.gz | 178.1 kB | Without provenance | Details for pyerk-0.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyerk-0.9.0-py3-none-any.whl | Python 3 | none | any | Details for pyerk-0.9.0-py3-none-any.whl |
Total release size: 280.3 kB
Release files / pyerk-0.9.0.tar.gz
| Download URL | pyerk-0.9.0.tar.gz |
|---|---|
| Size | 178.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84f456df6f7446cb91506db7472d73a54ae6e03891f39798d356228cc989f13a
|
|
BLAKE2b-256 checksum How to use checksums |
8353cba83917a839173f0f7811463965d1aad71faf89674f6a3a59d87d0e7fe6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / pyerk-0.9.0-py3-none-any.whl
| Download URL | pyerk-0.9.0-py3-none-any.whl |
|---|---|
| Size | 102.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
280f8e47a1a35d6803d87315774038a9d801c693079cc1c30813f8e036934644
|
|
BLAKE2b-256 checksum How to use checksums |
802f70e9a18990eead968948b86f9581ddec841a44bbe3984cac2851c983aa14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for pyerk 0.9.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.