[Json] Fwd: Re: Human JSON (Hjson)

Stefan Reich <stefan.reich.maker.of.eye@googlemail.com> Wed, 25 May 2016 16:27 UTC

Return-Path: <stefan.reich.maker.of.eye@googlemail.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 4A77212D84C for <json@ietfa.amsl.com>; Wed, 25 May 2016 09:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=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=googlemail.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 6IgEN6TooM0K for <json@ietfa.amsl.com>; Wed, 25 May 2016 09:27:33 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 2B07D12D855 for <json@ietf.org>; Wed, 25 May 2016 09:27:33 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id t40so35602051ioi.0 for <json@ietf.org>; Wed, 25 May 2016 09:27:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=/7523epmJ82kDtK58Dy6y7BVhxAcMEjEVnl5WJfg4Pg=; b=EuuTUveThsmPmIZVtr6bh3pzbgVdCeREwyvayun+1rw9w945UfVS2emEekr2nW5rSB JVl2OALaRVYcWxSdPVMMhZYfLb8DD/Gzjy3C7buLuL1u0+oL+B4JECVXikLZi6BtWnNN H0rJmg9rWbLGvBiIffGZrjPY/oV1n1E5mKGU0z7bbGoeR4I8y3vLUpmEkI79NZP3og3y 7UwCWdXMCV0eqiMOY21lL8alUN9jJODBdd+9nlFBA6B6zKB4ZxAS2C1oG4rWB9J8hgln tCiAFc5mLyti6Z6XVO16VCUIR9BTxZ/ZI024X0v8MbDb2jFEGHL+j0qDHou3UctmUf6S aykg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=/7523epmJ82kDtK58Dy6y7BVhxAcMEjEVnl5WJfg4Pg=; b=iA0K9T8FEKPAWERTmW8mdLNHjDQ0P6MLa6U18MRVDNDZGtY4gRSC2YM8/Nc8XE8M5y 6sb46qopAO/AJLSBdPHbV80vcLi5ULftEEJDXVOIrMtQls0JH9CQPb24fa0RKk4NYoG0 kBuFs7V3sJ9x7pyRVrEBnXTPZvJ35BCTKUZnSzpomXqNvnATRhNP9Hms3vAfchgcWBru rnCfS7/WyMfzPoWZm3Aat/k++4vy0YBctUBi6U8TZ5+OKTThhvD1n7oBYd4J7lpY7Zcu s/ancExMaFUX6D7Y2Jk1gNJe7xG7vRiEkNnbAr125HG3nrIA8U34zl873067OwLPOhTh /QUw==
X-Gm-Message-State: ALyK8tLoPuxahLLxYWD6wuRKVVSVjf203J7XoCdJwPfflyDX6jtTUUeDNeaw3QSgjzX4A7WjDCdUfO5xuL6lrA==
MIME-Version: 1.0
X-Received: by 10.107.62.196 with SMTP id l187mr4411808ioa.185.1464193652447; Wed, 25 May 2016 09:27:32 -0700 (PDT)
Received: by 10.64.77.233 with HTTP; Wed, 25 May 2016 09:27:32 -0700 (PDT)
Received: by 10.64.77.233 with HTTP; Wed, 25 May 2016 09:27:32 -0700 (PDT)
In-Reply-To: <CAC2-jLG35rgEyLWJAZ1Qn_KY=RjeL3+o__sJ7syG0D5Fi6PqLw@mail.gmail.com>
References: <9ec25767-7471-2ca3-ded5-afed67863742@gmail.com> <CAC2-jLG35rgEyLWJAZ1Qn_KY=RjeL3+o__sJ7syG0D5Fi6PqLw@mail.gmail.com>
Date: Wed, 25 May 2016 18:27:32 +0200
Message-ID: <CAC2-jLHfqDjirgO42__h9wAvXx-pJqLat1rGxGPTpo5zpWauSw@mail.gmail.com>
From: Stefan Reich <stefan.reich.maker.of.eye@googlemail.com>
To: json@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c0610628967980533ad26fe"
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/EqMmTgmNDWNVRsumLv_9VYfY5uc>
Subject: [Json] Fwd: Re: 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 16:27:35 -0000

---------- Weitergeleitete Nachricht ----------
Von: "Stefan Reich" <stefan.reich.maker.of.eye@googlemail.com>
Datum: 25.05.2016 18:27
Betreff: Re: [Json] Human JSON (Hjson)
An: "Christian Zangl" <coralllama@gmail.com>
Cc:

I did a similar thing called JSON+C (JSON with comments).

Stefan
Am 24.05.2016 23:36 schrieb "Christian Zangl" <coralllama@gmail.com>:

> JSON is used in a lot of places and has helped improve things like data
> exchange and data storage. It is also used in areas it's less suited for,
> like configuration files. People seem to prefer JSON for configuration over
> YAML and other config formats.
>
> I started Human JSON (Hjson) because I found the experience frustrating
> (for example missing/trailing comma problems, no comments). With Hjson you
> get a superset of JSON that allows you to
>
> - add #, // or /**/ comments,
> - omit quotes for keys,
> - omit quotes for strings (terminated by LF, no escapes),
> - omit braces for the root object,
> - omit the comma at the end of a line
> - add trailing commas and
> - use multiline strings with proper whitespace handling.
>
> These changes should make it easer to read and write configs while still
> preserving the power of JSON.
>
> Joe Hildebrand approached me with an idea to publish Hjson as a RFC. You
> can find the draft here: http://hjson.org/rfc.html There are also syntax
> diagrams and more at http://hjson.org/syntax.html
>
> Thoughts?
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>