Skip to content

Document rationale when conventions do not follow existing guidance #2245

@trask

Description

@trask

Sometimes there's a good reason not to follow existing guidance, but it can be hard to review semantic conventions without knowing this reasoning, or understanding the scope that the reasoning applies to, e.g. #2180 (comment).

It would be great if these rationales were documented somewhere under docs/non-normative.

We could even have one doc for the rationale "stabilized already 🤷".

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Need triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions