4 ms·
A lot of commentary here on if "MUST NOT" is too ambiguous, or not, or a problem for non-native speakers... This makes the authors point about citation. In te
by ska 7y ago
A lot of commentary here on if "MUST NOT" is too ambiguous, or not, or a problem for non-native speakers...
This makes the authors point about citation. In technical documentation any terms use like this must (MUST) be defined, either in line or by citation.
This is also part of the reason they are capitalized, to key you to the fact they are being used in a structurally important way. If you are reading them, you need to familiarize yourself with the context.
- bitminer 7y agoMy system engineering experience avoided "must" as insufficiently specific. We used "shall" and avoided "not". Because testing: how do you prove a "not"? Source: 35 years of SE
- ska 7y agoI've tended to use SHALL and MAY for the same reasons, but it is important they are defined anyway, somewhere everyone agrees. Agree "not" is tougher, and best avoided when you can.