logoalt Hacker News

0cf8612b2e1eyesterday at 11:42 PM4 repliesview on HN

  The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted exactly as how much we do not want to review your generated submission.
I know it is in jest, but I really hate that so many documents include “shall”. The interpretation of which has had official legal rulings going both ways.

You MUST use less ambiguous language and default to “MUST” or “SHOULD”


Replies

msylvesttoday at 8:39 AM

Around 1990 I attended ISO/JTC1 meetings generating standards for data communication. I still recall my surprise over the heated arguments over these words between the UK and the US delegations. (I'm from Denmark). In particular 'shall' and 'should' meant different things in English and American languages. ISO's first standard, ISO 1, states that ISO Standards shall be written in English so we had to do that, US delegation too. Similarly Scott Bradner stated in RFC 2219 how American conventions should be followed for future IETF STDs.

So I'm confident that the word 'shall' has a strong meaning in English; whether it has too in American legalese I cannot tell.

layman51today at 12:08 AM

Right. I think when these appear in some documentation related to computing, they should also mention whether it is using these words in compliance with RFC 2119 or RFC 6919.

wildzzztoday at 12:35 AM

Must is a strict requirement, no flexibility. Shall is a recommendation or a duty, you should do it. You must put gas in the car to drive it. You shall get an oil change every 6000 miles.

show 1 reply
Muhammad523yesterday at 11:46 PM

Many legal documents use "may" to say you must. That's why i hate legalese...

show 3 replies