Re: [Json] Working Group Last Call on draft-ietf-json-text-sequence

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 23 May 2014 22:00 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 672FA1A00BE for <json@ietfa.amsl.com>; Fri, 23 May 2014 15:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
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 bhLuXG_NpHNP for <json@ietfa.amsl.com>; Fri, 23 May 2014 14:59:59 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFAC91A00C9 for <json@ietf.org>; Fri, 23 May 2014 14:59:59 -0700 (PDT)
Received: from [10.20.30.90] (50-1-51-90.dsl.dynamic.fusionbroadband.com [50.1.51.90]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s4NLxsa0060069 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 May 2014 14:59:56 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-51-90.dsl.dynamic.fusionbroadband.com [50.1.51.90] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAK3OfOj55J1xBGjp6X72zzEUj33k3cm-S+MNCvZ4GwJ_LtBDog@mail.gmail.com>
Date: Fri, 23 May 2014 14:59:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC0F47E1-EDFC-4E4C-8332-EB782FD7CFFD@vpnc.org>
References: <F6B74FE0-AEBE-43CC-BDE6-BA443BC04F2D@vpnc.org> <CAHBU6itW=UQq=w_wFwYJkZLT2GotUg_J1LGs-Fhcqg_vBd4+6A@mail.gmail.com> <20140523013240.GF15289@mercury.ccil.org> <CAK3OfOg088r=4VMv6PJxb97oJ6ctoUvwgkmGzi58ZkpisjoaoA@mail.gmail.com> <CAHBU6it6agso2L8iFcsxCUWK36ccy8BYcXE+40DQhgXS5LuaKQ@mail.gmail.com> <CAK3OfOj55J1xBGjp6X72zzEUj33k3cm-S+MNCvZ4GwJ_LtBDog@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/WQF2uCGoZQ2V6USh5guYi9A9yRc
Cc: John Cowan <cowan@mercury.ccil.org>, Tim Bray <tbray@textuality.com>, IETF JSON WG <json@ietf.org>
Subject: Re: [Json] Working Group Last Call on draft-ietf-json-text-sequence
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, 23 May 2014 22:00:00 -0000

<no hat>
On May 23, 2014, at 1:45 PM, Nico Williams <nico@cryptonector.com> wrote:

> On Fri, May 23, 2014 at 12:02 PM, Tim Bray <tbray@textuality.com> wrote:
>> Clearly the current language is confusing readers of the spec. So I suggest
>> that you be careful to define specialized terms that you are going to use in
>> the spec.  An even better solution would be to structure the spec to avoid
>> having to bring in this level of implementation idiosyncrasy.
>> 
>> The more I think about the resync-after-error problem, the unhappier I get.
>> If the JSON texts in sequences were required to be JSON objects, and
>> required to start on new lines, this would be immensely easier for
>> implementors.
> 
> That is not sufficient.  Consider this text:
> 
> { "foo":
> { "bar":"baz" }
> }
> 
> Clearly looking only for LF '{' is insufficient.

Having this discussion in a short subsection in the introduction would be useful to answer a wary reader's question of "why is this needed?".

--Paul Hoffman