More clarity on where a "candidate addition" lives
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 84
- Forks
- 69
- Avg merge
- 14h 52m
- Merged PRs (30d)
- 2
Description
When taking a spec to Rec that [=allows new features=], it's unclear where "candidate additions" snapshots live.
Consider.
- A Proposed Rec that "allow new features" is published.
- Document is then published as REC
- "New feature" is specified (candidate addition).
Is a "candidate addition" published to TR at a "Working Draft"? Or do they get a special label?
I'm a bit unsure from:
https://www.w3.org/2020/Process-20200915/#candidate-changes
this text in particular:
In addition to their actual maturity level, published REC Track documents with candidate changes are also considered, for the purpose of the W3C Patent Policy [PATENT-POLICY], to be Working Drafts with those candidate changes treated as normative.
I was expecting something like "Candidate Addition Draft" or something similar to a CRD.... if it's just a regular "WD", that works :)
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
Start with the cited W3C Process section on candidate changes and trace how it describes published REC Track documents and Working Draft treatment. Clarify in the Guide whether candidate additions use an existing snapshot or label, with wording that resolves the question without assuming a new document type.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100