IETF Logo Mail Archive

Re: [Json] [abnf-discuss] Are the Core Rules (Appendix B.1 of RFC 5234) always present in an ABNF spec?

Joe Hildebrand <hildjj@cursive.net> Wed, 20 September 2023 18:17 UTC

Return-Path: <hildjj@cursive.net>
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 A8A3BC151555 for <json@ietfa.amsl.com>; Wed, 20 Sep 2023 11:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cursive.net
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 SxlhJkJdqaPg for <json@ietfa.amsl.com>; Wed, 20 Sep 2023 11:17:26 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 69E13C15155C for <json@ietf.org>; Wed, 20 Sep 2023 11:17:26 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id ca18e2360f4ac-792979d4cb5so6183339f.2 for <json@ietf.org>; Wed, 20 Sep 2023 11:17:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; t=1695233845; x=1695838645; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ycX/G2D/rpEPy+gzC+WZNxNHVu3YjwfnsK9Y9J8OVtI=; b=iHD1kMN7Jvs5QOMrQ5f0aXMGyWHg/aJMfC396aSFk2/nmITPX74hiQgZJfMK3xhtC1 UdcEXcgm9bSrRZJlax93RHhlVmGANJmiw6f8gXcQitutH3kt5fvYLKlxti1VVSBRVTyP pNq5W4So5+u4k29OM3G/oGom+/N4TC+a/+rOg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695233845; x=1695838645; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ycX/G2D/rpEPy+gzC+WZNxNHVu3YjwfnsK9Y9J8OVtI=; b=s31ACfXIylXFiBu8JghjyqyL7ztPI4kSBO0Mn1RU9K9QmwHv0cPTsQtxI3sqcTr7N/ OfmGbFUgR/hQHDDoi+qeH6hoHGsZnxPd17fYoJJO8d5U79prP3grHRbaIUILgXNoIpgF gqx1HX3cDw4cu/Yf3gfqnJuNP9IxWqSyDjVgTdQLg/fRgmJSnQfpnC6c5aUf2/YOm8Uu SY0OQ+Q2MaGy3tUrQzUQxTM5EWLBO/P6oIUcoBJcS0rsLF5rTOdIsrTwcesiaWVlYCqe qDFTpaj53zz6/9xfa2Inz+PphWIQ+OE1xdiyEo8987ADiGubHLSHwmPFn6YpxdCJVEPu txLw==
X-Gm-Message-State: AOJu0Yy8Gx7iDSLMEMaeK55vhwJYOaGCneSfZJ0R5hgi4sVX9NjTb3ME NXRyHmYyo1nCLXd3nRkWp0Er3w==
X-Google-Smtp-Source: AGHT+IGy9Ltg/0W5hnQksd/fXOfRvHkd8TfkkyxNroFkBLWHHVFBbc2ksSOh/B+6IER0PeoYN0WEtg==
X-Received: by 2002:a6b:6004:0:b0:792:8c52:b3b8 with SMTP id r4-20020a6b6004000000b007928c52b3b8mr3529719iog.14.1695233845215; Wed, 20 Sep 2023 11:17:25 -0700 (PDT)
Received: from smtpclient.apple ([2601:282:2101:423e:c189:8ade:95f7:a63a]) by smtp.gmail.com with ESMTPSA id s17-20020a6bd311000000b0077a1b6f73b9sm4166623iob.41.2023.09.20.11.17.24 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Sep 2023 11:17:24 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Joe Hildebrand <hildjj@cursive.net>
In-Reply-To: <818b73aa-f8b2-491e-8b6a-4e4b9f5f03b9@gmail.com>
Date: Wed, 20 Sep 2023 12:17:13 -0600
Cc: Carsten Bormann <cabo@tzi.org>, "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>, json@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <004A8556-FEC1-4803-A72D-AE86390A356B@cursive.net>
References: <A9C3993F-D73B-4529-A94B-A6A33589726E@tzi.org> <3c38cda7-98d5-48c8-9b36-ea25f1ab5da4@gmail.com> <360AE449-DFD5-44D7-BB57-18C5DECFB741@cursive.net> <818b73aa-f8b2-491e-8b6a-4e4b9f5f03b9@gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/K5P1hIMboGvBYzWKqHf9IiQ_iDg>
Subject: Re: [Json] [abnf-discuss] Are the Core Rules (Appendix B.1 of RFC 5234) always present in an ABNF spec?
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: Wed, 20 Sep 2023 18:17:31 -0000

Nod.  I don't think it's needed, but I don't think it's harmful if a few people double-check the work.

— 
Joe Hildebrand

> On Sep 20, 2023, at 12:15 PM, Dave Crocker <dcrocker@gmail.com> wrote:
> 
> On 9/20/2023 10:39 AM, Joe Hildebrand wrote:
>> and a statement that CHAR is NOT imported, to be absolutely specific. Changing the ABNF itself is neither needed nor desirable, IMO.
> 
> To be clear, I suspect it would be /much/ safer to /also/ use the different rulename, to avoid cognitive confusion, unless there is a strong basis for keeping the same name but different semantics.
> 
> d/
> 
> -- 
> Dave Crocker
> dcrocker@gmail.com
> mast:@dcrocker@mastodon.social
> 408.329.0791
> 
> Volunteer, Silicon Valley Chapter
> Information & Planning Coordinator
> American Red Cross
> dave.crocker2@redcross.org
>

v2.23.0 | Report a Bug | By Email