Re: [Json] Proposed minimal change for duplicate names in objects

Bjoern Hoehrmann <derhoermi@gmx.net> Sun, 07 July 2013 13:38 UTC

Return-Path: <derhoermi@gmx.net>
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 7929A21F9F0E for <json@ietfa.amsl.com>; Sun, 7 Jul 2013 06:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599]
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 chBIZrZPZqg2 for <json@ietfa.amsl.com>; Sun, 7 Jul 2013 06:38:31 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id C9C0A21F9F0D for <json@ietf.org>; Sun, 7 Jul 2013 06:38:30 -0700 (PDT)
Received: from =?utf-8?q?netb.Speedport=5fW=5f700V?= ([91.35.20.89]) by mail.gmx.com (mrgmx102) with ESMTPA (Nemesis) id 0LjLwB-1ULvJX3dnj-00dVX7; Sun, 07 Jul 2013 15:38:03 +0200
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Tim Bray <tbray@textuality.com>
Date: Sun, 07 Jul 2013 15:38:04 +0200
Message-ID: <8krit8hfboqbl6ipni5ef7l4dtl3dnuqnv@hive.bjoern.hoehrmann.de>
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> <CAHBU6itdi3B1rWv2TiOYhL1QuOVxrFKt7OTWRoG+6TgV8Bc_uw@mail.gmail.com>
In-Reply-To: <CAHBU6itdi3B1rWv2TiOYhL1QuOVxrFKt7OTWRoG+6TgV8Bc_uw@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:sLKOqeoATtc9653JDwI0xPHg36oeRLWcileokXmnifA6/gLMlmD vjfOzPjKvmMDVZ8kxNHOcWWcuMXXWyekrX0soEsKmjPnXqKFUMerW9MQQDZF0P3jiRhzpXZ hv069PbwU44VwSHP3ZbJvexmeoGWMVkNhUFxKkSY+D+LJ1DXJEawjfThUFeMIViSgLp1lTw /nHByrU0+CcT0xcSKmD7w==
Cc: Nico Williams <nico@cryptonector.com>, Jim Schaad <ietf@augustcellars.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposed minimal change for duplicate names in objects
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 13:38:35 -0000

* Tim Bray wrote:
>This feels like a no-brainer to me, but that’s probably because (as I’ve
>said before) I’m an API guy, and the only use for JSON objects in my world
>is to transfer a hash table or database record or whatever from here to
>there, and there, and in such a situation dupes can never be useful or
>intended and can only be a symptom of breakage (or, in the JOSE case, a
>symptom of a malicious attack on my crypto).

Designs like http://wiki.apache.org/solr/UpdateJSON#Solr_3.1_Example are
not uncommon.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/