[Json] CBOR Cross-Platform Spec @ IETF-123

[Anders Rundgren <[e-mail]>]

This mentioned event is currently unscheduled but the topic may be of interest anyway.  Here is a partial presentation:
https://cyberphone.github.io/doc/research/[e-mail]
I hope you don't mind, but the project is intended as a "JSON Challenger".

Rationale:
Imagine that in order to program in JavaScript, you would have to read (and understand) the ECMA specification.  The number of JavaScript programmers would most likely decrease by at least least 3 magnitudes 😆

The situation with CBOR has some similarities. Although RFC 8949 is great for advanced developers of CBOR tools, it is over the top for most application developers.  CBOR also supports multiple encoding options, something that JSON developers mostly have been relieved from.

The CBOR Cross-Platform Project (and the associated specification), is an effort to make CBOR more accessible, while maintaining the power of CBOR.  Unlike JSON, deterministic encoding is the default for tools adhering to this specification.  Sorting a 20 element map is hardly an issue for a Java, Go, or Python implementation running in a PC, Mobile phone, or Web server.  However, to maintain compatibility with "legacy" (non-deterministic) CBOR, compliant decoders should also support a "lenient" mode.

let cbor = CBOR.String("CBOR is not 🚀 science").encode();

Anders