Re: [Cbor] Cutting down base64 (b64'....') in diagnostic notation examples, before elision

[Carsten Bormann <[e-mail]>]

> 
>> If you randomly truncate a base64 string (no padding), there is only a
>> 1 out of 3 chance (actually 21/64) that the result will still be a
>> base64 string (no padding).  If you cut it down to a multiple of 4
>> characters, the result will always be valid.
> 
> That's a good point.

I once said that we don’t need CBOR or CDDL doctors.
I still strongly believe that, but this is an example of arcane ancient knowledge that is never written up properly…

> I wonder if this is worth sharing with the RPC people in some fashion.

So far, RPC was not the place where examples were checked.
But it is knowledge they could pass on to authors.

I’m wondering what checking I could add to kramdown-rfc to make it easier to submit healthy examples.  (Kramdown-rfc already checks your JSON.)

> "Is xml2rfc complaining about too long lines, and you just aren't sure how to
> fix that?"

{::include-fold foo1.cbor-diag}

(Ouch, this is more for YANG than for CBOR EDN.)

> "Available now, for an unlimited time, the CBOR how-to-elide HOWTO"

Yes, we need to start the WG wiki…

Grüße, Carsten