IETF Logo Mail Archive

Re: [Cbor] CDDL 2.0 import and paths

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 06 February 2023 15:54 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 A2FDEC14F731 for <cbor@ietfa.amsl.com>; Mon, 6 Feb 2023 07:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, 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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (bad RSA signature)" header.d=sandelman.ca
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 u6-nBmSvvL4v for <cbor@ietfa.amsl.com>; Mon, 6 Feb 2023 07:54:39 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (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 3EBE5C153CA1 for <cbor@ietf.org>; Mon, 6 Feb 2023 07:54:00 -0800 (PST)
Received: from dyas.sandelman.ca (ipv6.dyas.sandelman.ca [IPv6:2607:f0b0:f:6::1]) by relay.sandelman.ca (Postfix) with ESMTPS id C3B631F47B; Mon, 6 Feb 2023 15:53:58 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=mail; t=1675698839; bh=qOMG2zqvCdsmN7QKnTVBnTxpMOOpjjzfk13Wa2bD08Q=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=PhNQNjLE+zPlhfmpSIwAiFWeLenQ4CAlpjbqR+01hsV8pfF28uv5t2z8LdNs7XvOP CFwvaNhk1ygPwfX21mPrDCjx2Jcrh2vajMYlvHRRXbJIO9LG554hCZY+Y05MQSKfsR qceyDnOOeHMIY+9wg1lFFeA5HHNeAcqS+CJeG/nbk7jzQJR+yFcCda+vNL9OLamAhP pHxSJS3LXV/atJ58QGJ43tCPQSfSxzRnPfdO9PqwPW3/2nyrGmbmP9MCJnbv/DwWSw AEfxVRT91H783T94lH4QRZg+dmsvXh7T5WqJqOTtR6taNoUqD26ku0t6tZ6oDfvdqU vTMg7E860evpg==
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 4A145A1E97; Mon, 6 Feb 2023 10:53:55 -0500 (EST)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 47779A1E95; Mon, 6 Feb 2023 16:53:55 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Carsten Bormann <cabo@tzi.org>
cc: cbor@ietf.org
In-reply-to: <0F5E27CB-44D6-4112-A7BA-8372F36EF3B3@tzi.org>
References: <Y9FYSKde6bXgzep3@hephaistos.amsuess.com> <BAFC97D5-3B5A-4ED5-ADEC-93CB53CC2128@tzi.org> <2304074.1675693261@dyas> <0F5E27CB-44D6-4112-A7BA-8372F36EF3B3@tzi.org>
Comments: In-reply-to Carsten Bormann <cabo@tzi.org> message dated "Mon, 06 Feb 2023 15:31:58 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 06 Feb 2023 16:53:55 +0100
Message-ID: <2312048.1675698835@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/1p8mu-AubMcy4izI-CDrynxO-K8>
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 15:54:43 -0000

Carsten Bormann <cabo@tzi.org> wrote:
    >> Carsten Bormann <cabo@tzi.org> wrote:
    >>> ;# include rfc9052
    >>> ;;; include all the rules from rfc9052.cddl as well as the ones
    >>> imported/included there, no questions asked
    >>
    >> So that's recursive.

    > Well, cddlc will break its little mind quickly if it actually gets recursive…

I mean, it will pull in all the includes from the includes.

    >>> ;# import rfc9052
    >>> ;;; include only those rules from rfc9052.cddl that actually are
    >>> undefined references in the current CDDL file, treating rfc9052 as a
    >>> “library”.
    >>
    >> So, that's not recursive, and if there were dangling references in
    >> rf9062.cddl, I'd have to take care of it?

    > Actually, this also runs a transitive closure *within the imported CDDL
    > file*, and it acts on directives inside that (but not adding anything
    > nested based on undefined references from outside).  I added a nested
    > import directive to rfc9053.cddl, if you want to play with this.

I guess I'm not really sure I understand the utility of the difference.

    >> A question about CDDL_INCLUDE_PATH, does it always start at the beginning, or
    >> does it start at the place in the path where the current file was found?

    > The path always starts at the beginning.
    > So you can override/reach into dependency chains (on purpose or inadvertently).

okay.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

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