Re: [Json] Update Standard to support ECMA-262 BigInt

Pete Cordell <petejson@codalogic.com> Thu, 29 April 2021 11:22 UTC

Return-Path: <petejson@codalogic.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE2D3A3AE5 for <json@ietfa.amsl.com>; Thu, 29 Apr 2021 04:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7OkDdvzCGCS for <json@ietfa.amsl.com>; Thu, 29 Apr 2021 04:22:45 -0700 (PDT)
Received: from ppsa-online.com (ppsa-online.com [217.199.162.192]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DE9C3A3AE2 for <json@ietf.org>; Thu, 29 Apr 2021 04:22:44 -0700 (PDT)
Received: (qmail 4616 invoked from network); 29 Apr 2021 12:22:42 +0100
Received: from host31-49-16-155.range31-49.btcentralplus.com (HELO ?192.168.1.72?) (31.49.16.155) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPS (TLS_AES_128_GCM_SHA256 encrypted, authenticated); 29 Apr 2021 11:22:42 -0000
To: martin.barker=40thisisbeacon.com@dmarc.ietf.org, json@ietf.org
References: <014e01d73aa1$81aa0d30$84fe2790$@thisisbeacon.com>
From: Pete Cordell <petejson@codalogic.com>
Message-ID: <5987db79-06a7-69ab-faff-29c763a9a98d@codalogic.com>
Date: Thu, 29 Apr 2021 12:22:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <014e01d73aa1$81aa0d30$84fe2790$@thisisbeacon.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/uLpQmon6Yk2lyF5ontbMnXz7IO0>
Subject: Re: [Json] Update Standard to support ECMA-262 BigInt
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Apr 2021 11:22:51 -0000

As no one else has answered this, my understanding, more as an observer 
than as a key working group member, is that you would have to put such 
large numbers in a string and RFC 8259 doesn't care what you put in 
strings.  Things like dates, durations, IP addresses, geolocations and 
large numbers in strings are beyond its scope.

At some point some work towards a separate RFC on higher level semantics 
for JSON string contents might take place but I'm not aware of any such 
work on the table yet.

HTH,

Pete.
-- 
---------------------------------------------------------------------
Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com
---------------------------------------------------------------------
On 26/04/2021 14:38, martin.barker=40thisisbeacon.com@dmarc.ietf.org wrote:
> Hello,
> 
> I’m writing to you as a programmer for a company that uses massive 
> datasets and starting to utilize 64bit numbers as our system currently 
> heavily relies on JSON, RFC 8259 I was wondering if there were any plans 
> to add support for literal notation of BigInt E.G ` 
> "property":9007199254740991n`
> 
> Kind Regards
> 
> **
> 
> *Martin Barker*
> 
> Project Systems Manager.
> 
> Data Protection Officer for Beaconsoft Limited.
> 
> <https://aws.amazon.com/certification/certified-solutions-architect-associate/>
> 
> 	
> 
> Innovation award <https://www.jsclasses.org/award/innovation/>
> 
> 	
> 
> 	
> 
> 6 Time Nominee
> 4 Time Winner
> 
> 	
> 
> Level4
> 
> www.thisisbeacon.com 
> <https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.thisisbeacon.com%2F&data=02%7C01%7C%7C7707e043fb5341f5a4f008d823244e3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637297986116422304&sdata=Xgq1Z7ECM6LEpTYNgaL0B8aPuOwX3pG3xH2ocWU%2FRJU%3D&reserved=0> / 
> https://www.linkedin.com/in/martin-barker-7745731a/ 
> <https://www.linkedin.com/in/martin-barker-7745731a/>
> 
> t: +44 (0) 3302 234 588 / d : +44 (0)113 328 2367 / m: +44 (0) 7736160152
> 
> 
> <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbcn.to%2Fgy2&data=02%7C01%7C%7C7707e043fb5341f5a4f008d823244e3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637297986116432298&sdata=5xncC2Q8nff6PSAPiuUh6puzoVKPmBcl8ZtvM3XRC0c%3D&reserved=0>Breaking 
> news.... Beacon named as Tech Nation Rising Stars 3.0 Cyber Award 2021 
> Winners. #WeAreTechNation
> 
> Beaconsoft Limited. Registered in England 10209657. VAT number 258 0216 
> 17.Registered Office: 71-75 Shelton Street, Covent Garden, London, UK, 
> WC2H 9JQ.This email is confidential and is intended for the addressee 
> only. Beaconsoft Limited does not accept responsibility for reliance on 
> this email by anyone other than the intended addressee. Although we have 
> taken steps to ensure this email and any attachments are virus-free, we 
> cannot guarantee this to be the case as it has been sent over a public 
> network. Read our privacy policy 
> <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.thisisbeacon.com%2Fprivacy-policy%2F&data=02%7C01%7C%7C7707e043fb5341f5a4f008d823244e3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637297986116442294&sdata=BwOQTHmIzMB%2BYkc17ZVv1yoJQ%2FZrK%2BAJlUNK8%2F1VEI8%3D&reserved=0>.
> 
> 
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>