IETF Logo Mail Archive

Re: [Cbor] CDDL 2.0 import and paths

Carsten Bormann <cabo@tzi.org> Mon, 06 February 2023 23:38 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94703C1575DB for <cbor@ietfa.amsl.com>; Mon, 6 Feb 2023 15:38:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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] 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 o7LRwsROiqg2 for <cbor@ietfa.amsl.com>; Mon, 6 Feb 2023 15:38:40 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::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 175C4C14F744 for <cbor@ietf.org>; Mon, 6 Feb 2023 15:38:38 -0800 (PST)
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.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4P9jPk0KwSzDCbv; Tue, 7 Feb 2023 00:38:34 +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: <2340545.1675724990@dyas>
Date: Tue, 07 Feb 2023 00:38:33 +0100
Cc: Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>, "cbor@ietf.org" <cbor@ietf.org>
X-Mao-Original-Outgoing-Id: 697419513.659338-e6d0a2a85844fde7fcba589c4d7976e6
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1901B89-6951-484A-82C2-C58C39B714DB@tzi.org>
References: <Y9FYSKde6bXgzep3@hephaistos.amsuess.com> <BAFC97D5-3B5A-4ED5-ADEC-93CB53CC2128@tzi.org> <2304074.1675693261@dyas> <0F5E27CB-44D6-4112-A7BA-8372F36EF3B3@tzi.org> <2312048.1675698835@dyas> <PH0PR02MB72561C8C79F5B0A9E2ED4540F2DA9@PH0PR02MB7256.namprd02.prod.outlook.com> <7CABC53E-E18F-44C5-B6C1-B4A13E8FB55F@tzi.org> <2340545.1675724990@dyas>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/w8xwbNXJvYZunYJ6_Zs-C9rpqbM>
Subject: Re: [Cbor] CDDL 2.0 import and paths
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2023 23:38:42 -0000

> I'm at this point skeptical that we need include semantics at all, but I
> suppose it does not hurt.

The include semantics are really useful if you want to compose CDDL out of several files and can make good use of warnings about unused rules.  So this is what I mean by “within one project”.  “Between projects” (i.e., using a CDDL file as a library from another one) you will always use import, I agree.

Grüße, Carsten

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