[Cbor] Use of cuts in maps

Jim Schaad <ietf@augustcellars.com> Wed, 07 August 2019 21:50 UTC

From: Jim Schaad <ietf@augustcellars.com>
To: 'Carsten Bormann' <cabocabo@gmail.com>
CC: cbor@ietf.org
Date: Wed, 07 Aug 2019 14:45:33 -0700
Message-ID: <001301d54d69$722a3050$567e90f0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AdVNX+VPSR6jybaZRwWJKW5K0t0toA==
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/cctj-tgzuhLvVGzXN8wLwWtEL7Q>
Subject: [Cbor] Use of cuts in maps
Precedence: list

One of the issues that I have always had with the way that cuts are
specified in CDDL is that they don't behave the way that I think they should
in terms of going from the most specific to the most general.  I think that
I have found a way around this problem and want to verify that it would
work.


Start I start with

map-example = {
   ? "optional-key" : int,
   map-example-extensions,
   * tstr => any
}

map-example-extensions = ()

The next document comes along and does

map-example-extensions /= (
   "another-optional-key" : tstr,
  "and a third": bstr
)

If I compile the two modules together, do you believe that this would be a
match or not?
 
{ "and a third" : 15 }

Jim

[Cbor] Use of cuts in maps Jim Schaad
Re: [Cbor] Use of cuts in maps Carsten Bormann
Re: [Cbor] Use of cuts in maps Jim Schaad