[Cbor] Re: I-D Action: draft-mcnally-deterministic-cbor-10.html

[Anders Rundgren <[e-mail]>]

On 2024-06-17 11:23, Wolf McNally wrote:
> Anders,
> 
>> On Jun 16, 2024, at 7:50 AM, Anders Rundgren <[e-mail]> wrote:
>>
>> Revised text proposal:
>>
>> 2.3 Numeric Reduction
>>     To provide deterministic encoding in platforms that do not separate integer
>>     and floating point values (like JavaScript), numbers must be canonicalized.
>>     Numeric reduction ensures that semantically equal numeric values (e.g. 2 and 2.0)
>>     are encoded into identical byte streams (e.g. 0x02) by encoding "Integral floating point values"
>>     (floating point values with a zero fractional part) as integers when possible.
>>
>> Since this is the essence of dCBOR, I would drop all other parts of dCBOR, since similar restrictions and limitations can be found in just about any other CBOR-using application as well.
> 
> This is *not* the "essence of dCBOR.” There is *nothing* platform-specific in the motivation or specification of dCBOR, not for JavaScript or any other execution environment.

I know that.  Nowadays.


> The motivation for numeric reduction is: to give the most common types of numeric values a *deterministic* serialization.
> 
> That’s it.

Not really, this is obviously a sore point since nobody else have questioned my claim that numeric reduction in itself [*] is not more deterministic than the scheme used by CDE.

Anders

*] Disregarding any external factors, JSON compatibility, or API considerations.


> 
> No more no less.
> 
> Please stop mischaracterizing.
> 
> ~ Wolf