You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @e-grigorov
You are right, the DSL does not make any separation between these different container types.What would speak against putting this information into the mapping model for the device ?
I can imagine that there is a Functional Item Mapping file , that maps the (abstract) FB to the platform-specific Functional Item platform.
The mapping file is a platform/generator specific and it's possible to cover almost everything. To me, the question is: is it a platform specific feature? Does it mean that the pure Java generator has to do the same?
From the Vorto modelling perspective, I wouldnt necessarily care if a multiple property is of type collection or array. This is implementation/platform specific. In the platform, I would need this information in order to process the device data correctly. The platform mapping, e.g. FunctionalItems would map this concrete to FI Basic types. The FI Generator would use this information and generate the Java source code.
Does it mean that the pure Java generator has to do the same?
If the Java Generator belongs to the same platform, then yes.
I just realized that I am mapping semantically different data containers with the same keyword - multiple. For example:
What is the correct mapping from your point of view?
The text was updated successfully, but these errors were encountered: