Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Be consistent with normative / non-normative sections #396

Open
danielkhan opened this issue Mar 25, 2020 · 2 comments
Open

Be consistent with normative / non-normative sections #396

danielkhan opened this issue Mar 25, 2020 · 2 comments
Labels
Editorial The reported issue can be addressed with an editorial change. This tag could be combined with others privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. todo
Milestone
7. level-2

Comments

@danielkhan
Copy link
Contributor

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.
@plehegar plehegar added the privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. label Mar 27, 2020
@plehegar plehegar mentioned this issue Mar 30, 2020
Open
@plehegar plehegar added Editorial The reported issue can be addressed with an editorial change. This tag could be combined with others todo labels Apr 1, 2020
@plehegar
Copy link
Member

plehegar commented Apr 1, 2020

(see also #392 (comment) )

@w3cbot w3cbot added privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. and removed privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. labels Apr 30, 2020
@kalyanaj kalyanaj added this to the 7. level-2 milestone Nov 16, 2021
@kalyanaj kalyanaj removed privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. workshop-fall-2020 labels Nov 16, 2021
@kalyanaj
Copy link
Contributor

We will consider this cleanup for Level 2. Not absolutely required, but more of an editorial fix.

@w3cbot w3cbot added the privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. label Nov 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Editorial The reported issue can be addressed with an editorial change. This tag could be combined with others privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on. todo
Projects
None yet
Milestone
7. level-2
Development

No branches or pull requests
4 participants
@plehegar @danielkhan @kalyanaj @w3cbot