IETF Logo Mail Archive

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

Joe Hildebrand <hildjj@cursive.net> Thu, 25 January 2024 21:56 UTC

Return-Path: <hildjj@cursive.net>
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 AB497C14F686 for <json@ietfa.amsl.com>; Thu, 25 Jan 2024 13:56:22 -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, 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cursive.net
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 QeIoI-7xZnWj for <json@ietfa.amsl.com>; Thu, 25 Jan 2024 13:56:18 -0800 (PST)
Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 84FB8C14F682 for <json@ietf.org>; Thu, 25 Jan 2024 13:56:18 -0800 (PST)
Received: by mail-il1-x12f.google.com with SMTP id e9e14a558f8ab-36287843b64so15322845ab.0 for <json@ietf.org>; Thu, 25 Jan 2024 13:56:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; t=1706219777; x=1706824577; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5Vi8rUh/qZU3AVfX9uSfPgKVXICKQBE365s4Dn9+Z5E=; b=i8TVkUdGrxWOOptnJZEc5wIBIC+joWxdt0yPgbYmiCdMq7QUomd72zwC2TBX62i93O 2wvPQArjii6AC9uoHGFYBQgAqWtQv4apg6GPynfyz0m0ZDI057T3dvcpzs8EQpS4XRd4 rvEA20HpOh/DcdRQPNAd4GhONSrYD4/W90s+M=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706219777; x=1706824577; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=5Vi8rUh/qZU3AVfX9uSfPgKVXICKQBE365s4Dn9+Z5E=; b=J0iKX4GB77Dg7R+r3M5oN1rtz+j6o82n2Q48jwEJ/Hr8al4ycKrnP59P0S7XYrVOKa 5g4tO5vK8M/0chEtlesSD0WbYsbOx2SElDjounTQMchh4Yocoo2WX2t3K4iS0z+5zBo1 ehDsGarFPF7MrbGSnAHJOXjURB99tRtqKdJSSmPf51/FpsFZ6ojS4AWjrsCy8sed/d84 7qXuni0BDdVSI6cAgjYXijluRUTBQnatnmc7+cWrb0+nsquYuhtDrqP4HDKSlmlFAIhV lrUET5lsKIQQ79sjtWDnxu9mq++/c8wzYzh1DIjfCj/StNVXLxxvmV3U14exXRQvXAXB QGUg==
X-Gm-Message-State: AOJu0Yx3UTzLuxRng/leFrnI2yw8+ZUPPr9icbmQ8EdKszxNFRcf1Zhq q2vdTlsEX3SjE2DH5nJmdW1lgvJNQRwZecUNvtWmRk/c6ia+rVXMJKjqtmNQK6kC0M4CHrkgkOg =
X-Google-Smtp-Source: AGHT+IElIQd+ovPZ1iUvzrzyMzi9sYEWfsMNqlCKo/whQ1Lilq/0spqUlueXEVZHaeIF7H2Th/30WQ==
X-Received: by 2002:a92:dc10:0:b0:35f:f683:f76f with SMTP id t16-20020a92dc10000000b0035ff683f76fmr491777iln.32.1706219777521; Thu, 25 Jan 2024 13:56:17 -0800 (PST)
Received: from smtpclient.apple ([2601:282:2100:4fc9:25e1:9353:a850:2867]) by smtp.gmail.com with ESMTPSA id f13-20020a02cacd000000b0046f394096ddsm8685jap.105.2024.01.25.13.56.17 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Jan 2024 13:56:17 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
From: Joe Hildebrand <hildjj@cursive.net>
In-Reply-To: <CA+mwktLkT1ib-B6_Sye4OUUTbA762Hh2JDcLKr3AJxjUWKeWHA@mail.gmail.com>
Date: Thu, 25 Jan 2024 14:56:06 -0700
Cc: JSON WG <json@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E48392C-B183-4035-BCAA-A2028E20F964@cursive.net>
References: <mailman.58.1706212803.46199.json@ietf.org> <CA+mwktLkT1ib-B6_Sye4OUUTbA762Hh2JDcLKr3AJxjUWKeWHA@mail.gmail.com>
To: Daniel P <danielaparker@gmail.com>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/7AbFuhMNDfYXpo4TlPNlWSVYmd8>
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 21:56:22 -0000

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?

— 
Joe Hildebrand

> On Jan 25, 2024, at 1:48 PM, Daniel P <danielaparker@gmail.com> wrote:
> 
>> From: Joe Hildebrand <hildjj@cursive.net>
>> To: Carsten Bormann <cabo@tzi.org>
> 
>>> * leading/trailing decimal points.  What is the semantics that need to be defined here?
>> 
>> For leading, probably none.  For trailing, it might be a sign that the number should be treated as floating point, so that there is a difference between `1` and `1.` in environments where there are different types for float and int.  At the very least, the range checking should be different.
>> 
> Wouldn't `1.0` convey the same?
> 
> Daniel
> 
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json

v2.23.0 | Report a Bug | By Email