* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #258 (closed editorial: fixed)

Opened 4 years ago

Last modified 3 years ago

Avoid passive voice in message requirements

Reported by: mnot@pobox.com Owned by:
Priority: normal Milestone: unassigned
Component: content-disp Severity: In WG Last Call
Keywords: Cc:
Origin:

Description

=> Parameter names MUST NOT be repeated.

The document should not phrase normative requirements in the passive voice. Instead, the document should make clear which protocol partipants are bound by each requirement. For example, this requirement probably should read "servers MUST NOT generate Content-Disposition header field values with multiple instances of the same parameter name."

Suggested:

Senders MUST NOT generate C-D header field values with multiple instances of the same parameter name.

... and look for similar constructs throughout the draft.

Change History

comment:1 Changed 4 years ago by julian.reschke@gmx.de

  • Status changed from new to closed
  • Resolution set to incorporated

see [1073]

comment:2 Changed 3 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:3 Changed 3 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.