IETF Logo Mail Archive

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

Joe Hildebrand <hildjj@cursive.net> Thu, 18 January 2024 06:02 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 7BC80C14F747 for <json@ietfa.amsl.com>; Wed, 17 Jan 2024 22:02:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 HK7dfIP54hHz for <json@ietfa.amsl.com>; Wed, 17 Jan 2024 22:01:56 -0800 (PST)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 9A44CC14F69B for <json@ietf.org>; Wed, 17 Jan 2024 22:01:56 -0800 (PST)
Received: by mail-qk1-x72c.google.com with SMTP id af79cd13be357-7834dc40bd2so468836185a.1 for <json@ietf.org>; Wed, 17 Jan 2024 22:01:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; t=1705557715; x=1706162515; 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=BhSIsqUz6Z46vgV9D0nfgHd99iz6TF3Z/1tOX4efKm4=; b=CW0ZOPgv1yw2MsbLbGB7G0QHN2JFHKzD3hE6b8WZXw0y0DLVsNWwq4gKnkfuq0s7TD 2Y9bKWr8XiGpjWQiah7BJXYXJ2VnL6rjonr+wOhIn+ISEKYeaXv++Js39hS5URkYhmI9 WLsNc5qoW03OezZnXfNtxOhJLofEl5yrkdK0Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705557715; x=1706162515; 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=BhSIsqUz6Z46vgV9D0nfgHd99iz6TF3Z/1tOX4efKm4=; b=G0+CCeF31sdcshm/EKWZTqicgYR9iEUnFHDqacrIH3fEN0v8liXx+b+1lq4p7LU44I tuiukePNmMxC4B9Wr8v5YTe4A3zs83wCrYWVd2GpHF7MyXQGkv7cFlrbbtj4htpB2koW v9MHLHXua/Z6OszSy4XlEoVVii7akXknaMzjQRiPmX/G02S8pyyVYdLenL3bmr5z0zl0 drjBq5EPqIvLNB/pryoaENAJ3btlHNanEf26+mFoMfvCx60l7WxBBCaEnHOVI60/xW0S YG9+qBsjbB3G7C/T56zLi0ccPNbZjoGC0smF0hXN1sQg5A5sjD63Ic/Dsd5zpNxY6sYr 1OEg==
X-Gm-Message-State: AOJu0YxTwweuLJ3JFh8x+/F1JudsHp0SIniemu8asFJonA5smWYcx+// ZXUZMRZ8QLBJ/Qvblzqrdyd9KGLDklZDXGn989c4DOXhZNWcATMuksE9HZDaxg==
X-Google-Smtp-Source: AGHT+IGtCuzihE1M/P34dnq74w1tqGEFcGMb+6liMETAqvxtAxRkX88SujUpQJ9WaUW36QFh7x+QDA==
X-Received: by 2002:a05:6214:19e4:b0:681:79ce:8d2c with SMTP id q4-20020a05621419e400b0068179ce8d2cmr355897qvc.21.1705557715360; Wed, 17 Jan 2024 22:01:55 -0800 (PST)
Received: from smtpclient.apple (pool-71-163-33-223.washdc.fios.verizon.net. [71.163.33.223]) by smtp.gmail.com with ESMTPSA id ks17-20020a056214311100b0068189522cd3sm534120qvb.67.2024.01.17.22.01.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Jan 2024 22:01:54 -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: <E798F54D-B727-42E5-8229-DB1F75C9378F@cursive.net>
Date: Thu, 18 Jan 2024 01:01:44 -0500
Cc: Rob Sayre <sayrer@gmail.com>, Pete Cordell <petejson@codalogic.com>, "json@ietf.org" <json@ietf.org>, Carsten Bormann <cabo@tzi.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AF08FB2-B282-45A2-A1E1-4D55E9C95A1A@cursive.net>
References: <87527a42-aaac-4f39-b320-05f18a2808c1@codalogic.com> <C31BF4C8-9E6C-48F8-BF7B-D2C379273B3F@tzi.org> <CAHBU6it4SaLawSiBgK9ySkbxjtHE6CX-P3r=hzcVy4ksoQo-Cg@mail.gmail.com> <CAChr6SxHfLW-A1asAndKJz-AiyJv5QP18bi=_bNdKXw7zYHThw@mail.gmail.com> <CAChr6SweYdCWxSABZ7g20Zd-xBFzcK0Ritq53S7WtjSwc-vLmw@mail.gmail.com> <E5A68370-CC2F-4618-AB39-39A382656616@cursive.net> <807fea1b-a22b-4d6b-aa5d-720c9b12023c@codalogic.com> <09233A73-3A6B-4E6F-AEB8-596AC6442E24@cursive.net> <869950DC-647B-4481-AEF8-9E092384E99F@tzi.org> <CBD32B58-8328-4602-89C6-BC2A7A875A0D@cursive.net> <994E2C0A-4AE0-4720-8C67-913BBF033E11@tzi.org> <CAHBU6isiUhvhk5VPpQ1A_kGDJZhsGLc1xkyu6pNeLUBHw2_dzg@mail.gmail.com> <0D9273E3-A07F-4303-9AF7-89375FDC2496@tzi.org> <CAChr6Sw=em9poOXTEsYzxbFHSRsrWzFyZof50X4Tca0E2Fecuw@mail.gmail.com> <CAHBU6it4rvnYQGnrwrigAtL05O7SH2coRrq91Si1xr3u7oC47w@mail.gmail.com> <E798F54D-B727-42E5-8229-DB1F75C9378F@cursive.net>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/o_pdY9u8lCU3_Nj_ZFfrZe0m5tA>
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, 18 Jan 2024 06:02:00 -0000

> On Jan 17, 2024, at 1:48 PM, Joe Hildebrand <hildjj@cursive.net> wrote:
> 
> 
>> On Jan 17, 2024, at 1:32 PM, Tim Bray <tbray@textuality.com> wrote:
>> 
>> If there were going to be an ESON effort, the hills I’d die on are:
>> 
>>    • Lose the commas
> 
> Heh.  I was going to say "trailing commas" which is the exact opposite.  I'd have to do a little prototyping before I agreed with you that we don't need commas at all, but I suspect it would work.  This would also lose us backward-compatibility with JSON, unless the commas are optional instead of forbidden.

Thought about it some more, wrote some code, and yes, I'm fine with comma separators being optional; whitespace / comments are enough to terminate anything that needs it.  Hopefully we could then agree that the trailing comma is optional, and we'd both be happy.

— 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email