[Json] Duplicate names: are they erroneous or not?

John Cowan <cowan@mercury.ccil.org> Sun, 07 July 2013 05:53 UTC

Return-Path: <cowan@ccil.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8042521F9E3E for <json@ietfa.amsl.com>; Sat, 6 Jul 2013 22:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.577
X-Spam-Status: No, score=-3.577 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id wrL9xsfnImEl for <json@ietfa.amsl.com>; Sat, 6 Jul 2013 22:53:54 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org []) by ietfa.amsl.com (Postfix) with ESMTP id 82BD321F9E3A for <json@ietf.org>; Sat, 6 Jul 2013 22:53:41 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1Uvhuk-0007r5-Rl; Sun, 07 Jul 2013 01:53:38 -0400
Date: Sun, 7 Jul 2013 01:53:38 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Jim Schaad <ietf@augustcellars.com>
Message-ID: <20130707055338.GB2947@mercury.ccil.org>
References: <B86E1D4B-1DC8-4AD6-B8B3-E989599E0537@vpnc.org> <CAK3OfOj3MNNhjwo2bMa5CgoqynzMRVvviBXC8szxt5D17Z7FDg@mail.gmail.com> <51D3C63C.5030703@cisco.com> <51D48023.1020008@qti.qualcomm.com> <20130703201143.GL32044@mercury.ccil.org> <00cd01ce7a9f$19adeaa0$4d09bfe0$@augustcellars.com> <00d701ce7aa6$cc5fe700$651fb500$@augustcellars.com> <CAK3OfOiWrWCvNQneokyycV1Jb98M=UR-U7z0dhxUjzVdf+PwDw@mail.gmail.com> <00e401ce7ad5$00991c20$01cb5460$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00e401ce7ad5$00991c20$01cb5460$@augustcellars.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: 'Nico Williams' <nico@cryptonector.com>, json@ietf.org
Subject: [Json] Duplicate names: are they erroneous or not?
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: Sun, 07 Jul 2013 05:53:58 -0000

What I wish to avoid is a specification that says that having two
fields of the same name in an object is a perfectly okay thing to do.
In other words, such documents for my purposes have to be erroneous,
rather than a legitimate way of encoding multimaps.  Is there anyone
who can't live with that restriction?

If there isn't anyone, then we can talk about whether this is an error
that generators and/or parsers MUST or SHOULD detect.  But if we can't
even get consensus on that much, it's futile to discuss parser or
generator behavior.

Do I contradict myself?                         John Cowan
Very well then, I contradict myself.            cowan@ccil.org
I am large, I contain multitudes.               http://www.ccil.org/~cowan
        --Walt Whitman, Leaves of Grass