Re: [Json] JSON or I-JSON?

Anders Rundgren <anders.rundgren.net@gmail.com> Fri, 26 February 2021 12:49 UTC

Return-Path: <anders.rundgren.net@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 56FC93A14E9 for <json@ietfa.amsl.com>; Fri, 26 Feb 2021 04:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VGbmiyTe11un for <json@ietfa.amsl.com>; Fri, 26 Feb 2021 04:49:43 -0800 (PST)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 075033A14E2 for <json@ietf.org>; Fri, 26 Feb 2021 04:49:43 -0800 (PST)
Received: by mail-wm1-x32e.google.com with SMTP id w7so7337750wmb.5 for <json@ietf.org>; Fri, 26 Feb 2021 04:49:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=gEKWqTN3mU3XDbAsC4ISZgerioyX6wBnWkthMHEzByA=; b=tVrt4GQU6l3vslZOU+8kaGOh7uEaLEeauU5dAXDRFO6Vu5LWD3CwQiJARRwNprHmW8 lslPz9kDEFQwWdJ5uHnS+UEb5zcLlvOKwVBMGLTGEB3cIaCreegMvFRjWjEDUX7j4tgT lFR001hfkciMfAGkBg+osgtGFnpNsHx8rpDvH4PCV8pGJcmEy5zdhUUVPzYrVtTAbTkZ THCHGh3t6wqfFQpfD4tGOlvkL3rLWZTGaaQa61yMBtrk1FkNDbqp3qe6P8gTNOsceJDv 6Z4Iu5i15zt9Mv9VHEWt27GWcGSXCOmM7FrugzSAj0XMID0XXx56AIdU+JJP9cFbzeh+ tI7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=gEKWqTN3mU3XDbAsC4ISZgerioyX6wBnWkthMHEzByA=; b=BYnepkI70dncH7S5mJXwxP+85LrjRXzljZkiMlQ5Vtr9+EPyqqihWfjZsZhMggJV8x B0Dw5gTVKJaeHNHbnK4cdyN9Tt/khMVeVfXoaZO94GiroZV+ks+8jnIOUBhpg8JiVd4D 0P6hQKHWeRsXJ4G+w1GXQ/1sLL0DB27pD4/QHKOixJ6d7o0EOH0gJujv7KEVSPyz+KcW hnGcTLVPNF/OLODKswvUZ6W1uXf+IFs+vAgM06vHsuywH4KxbW8qWr0d2i87z/T1PgM1 Arke8SrXL+vPzvH9jwzDc7/ECHtoqIl8XTGjwhFrJzlb5rB6vP7mQi8frNaOClXa/fay hOIw==
X-Gm-Message-State: AOAM531be7BUrno0slUWFrHSsalRv0N6GsuCCMGFgi8cNBkHnaKxxjcf tGpET/WBS5YWZbopjufHUeQkm1wlzdFIiQ==
X-Google-Smtp-Source: ABdhPJwMPnegBY/zmfz63XQdE/PK8eQx6Qr05RaQsenKkM4qLsdnhAIfgfMiuuy5IpCSi0JF6cpKcw==
X-Received: by 2002:a1c:c257:: with SMTP id s84mr1529632wmf.96.1614343780978; Fri, 26 Feb 2021 04:49:40 -0800 (PST)
Received: from [192.168.1.67] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id v9sm13493516wrn.86.2021.02.26.04.49.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 26 Feb 2021 04:49:40 -0800 (PST)
To: Pete Cordell <petejson@codalogic.com>, "json@ietf.org" <json@ietf.org>
References: <90cddfc3-c320-5ac0-210b-c77636383a6b@codalogic.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <1c819bc9-283d-e36b-7de2-507553420faa@gmail.com>
Date: Fri, 26 Feb 2021 13:49:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <90cddfc3-c320-5ac0-210b-c77636383a6b@codalogic.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/q0mWPlE5Z-MQeDNajcVPUiUdrvs>
Subject: Re: [Json] JSON or I-JSON?
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 26 Feb 2021 12:49:48 -0000

On 2021-02-26 12:02, Pete Cordell wrote:
> Quick question if I may...
> 
> When defining new IETF standards that want to use JSON, are they
> referencing JSON (RFC8259) or I-JSON (RFC7493)?

If the standard-to-be is supposed to interoperate with browsers and node.js the only viable option is RFC7493.

If the standard-to-be also targets the financial market, further constraints apply since floating point arithmetic is ill-suited for monetary operations. E.g. a monetary amount of 46.99 should be represented in JSON as the string "46.99".

Anders

> 
> Thanks,
> 
> Pete.
>