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
Explore ways in which systems based on Vorto models can interoperate with WoT systems.
A Vorto repository stores and manages models; a WoT TD directory stores and manages WoT TDs describing device instances.
See if Vorto can be incorporated into PoCs, i.e. for EdgeX, etc.
Define the relationship between TDs (describing device instances) and Vorto models (describing classes of devices)
this should be consistent with other approaches to specify models (also ODM SDF, and TDTs)
proposal: use links (already in TDs), define relation types like "instanceOf" (need to look into existing IANA that might work here)
probably need registered IANA MIME contentType for Vorto models
Can TDTs be stored in Vorto repositories?
Can TDTs be automatically generated from Vorto models?
Can TDs be automatically generated from Vorto models, given some additional parameters (protocol binding information)?
Can a bidirectional translation be achieved?
Other:
Investigate whether Scripting API discovery filters using partial TD templates is suitable for "semantic discovery"
The text was updated successfully, but these errors were encountered:
Should look at this again in Discovery 2.0. One issue is that Vorto deals with Models, not instances, and we don't currently store models in directories. But we might in the next version.
Explore ways in which systems based on Vorto models can interoperate with WoT systems.
A Vorto repository stores and manages models; a WoT TD directory stores and manages WoT TDs describing device instances.
Other:
The text was updated successfully, but these errors were encountered: