IETF Logo Mail Archive

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

Daniel P <danielaparker@gmail.com> Thu, 25 January 2024 20:49 UTC

Return-Path: <danielaparker@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 CA49CC14F682 for <json@ietfa.amsl.com>; Thu, 25 Jan 2024 12:49:08 -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, RCVD_IN_DNSWL_BLOCKED=0.001, 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 wZHJPFte7R8a for <json@ietfa.amsl.com>; Thu, 25 Jan 2024 12:49:08 -0800 (PST)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 66E2DC14F5FA for <json@ietf.org>; Thu, 25 Jan 2024 12:49:08 -0800 (PST)
Received: by mail-io1-xd34.google.com with SMTP id ca18e2360f4ac-7ba903342c2so398973039f.3 for <json@ietf.org>; Thu, 25 Jan 2024 12:49:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706215747; x=1706820547; darn=ietf.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=lp4x/p9SugqGh+W7mZ94f7Uhwf574jS9OmRI7oXt3pU=; b=fVkwF6VieS2OP5AkGVjaOkkokBSrwBtv8/QBHoiBuLeO/vKXMyqNtxf6ztn4Ycjp3n yDRc1sipuZEkvE5dXN9KB0pNBboTKhU6K6GgI6iwzGPsHGTFr9xUaafs7TxbNSxtIamQ Z6RptfmLhCZQdlvoh7WWjr93z81CNDK7nfropgs9Fa6BCUgplEd82mIyheX2VoTn/hDM MVkJKKoZetTveyZDCiW66z1m+UKQF7CyhooFzDRGXzSuXnqNzJPwhYpBPsIm1IQkTfSB +3sN5N5r6619qbv8Ll6nwo5iLwDh2BAJWnvtKfOAuIHviZnlhelK0yiQshysmcktO9sy X4nA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706215747; x=1706820547; h=content-transfer-encoding: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=lp4x/p9SugqGh+W7mZ94f7Uhwf574jS9OmRI7oXt3pU=; b=sqMtRixh4tc+k6vW2pzO6IZ6rnXHlC8mvVwI9lD5ZZ5rWYizfoRHubBbLuQSR6es3W gxrSU+NwC+RYdQHbJPFppLlA029VVzgV4GqZV6k3exlvkcFJAkNPZSK1+FYYNWnwU24Q QyiHIyBresgobavWniXioFwmI4fwNVyBAUdq4Ph6XdVb2oDtBx/HWsKQ1KAxZnN+kYYi 3ZOc3YzP5+f4l/LtITleGNIWWD3DdKwnmIaV8AT2HPvvpSEU2hyoV+FAaeN7aRwk963w Vyg2PZ4F3MYammB+rA3RV5DtH5snfM2Wt4bHj9iyedqHtoDCCcMncSYzx0RKX5NjIf9s kmyw==
X-Gm-Message-State: AOJu0YyqOMMiLCqf300Etd0H5e1ln4VUCGSej+/giLUu4O6/aPJk41tH xLqPrqY6jeUi+AighNIk/F0fVoh8lOvQdpsTaW0adSR1FGT0B6zpMJy5p3l3pvBesxurflQKWl6 eP7stud8Zf6JFWe1qC3mtDIeUUnShuEzmE7E=
X-Google-Smtp-Source: AGHT+IHQPhSPBRyMdxSCMxvwHXjnTHnlHD5iH8Nu08KlnlcpHexCPG9/GzYxdGNQcY1lYm2r5JoNtd5v4F4f2pqEII4=
X-Received: by 2002:a05:6602:330e:b0:7bc:484e:7c73 with SMTP id b14-20020a056602330e00b007bc484e7c73mr400938ioz.1.1706215747496; Thu, 25 Jan 2024 12:49:07 -0800 (PST)
MIME-Version: 1.0
References: <mailman.58.1706212803.46199.json@ietf.org>
In-Reply-To: <mailman.58.1706212803.46199.json@ietf.org>
From: Daniel P <danielaparker@gmail.com>
Date: Thu, 25 Jan 2024 15:48:56 -0500
Message-ID: <CA+mwktLkT1ib-B6_Sye4OUUTbA762Hh2JDcLKr3AJxjUWKeWHA@mail.gmail.com>
To: JSON WG <json@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/ZySv0w26r2dglU3ZrXISLWhFJro>
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 20:49:08 -0000

> 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

v2.23.0 | Report a Bug | By Email