Re: [Json] Human JSON (Hjson)
Carsten Bormann <cabo@tzi.org> Fri, 27 May 2016 10:32 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 371EC12D6E6 for <json@ietfa.amsl.com>; Fri, 27 May 2016 03:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 7K2gWd4qFu7u for <json@ietfa.amsl.com>; Fri, 27 May 2016 03:32:28 -0700 (PDT)
Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [IPv6:2001:4b98:c:538::195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89D3212D79B for <json@ietf.org>; Fri, 27 May 2016 03:32:28 -0700 (PDT)
Received: from mfilter21-d.gandi.net (mfilter21-d.gandi.net [217.70.178.149]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id 351DFA80C6; Fri, 27 May 2016 12:32:27 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter21-d.gandi.net
Received: from relay3-d.mail.gandi.net ([IPv6:::ffff:217.70.183.195]) by mfilter21-d.gandi.net (mfilter21-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id JfW4F1pcs8Ya; Fri, 27 May 2016 12:32:25 +0200 (CEST)
X-Originating-IP: 134.102.48.248
Received: from eduroam-pool5-248.wlan.uni-bremen.de (eduroam-pool5-248.wlan.uni-bremen.de [134.102.48.248]) (Authenticated sender: cabo@cabo.im) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id EBC2CA80E6; Fri, 27 May 2016 12:32:24 +0200 (CEST)
Message-ID: <57482236.2030402@tzi.org>
Date: Fri, 27 May 2016 12:32:22 +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> <82b2ba3f-a6c2-c98b-b365-b698ab285149@codalogic.com> <CAMm+Lwjw-FgrH1yED5B98=3vsx_KjX_VANn=7efPVoD_yPcC1w@mail.gmail.com> <3902e167-6a07-9311-4569-484f015f08be@gmail.com> <CAMm+Lwhh=h0DfWR4LFPgKVLpz-vg8RvFDLfm5DCUxv5tdC-=_g@mail.gmail.com> <2a9060c3-7f2a-6675-2eba-9a14dc823138@gmail.com>
In-Reply-To: <2a9060c3-7f2a-6675-2eba-9a14dc823138@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/oD-48xvRfmbjaPbpbqFWOqWBM5Q>
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: Fri, 27 May 2016 10:32:30 -0000
>> I don't like quoteless strings with spaces. I think they are going to >> cause serious problems. > > Please explain. They sure work very well in YAML. But the rules for what you can and cannot do there are sometimes perceived as complicated (why do you need quotes here? Oh, the colon.): title: "6LoWPAN: the Wireless Embedded Internet" But then YAML has additional, more powerful quoting mechanisms, such as: title: >- Information Technology -- ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) 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