---
This message is a formal comment which was submitted to [EMAIL PROTECTED],
following the requirements described at: http://www.r6rs.org/process.html
---
submitter's name: Aubrey Jaffer
submitter's email address: [EMAIL PROTECTED]
type of issue: Defect
priority: Minor
R6RS component: Concepts
version of the report: 5.92
one-sentence summary of the issue: 5.1. Requirement levels is MAXxed out
full description of the issue:
On page 20 "5.1. Requirement levels", the two occurences of the word
"max" should be replaced by "may" (marked with ^^^ below):
5.1. Requirement levels
The key words "must", "must not", "required", "shall", "shall not",
"should", "should not", "recommended", "may", and "optional" in this
document are to be interpreted as described in RFC 2119 [4].
Specifically:
must
This word means that a statement is an absolute requirement of
the specification.
must not
This phrase means that a statement is an absolute prohibition
of the specification.
should
This word, or the adjective "recommended", mean that valid
reasons max exist in particular circumstances to ignore a
------------^^^
statement, but that the implications must be understood and
weighed before choosing a diļ¬erent course.
should not
This phrase, or the phrase "not recommended", mean that valid
reasons max exist in particular circumstances when the behavior of
------------^^^
a statement is acceptable, but that the implications must be
understood and weighed before choosing the course described by the
statement.
may
This word, or the adjective "optional", mean that an item is
truly optional.
_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
