Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make selection of specific form element available #8

Open
eileenoo opened this issue May 28, 2020 · 3 comments
Open

Make selection of specific form element available #8

eileenoo opened this issue May 28, 2020 · 3 comments
Labels
enhancement New feature or functionality

Comments

@eileenoo
Copy link
Collaborator

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.

@eileenoo eileenoo added the enhancement New feature or functionality label May 28, 2020
@egekorkan
Copy link
Member

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:

  1. Question: How to choose the binding to use on client side when thing description has several ? eclipse-thingweb/node-wot#199
  2. Fix property interaction algorithms to correctly handle Forms, contentType and DataSchema w3c/wot-scripting-api#201

@egekorkan
Copy link
Member

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.

@eileenoo
Copy link
Collaborator Author

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:

  1. eclipse/thingweb.node-wot#199
  2. w3c/wot-scripting-api#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 agree.
It is not an easy thing to implement and some more thoughts have to be put into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or functionality
Projects
None yet
Development

No branches or pull requests

2 participants