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
Currently, Vorto converts an (information) model to a platform specific output format using code generators with the support of mapping definitions. This process is uni-directional.
The problem in that is that you cannot re-verse lookup a model from this mapped output in order to find out from which Vorto Model it originated. This issue ought so solve this problem.
A possible use case is for example , when a LWM2M server receives a message containing a specific object ID and payload, the server could ask Vorto to lookup the function block associated with the Object ID and validate its payload.
A second use case would be that a message sent in one format (known to Vorto) can be converted into another Vorto-known platform format (on-the-fly).
The text was updated successfully, but these errors were encountered:
Currently, Vorto converts an (information) model to a platform specific output format using code generators with the support of mapping definitions. This process is uni-directional.
The problem in that is that you cannot re-verse lookup a model from this mapped output in order to find out from which Vorto Model it originated. This issue ought so solve this problem.
A possible use case is for example , when a LWM2M server receives a message containing a specific object ID and payload, the server could ask Vorto to lookup the function block associated with the Object ID and validate its payload.
A second use case would be that a message sent in one format (known to Vorto) can be converted into another Vorto-known platform format (on-the-fly).
The text was updated successfully, but these errors were encountered: