Re: NEW ISSUE: Define "ought to"
Dave Crocker <dhc2@dcrocker.net> Wed, 31 July 2013 04:43 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 D6A5121E80E7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 21:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 sEZadb-bpVuq for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 30 Jul 2013 21:43:00 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id B21B311E8160 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 30 Jul 2013 21:43: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 1V4OEm-0003zv-1c for ietf-http-wg-dist@listhub.w3.org; Wed, 31 Jul 2013 04:42:12 +0000
Resent-Date: Wed, 31 Jul 2013 04:42:12 +0000
Resent-Message-Id: <E1V4OEm-0003zv-1c@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <dhc2@dcrocker.net>) id 1V4OEc-0003zC-St for ietf-http-wg@listhub.w3.org; Wed, 31 Jul 2013 04:42:02 +0000
Received: from sbh17.songbird.com ([72.52.113.17]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <dhc2@dcrocker.net>) id 1V4OEb-0005bo-Ju for ietf-http-wg@w3.org; Wed, 31 Jul 2013 04:42:02 +0000
Received: from [192.168.1.203] (e178124165.adsl.alicedsl.de [85.178.124.165]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r6V4fP9Q005873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Jul 2013 21:41:31 -0700
Message-ID: <51F89572.1080506@dcrocker.net>
Date: Wed, 31 Jul 2013 06:41:22 +0200
From: Dave Crocker <dhc2@dcrocker.net>
Reply-To: dcrocker@bbiw.net
Organization: Brandenburg InternetWorking
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: cowwoc <cowwoc@bbs.darktech.org>, 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-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 30 Jul 2013 21:41:34 -0700 (PDT)
Received-SPF: none client-ip=72.52.113.17; envelope-from=dhc2@dcrocker.net; helo=sbh17.songbird.com
X-W3C-Hub-Spam-Status: No, score=-2.3
X-W3C-Hub-Spam-Report: RCVD_IN_DNSWL_MED=-2.3
X-W3C-Scan-Sig: maggie.w3.org 1V4OEb-0005bo-Ju e07b516d3385027a8db9a34bfded6be2
X-Original-To: ietf-http-wg@w3.org
Subject: Re: NEW ISSUE: Define "ought to"
Archived-At: <http://www.w3.org/mid/51F89572.1080506@dcrocker.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18997
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 7/30/2013 5:29 PM, Julian Reschke wrote:
> 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.
Well, the choice of non-normative vocabulary would do better to be for
words and phrasing that are not too easily confused with the normative
terms. Cognitive separation will help the reader.
Since this is a continuing issue in the IETF, Tony Hansen recruited me
to work on a document to help folk:
Non-Normative Synonyms in RFCs
http://tools.ietf.org/html/draft-hansen-nonkeywords-non2119-02
In looking at this thread, I'm thinking we should take out the word
'ought'...
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
- Re: NEW ISSUE: Define "ought to" cowwoc
- NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- RE: NEW ISSUE: Define "ought to" Mike Bishop
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" Willy Tarreau
- Re: NEW ISSUE: Define "ought to" Willy Tarreau
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" Dave Crocker
- Re: NEW ISSUE: Define "ought to" Martin Thomson
- Re: NEW ISSUE: Define "ought to" cowwoc
- Re: NEW ISSUE: Define "ought to" Dave Crocker
- Re: NEW ISSUE: Define "ought to" Julian Reschke
- Re: NEW ISSUE: Define "ought to" Dave Crocker
- Re: NEW ISSUE: Define "ought to" Willy Tarreau
- Re: NEW ISSUE: Define "ought to" Yoav Nir
- Re: NEW ISSUE: Define "ought to" Eliot Lear
- Re: NEW ISSUE: Define "ought to" Mark Nottingham
- Re: NEW ISSUE: Define "ought to" Michael Sweet
- Re: NEW ISSUE: Define "ought to" Eliot Lear
- Re: NEW ISSUE: Define "ought to" cowwoc