@@ -46,4 +46,11 @@ SAP i40-aas is the only framework as of now to explicitly list interaction betwe
[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
To me this seems more like a library than a framework on second thought.
BaSyx seems to at least provide an environment, in which they can host static AAS and those that contain references to submodels elsewhere. They mentioned in a comment under [this YouTube video](https://www.youtube.com/watch?v=nGRNg0sj1oY), that "Right now, [an active AAS] would be realized by having an AAS/Submodel with its own thread. In future, however, we’re planning to provide easy to instantiate classes that would accept, e.g., a Runnable."
I'm not yet quite sure what that means exactly. [here, page 94](https://www.dke.de/resource/blob/778174/cf0125ab96499cb80621518ca642d818/deutsche-normungs-roadmap-industrie-4-0-version-4-data.pdf) BaSyx is described as providing SDKs in Java, C++ and C#, which would make it not a framework in the strict sense again.
The goal of this Project is as far as I understood to provide a Demonstration and Playground for proactive AAS. An active AAS (ie. one that provides live data) can be done with BaSyx, there this would mean that a submodel would have to be implemented on an ESP for example.
I might have to get clarification on this goal.
Proactive AAS might be a lot harder, as I might have to practically reimplement a lot of the spec. either on an ESP directly or as part of some standalone thing. If VDI/VDE 2193-I had to be used that would pose a further roadblock.
