Discovery of exposed Things on the same runtime - Issue 233 from w3c/wot
Open
Nobody has claimed this yet.
discovery
for next iteration
priority: low
use case
Waiting for other Taskforce
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
This is a rather issue coming over from w3c/wot at https://github.com/w3c/wot/issues/233
There is also a somewhat related issue at node-wot at https://github.com/eclipse/thingweb.node-wot/issues/160
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 linked w3c/wot issue 233 and the related node-wot issue 160, then compare their discussion with this issue. The work needs clarified requirements and an agreed definition of the discovery behavior before implementation can be scoped or considered done.
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