w3c / w3c/wot-scripting-api

[Use-case] WoT in the Browser

Open
#566 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
45
Forks
21
PR merge metrics
No merged PRs in 30d

Description

This is a feature proposal, need a user story (and MAYBE a new use case) to define what it is for. Should discuss with node-wot and the Scripting API TF (who would probably be the ones submitting use cases and user stories).
@danielpeintner @zolkis @relu91

Originally posted by @mmccool in #3

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 original use-case discussion in wot-usecases issue #3 and the references to node-wot and the Scripting API TF. Define the browser user story, decide whether a new use case is needed, and record the agreed proposal after discussion with the named participants.

Written by the indexing model from the issue text.

Assessment

Domain
api, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.