Ambiguity in new features for registries versus recommentations
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 262
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Description
Section 6.5.2 of the process says:
Changes that add new features (i.e., class 4 changes) are allowed in all W3C Registries, without needing them to explicitly indicate that this is allowed.
This is fine, but it might be better to add that explicit indicator to all registries so that no one has to dig into the depths of the process to find out why it’s OK for registries but not recommendations.
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 section 6.5.2, the linked correction classes, and the W3C Registry definition in the process document. Review how registries are described and clarify their text so the allowance for new features is explicit; the issue is done when readers no longer need to search the process rules to find that permission.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100