Re: NEW ISSUE: Define "ought to"

cowwoc <cowwoc@bbs.darktech.org> Tue, 30 July 2013 16:07 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 8006511E81F3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 09:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.973
X-Spam-Level:
X-Spam-Status: No, score=-7.973 tagged_above=-999 required=5 tests=[AWL=2.626, 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 kz9nQDNyNdRr for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 09:07:34 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6CF11E821F for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 30 Jul 2013 09:05:12 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V4CPU-0006Pj-80 for ietf-http-wg-dist@listhub.w3.org; Tue, 30 Jul 2013 16:04:28 +0000
Resent-Date: Tue, 30 Jul 2013 16:04:28 +0000
Resent-Message-Id: <E1V4CPU-0006Pj-80@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <cowwoc@bbs.darktech.org>) id 1V4CPK-0006Ow-Ij for ietf-http-wg@listhub.w3.org; Tue, 30 Jul 2013 16:04:18 +0000
Received: from mail-qe0-f54.google.com ([209.85.128.54]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <cowwoc@bbs.darktech.org>) id 1V4CPF-0002pA-UV for ietf-http-wg@w3.org; Tue, 30 Jul 2013 16:04:18 +0000
Received: by mail-qe0-f54.google.com with SMTP id 1so3145735qee.13 for <ietf-http-wg@w3.org>; Tue, 30 Jul 2013 09:03:48 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=3AmqotxjI7KvuRSkEZuqAWwLTZcOX6b0ZBDR0rxHONY=; b=j13jqGJ6VjrsynGYXvcG5xtqMZTvUsB4F9OKsN8krtevyiIJTpcitGjmJGM35HtAAE Nw4Oykf4SlhR/x9Y2TBIOJHd+haRVqMnW9Y4DLrVnxC5/BIGM4Z+iJyFDb+YzY8kEoQd G5rWObw3eh82ABgwM5k9Urdj+Nc19WTdKqSkQ/Q9XNNw5M8rzFEDEWftJsUaU9KzOy4J OZ+akT3evwuvoTab1GkndV5wseXSugus5UkFVibLPXz+/86OfmpIJ+QDSgoxvXd3kcdr LVcoSPHXdlt1S0PtlK1s6wAVCEAibJwAAIl3WdWSdDR+c8kNqEuU6TfDUbi8p9Xe740f rkcA==
X-Received: by 10.49.131.36 with SMTP id oj4mr76987248qeb.51.1375200228224; Tue, 30 Jul 2013 09:03:48 -0700 (PDT)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id a8sm28974970qae.11.2013.07.30.09.03.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 30 Jul 2013 09:03:47 -0700 (PDT)
Message-ID: <51F7E3DE.4020804@bbs.darktech.org>
Date: Tue, 30 Jul 2013 12:03:42 -0400
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
CC: ietf-http-wg@w3.org
References: <51F7D951.3050204@bbs.darktech.org> <51F7DBF5.3030403@gmx.de>
In-Reply-To: <51F7DBF5.3030403@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQk0yPS2/dPRn4rTSrySzbPDvrl2mhGObW0hVRRi2Q0/cL/12aDoSMgebgbB+GwIIkkkXQqA
Received-SPF: none client-ip=209.85.128.54; envelope-from=cowwoc@bbs.darktech.org; helo=mail-qe0-f54.google.com
X-W3C-Hub-Spam-Status: No, score=-3.8
X-W3C-Hub-Spam-Report: AWL=-3.054, RCVD_IN_DNSWL_LOW=-0.7
X-W3C-Scan-Sig: maggie.w3.org 1V4CPF-0002pA-UV 6788485aaeb6f524b8f80c65a1c55253
X-Original-To: ietf-http-wg@w3.org
Subject: Re: NEW ISSUE: Define "ought to"
Archived-At: <http://www.w3.org/mid/51F7E3DE.4020804@bbs.darktech.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18981
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 30/07/2013 11:29 AM, Julian Reschke wrote:
> 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.

Julian,

     I understand the "legal" difference between the two but your reply 
didn't actually explain the benefit of using "ought to" instead of 
"SHOULD" (especially in light of the fact that the former causes confusion).

Gili