Open arnoweiss opened 9 months ago
Hi @arnoweiss , I believe that this has been discussed multiple times in the IDTA workgroup.
@s-heppner @sebbader-sap can you maybe provide more information?
@arnoweiss we are also working on formalizing the meta-model part 2 and then transpiling it into server stubs and client implementations (in different languages × different protocols).
It's not only about data structures, but we also want to transpile the pre and postconditions of the operations.
All that is great and will make server-development a lot easier. However, I'm just looking for json-schemas to validate shell-descriptors. That's very basic but still unavailable to the community. Will those schemas be a byproduct of generating the server-stubs?
@arnoweiss wrote:
Will those schemas be a byproduct of generating the server-stubs?
Yes, we plan that as well (+ OpenAPI, OPC UA nodeset and other interface schemas).
In the meanwhile, if you already want to start working on it, we can schedule a call and synchronize.
Multiple times, I've faced the issue that I was looking to validate the schema of incoming requests carrying AssetAdministrationShellDescriptor or SubmodelDescriptor objects - both specified in Pt. 2. The only machine-readable definition is contained in the openApi-files of the aas-specs-api repository. However, the openApi file format has only a fraction of the descriptive power that shacl/xsd/json-schema have. Adding the classes here would also with the push of a button allow to generate examples.
Have y'all thought about adding this? What was the reasoning for leaving them out?