| ... | ... | @@ -39,3 +39,11 @@ aas.backend might be a way to provide active or even proactive AAS, I'll need to |
|
|
|
"Main features include: [...] Enable interactions between administration shells based on semantic protocols (VDI/VDE 2193-1)" [[2](https://github.com/SAP/i40-aas#main-features)]
|
|
|
|
Interaction between AAS AFAIK requires at least one proactive partner.
|
|
|
|
The BaSyx Project classes "VDI/VDE 2139 [as] a language for type 3 AAS." [[1](https://wiki.eclipse.org/BaSyx_/_Documentation_/_AssetAdministrationShell)]
|
|
|
|
|
|
|
|
## Deciding with which frameworks to continue
|
|
|
|
|
|
|
|
SAP i40-aas is the only framework as of now to explicitly list interaction between AAS as a feature. It doesn't implement v3 of the specification though. Further it is written in a language I'm unfamiliar with. While this is a personal shortcoming on my part it's still relevant to the decision as success of this project is the most important requirement overall.
|
|
|
|
[Last significant commit](https://github.com/SAP/i40-aas/commit/525e844711bd1a51ea2365f0106d7f9aa60e28b6) was a merge on 2021-01-15 with open issues. To me this indicates a stale (or "done") project, as they might be waiting for v3 to release.
|
|
|
|
|
|
|
|
PyI40AAS does have an active branch implementing AAS v3. Using `aas.backend` as a way to implement communication between AAS might be at best considered a hack, as this submodule is intended for "integrating data from existing systems into AAS objects" [That is very hard to cite! Its part of `docs/build/backend/index.html` of their documentation, which doesn't seem to be publicly hosted, AFAIK it's only available as a build artifact .zip [eg. here](https://git.rwth-aachen.de/acplt/pyi40aas/-/jobs/2060272/artifacts/download)]
|
|
|
|
To me this seems more like a library than a framework. |
|
|
\ No newline at end of file |
