Re: [Json] The names within an object SHOULD be unique.

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 07 June 2013 15:46 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 EAB8021F9346 for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 08:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.345
X-Spam-Level:
X-Spam-Status: No, score=-102.345 tagged_above=-999 required=5 tests=[AWL=0.254, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFnrO4es6-ut for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 08:46:06 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6CCDF21F9302 for <json@ietf.org>; Fri, 7 Jun 2013 08:46:06 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r57Fk3Bn081705 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 7 Jun 2013 08:46:03 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAChr6SxDaa981O3w2hixE4RFpJhUQB6TZ12j7sCOQ3HvpQvMPA@mail.gmail.com>
Date: Fri, 07 Jun 2013 08:46:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <296843F3-7933-4DF3-9FAF-841CDFD697BB@vpnc.org>
References: <51AF8479.5080002@crockford.com> <CAK3OfOgtYoPRZ-Gj5G8AnNipDyxYs=6_KD=rQTxKbhDPX6FZNA@mail.gmail.com> <51b1168c.e686440a.5339.5fc4SMTPIN_ADDED_BROKEN@mx.google.com> <CAK3OfOhL3zXHfg9EEDWLXhjLQ1aBvvxikKAiR+nUpDHJaVh+Qg@mail.gmail.com> <CAChr6SxDaa981O3w2hixE4RFpJhUQB6TZ12j7sCOQ3HvpQvMPA@mail.gmail.com>
To: R S <sayrer@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: json@ietf.org
Subject: Re: [Json] The names within an object SHOULD be unique.
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: <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: Fri, 07 Jun 2013 15:46:07 -0000

On Jun 6, 2013, at 7:59 PM, R S <sayrer@gmail.com> wrote:

> JSON is sometimes produced by naive string concatenation, which will probably never change. It is consumed by browsers, which will probably never change their duplicate key handling.
> 
> The text from RFC 4627 should stay unchanged. The suggestions for requirements on encoders are prescriptive and therefore inaccurate at this stage in JSON's adoption.

Your first paragraph does not match your second. Many of the proposals here keep the gist of RFC 4267 for encoders, "The names within an object SHOULD be unique.".  For parsers in browsers, so far all the examples we have seen have followed the proposed wording of "MUST choose the last one".

--Paul Hoffman