What's a Number? Was: TJSON from Anders Rundgren on 2016-11-04 (public-interledger@w3.org from November 2016)

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Fri, 4 Nov 2016 06:11:58 +0100
To: Tony Arcieri <bascule@gmail.com>
Cc: Interledger Community Group <public-interledger@w3.org>
Message-ID: <ea62a6a2-c9d8-4f9a-66f1-644098c1b3f3@gmail.com>

There's probably a single data type in JSON that cause 99% of the problems and that's numbers.

The scientific people want 80-bits IEEE
The Java/Python/C# folks want true 64-bit integers
The crypto geeks want really big integers
The financial guys want big decimals

These problems stem from JavaScript and they all have the same solution/workaround; put the data in a JSON "string".

Does this limitation/deficiency motivate a [sort of] new JSON?

In my book it does not but it seems that a lot of other people think it is a great idea so I can only wish you good luck!

Anders

Received on Friday, 4 November 2016 05:12:34 UTC