Skip to content

Guidelines for parts that are intentionally unspecified #2026

@ehuss

Description

@ehuss

I think the authoring guide should have some guidelines on when something can be intentionally unspecified. Do we want to ever allow that? If so, do we want to formalize that (similar to how C spec does)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Authoring guideIssues for the authoring guide and style guidelinesMetaNon-content issues (procedure, tooling, website, etc.)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions