Re: [Json] About JSON equality

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 20 February 2013 00:23 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 CAE3221F85F0 for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 16:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level:
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qaFSvuJ1zVET for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 16:23:34 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5CACF21F85ED for <json@ietf.org>; Tue, 19 Feb 2013 16:23:33 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-12.dsl.dynamic.sonic.net [50.1.98.12]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r1K0NScg055671 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 19 Feb 2013 17:23:29 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CALcybBCaLQcrE8hYdTgnmthcc884JMyBA+V4kS+SKONt4_xAfg@mail.gmail.com>
Date: Tue, 19 Feb 2013 16:23:28 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A83DAEF-3C96-4659-8554-89247EB6A195@vpnc.org>
References: <CALcybBAqONQ+UAzcnJFkphsQk=qSpLwdEoYR-6YETY2GP_EN6w@mail.gmail.com> <A723FC6ECC552A4D8C8249D9E07425A70F8980FE@xmb-rcd-x10.cisco.com> <CALcybBCaLQcrE8hYdTgnmthcc884JMyBA+V4kS+SKONt4_xAfg@mail.gmail.com>
To: Francis Galiegue <fgaliegue@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] About JSON equality
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 20 Feb 2013 00:23:36 -0000

On Feb 19, 2013, at 3:19 PM, Francis Galiegue <fgaliegue@gmail.com> wrote:

> On Wed, Feb 20, 2013 at 12:10 AM, Joe Hildebrand (jhildebr)
> <jhildebr@cisco.com> wrote:
>> Are you proposing that this be added to 4627bis, or that it be in a
>> separate document?
>> 
> 
> That is what I am asking.

OK, then. I fully disagree.

> I believe the more JSON is used, the more
> people will want to "compare" JSON values, whatever they may be (and a
> hint again: please make RFC 4627bis allow to transfer _any_ JSON
> value, not just arrays and objects).

JSON has been used for many, many years without any strong need for such a comparison semantic in the base spec.

It is fine for there to be a separate standard that is usable by applications that want to compare JSON documents; the rest of the world (and that seems like the large majority) can ignore the comparison document and just use the base spec to understand how to create and consume JSON objects and JSON files.

--Paul Hoffman