Re: [Json] Human JSON (Hjson)
Carsten Bormann <cabo@tzi.org> Thu, 26 May 2016 15:11 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 E9CC912D5A9 for <json@ietfa.amsl.com>; Thu, 26 May 2016 08:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 3NjiTAxPYhtz for <json@ietfa.amsl.com>; Thu, 26 May 2016 08:11:17 -0700 (PDT)
Received: from slow1-d.mail.gandi.net (slow1-d.mail.gandi.net [217.70.178.86]) by ietfa.amsl.com (Postfix) with ESMTP id 7DFBF12D10A for <json@ietf.org>; Thu, 26 May 2016 08:11:17 -0700 (PDT)
Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by slow1-d.mail.gandi.net (Postfix) with ESMTP id 1E68E47E824; Thu, 26 May 2016 17:10:41 +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 relay3-d.mail.gandi.net (Postfix) with ESMTPSA id C6CE0A80D5; Thu, 26 May 2016 17:10:40 +0200 (CEST)
Message-ID: <574711EE.2010405@tzi.org>
Date: Thu, 26 May 2016 17:10:38 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: JSON WG <json@ietf.org>
References: <9ec25767-7471-2ca3-ded5-afed67863742@gmail.com> <82b2ba3f-a6c2-c98b-b365-b698ab285149@codalogic.com> <CAMm+Lwjw-FgrH1yED5B98=3vsx_KjX_VANn=7efPVoD_yPcC1w@mail.gmail.com> <57471154.1050107@tzi.org>
In-Reply-To: <57471154.1050107@tzi.org>
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/3ZeGpHJzDb2p2bpgi3L9GlE9PM8>
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 15:11:19 -0000
Carsten Bormann wrote: (Things that I don't like to write.) And back to something productive: I think there is consensus that something would need to be added to JSON to make it more amenable to configurations and other data entered and edited by humans. We all have different experience with the various, well-tried approaches here (e.g., some found YAML too complex, some have good experience with it; various other extensions to and variations of JSON are embodied in various open source projects, and there are even other approaches like TOML where it would be nice to understand the reasons for their existence). Based on these different experience backgrounds we also have different opinions. But that doesn't mean we can't converge on something. The nature of a a JSON working group is that it would tend to converge on "fixing" JSON. Since this natural tendency (hammer/nail) always needs a bit of a counteraction, I've been stressing that there are other approaches, such as formalizing existing standards in this space. Grüße, Carsten
- [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