Re: [Json] About JSON equality
Francis Galiegue <fgaliegue@gmail.com> Wed, 20 February 2013 00:33 UTC
Return-Path: <fgaliegue@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 A9A6621F874E for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 16:33:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 ND8MmBlw93Ob for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 16:33:51 -0800 (PST)
Received: from mail-ea0-f171.google.com (mail-ea0-f171.google.com [209.85.215.171]) by ietfa.amsl.com (Postfix) with ESMTP id CE5A321F873C for <json@ietf.org>; Tue, 19 Feb 2013 16:33:50 -0800 (PST)
Received: by mail-ea0-f171.google.com with SMTP id c13so3159701eaa.2 for <json@ietf.org>; Tue, 19 Feb 2013 16:33:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=a60f7iQdJ/dPP5TPWdy8hrTN/rH73ELpynTrxk8qgHw=; b=ee+NXJh3hv9fHCRVQU8yk/HAmt6hZcBQB0WDn4dOAmZ/t3VQJ12pBggToTn87B4wnD +1x/ogKHLI/BfvKKalMkso3Jh+gYFOKBYsSPpByvEXY7AOKtgXZ06L3K90vkWXKh0rBb MofbR1rH/dXtZFRXQAl5sNLRqGw1Fuf5gIL+ZoYmMZpu2xanhDnAjHdpf5hrKa9TmMkY 5IK9rIRdFz3wjW3IXBd0WojePGe2xzgfxIHYiWeJm7d22iTQ7lyOIQlJA1oVEOm9RK1u PlFrZXRhoz3B78DbETxNYNnZJ5MundU6dvMb08M+vEECf4Od6Rp40zICcvqlA/02VUV+ cdYg==
MIME-Version: 1.0
X-Received: by 10.14.179.5 with SMTP id g5mr62660169eem.41.1361320429968; Tue, 19 Feb 2013 16:33:49 -0800 (PST)
Received: by 10.14.1.7 with HTTP; Tue, 19 Feb 2013 16:33:49 -0800 (PST)
In-Reply-To: <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> <0A83DAEF-3C96-4659-8554-89247EB6A195@vpnc.org>
Date: Wed, 20 Feb 2013 01:33:49 +0100
Message-ID: <CALcybBBQvBdQ+rtCdqz3sE4ewWrpnCZGf3+whDo_zWuqdiyeVA@mail.gmail.com>
From: Francis Galiegue <fgaliegue@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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:33:51 -0000
On Wed, Feb 20, 2013 at 1:23 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote: [...] >> >> 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 Point taken. Equality defined in the JSON RFC itself is not the way to go, and if such an equality is defined, it could be defined in another document. Now, is there a need for such a document? -- Francis Galiegue, fgaliegue@gmail.com Try out your JSON Schemas: http://json-schema-validator.herokuapp.com
- [Json] About JSON equality Francis Galiegue
- Re: [Json] About JSON equality Joe Hildebrand (jhildebr)
- Re: [Json] About JSON equality Francis Galiegue
- Re: [Json] About JSON equality Nico Williams
- Re: [Json] About JSON equality Paul C. Bryan
- Re: [Json] About JSON equality Paul Hoffman
- Re: [Json] About JSON equality Francis Galiegue