Opened 6 years ago

Closed 4 years ago

#145 closed defect (fixed)

RFC 2119 compliance

Reported by: cowan Owned by: cowan
Priority: major Milestone:
Component: WG1 - Core Keywords:
Cc:

Description

Scrutinize every use of the RFC 2119 modal verbs "may", "should", "must", "shall", "should not", "must not", "shall not" and the RFC 2119 adjectives "required", "recommended", and "optional" to make sure they are compliant and fix them if not. Introduce them in situations where they ought to be used. If you find "may not", it probably should be "must not".

We will probably need to use different markup for compliant and non-compliant usage, hopefully not as intrusive as ALL CAPS.

Note that "shall" is a synonym for "must".

We should talk only about what implementations may, should, or must do, and use "can" or similar terms for user choices.

Beware the unexpressed subject. "X must be done" isn't properly 2119-compliant, because we don't know who must do it.

Change History (5)

comment:1 Changed 6 years ago by cowan

  • Status changed from new to decided

WG1 accepted this proposal.

comment:2 Changed 6 years ago by cowan

WG1 decided to add the long-form names currently in use to the list.

comment:3 Changed 6 years ago by cowan

Ignore the above comment!

comment:4 Changed 5 years ago by cowan

  • Owner changed from alexshinn to cowan
  • Status changed from decided to writing

comment:5 Changed 4 years ago by cowan

  • Resolution set to fixed
  • Status changed from writing to closed

Cleaned up all remaining bad MUSTard, I hope.

Note: See TracTickets for help on using tickets.