Re: [Cbor] dCBOR moving from numerically-typeless systems

[Carsten Bormann <[e-mail]>]

On 2023-03-12, at 23:02, Wolf McNally <[e-mail]> wrote:
> 
> it *can’t* be a requirement as not all CBOR is valid dCBOR, and by extension not all JSON can be converted to dCBOR,

Non sequitur.

Of course not all CBOR is valid dCBOR.
You could design dCBOR so that all valid CBOR can be converted to valid dCBOR, but you chose to (slightly) subset the generic data model instead.
I’d say, quite appropriate for dCBOR’s area of application.

The part I don’t understand is about JSON: JSON’s generic data model already is a pretty heftily proper subset of CBOR.
(JSON does not define a generic data model, but I-JSON RFC 7493 does record the common assumptions that are needed to make JSON’s generic data model interoperable).  
What is in there that can’t be converted to your design of dCBOR?

Grüße, Carsten