antelope
Standard Interface and reference framework for LCA
The antelope package is an interface specification for accessing LCA data resources.
The goal of the Antelope project is to reduce the complexity of LCA along three central
fronts:
- Reduce complexity of modeling by providing a simple, recursive data structure (the fragment) that can effectively describe complex, dynamic LCA models;
- Reduce complexity of software by liberating users from costly and cumbersome desktop LCA software applications and relocating reference data to the cloud, without compromising computational sophistication;
- Reduce complexity of communication by providing online tools for describing and sharing LCA models that conceal or omit confidential and proprietary information.
Principles
The Antelope framework is distributed by design, intended to allow data owners to independently create and manage their own intellectual property, allowing access by others while regulating what can be seen and concealed.
Antelope provides a hosting platform for working online and sharing information within a trust network. User-owned data is managed by owners, while reference data is curated by the user community.
Antelope uses separation of concerns to help organize different computational facets of the LCA problem into separate services.
Documentation
Coming to github.io
See Also
- vault.lc Home to the Antelope authentication service
- antelope_core The reference implementation including local data source management.
- antelope_background Used for partial ordering of databases and construction and inversion of matrices
- antelope_foreground Used for building foreground models
Metadata
Release files for antelope-interface 0.3.5.1
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 |
|---|---|---|---|---|
| antelope_interface-0.3.5.1.tar.gz | 63.0 kB | Without provenance | Details for antelope_interface-0.3.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| antelope_interface-0.3.5.1-py3-none-any.whl | Python 3 | none | any | Details for antelope_interface-0.3.5.1-py3-none-any.whl |
Total release size: 134.7 kB
Release files / antelope_interface-0.3.5.1.tar.gz
| Download URL | antelope_interface-0.3.5.1.tar.gz |
|---|---|
| Size | 63.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a31e4af734ba7d62b3f721ec23c41fae50a5aae7e215f9637068b266a07d92d
|
|
BLAKE2b-256 checksum How to use checksums |
a990678ad3d40f03fd7426a0bbacc41f4b2c9fd767847c95b718de07373500ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Release files / antelope_interface-0.3.5.1-py3-none-any.whl
| Download URL | antelope_interface-0.3.5.1-py3-none-any.whl |
|---|---|
| Size | 71.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09a01ac9d32d69319a63ad656aad4a166bdeb7305b285dd8a97e1221f5dda9b0
|
|
BLAKE2b-256 checksum How to use checksums |
c2463bd7595da1b76cad571cb46bb9ec2f4904828ffe5ad27e6b74d6bf5baee8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Security for antelope-interface 0.3.5.1
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.