CG Draft maturity indicator should depend on maturity of draft's normative references
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
This idea is inpired from discussions in this issue back in 2023
W3C has strict requirements for maturity of normative references. If some references in the draft don't meet those requirements, it could be used as a data point when evaluating maturity of the draft itself.
Related idea for a quality of life tool.
When CG draft gets added as input in WG charter, a tool could check all normative references. For any of them that don't meet maturity requirements. It could check if they are also included as inputs in the same WG charter or some other charter. Otherwise it would indicate in WG charter that those normative references will need to be replaced or somehow removed all together.
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 by reading this issue and the linked 2023 discussion in solid/solid-wg-charter#37. Define how normative-reference maturity requirements should be evaluated and how missing or insufficient references should be reported in a WG charter; the work is done when those checks and reporting expectations are specified.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100