IETF Logo Mail Archive

Re: [Json] Human JSON (Hjson)

Carsten Bormann <cabo@tzi.org> Wed, 25 May 2016 21:59 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 3B4C712DD92 for <json@ietfa.amsl.com>; Wed, 25 May 2016 14:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=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 NchqkXmd4yMT for <json@ietfa.amsl.com>; Wed, 25 May 2016 14:59:01 -0700 (PDT)
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 604EB12DD0E for <json@ietf.org>; Wed, 25 May 2016 14:59:01 -0700 (PDT)
Received: from mfilter30-d.gandi.net (mfilter30-d.gandi.net [217.70.178.161]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id E167B41C08A; Wed, 25 May 2016 23:58:59 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter30-d.gandi.net
Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter30-d.gandi.net (mfilter30-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id iZDx6XozHkV3; Wed, 25 May 2016 23:58:58 +0200 (CEST)
X-Originating-IP: 93.199.242.26
Received: from nar-3.local (p5DC7F21A.dip0.t-ipconnect.de [93.199.242.26]) (Authenticated sender: cabo@cabo.im) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id BC7FF41C080; Wed, 25 May 2016 23:58:57 +0200 (CEST)
Message-ID: <5746201F.7080707@tzi.org>
Date: Wed, 25 May 2016 23:58:55 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Christian Zangl <coralllama@gmail.com>
References: <9ec25767-7471-2ca3-ded5-afed67863742@gmail.com> <5744E92B.3010704@tzi.org> <aba11a1f-d81f-b9dd-84c9-c5b16df886de@gmail.com> <57455F43.6010506@tzi.org> <2eec2464-3315-9cd6-f850-ab83d98a94a8@gmail.com>
In-Reply-To: <2eec2464-3315-9cd6-f850-ab83d98a94a8@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/Mkaq9CzDY-dwD3do6UarCjBcRVM>
Cc: json@ietf.org
Subject: Re: [Json] Human JSON (Hjson)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 25 May 2016 21:59:03 -0000

Christian Zangl wrote:
> When you look at YAML it's not easy to guess what it does 

Not so sure about that -- kramdown-rfc is using YAML as its structured
part and people seem to be picking it up from the examples nicely.  (I
probably still have to improve those examples some more.)

> and yaml.org
> only makes it worse.

Now, there we have strong agreement.

(But that would be true for any format that tries to offer its spec as
its only documentation, or worse, its documentation as its spec :-)

This could be fixed without even changing the format at all.

Curious question: What part of HJSON is actually a subset of YAML?
What did you do that YAML doesn't have?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email