Skip to content

Be consistent with normative / non-normative sections #396

@danielkhan

Description

@danielkhan

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    EditorialThe reported issue can be addressed with an editorial change. This tag could be combined with othersprivacy-needs-resolutionIssue the Privacy Group has raised and looks for a response on.todo

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions