IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Fri, 30 April 2021 20:53 UTC

Return-Path: <cabo@tzi.org>
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 96B273A268E for <json@ietfa.amsl.com>; Fri, 30 Apr 2021 13:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=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 UVHvwy8fXJrP for <json@ietfa.amsl.com>; Fri, 30 Apr 2021 13:53:25 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 434C83A268D for <json@ietf.org>; Fri, 30 Apr 2021 13:53:25 -0700 (PDT)
Received: from smtpclient.apple (p548dcb12.dip0.t-ipconnect.de [84.141.203.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4FX4Ml0Nt3zyTV; Fri, 30 Apr 2021 22:53:23 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CA+mwktLWwDRYtF9BFSRnF4e7_v=e3F4HERS5yHptSksxGBysnQ@mail.gmail.com>
Date: Fri, 30 Apr 2021 22:53:22 +0200
Cc: JSON WG <json@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1A006F9-8743-4930-B879-F83339A38485@tzi.org>
References: <CA+mwktLWwDRYtF9BFSRnF4e7_v=e3F4HERS5yHptSksxGBysnQ@mail.gmail.com>
To: Daniel P <danielaparker@gmail.com>
X-Mailer: Apple Mail (2.3654.80.0.2.43)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/GEwGIQO1CR8j5nN7VWahFl5xvgw>
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: Fri, 30 Apr 2021 20:53:30 -0000

On 30. Apr 2021, at 21:36, Daniel P <danielaparker@gmail.com> wrote:
> 
> From: Pete Cordell <petejson@codalogic.com>
> 
>> 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.
> 
> Do you mean in the context of a schema specification?

CDDL (RFC 8610) can already do much of what is probably needed here.
If there is anything else to be added, CDDL has an extension point (control operators) that is rather flexible.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email