Re: [Cbor] eliding CBOR diagnostic notation binary contents

[Carsten Bormann <[e-mail]>]

> On 2022-03-13, at 22:29, Michael Richardson <[e-mail]> wrote:
> 
> Signed PGP part
> 
> Carsten Bormann <[e-mail]> wrote:
>>>> Actually processing elisions should be a special flag.  That should
>>>> address your concern.
>>> 
>>> Yes, that works for me.
> 
>> In cbor-diagnostic, this flag is now “-ah”.
> 
> Cool.
> 
>> $ gem install cbor-elision
> 
>> $ echo "h'...4711...'" | diag2pretty.rb -ah
> 
> The direction I really want to automate is cbor2pretty, when generating examples.

Are you sure about cbor2pretty (annotated hexdump) vs. cbor2diag?

A hexdump is much harder to have elisions that you can read in again:
The length information implicitly conveyed by the syntactic structure of diagnostic mode is missing.
So you don’t know how many bytes the elision is supposed to cover.
(Unless you start parsing the annotations…)

> There are some ways in which I can see doing this:
>  1) some option which just elides any bstr longer than X.
>  2) some option which elides based upon some other (content-relevant) tag.
>  3) some option which takes some kind of CBOR-PATH to specify what to elide.
> 
> I think that "CBOR-PATH" is not yet a thing, but I think I've heard you talk
> about how we can essentially use JSONPATH to do this?

Also, it might be useful to mix in a CDDL spec and build a path based on the parse tree.

CBOR-Path should be able to handle all of these, but it still needs to be invented (after JSONPath is done, presumably).

Grüße, Carsten