Behavior of affordances
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
@egekorkan mentioned during todays TPAC meeting that the Scripting API taskforce might want to look into the following aspects:
What is the behavior/result of some affordances?
He was pointing at the web-thing-protocol that has notes for some of the expected behaviors.
e.g.,
Personally, I am not sure if it is really a scripting topic. I think it goes way beyond scripting. What do others think?
Anyhow, having guidance/rules or a way to clarify what a certain affordance may trigger seems reasonable.
It may differ depending on the binding also...
What is the right place to work on it?
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 by reading the behavior notes in the linked web-thing-protocol and reviewing the TPAC discussion referenced in the issue. Determine whether affordance behavior belongs in the Scripting API or another WoT specification, including how bindings affect it. Done means an agreed location, scope, and guidance for defining affordance results.
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
- 25/100