w3c / w3c/wot-scripting-api

Explore directory process

Open
#526 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discovery
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:

  1. Is the directory URL supposed to be the directory's Thing Description? Or is it supposed to point to a resource related to the things property of the directory?
  2. 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 things property? 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.