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

Tim Bray <tbray@textuality.com> Fri, 07 June 2013 17:34 UTC

Return-Path: <tbray@textuality.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 2619821F8F5C for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 10:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.714
X-Spam-Level:
X-Spam-Status: No, score=-1.714 tagged_above=-999 required=5 tests=[AWL=1.262, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 jpxUABlYW-Tu for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 10:34:09 -0700 (PDT)
Received: from mail-vc0-f170.google.com (mail-vc0-f170.google.com [209.85.220.170]) by ietfa.amsl.com (Postfix) with ESMTP id 3D17921F955A for <json@ietf.org>; Fri, 7 Jun 2013 10:34:09 -0700 (PDT)
Received: by mail-vc0-f170.google.com with SMTP id hf12so2975129vcb.15 for <json@ietf.org>; Fri, 07 Jun 2013 10:34:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=EByY7aH5/yYCZo079509YM/HsEb1breSpgk6OBTYjcg=; b=NHLwrVgwpZvl5kVhuKSeWnNcNmkhyOUGPSdUzgsLQ+hRWNAjJ70GZix+3DRZQ9tiQl io4Nm0/OioGB9cwreEPldHqCI0I2k6wr8y/fogXU9svSJkF/LotnJETvGrCpCBCvRJXr 1z4E+iyMWTDhis4JoilvngvQtTD9u0WnWSTDHCwav9y8sRmE0Ih6NQBRdZMGB4v2CkoE jYmxQwybBJJ7aOhlji1hwAXgR1vEWtPOHYpqULqwczmEmrXtUCjIMd8XAO8Yt/QSIOY+ 2tXEfmfLWpQnaSwMNTNwy3B418qReD9253ZxOtMbEGVF4UuHNAXKMAos5lS+Rd3fP6ru Q9XQ==
MIME-Version: 1.0
X-Received: by 10.58.6.141 with SMTP id b13mr1308090vea.45.1370626448546; Fri, 07 Jun 2013 10:34:08 -0700 (PDT)
Received: by 10.220.48.14 with HTTP; Fri, 7 Jun 2013 10:34:08 -0700 (PDT)
X-Originating-IP: [96.49.81.176]
In-Reply-To: <CAO1wJ5SF_SEc4NCJwSehmSZyVcDjdoxNZSMktdn_JcSLvMFUrw@mail.gmail.com>
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> <CAO1wJ5SF_SEc4NCJwSehmSZyVcDjdoxNZSMktdn_JcSLvMFUrw@mail.gmail.com>
Date: Fri, 07 Jun 2013 10:34:08 -0700
Message-ID: <CAHBU6itdoz_U9ZTEVV=M6WYJx=gQrBjpHTUYdTq4QXUfPfG5ig@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Jacob Davies <jacob@well.com>
Content-Type: multipart/alternative; boundary="047d7b672c48976b9204de93d6b1"
X-Gm-Message-State: ALoCoQkta9/+glcEm4Gk7uAFmArkd5t9VVelj77WSHcaOoxDVJtDyx1ZaH9DjP6cMn0lFINzSjss
Cc: Nico Williams <nico@cryptonector.com>, "json@ietf.org" <json@ietf.org>, Markus Lanthaler <markus.lanthaler@gmx.net>, R S <sayrer@gmail.com>
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 17:34:14 -0000

+1


On Fri, Jun 7, 2013 at 10:30 AM, Jacob Davies <jacob@well.com> wrote:

> On Thu, Jun 6, 2013 at 7:59 PM, R S <sayrer@gmail.com> wrote:
> > 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.
>
> +1
>
> I don't think there is anything you can do about this in the
> specification except give the doctor's advice: "Don't do that." It is
> better to leave the behavior unspecified and advise against using it
> than to try to specify some one way of handling it that can't be
> relied on in the real world.
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>