IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Wed, 20 September 2023 15:58 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 04E52C15153D; Wed, 20 Sep 2023 08:58:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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=ham 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 5UM5SHL17HRD; Wed, 20 Sep 2023 08:57:58 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (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 34209C14CE51; Wed, 20 Sep 2023 08:57:58 -0700 (PDT)
Received: from [192.168.217.124] (p548dc15c.dip0.t-ipconnect.de [84.141.193.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RrNTw2ghjzDCdn; Wed, 20 Sep 2023 17:57:56 +0200 (CEST)
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: <ZQsRoQ64h6JA3jA6@ubby21>
Date: Wed, 20 Sep 2023 17:57:55 +0200
Cc: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>, json@ietf.org
X-Mao-Original-Outgoing-Id: 716918274.896892-0017a80c0ccec6d34aafef1a6de98276
Content-Transfer-Encoding: quoted-printable
Message-Id: <273161FF-F3CF-4782-B85D-F9C313A016F4@tzi.org>
References: <A9C3993F-D73B-4529-A94B-A6A33589726E@tzi.org> <ZQsRoQ64h6JA3jA6@ubby21>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/CMkburTGMufJZJSNY7EUJA_rmaw>
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 15:58:02 -0000

On 2023-09-20, at 17:37, Nico Williams <nico@cryptonector.com> wrote:
> 
> ABNF lacks
> import/export syntax (and therefore also rule name namespacing), so
> conflicts must be very likely.

Somewhat off-topic, some notes from a related, almost isomorphic standard (CDDL):

* CDDL has a well-defined “prelude” (Appendix D [1]), which is always included.  Only one prelude exists, and there is no intention to ever change it.

* CDDL is growing an import syntax now [2], which could be made to work almost exactly the same way with ABNF.  Since CDDL is designed to be able to use/interact with ABNF [3], we might want to do an import mechanism for both in a similar way.

Grüße, Carsten

[1]: https://www.rfc-editor.org/rfc/rfc8610#appendix-D
[2]: https://www.ietf.org/archive/id/draft-ietf-cbor-cddl-modules-00.html#name-basic-set-of-directives
[3]: https://www.rfc-editor.org/rfc/rfc9165#name-embedded-abnf

v2.23.0 | Report a Bug | By Email