Hi Folks, IMO, deterministic serialization makes no sense if decoders anyway are more or less obliged to cope with anything that smells like CBOR.
As a comparison, JavaScript's JSON object offers zero serialization options (*). This enables users to concentrate on their application. The same goes for Google's Protocol Buffer. There is obviously (IMO of course...), room for a comparable (but potentially better) solution for CBOR. I would be interested to hear how YOU would design such a thing. BTW, deterministic encoding of IEEE 754 numbers can be performed without a math library: https://github.com/cyberphone/openkeystore/blob/82543e8b7ad421e950366ed6a4acac4c3311f64d/library/src/org/webpki/cbor/CBORFloatingPoint.java#L47 https://github.com/laurencelundblade/QCBOR/blob/master/src/ieee754.c Cheers, Anders *) For you nit-pickers: That 1.0 and 1 are equivalent may be regarded as a serialization option but that's not comparable to more fundamental stuff like indefinite-length encoding. _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
