use of markdown style [@!RFC9901] references
Open
Nobody has claimed this yet.
editorial
- Dominant language
- Python
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The current draft doesn't use the normal [@!RFC9901] to track normative/informative references, and the normative references section is currently empty.
I think not using the normal mechanism might've been deliberate as it might not be compatible with keeping the doc in ISO format but I don't think we ever discussed that or looked at options.
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 reviewing the current draft's reference syntax and the empty normative references section. Check whether [@!RFC9901] references can coexist with the ISO format, then document the chosen approach and populate the normative references section as appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100