IETF Logo Mail Archive

[Tools-discuss] Re: [abnf-discuss] Re: [art] Re: Exploring ABNF extracts from RFCs

Carsten Bormann <cabo@tzi.org> Mon, 29 July 2024 14:54 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D400C15199A; Mon, 29 Jul 2024 07:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 m-nPqQBZUTJo; Mon, 29 Jul 2024 07:54:52 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 942E7C151548; Mon, 29 Jul 2024 07:54:50 -0700 (PDT)
Received: from [192.168.217.145] (p5dc5d6c5.dip0.t-ipconnect.de [93.197.214.197]) (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 4WXhGb5fcmzDCbG; Mon, 29 Jul 2024 16:54:47 +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: <da4c5ded-24dc-46c8-b011-cea627107f19@gmail.com>
Date: Mon, 29 Jul 2024 16:54:47 +0200
X-Mao-Original-Outgoing-Id: 743957687.321187-bc493057c43aab615480a20d06ce5924
Content-Transfer-Encoding: quoted-printable
Message-Id: <99B795A8-DC51-409A-8395-A0CD5E5C24BF@tzi.org>
References: <89a4a566-8ffe-413e-9196-3f08bebe8d20@w3.org> <99E8B992-AF60-4CD6-9786-2EC180E95E4D@tzi.org> <2867abac-8c62-41b2-a20c-cb9fe8d3736d@alum.mit.edu> <ff29ebe0-efbc-4bfc-8c79-f09ccbe3ffe3@w3.org> <b864092b-477b-4866-a2b1-481313545917@alum.mit.edu> <da4c5ded-24dc-46c8-b011-cea627107f19@gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Message-ID-Hash: HE2PYMJEZRDTAQIBJ3MURC6XEH45VIMM
X-Message-ID-Hash: HE2PYMJEZRDTAQIBJ3MURC6XEH45VIMM
X-MailFrom: cabo@tzi.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Paul Kyzivat <pkyzivat@alum.mit.edu>, Dominique Hazael-Massieux <dom@w3.org>, art@ietf.org, tools-discuss <tools-discuss@ietf.org>, CBOR <cbor@ietf.org>, abnf-discuss@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Tools-discuss] Re: [abnf-discuss] Re: [art] Re: Exploring ABNF extracts from RFCs
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Nb3nMkqbO6vS0l_hzhLjkAzPXVY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>

On 2024-07-29, at 16:47, Dave Crocker <dcrocker@gmail.com> wrote:
> 
> As for namespaces, something like organization-document probably suffice to take care of the global uniqueness part.  So, for example, ietf-rfc-nnn-…

Generally, it is advantageous to separate the document reference (which may need to carry a lot of information to properly select the document, its revision, provenance, ...) from how the referenced item is used in the actual specification.

So in CDDL, we do something like

   ;# import cose.label, cose.values from rfc9052 as cose

Which makes cose.label (cose--label when using ABNF name characters only) the rule name to be used in the CDDL (ABNF) and keeps the detailed document reference (in this example rfc9052) in the import statement, which acts as the glue.

Grüße, Carsten

v2.26.15 | Report a Bug | By Email | System Status