IETF Logo Mail Archive

Re: [Json] Counterproposal #2 on work items

Vinny A <jsontest@yahoo.com> Thu, 21 February 2013 01:12 UTC

Return-Path: <jsontest@yahoo.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 A74B921E804B for <json@ietfa.amsl.com>; Wed, 20 Feb 2013 17:12:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Level:
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_35=0.6, MIME_QP_LONG_LINE=1.396]
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 C32dtW5pshti for <json@ietfa.amsl.com>; Wed, 20 Feb 2013 17:12:05 -0800 (PST)
Received: from nm37-vm8.bullet.mail.gq1.yahoo.com (nm37-vm8.bullet.mail.gq1.yahoo.com [98.136.217.44]) by ietfa.amsl.com (Postfix) with ESMTP id 192B921E8049 for <json@ietf.org>; Wed, 20 Feb 2013 17:12:04 -0800 (PST)
Received: from [98.137.12.61] by nm37.bullet.mail.gq1.yahoo.com with NNFMP; 21 Feb 2013 01:12:04 -0000
Received: from [98.136.185.199] by tm6.bullet.mail.gq1.yahoo.com with NNFMP; 21 Feb 2013 01:12:04 -0000
Received: from [127.0.0.1] by smtp108-mob.biz.mail.gq1.yahoo.com with NNFMP; 21 Feb 2013 01:12:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1361409124; bh=Btisi2AKx9SXl3BIARb3muzbtEJWBOr3LRnHrkkugWk=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:References:In-Reply-To:Mime-Version:Content-Transfer-Encoding:Content-Type:Message-Id:Cc:X-Mailer:From:Subject:Date:To; b=y/sLqMKSNzafprWhF6Gjjg99u6ddjqDhxNVyClSiqmYNvJePDHDdCB4hopWtGCgKeb7wkniU24qn2KPB02UPe+OANG3Jn6ISL18aZH24llfQ8fTCu6A6N9SEWQquXHu+XP+77AlZlsNpZYz9MMywCqLCOT7avKZC/xQSkl9gAl0=
X-Yahoo-Newman-Id: 615545.45428.bm@smtp108-mob.biz.mail.gq1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: .HGXQNIVM1kLvmONHqxWdFrJsVw86Wg09lT0_TMz.ma9XD5 au_XCYZO1ZPRKOQiqJue7vziafRkBFtymViFBn.HQTWxT9Lx3y.JCyLxwv0a 5QvcUFGjp6bTxuF0tZSX3slHBMdsKjK33SkYVF9lV4I2C5DOxyqDEWZq6Nxl 7kSNnd6JEcSXLCWTUOywO1mdzAZRnJ8qW60mP4RQMf9VfiyI6O3FHCGN6gAx TCeNmjpw77a4BS65YfgOU2jB2650HEL_UMqwBmz7gN03XHPQEO21PtG6uADp XBp4wEEBA9pA4D8C_F6SitA2zacFGGvPNhg66aSx.Dps8O1jLqoo5PhqVrnd E_KLAOCPllee4.g3Jfqo2HI_kGGyD.o0P5wECh.aAglkNn8X0t8EdNYlS1FB lx9FAh10P1tAy2LG8409Hl2LbhuAdPbwupA--
X-Yahoo-SMTP: indQcmSswBC8IKsm6t4aCAPskK3T
Received: from [192.168.0.102] (jsontest@76.29.100.42 with xymcookie) by smtp108-mob.biz.mail.gq1.yahoo.com with SMTP; 20 Feb 2013 17:12:04 -0800 PST
References: <CALcybBC87P7FT7n5d8xmXMxSFU1LBS9eJUsRX4hfYP5CUJr3QA@mail.gmail.com> <A723FC6ECC552A4D8C8249D9E07425A70F89B751@xmb-rcd-x10.cisco.com> <CALcybBBSL3w1-JRzUVWMmfS+jzytKNOv6omD1cR+_CLjze6WsA@mail.gmail.com>
In-Reply-To: <CALcybBBSL3w1-JRzUVWMmfS+jzytKNOv6omD1cR+_CLjze6WsA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
Message-Id: <12CE5BFB-49C5-48D0-96DF-F78F0D60578A@yahoo.com>
X-Mailer: iPod Mail (9B206)
From: Vinny A <jsontest@yahoo.com>
Date: Wed, 20 Feb 2013 19:12:01 -0600
To: Francis Galiegue <fgaliegue@gmail.com>
Cc: Tim Bray <tbray@textuality.com>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Counterproposal #2 on work items
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: Thu, 21 Feb 2013 01:12:07 -0000

On Feb 20, 2013, at 2:39 PM, Francis Galiegue <fgaliegue@gmail.com> wrote:
> Duplicate keys in an object, on the other hand, are indeed an
> important subject


There's a lot of interesting discussion in this thread, but I'd like to see more on duplicate keys. Various parsers either throw errors or record the last key:value pair when encountering duplicate keys, and I'd like to see a recommendation consensus.

One parser I've seen took a fascinating approach: it copied all values of a shared key and added them to an array, keyed to the duplicate key.

v2.23.0 | Report a Bug | By Email