Rechartering Input from the TD TF
Open
Nobody has claimed this yet.
WG Charter 2026
- Dominant language
- HTML
- Stars
- 234
- Forks
- 136
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 9
Description
No big changes for the TD TF related deliverables in content but its management has changed in an important way. Below are the inputs we have from the TD call of 07 August 2025:
Normative Documents:
- TD 2.0
- Alignment with other specs (arch, discovery)
- New features: Initial Connection, Manageable Affordances, Data Mapping
- Establishing a User Story driven feature development
- WoT Bindings Registry on the W3C Registry Track
- Establishing the registry document
- Establishing the mechanical process to accept entries
Informative Documents:
- Individual Group Notes each binding written by the WG
- Working on adapting the documents to the registry requirements
- Doing the testing needed for each document
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. First determine where rechartering inputs for the TD TF are recorded, then review the listed normative and informative deliverables against that record. Done means the management change and all stated deliverables are accurately reflected in the appropriate project documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100