Clarify Discovery API scope
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
As discussed in the Discovery TF call on 24.2.2020, the scope of the Scripting API for discovery needs some clarifications vs device lifecycle, discussed in Architecture TF.
There are several types of discovery:
- discovery during onboarding/provisioning (e.g. of unowned devices)
- discovery of Thing directories, during provisioning or in operational mode
- discovery of Things (when in operational mode).
The current API has been designed with 3. in mind, but could be adapted to be used also for 1. and 2.
Related issues:
https://github.com/w3c/wot-discovery/issues/2
https://github.com/w3c/wot-architecture/issues/48
https://github.com/w3c/wot-architecture/issues/425
See also:
Device lifecycle comparisons
WoT Device Lifecycle working draft
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 reviewing the Discovery TF and Architecture TF context, then read related issues 2, 48, and 425 and the linked device-lifecycle documents. Compare the current Scripting API scope with discovery during onboarding, directory discovery, and operational Thing discovery. Done means the supported scope and any needed adaptations are agreed and clearly recorded.
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