Re: [Cbor] Consolidated set of tags for map-like entities

[Emile Cormier <[e-mail]>]

I don't know anything about "mt5", but with my proposed tag set, you could
check for the presence of tag 132 (homegenous key) and you would know after
decoding the first key if all the key-value pairs can be safely decoded
into a JS Object. Of course, this requires that the sender "play along" and
actually bothers to use the tags.

On Mon, Mar 15, 2021 at 4:44 PM Joe Hildebrand <[e-mail]> wrote:

> > On Mar 15, 2021, at 12:51 PM, Carsten Bormann <[e-mail]> wrote:
> >
> > On 2021-03-15, at 19:50, Joe Hildebrand <[e-mail]> wrote:
> >>
> >> Data Item being major type 5 should really only be used if the keys are
> homogeneously strings, in my opinion.
> >
> > We are using a lot of integer labels with mt5, so why would we make that
> restriction?
>
> This is a consequence of my implementation that others probably don't
> have.  When decoding mt5, I always keep a set of [key,value] tuples until
> all of the items have been decoded.  Then, if the keys are all strings, I
> convert the tuples to a JS Object, otherwise I convert them to a Map.  If
> I've already converted to a Map in mt5 processing, it's too late to (for
> example) throw an error if there is an unexpected duplicate key.
>
> —
> Joe Hildebrand