Be consistent with normative / non-normative sections
Open
@SergeyKanzhelev is already working on this.
Since Jun 30, 2026.
Editorial
privacy-needs-resolution
todo
- Dominant language
- Python
- Stars
- 510
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
See https://lists.w3.org/Archives/Public/public-trace-context/2020Feb/0004.html
A few sections of the document are marked as non-normative, but then their subsections include many direct normative requirements. The Problem Statement and Solution sections (which read to me as non-normative overviews) are not marked as non-normative. I don’t really have any strong feelings about use of non-normative section headers, I’m just passing on that the distinctions in the current spec are confusing.
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.
Assessment
This issue has not been assessed yet.