Skip to content

style: headers *and* trailers #30

@LPardue

Description

@LPardue

In https://github.com/httpwg/admin/blob/main/style-guide.md#header-and-trailer-fields the guidance says

If the field is specific to headers, trailers, requests, and/or responses, the definition should include the relevant terms, as above.

and

Subsequent occurrences should be unquoted, but always be followed by "field", "header field", or "trailer field" as appropriate.

Content-Digest, for example, is all of these things. So ends up being defined as "the Content-Digest request and response header and trailer field". We refreain from saying "header and trailer" everywhere though. Should we really just be saying "field" or does that gloss over the definition of the field too much?

Perhaps the style guide would benefit from the explicit counter case in the guidance along the lines of "if a field applies to multiple categories, those categories can be ommited and only "field" used. Or some other guidance if I'm not on the money,

Metadata

Metadata

Assignees

No one assigned

    Labels

    style-guideDiscussion of the style guide

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions