IETF Logo Mail Archive

Re: [IETF] RE: RFC 2119 terms, ALL CAPS vs lower case

Warren Kumari <warren@kumari.net> Wed, 16 May 2012 21:22 UTC

Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCDA21F8722 for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:22:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.137
X-Spam-Level:
X-Spam-Status: No, score=-106.137 tagged_above=-999 required=5 tests=[AWL=0.462, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 EBXJxpznKSdV for <ietf@ietfa.amsl.com>; Wed, 16 May 2012 14:22:53 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 0290121F8720 for <ietf@ietf.org>; Wed, 16 May 2012 14:22:52 -0700 (PDT)
Received: from [192.168.0.12] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 5BD301B40300; Wed, 16 May 2012 17:22:52 -0400 (EDT)
Subject: Re: [IETF] RE: RFC 2119 terms, ALL CAPS vs lower case
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="windows-1252"
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0AFA@DC-US1MBEX4.global.avaya.com>
Date: Wed, 16 May 2012 17:22:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BF1213D-76DC-4666-8D09-CE38F42BC174@kumari.net>
References: <562A61B995B24BD854A4D154@192.168.0.2> <m262bwchr9.wl%randy@psg.com> <08ab01cd3372$65934110$30b9c330$@olddog.co.uk> <tslaa18w21n.fsf@mit.edu> <4FB3E99D.1040606@stpeter.im> <CAHBDyN6SVUxKm4K1__zu47qNup-RF1L8exfb8n9n199y7fpGAQ@mail.gmail.com> <alpine.OSX.2.01.1205161124380.47757@bxb-vpn3-744.cisco.com> <4FB3F54F.2030705@stpeter.im> <097701cd3394$113cb520$33b61f60$@olddog.co.uk>, <867B9B680EBE3644D4CCD518@PST.JCK.COM> <CD5674C3CD99574EBA7432465FC13C1B22726A0AFA@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1257)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2012 21:22:53 -0000

On May 16, 2012, at 4:10 PM, Worley, Dale R (Dale) wrote:

>> From: John C Klensin [john-ietf@jck.com]
>> 
>>> Remind me:
>>> Is bold must more or less compelling that underlined must. And
>>> where does uppercase MUST fit in?
>>> 
>>> I fear the slightly richer publication format will give rise
>>> to a slightly more complex revision of RFC 2119.
>> 
>> Let's try to remember that many of the comments/ requests for
>> alternate publication formats have been to make "display" more a
>> function of the devices being used.  Depending on type style
>> variations (style, size, font variations, underlining, etc.)
>> would pretty much defeat that particular claimed requirement.
>> As I take Sam's note to sort of point out, even the use of
>> uppercase to imply specific semantics can be problematic; we
>> should at least strive to not make things worse, IMO.
> 
> I'm looking forward to the normative use of <BLINK>...</BLINK>.

Errr… would that be more or less strong then the non-<BLINK> version of a word?

Initially I'd think more, but on reflection it only visible for half the time, so I guess it is half as strong?!  ;-)

W

> 
> Dale
>

v2.23.0 | Report a Bug | By Email