AAS compliance checker based on the Eclipse BaSyx Python SDK
Project description
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 official 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
Installation
Default installation
Install the latest release from PyPI:
pip install basyx-compliance-tool
Developer installation
When working from a checkout of this repository, install the sibling SDK from the source tree first, then the compliance tool:
pip install ./sdk
pip install ./compliance_tool
Installing the local SDK first is what lets the tool check against your in-development metamodel: pip keeps the
already-installed local SDK instead of pulling a release from PyPI.
[!IMPORTANT] The compliance checks are only as current as the installed
basyx-python-sdk— the tool reports compliance against whatever metamodel version that SDK implements, not against the version named in this README. Because the dependency is currently declared loosely (basyx-python-sdk>=1.0.0),pipwill not replace an SDK that is already installed and satisfies that constraint, even if it is older than the one you intend to test against. This happens silently, with no error. To be sure you are checking against the intended metamodel, install or upgrade the SDK explicitly, e.g. the local source tree withpip install ./sdkor a specific release withpip install --upgrade "basyx-python-sdk==2.1.0".This manual version matching is a temporary workaround; see #592.
Usage
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.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file basyx_compliance_tool-2.1.0.tar.gz.
File metadata
- Download URL: basyx_compliance_tool-2.1.0.tar.gz
- Upload date:
- Size: 20.4 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
9d903feb9b8a302957ac6d1facb7037729bc5fda51f499494c085960e68b2db3
|
|
| MD5 |
091158f94bf13625b274093bed628b78
|
|
| BLAKE2b-256 |
76ee5265db127f6dd863c9814c25bbade09fd648ac762bcce72133cadd734111
|
File details
Details for the file basyx_compliance_tool-2.1.0-py3-none-any.whl.
File metadata
- Download URL: basyx_compliance_tool-2.1.0-py3-none-any.whl
- Upload date:
- Size: 18.9 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
0870f61f1bdbac81f280058441efffa706f2953316bc51c5bcc29641bc2a0bab
|
|
| MD5 |
8c4c553a3dc5e247b1f3e69f0cb31d5d
|
|
| BLAKE2b-256 |
34fcd5ab3cf42b3e80c3de0e7b979e6281f5f7067156eb649660801fe5eee71b
|