Re: [Cbor] Getting diagnostic notation examples in drafts under control

Carsten Bormann <cabo@tzi.org> Tue, 27 February 2024 10:06 UTC

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: <97D9FAA8-5EEC-4AA8-8307-96BD1A5884BC@wolfmcnally.com>
Date: Tue, 27 Feb 2024 11:06:37 +0100
Cc: cbor@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <02654D5F-BEC2-4F30-8F98-A16B0B8D8F5B@tzi.org>
References: <FD64709D-2B97-4DED-9915-331FE7188EE8@tzi.org> <97D9FAA8-5EEC-4AA8-8307-96BD1A5884BC@wolfmcnally.com>
To: Wolf McNally <wolf@wolfmcnally.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/EwoZuRzA4Yl4oBErbg9ebteCsgc>
Subject: Re: [Cbor] Getting diagnostic notation examples in drafts under control
Precedence: list

Hi Wolf,

On 2024-02-27, at 01:16, Wolf McNally <wolf@wolfmcnally.com> wrote:
> 
> I was wondering about the right way to declare CBOR tag values in a single place and then use them as symbols throughout the rest of my CDDL. For example, something like:
> 
> ```cddl
> tag-my-struct = #6.123456
> 
> ; …
> 
> my-struct = tag-my-struct(
>    bstr .size 32
> )
> ```

This is usually done using generics:

tag-my-struct<T> = #6.123456(T)
my-struct = tag-my-struct<bstr .size 32>

With new syntax coming in ietf-cbor-update-8610-grammar, this could be further unbundled:

tag-my-struct<T> = #6.<my-struct-tag>(T)
my-struct-tag = 123456
my-struct = tag-my-struct<bstr .size 32>

But I don’t think that adds much in this example, so I’d stick with the simple use of generics.

Grüße, Carsten

[Cbor] Getting diagnostic notation examples in dr… Carsten Bormann
Re: [Cbor] Getting diagnostic notation examples i… Wolf McNally
Re: [Cbor] Getting diagnostic notation examples i… Carsten Bormann
Re: [Cbor] Getting diagnostic notation examples i… Carsten Bormann