Re: [Json] draft-williams-json-text-sequence-00
John Cowan <cowan@mercury.ccil.org> Sat, 15 March 2014 19:41 UTC
Return-Path: <cowan@ccil.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 891B01A01BF for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 12:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level:
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] 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 GtMN0GUJjD8N for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 12:41:31 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 54A9B1A01BC for <json@ietf.org>; Sat, 15 Mar 2014 12:41:31 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1WOuSR-0002qw-4f; Sat, 15 Mar 2014 15:41:23 -0400
Date: Sat, 15 Mar 2014 15:41:23 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Nico Williams <nico@cryptonector.com>
Message-ID: <20140315194123.GG24343@mercury.ccil.org>
References: <CAK3OfOg7Ly=unmjJY2E34LZT1DyqZ9VFUs4gtNNEiMJGA9cQKA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAK3OfOg7Ly=unmjJY2E34LZT1DyqZ9VFUs4gtNNEiMJGA9cQKA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/json/29HKRF0h6V2J8Ofo6msc9I602A0
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] draft-williams-json-text-sequence-00
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: Sat, 15 Mar 2014 19:41:33 -0000
Nico Williams scripsit: > Just submitted. 1) Your terminology of "online parsers" and "incremental parsers" is very confusing. What you call an "online parser", I would call a "streaming parser", because it returns portions of arrays, objects, and possibly even strings as a stream of events. Your "incremental parser" is simply a parser that stops reading when it reaches the end of a JSON text without insisting that there be no additional characters. 2) The sentence "Encoders MUST emit" should refer explicitly to the grammar. Currently the grammar is completely unmoored from the requirements. "Encoders MUST emit JSON text sequences that conform to the ABNF" is sufficient. 3) The sentence "Two contiguous separators do not" is unnecessary, because there are no empty JSON texts. 4) In "Parsers MUST be able", for "to parser" read "to parse". But as in #2, this should simply say "Parsers MUST be able to parse any text conforming to the ABNF" for the same reasons. 5) The recommendation seems entirely unnecessary to me. 6) I still don't see that there is any ambiguity in "truefalse" considered as two JSON-texts. So I would strip "Parsers MAY parse" to just say "sequences where the separators are missing." Note that such sequences don't conform anyway. 7) If you want newline-free JSON-texts to be in serious use, the second MAY should be promoted to a SHOULD. -- "The serene chaos that is Courage, and the phenomenon cowan@ccil.org of Unopened Consciousness have been known to the John Cowan Great World eons longer than Extaboulism." "Why is that?" the woman inquired. "Because I just made that word up", the Master said wisely. --Kehlog Albran, The Profit http://www.ccil.org/~cowan
- [Json] draft-williams-json-text-sequence-00 Nico Williams
- Re: [Json] draft-williams-json-text-sequence-00 John Cowan
- Re: [Json] draft-williams-json-text-sequence-00 Phillip Hallam-Baker
- Re: [Json] draft-williams-json-text-sequence-00 Nico Williams
- Re: [Json] draft-williams-json-text-sequence-00 Nico Williams
- Re: [Json] draft-williams-json-text-sequence-00 Phillip Hallam-Baker
- Re: [Json] draft-williams-json-text-sequence-00 Paul Hoffman
- Re: [Json] draft-williams-json-text-sequence-00 Joe Hildebrand (jhildebr)
- Re: [Json] draft-williams-json-text-sequence-00 Nico Williams
- Re: [Json] draft-williams-json-text-sequence-00 Manger, James
- Re: [Json] draft-williams-json-text-sequence-00 Nico Williams