| Re: [basyx-dev] Hello World! |
|
Dear Julian, we’re currently working on a TCK. Most of the tests for core components (providers, registry, …) are already set up in a way to be reusable as TCK (e.g. org.eclipse.basyx.testsuite.regression.aas.registration.TestRegistryProviderSuite)
. Thus, arbitrary implementations can be validated against the test cases, even from different SDKs as long as they expose an HTTP endpoint. Additionally, we’re currently working on an OpenAPI specification of interfaces and AAS metamodel. When this is done, we’ll update the project wiki accordingly. Best regards, Frank ---------------------------------------------------------------------------------- M.Sc. Frank Schnicke Project Manager Embedded Software Engineering Fraunhofer IESE
Fraunhofer-Platz 1 | 67663 Kaiserslautern
Phone: +49 631 / 6800-2259 | Fax: +49 631 / 6800-9-1199 Von: basyx-dev-bounces@xxxxxxxxxxx <basyx-dev-bounces@xxxxxxxxxxx>
Im Auftrag von Julian Feinauer Hi folks, my name is Julian and I took a deeper look into BaSyx (and also BaSys and RAMI 4.0) in the last weeks. I work a lot in the industrial area doing „digitalization“ and „industry 4.0“
and we heavily rely on open source projects (mostly Apache and Eclipse). So far I quite like the concept I saw and the Demo Examples also look good. Do you plan on releasing some kind of TCK (technical compatibility kit) and standard interfaces where others could implement their solutions against? I really liked the way reactive streams approached this in java (https://en.wikipedia.org/wiki/Reactive_Streams). First, they did a specification and then they provided vendor independent java interfaces as a module with a clear contract for each method and the overal behavior. To ensure that, they provieded a TCK that every implementation could check against. I think this would be a good way to push the BaSys Konzepts as well. Do you altreay plan such things? Best! |