Loading repository data…
Loading repository data…
eclipse-basyx / repository
The Eclipse BaSyx Python SDK, an implementation of the Asset Administration Shell (AAS) for Industry 4.0 systems
A transparent discovery signal based on current public GitHub metadata.
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
The Eclipse BaSyx Python project focuses on providing a Python implementation of the Asset Administration Shell (AAS) for Industry 4.0 Systems.
Please note that the SDK version number is independent of the supported AAS versions!
These are the implemented AAS specifications of the current SDK release, which can be also found on PyPI:
| Specification | Version |
|---|---|
| Part 1: Metamodel | v3.1.2 (01001-3-1-2) |
| Schemata (JSONSchema, XSD) | v3.1.2 (IDTA-01001-3-1-2) |
| Part 2: API | v3.1.1 (01002) |
| Part 3a: Data Specification IEC 61360 | v3.1.1 (01003-a) |
| Part 5: Package File Format (AASX) | v3.1 (01005) |
If you need support to an older version of the specifications, please refer to our prior releases. Each of them has a similar table at the top of the release notes.
This repository is structured into separate packages.
The sdk directory provides the AAS metamodel as Python objects and fundamental functionalities to handle AAS.
The server implements a specification-compliant Docker HTTP server for AASs.
The compliance_tool is a command-line tool for checking whether JSON and XML files comply with the AAS specification.
The BaSyx Python SDK project is licensed under the terms of the MIT License.
SPDX-License-Identifier: MIT
For more information, especially considering the licenses of included third-party works, please consult the NOTICE
file.
The Eclipse BaSyx-Python SDK Team evaluates bi-monthly the newly added commits to the main branch towards the need of releasing a new version. If decided the changes warrant a release, it is initiated, using semantic versioning for the new release number. If the changes do not warrant a release, the decision is postponed to the next meeting.
Additionally, security fixes may be released at any point.
For contributing with issues and code, please see our Contribution Guideline.
To contribute code to this project you need to sign the Eclipse Contributor Agreement (ECA). This is done by creating an Eclipse account for your git e-mail address and then submitting the following form: https://accounts.eclipse.org/user/eca