Re: [Cbor] CDDL 2.0 import and paths

[Michael Richardson <[e-mail]>]

Carsten Bormann <[e-mail]> 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.

    > ;# 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?

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?

    > I plan to add something like

    > ;# import rfc9052 as COSE

    > which would rename the names in the imported rules to start with COSE(*).
    > (This is of course interesting because of other imported names, as well as prelude names…)

A good idea.
I'll update my use of cddlc later this month when I return to that work.

    > (*) I’m not yet sure whether the auto-import mechanism should add glue
    > rules automatically, so you don’t have to call your referencing names
    > COSE.COSE_Encrypt0 while still getting overly generic names such as
    > `label` or `values` prefixed as `COSE.label` and `COSE.values`.  This
    > could be limited to specific names listed in a “import … from” part of
    > the directive.  I need to see more examples to make a useful
    > suggestion.

A good question, I think prefixing is okay.

    > (**) I also need to reserve an afternoon for submitting all the errata
    > reports for the extracted CDDL.  From a missing closing parenthesis via
    > word wrapping out of a comment to using # as the comment character.
    > Ouch.

HAHA.


--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-