home.md

@@ -18,3 +18,24 @@ Currently, this project is planned to happen in the following stages:
 1. [BaSyx](https://wiki.eclipse.org/BaSyx)
 2. [PyI40AAS](https://git.rwth-aachen.de/acplt/pyi40aas/-/tree/improve/V30RC02)
 3. [SAP i40-aas](https://github.com/SAP/i40-aas)
+
+## Checking requirements per framework
+### Implementing RC for AAS v3
+#### BaSyx
+The [releases Page](https://wiki.eclipse.org/BaSyx_/_Releases_and_Features) claims Support for v2.0.1 for Java Release 1.0, the only existing release as of date. Implementation for v3 is planned in Java Release 2.0.
+#### PyI40AAS
+[This Branch](https://git.rwth-aachen.de/acplt/pyi40aas/-/tree/improve/V30RC02) is the ongoing implementation for RC2 of v3
+#### SAP i40-aas
+As per [This comment](https://github.com/SAP/i40-aas/issues/150#issuecomment-653456569) they are currently working on support for v2.
+
+### Support for active and proactive AAS
+#### BaSyx
+BaSyx claims support for all three kinds of AAS. As far as I understood it, a Submodel can live anywhere and only needs to expose an API via eg. REST.
+"BaSyx provides server components that can host Type 1 AAS. Type 2 AAS can be hosted on a shared AAS server, or they can be deployed as individual executables in the system." [[1](https://wiki.eclipse.org/BaSyx_/_Documentation_/_AssetAdministrationShell)] I take from this that proactive AAS are supported, but they need to register themselves and may live anywhere in the system.
+#### PyI40AAS
+aas.backend might be a way to provide active or even proactive AAS, I'll need to evaluate this.
+
+#### SAP i40-aas
+"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)]
\ No newline at end of file