Re: [Json] Human JSON (Hjson)
Sean Leonard <dev+ietf@seantek.com> Wed, 25 May 2016 05:33 UTC
Return-Path: <dev+ietf@seantek.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 4EDF112DA3C for <json@ietfa.amsl.com>; Tue, 24 May 2016 22:33:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-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 asfoi-qh_zJg for <json@ietfa.amsl.com>; Tue, 24 May 2016 22:33:11 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0292212DA3E for <json@ietf.org>; Tue, 24 May 2016 22:33:10 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D23F0509B5 for <json@ietf.org>; Wed, 25 May 2016 01:33:09 -0400 (EDT)
To: json@ietf.org
References: <9ec25767-7471-2ca3-ded5-afed67863742@gmail.com> <5744E92B.3010704@tzi.org>
From: Sean Leonard <dev+ietf@seantek.com>
Message-ID: <cabe05b6-342a-fec4-8f3f-b5c281d02731@seantek.com>
Date: Tue, 24 May 2016 22:31:54 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <5744E92B.3010704@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/-Hd1UYuo0gmszLJJHtft1Ix-ETg>
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 05:33:12 -0000
On 5/24/2016 4:52 PM, Carsten Bormann wrote: > First, the name. If something calls itself X, it should be an X. > > HJSON is not JSON. It is a Hacked JSON. > > Second, > >> People seem to prefer JSON for >> configuration over YAML and other config formats. > Can't be. YAML *contains* JSON. > If you like JSON, you already like YAML, because every JSON file is a > YAML file. > (You may not like what else YAML brings to the table, but that would be > a mistake.) > > (If you like JSON mostly because everything is JSON, well: HJSON isn't.) > > Third, YAML also isn't stuck with the limitations of the JSON data model. > Binary data, maps with keys that aren't strings, etc. > > I'm not opposed to writing a spec for a Hacked JSON. However, I think > the time spent for doing that would be much better invested in an > updated spec for YAML. Yeah I pretty much agree with Carsten. A nice effort, but I do not support moving forward with this as-is. More thoughts in a separate e-mail (eventually). Regards, Sean
- [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Carsten Bormann
- Re: [Json] Human JSON (Hjson) Sean Leonard
- Re: [Json] Human JSON (Hjson) Sean Leonard
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Carsten Bormann
- Re: [Json] Human JSON (Hjson) Christian Zangl
- [Json] Fwd: Re: Human JSON (Hjson) Stefan Reich
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Carsten Bormann
- [Json] Comments in JSON = De facto standard. Re: … Anders Rundgren
- Re: [Json] Comments in JSON = De facto standard. … Stefan Hagen
- Re: [Json] Human JSON (Hjson) Peter Cordell
- Re: [Json] Human JSON (Hjson) Phillip Hallam-Baker
- Re: [Json] Human JSON (Hjson) Stefan Hagen
- Re: [Json] Human JSON (Hjson) Carsten Bormann
- Re: [Json] Human JSON (Hjson) Carsten Bormann
- Re: [Json] Human JSON (Hjson) Phillip Hallam-Baker
- Re: [Json] Human JSON (Hjson) Carsten Bormann
- Re: [Json] Human JSON (Hjson) Phillip Hallam-Baker
- Re: [Json] Human JSON (Hjson) Peter Cordell
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Comments in JSON = De facto standard. … Christian Zangl
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Carsten Bormann
- Re: [Json] Human JSON (Hjson) Peter Cordell
- Re: [Json] Human JSON (Hjson) Carsten Bormann
- Re: [Json] Human JSON (Hjson) Peter Cordell
- Re: [Json] Human JSON (Hjson) Phillip Hallam-Baker
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Christian Zangl
- Re: [Json] Human JSON (Hjson) Martin J. Dürst
- Re: [Json] Human JSON (Hjson) Phillip Hallam-Baker