IETF Logo Mail Archive

Re: [Json] Human JSON (Hjson)

Christian Zangl <coralllama@gmail.com> Thu, 26 May 2016 21:44 UTC

Return-Path: <coralllama@gmail.com>
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 02C7B12D11E for <json@ietfa.amsl.com>; Thu, 26 May 2016 14:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6RHIZb2zDh3Q for <json@ietfa.amsl.com>; Thu, 26 May 2016 14:44:47 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F76812D0C2 for <json@ietf.org>; Thu, 26 May 2016 14:44:47 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id a136so45966045wme.0 for <json@ietf.org>; Thu, 26 May 2016 14:44:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=LHFNKjZpEnejHAB2DQwIj7qHn5MBEVFgFcMsQG1XvpY=; b=ofxUovP15wZCeevJB92//h6O22RDd3ZlF+MWIDiuoX1rTPJWObvjqnFHV0bAS8q3+M Ey4c+ZwO2f8qbWm3o5fM+O++OLo3D25lxpQTO3G4OrQExAyg7gJv6QZMvBEIOZBXTvTo P5lz/QtASr+ZYZ38lvvh7E0PP2lMjjg206LVFOlJi+PSQcA8kTR2Ou3Yi0bDwbanmQxa SRk2emI0andDxoU+LbX3encVa8j5iWEvkyzZwGQxWstu0JELMw7gLkcX73C5b5GatB47 r7SYmFkbocqJklJS4aoHXLxQkc7xjFtlcSVu5FdDQPyZAFd68HJnM4JHkzV0cmXCgpBn eZnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=LHFNKjZpEnejHAB2DQwIj7qHn5MBEVFgFcMsQG1XvpY=; b=cc2zaZi1Ccn6sWa/Kfjv1Kp4E1Dh/AjT5c7b6IOdnozni06kAbUvYmfYdHfqccjdYy QvPaoNohtfrajkTBvVVlFQpCWEGHFr8KNKlg658uNutIJKIrX4sC7i7Ab7hE+9Skl6Hv WvTKaH4+dG44wXbd/vaZleUyASGSrIvoD1Jr24Yt48/NMtB5RQNELvvjHJmet3thDZa7 3aVreldi+XwcCpS4QHVrI2Lc/+xn4h8Urm1Kl+QMDkviDzfi/qsjW5uiaPHWUCk5tHvz BddubkkCZKrmwCD8QhLXdGhmgUA5ZEpUb+31Z6r5spMRSM7owOLMeIFP0BEkVguOwWC7 czIw==
X-Gm-Message-State: ALyK8tK0F1knzoOBvcKch9qHXtgeWm4f/pbUma/OUbh20U8TAGIPZyD2e4Gp38GNjnqCdg==
X-Received: by 10.194.221.37 with SMTP id qb5mr11054748wjc.171.1464299086096; Thu, 26 May 2016 14:44:46 -0700 (PDT)
Received: from [192.168.1.181] (77.116.171.9.wireless.dyn.drei.com. [77.116.171.9]) by smtp.googlemail.com with ESMTPSA id d86sm5417254wmh.4.2016.05.26.14.44.44 for <json@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 26 May 2016 14:44:45 -0700 (PDT)
From: Christian Zangl <coralllama@gmail.com>
To: json@ietf.org
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> <5746201F.7080707@tzi.org>
Message-ID: <a2f851e2-b40b-3ebe-54c0-a6145bf3fa9d@gmail.com>
Date: Thu, 26 May 2016 23:44:44 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <5746201F.7080707@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/YWt7dfZIs5eS9lEA8fhdB5i60GU>
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: Thu, 26 May 2016 21:44:49 -0000

On 2016-05-25 23:58, Carsten Bormann wrote:
> 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?

There is no relation to YAML (other than being a superset of JSON), at 
least not on purpose.

> What did you do that YAML doesn't have?

I think it's the other way around. Hjson is less complex and easier to 
understand.

Also YAML is based on whitespace for structure while Hjson uses braces. 
(there are apparently two camps on what is better)

v2.23.0 | Report a Bug | By Email