IETF Logo Mail Archive

Re: [Json] Human JSON (Hjson)

Peter Cordell <petejson@codalogic.com> Fri, 27 May 2016 11:06 UTC

Return-Path: <petejson@codalogic.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 C76EA12D971 for <json@ietfa.amsl.com>; Fri, 27 May 2016 04:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level:
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 QdYloagQKWj6 for <json@ietfa.amsl.com>; Fri, 27 May 2016 04:06:57 -0700 (PDT)
Received: from ppsa-online.com (lvps217-199-162-192.vps.webfusion.co.uk [217.199.162.192]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9016B12D9C2 for <json@ietf.org>; Fri, 27 May 2016 04:06:51 -0700 (PDT)
Received: (qmail 8304 invoked from network); 27 May 2016 12:01:59 +0100
Received: from host86-135-56-118.range86-135.btcentralplus.com (HELO ?192.168.1.72?) (86.135.56.118) by lvps217-199-162-217.vps.webfusion.co.uk with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 27 May 2016 12:01:59 +0100
To: Carsten Bormann <cabo@tzi.org>, 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> <57482236.2030402@tzi.org>
From: Peter Cordell <petejson@codalogic.com>
Message-ID: <620cd39b-1648-1b8f-57f4-c58678ff1ede@codalogic.com>
Date: Fri, 27 May 2016 12:06:45 +0100
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: <57482236.2030402@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/lX2HHg8QXLETVT9cp5WuMNrissg>
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 11:07:00 -0000

On 27/05/2016 11:32, Carsten Bormann wrote:
>>> 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"
>

And the '6' would prevent you using unquoted strings in HJSON.  That 
seems a bit error prone and worries me.

Something like the following might work:

     title :> 6LoWPAN: the Wireless Embedded Internet

But then it's not that much harder just to quote the whole string.  Hum!

Pete Cordell
Codalogic Ltd
Read & write XML in C++, http://www.xml2cpp.com

v2.23.0 | Report a Bug | By Email