Re: [Json] 2-step proposal 4627bis + I-JSON
Nico Williams <nico@cryptonector.com> Thu, 04 July 2013 00:00 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 8DCC211E8104 for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 17:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 HgSAGlBbnIXG for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 17:00:39 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id 1BD5511E826B for <json@ietf.org>; Wed, 3 Jul 2013 17:00:34 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id A41F05406F for <json@ietf.org>; Wed, 3 Jul 2013 17:00:33 -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:content-transfer-encoding; s= cryptonector.com; bh=MGGclFjyBmqHKQckJnslCD/MqOs=; b=mJ+4EiA+K+c Axz/NsPd7zrEcC8Ibo3Sy5Pnsi9ewkJY82Wv/S6WHz0j5qQT1AlaE8dgIZrTyJC+ HnLpRTJz8Y25PIoptWiBKOOXEkG7+PDVyMVobI7tfp7azh7pv011+KVMUQKGMkKG DwYKAk1YGFpY3Fh8Sk0PbgCkDke9yMG8=
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 486015405B for <json@ietf.org>; Wed, 3 Jul 2013 17:00:33 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id k10so679312wiv.5 for <json@ietf.org>; Wed, 03 Jul 2013 17:00:31 -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:content-transfer-encoding; bh=/lnS4brH8x5uB2+xwDZMChuv2sdJYz0UipaF5pEwU9U=; b=YO1XTrHfe/rKvQ+MDUqaGBIdkfnVmlTf1ffCqXrIdrulJyQHxTp0710xUc+ZH7Lvl1 KbVo7uH8VQimc/Mktghu5LJs+r+lfRpnM3/mqX6UFYyoF58PNKQT6URyJ+yonC59M0QZ E6IBh1mRJlRfQBXuJ5Uzgrxbl/LjT4iHWGnGDfWR/Q/rOxAUvr2X82endTX2dGNM8mX9 85yifTASfX19PO8x3foLLSgcK5JDmYeX7sm6O5o1uCK84j0Odit/wEjrhPf3pgNMt743 SEoyNl9Xm9OGPlCtlYNwIubuexqYwJxEk0ni21FYWPp4McGHt8jkDvLE1KEklOhScVMX XYPQ==
MIME-Version: 1.0
X-Received: by 10.180.107.71 with SMTP id ha7mr1657886wib.28.1372896031563; Wed, 03 Jul 2013 17:00:31 -0700 (PDT)
Received: by 10.216.152.73 with HTTP; Wed, 3 Jul 2013 17:00:31 -0700 (PDT)
In-Reply-To: <CAHBU6itqGgndUKRUHH_q6fv8jonGL3VVHhkezFne0sC3T12c_Q@mail.gmail.com>
References: <CAHBU6itqGgndUKRUHH_q6fv8jonGL3VVHhkezFne0sC3T12c_Q@mail.gmail.com>
Date: Wed, 03 Jul 2013 19:00:31 -0500
Message-ID: <CAK3OfOi_ZYMBZPc1B1632zBFNaRy=Vfge7d9x70fC+2B_VhrxA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] 2-step proposal 4627bis + I-JSON
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: Thu, 04 Jul 2013 00:00:43 -0000
On Wed, Jul 3, 2013 at 6:46 PM, Tim Bray <tbray@textuality.com> wrote: > I look forward to hearing what path Pete suggests through the thicket. > Here’s one that I think is plausible: > > 1. Do a 4267bis along the lines of the minimal-work proposals. It describes > JSON as she are spoke (wildly successful), changes as little as we possibly > can, documents the areas of interoperability breakage (dupes, surrogates, > top-level primitives), whacks the regex in the security section, uses > SHOULD in the manner that Pete suggested is perfectly kosher. Declare > victory! > > 2. Recharter in a way that will allow us to produce something like a > strawman I cooked up, I-JSON: https://www.tbray.org/tmp/i-json.html Produce > something like that. Second victory! A hearty +1. When I'm done with more pressing I-Ds (i.e., by Monday) I'll propose text for (1). Nico --
- [Json] 2-step proposal 4627bis + I-JSON Tim Bray
- Re: [Json] 2-step proposal 4627bis + I-JSON Mark Nottingham
- Re: [Json] 2-step proposal 4627bis + I-JSON Nico Williams
- Re: [Json] 2-step proposal 4627bis + I-JSON R S
- Re: [Json] 2-step proposal 4627bis + I-JSON John Cowan
- Re: [Json] 2-step proposal 4627bis + I-JSON Manger, James H
- Re: [Json] 2-step proposal 4627bis + I-JSON Martin J. Dürst
- Re: [Json] 2-step proposal 4627bis + I-JSON Tim Bray
- Re: [Json] 2-step proposal 4627bis + I-JSON John Cowan
- Re: [Json] 2-step proposal 4627bis + I-JSON John Cowan
- Re: [Json] 2-step proposal 4627bis + I-JSON Pete Cordell