Explore directory process
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Hi everyone :) I was dealing with implementing directory discovery in dart_wot lately and I was wondering a bit about how exactly the process should work here:
- Is the directory URL supposed to be the directory's Thing Description? Or is it supposed to point to a resource related to the
thingsproperty of the directory?- In the case that the URL is supposed to point to the TDD's Thing Description, should the implementation first consume the TD and then read the
thingsproperty? Or is this implementation-specific?Sorry if the answer to these questions should be obvious, unfortunately, I haven't really been able to follow the discussions in the TF in detail for the last couple of months :/ In any case: Thank you! :)
Originally posted by @JKRhb in https://github.com/w3c/wot-scripting-api/issues/364#issuecomment-1554391976
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 two directory-URL and Thing Description questions in this issue, then read the linked discussion in w3c/wot-scripting-api#364. Resolve whether discovery consumes the directory Thing Description and reads its things property; done means the expected process is agreed for dart_wot implementers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100