Use-case for selecting the preferred binding for a given interaction or all interactions
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
The scripting API allows for providing a formIndex.
see https://w3c.github.io/wot-scripting-api/#dom-interactionoptions-formindex
This optional index may define the interaction to be used.
In the scripting call today it was found that we should look into use-cases that demand this feature.
Use-cases that were mentioned:
- consumer can choose the desired binding
- consumer can choose the desired security (e.g., prefer stronger security)
Are there any other use-cases that require this feature?
Having said that, in the ideal case a consumer should not need to deal with parsing the TD and pick a specific form(Index).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the W3C Scripting API definition of InteractionOptions.formIndex and review the use cases listed in this issue: choosing a binding or stronger security. Identify any additional cases that require selecting a form, then document whether the optional feature is necessary and how consumers should use it.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100