Re: [Json] [OT] Re: Radically changing 4627bis

Carsten Bormann <cabo@tzi.org> Thu, 10 October 2013 07:32 UTC

Return-Path: <cabo@tzi.org>
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 E963221E80E0 for <json@ietfa.amsl.com>; Thu, 10 Oct 2013 00:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.974
X-Spam-Level:
X-Spam-Status: No, score=-105.974 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, 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 lq+kOVse+EPK for <json@ietfa.amsl.com>; Thu, 10 Oct 2013 00:32:52 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2A111E8142 for <json@ietf.org>; Thu, 10 Oct 2013 00:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r9A7WjxG016159; Thu, 10 Oct 2013 09:32:45 +0200 (CEST)
Received: from [192.168.217.105] (p54891327.dip0.t-ipconnect.de [84.137.19.39]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3A7F9256; Thu, 10 Oct 2013 09:32:45 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <52563E62.6080402@it.aoyama.ac.jp>
Date: Thu, 10 Oct 2013 09:32:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9B01770-974D-4787-81D2-46EA28AC0276@tzi.org>
References: <20131008234810.28645.8207.idtracker@ietfa.amsl.com> <CAHBU6isT8yv4-xf+cL0-RCdNu6DB=6G97MSaR7Z=F-Fz11BM3w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E11531C3C187@WSMSG3153V.srv.dir.telstra.com> <E2C3B3A8-3897-44B4-8C9B-A784F63EED59@vpnc.org> <C68CB012D9182D408CED7B884F441D4D3482260D4F@nambxv01a.corp.adobe.com> <D14308C3-4D2B-4136-B2E7-4A752AC5A0BE@tzi.org> <52562772.3020308@it.aoyama.ac.jp> <20131010043302.GE32580@mercury.ccil.org> <52563E62.6080402@it.aoyama.ac.jp>
To: =?iso-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
X-Mailer: Apple Mail (2.1510)
Cc: John Cowan <cowan@mercury.ccil.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] [OT] Re: Radically changing 4627bis
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: Thu, 10 Oct 2013 07:32:57 -0000

On Oct 10, 2013, at 07:42, "Martin J. Dürst" <duerst@it.aoyama.ac.jp> wrote:

> On 2013/10/10 13:33, John Cowan wrote:
>> "Martin J. Dürst" scripsit:
>> 
>>> I assume that "car racing" refers to a style of specification close
>>> to pseudocode, with step-by-step descriptions.
>> 
>> Not at all.  See<https://en.wikipedia.org/wiki/Syntax_diagram>am>.
>> There are usually called "railroad diagrams", at least by me.
> 
> Oh, I see. So it's not about specification style, just about notation.

Yes, sorry for being opaque.  (When they were popular in the 1970s, we sometimes derided them as "Rennbahndiagramme", "racetrack diagrams".)

I can put the ABNF into tools.  Harder to do that with those nice figures.
These have the higher tutorial value, though, and are more accessible to people without CS background.
(Instead of trying to be a complete notation, they rely on the text, e.g. "hexadecimal digits".)

More generally speaking, I read ECMA 404 as a nice JSON tutorial, which it does quite well.
If I can get someone to read only 6 pages about JSON, these are the ones I'd suggest.

As with most tutorials, it wins by not addressing some of the more difficult issues.

Grüße, Carsten