Re: NEW ISSUE: Define "ought to"

Julian Reschke <julian.reschke@gmx.de> Tue, 30 July 2013 15:31 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9612811E81D6 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 08:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.832
X-Spam-Level:
X-Spam-Status: No, score=-9.832 tagged_above=-999 required=5 tests=[AWL=0.767, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06b3o7OmZ1qC for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 08:31:02 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id C8F8521E80E8 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 30 Jul 2013 08:31:00 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V4Bsq-0006YD-RV for ietf-http-wg-dist@listhub.w3.org; Tue, 30 Jul 2013 15:30:44 +0000
Resent-Date: Tue, 30 Jul 2013 15:30:44 +0000
Resent-Message-Id: <E1V4Bsq-0006YD-RV@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1V4Bsh-0006U5-7w for ietf-http-wg@listhub.w3.org; Tue, 30 Jul 2013 15:30:35 +0000
Received: from mout.gmx.net ([212.227.17.20]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1V4BsY-000533-CA for ietf-http-wg@w3.org; Tue, 30 Jul 2013 15:30:35 +0000
Received: from [192.168.1.104] ([217.91.35.233]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MNq8p-1V18Wx08fD-007UOD for <ietf-http-wg@w3.org>; Tue, 30 Jul 2013 17:30:00 +0200
Message-ID: <51F7DBF5.3030403@gmx.de>
Date: Tue, 30 Jul 2013 17:29:57 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: cowwoc <cowwoc@bbs.darktech.org>
CC: ietf-http-wg@w3.org
References: <51F7D951.3050204@bbs.darktech.org>
In-Reply-To: <51F7D951.3050204@bbs.darktech.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:qRoCrwxSCowDadjxbHrxf8J7aW5ORgtSWlyQOqLE5zG/CKSrAGM ko6fR70B8CWfxzbvKcf23N10Owts5W2FoDgwCC++/RDDQubdVi3JfOA499UQuHBSYO2HbrC f62FxXEXZMKlUQEHySwYs1jdHcFhNJJ3vrQhK5A01eBuySaoNYys4+FPJ8w6kOcDt2/Z0Tk aoVWdWVlQS4v2DMUwDzLQ==
Received-SPF: pass client-ip=212.227.17.20; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-3.450, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1V4BsY-000533-CA 7350c176463cc8cbdeba218a8c8473f7
X-Original-To: ietf-http-wg@w3.org
Subject: Re: NEW ISSUE: Define "ought to"
Archived-At: <http://www.w3.org/mid/51F7DBF5.3030403@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18978
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On 2013-07-30 17:18, cowwoc wrote:
> Hi,
>
>      According to
> http://lists.w3.org/Archives/Public/ietf-http-wg/2013JulSep/0183.html:
>
> The WG practice has been to replace overly restrictive
> SHOULD with a phrase that lacks the normative strictness while still
> conveying some importance for the instruction - "ought to".
>
>      I'd like to propose explicitly defining "ought to" alongside
> "SHOULD" because it is not clear what the practical difference is
> between the two. "ought to" is actually a synonym of "should", see
> http://thesaurus.com/browse/ought+to and http://thesaurus.com/browse/should
>
>      It seems that you meant for "ought to" to lie somewhere between
> "MAY" and "SHOULD" but I don't think you're gaining anything by not
> defining exactly what it means, especially for people whose English is
> not their first language.
>
>      Please consider:
>
>  1. Replacing "ought to" with a word that is not a synonym of SHOULD,
>     unless you mean SHOULD in which case you should use SHOULD :)
>  2. Defining "ought to" explicitly at the top of the document.
>
> Thank you :)
> Gili

The point being that "ought to" being just prose, while "SHOULD" being 
defined by RFC 2119. Both of them having roughly the same meaning in 
English sounds absolutely right to me.

Best regards, Julian