IETF Logo Mail Archive

Re: [Json] JSON and int64s - any change in current best practice since I-JSON

Rob Sayre <sayrer@gmail.com> Thu, 25 January 2024 22:16 UTC

Return-Path: <sayrer@gmail.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 B8E66C14F682 for <json@ietfa.amsl.com>; Thu, 25 Jan 2024 14:16:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCLUTGzpuQhd for <json@ietfa.amsl.com>; Thu, 25 Jan 2024 14:16:35 -0800 (PST)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5311DC14F5F4 for <json@ietf.org>; Thu, 25 Jan 2024 14:16:35 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-55c2c90c67dso5871486a12.1 for <json@ietf.org>; Thu, 25 Jan 2024 14:16:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706220993; x=1706825793; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JnDKurnnpKph/aM/glJa1A1bEBtqWJVmqxKRhZiWOHM=; b=Jy5dW5Gp9sqUmiyAX1E8kfxUHEEPjUc28VqNk8Vl3MHaa5E5oYcf05o1qX7eoMKm2I 4EK8eeHyl7EpB1fWfAS03JAKQxRM3ulgQf0nSNz0DMWhx3hoFcsXeHjA8tuTTobI51FF 8AH9oRTqeXF+dpO5dsD2u06ryLbHuNC165ZOblzWY+cqYj7crkSqXTRFG65t09hEibLy 7VYCmFUomtGcvZvCmOMGChw9I6Z2dfnyx9PXvPqQa7hnDi5oW1DtUVH/WykvPeEQUFtI zdUVlRbTzfHZjmVs4v1vwyUPCLB//t361TUSDFwgqcyt2fMHpirWF5KNvKw+EkLK6ZOZ PtdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706220993; x=1706825793; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JnDKurnnpKph/aM/glJa1A1bEBtqWJVmqxKRhZiWOHM=; b=bgkk2IEPbSjzhtPTq23tz2KEB2sy+ConxxmDOtkzyqE0L01HXUILrkVfyszS+bIoiI fgiVijVPc87tqFaCb499FTzVT0VRjCuBItC2gWvusXRgc7bAnqwn/yebIMHCmMHH0e0W XfObwh1k7MC/WJf+HFGrvCfxt7DukWLWP3xcdQ+3njyXgSiYjUzAgeJFV34QA+Er+zCo bBXNMTMpZSGvFkrPBsGCLXkQ1gJ6aR3kj3G0ySQkAKZ/N3f0lQ2ECt2IjnnTQdhkFt9O y9E2LvSykHAEjlMcA8ACPcqI4NgzT8bUw26NcOc4X1T7EUyahyu//4uXA8iO4dfk+ZKC anig==
X-Gm-Message-State: AOJu0Ywz76c7hTKEJCWLp3QTyvZYhNLneV7CvSrrVnEmxNVOxZS2+vIv j7ivQ6YRAL5v45RZ0a7IR3ytHleUtOiM/lREp3Z9TKn7syXr17XX2oVb7YTtX1TxQ1521cfXh2m vUBi8wQ98Y5q8OTfri19iO/1AJX36+3cT
X-Google-Smtp-Source: AGHT+IHo45xUb53KJ9ndto51Qljxjnrv/kLhxWl0pKhxLs0kzr+OIfzYbjQTndZVteMKrkhABQMLDfnxW6wM05MTiBY=
X-Received: by 2002:a17:906:dfe9:b0:a2d:60c5:f18f with SMTP id lc9-20020a170906dfe900b00a2d60c5f18fmr119052ejc.149.1706220993146; Thu, 25 Jan 2024 14:16:33 -0800 (PST)
MIME-Version: 1.0
References: <mailman.58.1706212803.46199.json@ietf.org> <CA+mwktLkT1ib-B6_Sye4OUUTbA762Hh2JDcLKr3AJxjUWKeWHA@mail.gmail.com> <8E48392C-B183-4035-BCAA-A2028E20F964@cursive.net>
In-Reply-To: <8E48392C-B183-4035-BCAA-A2028E20F964@cursive.net>
From: Rob Sayre <sayrer@gmail.com>
Date: Thu, 25 Jan 2024 14:16:21 -0800
Message-ID: <CAChr6SxSN_Vr55ssgyWPb+SVRSJhKfv1SHKZn5ctcZ9es582KQ@mail.gmail.com>
To: Joe Hildebrand <hildjj@cursive.net>
Cc: Daniel P <danielaparker@gmail.com>, JSON WG <json@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003474b7060fcc8867"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/aijzu9CKGzBwX4Olg9bGTop3PwY>
Subject: Re: [Json] JSON and int64s - any change in current best practice since I-JSON
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.39
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, 25 Jan 2024 22:16:35 -0000

On Thu, Jan 25, 2024 at 1:56 PM Joe Hildebrand <hildjj@cursive.net> wrote:

> Yes, unless we decided that significant digits mattered.  This was just
> copied from JSON5, I don't feel strongly about it myself, but apparently
> it's a thing that bites people trying to hand-type JSON sometimes?
>

That is a philosophical difference your effort should take a stand on. JSON
has no comments, and it does not allow trailing commas because "that would
mean someone is hand-writing it" (loose paraphrase). I think for the
numbers you should check what David M. Gay's strtod things do. There, I
think there is no debate, just reality (the GNU versions are close).

If you write Protocol Buffers or something, there are comments and trailing
commas. This is because to disallow them would be a pain for the person
adding the next field. You always have to add a field, because there is an
inevitable transition phase, even if you intended to make one unused.

thanks,
Rob

v2.23.0 | Report a Bug | By Email