wade
wade copied to clipboard
tum-esi
Make selection of specific form element available
Node-wot automatically selects the first available form of an interaction affordance. Therefore, users aren't able to select a specific form nor protocol This needs to be implemented.
A possible solution / workaround for now: before consuming the TD remove all form elements and only leave the desired one.
When users can select the form/ protocol, the dynamic- and staticTiming elements need to be added to the specific form element.
I support this, however, how will the user select the forms? This is also being discussed in node-wot and scripting api. The relevant issues are below:
- https://github.com/eclipse/thingweb.node-wot/issues/199
- https://github.com/w3c/wot-scripting-api/issues/201
It could also be that two forms are both HTTP but one is a local IP and the other one is a WWW URI that needs Internet access. node-wot is not able to choose one or the other based on which one it can access.
Hopefully, we will not see this for a while but it can also be that for eventing, one form can have something like HTTP longpoll whereas the other one has proper eventing with websub, sse etc.
I support this, however, how will the user select the forms? This is also being discussed in node-wot and scripting api. The relevant issues are below:
It could also be that two forms are both HTTP but one is a local IP and the other one is a WWW URI that needs Internet access. node-wot is not able to choose one or the other based on which one it can access.
Hopefully, we will not see this for a while but it can also be that for eventing, one form can have something like HTTP longpoll whereas the other one has proper eventing with websub, sse etc.
I agree. It is not an easy thing to implement and some more thoughts have to be put into it.