Re: [Json] 2-step proposal 4627bis + I-JSON

Mark Nottingham <mnot@mnot.net> Wed, 03 July 2013 23:57 UTC

Return-Path: <mnot@mnot.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 45AED11E8108 for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 16:57:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.562
X-Spam-Level:
X-Spam-Status: No, score=-105.562 tagged_above=-999 required=5 tests=[AWL=-2.962, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 IRI5HFCD1F4p for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 16:57:19 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id F32FE11E8104 for <json@ietf.org>; Wed, 3 Jul 2013 16:57:18 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.244.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 8B78322E1FA; Wed, 3 Jul 2013 19:57:11 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAHBU6itqGgndUKRUHH_q6fv8jonGL3VVHhkezFne0sC3T12c_Q@mail.gmail.com>
Date: Thu, 4 Jul 2013 09:57:07 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B669A34-7CFC-4B11-8BFB-5417CD9CB11F@mnot.net>
References: <CAHBU6itqGgndUKRUHH_q6fv8jonGL3VVHhkezFne0sC3T12c_Q@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1508)
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: Wed, 03 Jul 2013 23:57:23 -0000

+1, although I'd strongly suggest that the top-level value NOT be a boolean, but instead an object; lots of people have talked about a top-level _"meta" object to hold information like profile identity, and if we're going to go to the trouble of defining something that intrudes into content, we might as well just do it once.

Cheers,


On 04/07/2013, at 9:46 AM, 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!
> 
>  -T
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json

--
Mark Nottingham   http://www.mnot.net/