IETF Logo Mail Archive

Re: [Json] JSON Concluded? Well, maybe not

Richard Gibson <richard.gibson@gmail.com> Sun, 31 December 2017 23:39 UTC

Return-Path: <richard.gibson@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 2C01A126C89 for <json@ietfa.amsl.com>; Sun, 31 Dec 2017 15:39:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 NrQR0Z3-Bkru for <json@ietfa.amsl.com>; Sun, 31 Dec 2017 15:39:06 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 AE81E124217 for <json@ietf.org>; Sun, 31 Dec 2017 15:39:06 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id i11so55624065wmf.4 for <json@ietf.org>; Sun, 31 Dec 2017 15:39:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gqBUlM3K29gY9joCenL2anpfcHk8xgbggAhZbn0qfYQ=; b=cBl/0hBb/u9fY3ZRbU1pMk+QsN6VC/2Mf4hWKOda2hsgep01T/Os5n1oa7z38VxwcG j+y17itfh8usgzrTV5I1D5cnWvgWjiwYvPtn26PGM81JXz/q52thBIJLV4J0QC5OmI0+ zdQygCfU378cq5MvA9gdEuGMxVjySSWBNEOy8OKQeJevOJKE4GkDo4j/9ZxNLWVqiJ9W yVqtDetSA+Es0gRKargyGv9tj44L/gC/yj44OpkNQL10tU1eH0BtiZpJtjgc79MXMP9F Ul7adZ2RZC4WDrYi+ASvVmF0L5jGxcdKJWWKtKksly9+H+FCOxjSb2uVdbULZ5sbF0ol YcsA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gqBUlM3K29gY9joCenL2anpfcHk8xgbggAhZbn0qfYQ=; b=dP3EGVB8KCVjMUwuqW0XVS4Btin/bkC9jndH0JexMXUAdVzgRGD2zwLHwxkBteKvLU Dr5mpgX/WIGdT1v6HwtJl5SZsvf9Cus5gnIew6UsTljLHXLFzsVn07UVa7wEVVPszk63 aiQkEt/pvE+XlRFqsX9Lhk3aHLTcnN1LF6ETq4LUcZkyM3aTfcPce1u4z31fTj+3qhkn +5On4JlcmSm0ycyoh/g7DybA3ykahuiUwyHL4v5UN7h0ij2rg06HuSd7QJlKW6rU6tjW bsqiRiUdZWqPwa/ZiRVZ9ZkUxsO8VDTMcXMEC2z0zE9bP6ULVIxTpmO/uzCbx6ZA9gK1 PFVg==
X-Gm-Message-State: AKGB3mLC6Hy3hrHQLmS0TrXrby5yVM5PlslPYyhtTIVUcOS4vT6THM+Y PqFtpVUQdwnqkPP/KElNjxeGi4jNXlEXHlgGWz4=
X-Google-Smtp-Source: ACJfBovnZ6nSN47u7YtZfGFdHg36UurS83V5C1KmvTVr+rOvPepxmfEeJ0F5jUvk90+UAQFDFQQJWEWsm4Nd+z2Ca5M=
X-Received: by 10.28.134.133 with SMTP id i127mr34514134wmd.79.1514763545074; Sun, 31 Dec 2017 15:39:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.160.189 with HTTP; Sun, 31 Dec 2017 15:39:04 -0800 (PST)
In-Reply-To: <CADEL5zshRaHtVNAtNggwHaPKP9xWeePcBZcQc1EM8SEfUu41Uw@mail.gmail.com>
References: <13860352-ef8e-1d4b-2eff-27e275c25e3a@gmail.com> <CALH+fvqBGu0i=LcciYgOLSwbQJXfqgcXTdd=rxvfHfqiRyBj7g@mail.gmail.com> <CAHBU6itC+XAKhc_m_ywG5O2bpky9DnmzfiNVqP3WrxLaE7uenA@mail.gmail.com> <92077f95-5dd6-3f5b-4765-d14067f698ac@dret.net> <CADEL5zshRaHtVNAtNggwHaPKP9xWeePcBZcQc1EM8SEfUu41Uw@mail.gmail.com>
From: Richard Gibson <richard.gibson@gmail.com>
Date: Sun, 31 Dec 2017 18:39:04 -0500
Message-ID: <CALH+fvqkBkQCiXfx1cxXaX092sbW6fgUmUizXP1f=ScMZ3bBqQ@mail.gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: JSON WG <json@ietf.org>
Content-Type: multipart/alternative; boundary="001a11441c0205e1290561ab5f72"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/tUGe-m_81cvBC6d05Q5tMkh_Pjw>
Subject: Re: [Json] JSON Concluded? Well, maybe not
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 31 Dec 2017 23:39:09 -0000

On Sun, Dec 31, 2017 at 4:34 PM, Anders Rundgren <
anders.rundgren.net@gmail.com> wrote:

> For normalization it turns out that JSON.parse() and JSON.stringify() as
> specified by ECMA and already supported by the most widely available JSON
> tools is all you need!
>

That is definitely not true. A trivial counterexample:
https://jsbin.com/luyoveyuqu/edit?js,console,output

v2.23.0 | Report a Bug | By Email