Re: [Json] Seeking more input on draft-ietf-json-text-sequence

Stefan Drees <> Wed, 21 May 2014 05:33 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 991B01A0814 for <>; Tue, 20 May 2014 22:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PfUq9PMZXVxd for <>; Tue, 20 May 2014 22:33:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA256 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 52F491A049D for <>; Tue, 20 May 2014 22:33:04 -0700 (PDT)
Received: from ([]) by (mrweb003) with ESMTPSA (Nemesis) id 0MNcHy-1WguLB160A-007B8k; Wed, 21 May 2014 07:32:59 +0200
Message-ID: <>
Date: Wed, 21 May 2014 07:32:58 +0200
From: Stefan Drees <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Nico Williams <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:o9k+J3OZoGJ6DOQqRNZKh9oyOGOpoYF+/eT87OebaV4snKUU7kw cdLZu1eZqJQKAlEDVioaPmCboum4WFxOil6pe+4BulaQsKDe91JIKxfC2dk2Klu7MR5E9fZ j63A4551R14Y1WTAm4O3OHTNBx2Cm3RrPBy7km6MErO2oE3ybQFru7l7UODzWLCEmODXrr2 /BMlA/8mkNng2BnLtpGLA==
Cc: "" <>
Subject: Re: [Json] Seeking more input on draft-ietf-json-text-sequence
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 21 May 2014 05:33:05 -0000

On 2014-05-21 05:36 +02:00, Nico Williams wrote:
> James Manger points out that I can't help the greedy parser problem
> because the JSON-text rule uses the ws rule.  Well, yeah.  Therefore
> the ABNF can be a bit simpler.

I seem to have not received that mail of James Manger. But maybe some 
feedback on top of that "bridged" comment:

We define a profile here, extending JSON-text (seen as a core).
So how someone implemented her JSON-text parser is not our business.
How we suggest parsing our decorating functionality is our business.
Maybe the single nicely coined "natural language rule" would suffice.

If we use ABNF, I suggested how to translate the simple recipe of this 
profile "just add at least one newline character between JSON-texts and 
you're done" into a concise ABNF plus relating (as a service) to the 
overlapping construct in the referenced JSON-text grammar.
why not have the same term stand out in the grammar, that we use in the 
nicely coined "natural language rule"?

All the best,