Re: [Json] [Editorial Errata Reported] RFC8259 (7383)

Carsten Bormann <cabo@tzi.org> Sun, 12 March 2023 20:39 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06CB1C151527 for <json@ietfa.amsl.com>; Sun, 12 Mar 2023 13:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QETpHTFmEAhj for <json@ietfa.amsl.com>; Sun, 12 Mar 2023 13:39:22 -0700 (PDT)
Received: from smtp.uni-bremen.de (smtp.uni-bremen.de [134.102.50.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F308C151540 for <json@ietf.org>; Sun, 12 Mar 2023 13:39:22 -0700 (PDT)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 4PZWqB6ZwczDCbJ; Sun, 12 Mar 2023 21:39:18 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBU6iu8Aa2NfCAWFwqMPNaRFcD=PdtQBswntwfWofyWG04a+w@mail.gmail.com>
Date: Sun, 12 Mar 2023 21:39:18 +0100
Cc: Rob Sayre <sayrer@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>, 00mk01@gmail.com, json@ietf.org
X-Mao-Original-Outgoing-Id: 700346358.512203-ca03232a83b0a26ef2c176d72c16701b
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8D5AB1F-14D7-4069-9485-940E2F268CBD@tzi.org>
References: <20230312155302.346FE5668D@rfcpa.amsl.com> <CAChr6SxstNP4zrsB1_--nv9=5=YNz2_daE_KLR5HZ5vF-trKxA@mail.gmail.com> <CAHBU6iu8Aa2NfCAWFwqMPNaRFcD=PdtQBswntwfWofyWG04a+w@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/TcZNFWy7G5nZyAKjKgzqOVAxvoY>
Subject: Re: [Json] [Editorial Errata Reported] RFC8259 (7383)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Mar 2023 20:39:26 -0000

On 2023-03-12, at 19:07, Tim Bray <tbray@textuality.com> wrote:
> 
> Heh, this goes back to RFC4627, dated July 2006.

Much of ABNF was designed in 1977, when many computing environments only were starting to embrace lower-case (as usual, the future was already there, just not evenly distributed).
In keeping with what was the normal way to cope at the time, ABNF literals are case-insensitive.

When case-insensitive finally went out of fashion(*), misunderstandings started to multiply, in both directions.

By now, we tend to have little refreshers about this in our documents, e.g. [1].
(We forgot to put in another one for HEXDIG [2], but maybe that’s not needed.)

Grüße, Carsten

(*)  (I’d say around 1999, but zombies have been observed as late as 2005 [0].)

[0]: https://blog.codinghorror.com/the-case-for-case-insensitivity/
[1]: https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base-11#section-2.5.5.1-11
[2]: https://datatracker.ietf.org/doc/html/draft-ietf-jsonpath-base-11#section-2.5.1.1-3