AAS Compliance Tool
An AAS compliance checker based on the Eclipse BaSyx Python SDK for testing xml and json files. Following functionalities are supported:
- create an xml or json file compliant to the official schema containing example Asset Administration Shell elements
- create an aasx file with xml or json files compliant to the official schema containing example Asset Administration Shell elements
- check if a given xml or json file is compliant to the official schema
- check if a given xml, json or aasx file is readable even if it is not compliant to the offical schema
- check if the data in a given xml, json or aasx file is the same as the example data
- check if two given xml, json or aasx files contain the same Asset Administration Shell elements in any order
Invoking should work with either python -m aas_compliance_tool.cli or (when installed correctly and PATH is set
correctly) with aas-compliance-check on the command line.
For further usage information consider the aas_compliance_tool-package or invoke with
python -m aas_compliance_tool.cli --help respectively aas-compliance-check --help.
Metadata
Release files for aas-compliance-tool 1.0.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 |
|---|---|---|---|---|
| aas_compliance_tool-1.0.0.tar.gz | 25.0 kB | Without provenance | Details for aas_compliance_tool-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aas_compliance_tool-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for aas_compliance_tool-1.0.0-py3-none-any.whl |
Total release size: 51.4 kB
Release files / aas_compliance_tool-1.0.0.tar.gz
| Download URL | aas_compliance_tool-1.0.0.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d4c855674076642005f14ac9a30a227b63a4b6344440ddabda0bc7a4ae00fde
|
|
BLAKE2b-256 checksum How to use checksums |
91fff08ee506babd2a5b16189388bf731c33004bf581ca88c66080b0e37c365f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Release files / aas_compliance_tool-1.0.0-py3-none-any.whl
| Download URL | aas_compliance_tool-1.0.0-py3-none-any.whl |
|---|---|
| Size | 26.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4b134727cb7be189509c43aad3a9a1bcb9b88cfc8442f029748a90c49bd59b2f
|
|
BLAKE2b-256 checksum How to use checksums |
4ae88aa3cb2a327bacaf866aaf85aeb90157b235030ba55eac2e7db4339317cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.0.0 CPython/3.12.2
|
Security for aas-compliance-tool 1.0.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.