Re: [Json] Proposal to move forward on acceptable roots

Tim Bray <tbray@textuality.com> Fri, 30 May 2014 22:58 UTC

Return-Path: <tbray@textuality.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB5801A0981 for <json@ietfa.amsl.com>; Fri, 30 May 2014 15:58:12 -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=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hKjCbG0Jevq2 for <json@ietfa.amsl.com>; Fri, 30 May 2014 15:58:10 -0700 (PDT)
Received: from mail-ve0-f175.google.com (mail-ve0-f175.google.com [209.85.128.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12D551A094F for <json@ietf.org>; Fri, 30 May 2014 15:58:09 -0700 (PDT)
Received: by mail-ve0-f175.google.com with SMTP id jw12so2868730veb.6 for <json@ietf.org>; Fri, 30 May 2014 15:58:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=hNUuwACw25bqfvjb0Wd/ZAVVR1kYL1auiN9H7WfMZ30=; b=jgcRLq5vCuhY1SF4cacg6LA5UunnUDgn63a6bZT4FQTXBFZ0/bsJNGbgrNdwtfppul hjAc9W0WuqyyMweyo9SNhq2EABDRAZioZdyXNya+4ycR5W+/HmiCJsSy7M/dN4wBafvb ecKQpIVuc9f+or0A2TpAelzhYjsMwcC+m6ze1UtmYcJAx/jzm4gOjBNRuj0HKVkvfyiN UC3jeLAWcRRwXBxICWbm0YpNDxiaVAgmZcaN7EqaUOiQFnDsfP2XjnTb+1wG2CkmQDEo xXla3EXXvMmjy662jVF9QUk9bPoQ7/XSrWdDXcIWj92MmKSJHEnH08+sPT6GJqFLiNnM k6gA==
X-Gm-Message-State: ALoCoQl27U2z2p5FL04FiUz3acGm0ea3KIpyjG2atuwSG75owbzw7rfZ1ZvwN7bIFWi1mezH7niQ
X-Received: by 10.52.154.241 with SMTP id vr17mr14143067vdb.40.1401490685035; Fri, 30 May 2014 15:58:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.98.73 with HTTP; Fri, 30 May 2014 15:57:44 -0700 (PDT)
X-Originating-IP: [24.85.103.37]
In-Reply-To: <CAOXDeqpOpDGffggUmYp_8wMgRy=++mMaCRuFVJJQ3e9znA56Bw@mail.gmail.com>
References: <CFAE0A52.4C56C%jhildebr@cisco.com> <CAOXDeqpOpDGffggUmYp_8wMgRy=++mMaCRuFVJJQ3e9znA56Bw@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Fri, 30 May 2014 15:57:44 -0700
Message-ID: <CAHBU6iuDz-RwKAKq-jsNWTnGTbeBLMGcePHx5dqBD6axoAu54Q@mail.gmail.com>
To: Matthew Morley <matt@mpcm.com>
Content-Type: multipart/alternative; boundary=bcaec51a8e2a7014b404faa5fa70
Archived-At: http://mailarchive.ietf.org/arch/msg/json/7IzZjECAE2o-3OG0C4YuqN-GP8A
Cc: "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposal to move forward on acceptable roots
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 30 May 2014 22:58:13 -0000

OK, I’ve got a i-json-01 in progress at
http://www.tbray.org/tmp/draft-ietf-json-i-json-01.html which I think
captures all the consensus calls and also includes a “Protocol-design
Recommendations” section and drops the array-or-object top-level constraint.

Diffs at
http://tools.ietf.org/rfcdiff?url1=http://www.tbray.org/tmp/draft-ietf-json-i-json-00.txt&url2=http://www.tbray.org/tmp/draft-ietf-json-i-json-01.txt


On Fri, May 30, 2014 at 2:18 PM, Matthew Morley <matt@mpcm.com> wrote:

> +1
>
>
> On Fri, May 30, 2014 at 12:13 PM, Joe Hildebrand (jhildebr) <
> jhildebr@cisco.com> wrote:
>
>> One way we could go on the topic of what goes in the root that would work
>> for me would be for us to add a non-normative section to I-JSON giving
>> protocol design advice, and move the issue of potential incompatibility of
>> non-[object,array] roots to that section.
>>
>> Into that section, we can also put some suggestions about how to encode
>> integers, floats, and dates in strings, how to do forward-compatibility
>> with objects (MUST ignore what you don't understand), and whatever other
>> pearls of wisdom we come up with.
>>
>> Yes, I know that will make the document take longer, and open up other
>> areas for us to argue about.
>>
>> --
>> Joe Hildebrand
>>
>>
>>
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json
>>
>
>
>
> --
> Matthew P. C. Morley
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>
>


-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)