TD common definition and affects on formIndex
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 45
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
@relu91 @danielpeintner I have added that TD as example but not as recommended as we don't want to encourage that as generic mechanism. I also now think that indicating formIndex in ScriptingAPI will not work nicely in compacted TDs that the developer sees. They would need to say that they prefer the form with this form/connection definition
Originally posted by @egekorkan in https://github.com/w3c/wot-thing-description/issues/2163#issuecomment-3607266515
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 referenced issue #2163 and the discussion about common Thing Description definitions, compacted TDs, and formIndex in the Scripting API. The issue does not identify files, tests, or a settled expected behavior, so the work is not complete until the desired API direction and acceptance criteria are agreed.
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