IETF Logo Mail Archive

Re: [Json] JSON for Internet messages

Nico Williams <nico@cryptonector.com> Wed, 03 July 2013 17:31 UTC

Return-Path: <nico@cryptonector.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 452D821F8956 for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 10:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.947
X-Spam-Level:
X-Spam-Status: No, score=-1.947 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 Xgiq54bOVSrU for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 10:31:12 -0700 (PDT)
Received: from homiemail-a32.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id 6C11821F889C for <json@ietf.org>; Wed, 3 Jul 2013 10:31:12 -0700 (PDT)
Received: from homiemail-a32.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTP id 30DD3584059 for <json@ietf.org>; Wed, 3 Jul 2013 10:31:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=UYq7/A9NT+HeTxcd8ac6 s2P/j0c=; b=XRd7jwf7yAufOnwqpak0tLaUSJkYg434ZodCTtP1JQFuHWg0XP7q 4uwLQ707B5+cTINh2swNCypDqT9RsDWMOkIf7rHNoul3AXqfupDYWIMSndfgCclK 74iimsPsGHpE0pXBuvYjs98CMEcdl7zrkHRFZ9wN2bCmcPNroq3eKK4=
Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com [74.125.82.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTPSA id CCA1F584058 for <json@ietf.org>; Wed, 3 Jul 2013 10:31:11 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id b12so359158wgh.31 for <json@ietf.org>; Wed, 03 Jul 2013 10:31:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pG8rcNfHqF+PM6/moQHw8Ty1jPwW+8D3Uig8r/f8zus=; b=HDYDafpCWxkyeW1b/ppAZ4IjcHpYU1DrN0IzS8WDPjnTi8HbAKfHJ8UPVrGeg4UgdE NClJ4lDffsI3oLM81pOqwm4Kd7LvdlYNE+tjVakCVXaoT+9AT3+SmWww+lCDV1Axx3bk 5ztGbPoDTogjc27Spowc7txKOHJnTBBFS1Bd044vaL8D9kyoegi0G9XkynCkOApFWLbo E/jW6tURwTmwhHHakhbf4C9zr7XGj8YGLOiwrOHLT3hms35cgDamO+PNBpBQs8wSZSLv BuFZ9DRc4GMqwdn8xJEseee8Qbryb2tRw5DGqOeV0Uqg00d3JubT5fz8HRYJJBNFDIeA KOvQ==
MIME-Version: 1.0
X-Received: by 10.194.20.97 with SMTP id m1mr1256371wje.31.1372872670486; Wed, 03 Jul 2013 10:31:10 -0700 (PDT)
Received: by 10.216.152.73 with HTTP; Wed, 3 Jul 2013 10:31:10 -0700 (PDT)
In-Reply-To: <20130703171547.GH32044@mercury.ccil.org>
References: <CAHBU6it55C5vCNLBki1LvjpWd4fANY8LdC4fzxj3a2G_+q=qSA@mail.gmail.com> <20130703171547.GH32044@mercury.ccil.org>
Date: Wed, 03 Jul 2013 12:31:10 -0500
Message-ID: <CAK3OfOhEBFCiT1BdtWXXTkDL+BM5JsHs3gbYXXtgaLRV6A5saA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: John Cowan <cowan@mercury.ccil.org>
Content-Type: text/plain; charset="UTF-8"
Cc: Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] JSON for Internet messages
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: Wed, 03 Jul 2013 17:31:17 -0000

On Wed, Jul 3, 2013 at 12:15 PM, John Cowan <cowan@mercury.ccil.org> wrote:
> Tim Bray scripsit:
>> - All JSON objects MUST have unique keys
>> - All JSON messages MUST be either arrays or objects
>> - Software receiving something violating any of these MUSTs has encountered
>> conclusive evidence of serious upstream breakage and MUST NOT trust the
>> contents nor act upon them.
>
> The trouble with all this is that They Break Data.  All of a sudden, what
> was valid JSON before is not valid JSON now.  That's serious, especially
> as people *do* keep around their JSON rather than using it only transiently
> See above remarks about databases: it doesn't matter if the JSON is stores
> as JSON or regenerated on the fly, because if I put in JSON today I expet
> to get back JSON tomorrow, and not something that no longer counts as JSON.

Tim is proposing a different JSON, "Internet JSON", to be used where
appropriate.  Consider this like the BCP, only as a Standards-Track
RFC, and NOT updating/obsoleting RFC4627, but competing with it.

I could live with that.

v2.23.0 | Report a Bug | By Email