Another Question that I have. Currently Vorto allows us only to define the „capabilities“ or „properties“ of a device but we do not have a chance to define how a „gateway“ could access them (e.g. "read from address xyz“). So I see the need for
This would help us to get rid of client side code generation in some (standardized) environments. This would especially make sense in areas like IIoT (usually always PLCs to address) or think of the Bosch DYI products which I guess, have often times similar hardware with a standardized Layout and API.
@JulianFeinauer if I understand your question correctly you are asking, how platform-specific information (i.e. which address the gateway needs to use) can be added to a functionblock?
That's something that could be done with Functionblock mappings, I think. They can be used to add additional platform-specific information to a functionblock.
Here is an example how that currently looks in Vorto:
A Functionblock: https://vorto-dev.eclipse.org/#/details/com.kevin.official.test:VehicleGearFb:1.0.0
and the corresponding mapping that adds platform-specific information: https://vorto-dev.eclipse.org/#/details/com.kevin.official.test:VehicleGearCANMapping:1.0.0
To see the result you can use this API: GET https://vorto-dev.eclipse.org/api/v1/models/com.kevin.official.test.VehicleGearFb:1.0.0/content/CAN
Does this fulfil that requirement or did I misread your question?