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 13:19 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 DAE36C14F6AA for <json@ietfa.amsl.com>; Thu, 18 Jan 2024 05:19:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.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_DNSWL_HI=-5, 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 sqZPsWuWoDv0 for <json@ietfa.amsl.com>; Thu, 18 Jan 2024 05:19:25 -0800 (PST)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 B1C1BC15170B for <json@ietf.org>; Thu, 18 Jan 2024 05:19:25 -0800 (PST)
Received: by mail-qk1-x732.google.com with SMTP id af79cd13be357-783045e88a6so879851285a.0 for <json@ietf.org>; Thu, 18 Jan 2024 05:19:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; t=1705583964; x=1706188764; 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=Cx5uMK1XVRQVAUTglDQS0GmtHn0eHRqUiZ5vqSp4KmY=; b=J+9s91/8F37oN/eTu5XuZ7R4KlbOUlfk9QsWK0fwqJno1Vg5E/Sone/wqC4dr9ttaV bi1LmlGI0mODCJJbatEIl4LHkIgUe6R+5+QyawGrKmEZ7p6uaCQjS9YPAgipVIFF6zeS IXcYqQ9i8D+8deEfS1WcCm5uYkkq4yomnZYIk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705583964; x=1706188764; 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=Cx5uMK1XVRQVAUTglDQS0GmtHn0eHRqUiZ5vqSp4KmY=; b=maQKJPzNOH8nym8RB5eIu+b9vOhoA2GiF4mBE7pmCfwbigNgmEM9cW6lQYbrVm1k27 5Jpdr5bcTZ9zhfNkOavHqMbLilyBkO0eqmVJTaKKVs2C8f+kGp96WBghU1b9C23/s43V 6+dzsAVODCH1+bOLXBk2RxtcDY5ojJrDO1ZnTcgYkrAniCSr3CgC3ssiKf4rOPSDX1GZ qu1hR5PI1EjwdBsKJ1OVAjZHWEZb/+CdL7FIho0NhFM5yG5awijtpZWFcBFn2ETNDxec RTJwixPUWHAJ6ezLxOt7GXFqoSv+kTS495pDiL8ccpLL+uhNMLsh6BQbbEiXYLZQA0zK 1OlQ==
X-Gm-Message-State: AOJu0Yx+ntxpRwPM8KVbzJ3P6B5qk9kMns57O6W/fKY6Y9pMmreOl0JE vwCjxemNMtfMUU0G1l8rPRRzqA1f2kMQxAfxPc7FeOOk9kymI88em8SKLkh0aTieK8NZyUvN04Y =
X-Google-Smtp-Source: AGHT+IFtOI+XViXhqecyTakCp66Gpw5UIjSfRNVVLlrDsq724W0dwuO8vJUQhW+1zjR04QA32lwuhg==
X-Received: by 2002:a05:620a:4713:b0:783:6904:dadc with SMTP id bs19-20020a05620a471300b007836904dadcmr1054614qkb.32.1705583964287; Thu, 18 Jan 2024 05:19:24 -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 i1-20020a05620a144100b0078344e29771sm5029064qkl.57.2024.01.18.05.19.23 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Jan 2024 05:19:23 -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: <B22EDB2D-0AD1-4582-9191-EFB40E163F19@tzi.org>
Date: Thu, 18 Jan 2024 08:19:12 -0500
Cc: "json@ietf.org" <json@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6EB02CA-C240-4FA1-92A8-C5BB883929C7@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> <0BB09B30-B606-44CC-85DC-95A47E485316@cursive.net> <B22EDB2D-0AD1-4582-9191-EFB40E163F19@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/lO51tSBN8ZQTV5zvDK3meJBS7mk>
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 13:19:29 -0000

> On Jan 18, 2024, at 6:47 AM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> [1] has an ABNF grammar, so this should be much easier now.
> 
> [1]: https://www.ietf.org/archive/id/draft-ietf-cbor-edn-literals-07.html#name-abnf-definitions
> 
> I’m sure we handle commas right here...
> 
>> and EDN has features around encoding size that would be actively harmful a text-based interchange format, IMO.
> 
> You wouldn’t use encoding indicators in the JSON subset.

We would need to rework that grammar to make it suitable for interchange:
- Remove encoding indicators as mentioned
- Reference IEEE754 for the 0x1.2p3 format, or remove it
- Remove embedded notation
- Remove ellipsis processing
- Discuss whether results should always be an array, as sequence is currently top-level
- Discuss adding other JSON5 features

We wouldn't get Tim's desired property of one character look-ahead.

Other than that, it's as good a place to start as anywhere else.

— 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email