IETF Logo Mail Archive

Re: [Json] Comments in JSON = De facto standard. Re: Human JSON (Hjson)

Stefan Hagen <stefan@dilettant.eu> Thu, 26 May 2016 11:00 UTC

Return-Path: <stefan@dilettant.eu>
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 127DF12D64A for <json@ietfa.amsl.com>; Thu, 26 May 2016 04:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.718
X-Spam-Level:
X-Spam-Status: No, score=-2.718 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dilettant.eu
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 vbQczKTmAEPB for <json@ietfa.amsl.com>; Thu, 26 May 2016 04:00:22 -0700 (PDT)
Received: from mailrelay4.public.one.com (mailrelay4.public.one.com [195.47.247.71]) (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 4123D12D782 for <json@ietf.org>; Thu, 26 May 2016 04:00:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dilettant.eu; s=20140924; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=WTCOcv3rLmgEqPwJSsUd6teM26dQU2iz6vlQHC2kjkc=; b=RjjJEeo5gNcgTSi4UDpS5XgXZ5TLiPh06k7l10Ozn0R0Eo5VlnvSE1Ai0ca3oK1yVMV6GsJytub0I nL+w2nPyLlWqk9duDXuO9Aa7UsPGu9OYMko+SV5d739Jsj7Pfm6rEzhznVsCBKGHYubDrjGoXZZWWB /x66ddGots+Z89nQ=
X-HalOne-Cookie: 56a71fad1abce7180d67b41e4c1d5e0efa32c034
X-HalOne-ID: 08d3851f-2331-11e6-a8e4-b8ca3afa9d73
Received: from [192.168.0.17] (unknown [37.201.170.50]) by smtpfilter1.public.one.com (Halon Mail Gateway) with ESMTPSA; Thu, 26 May 2016 11:00:18 +0000 (UTC)
Content-Type: multipart/alternative; boundary="Apple-Mail-70643EF2-75B4-48DA-A977-71D572C6CCF2"
Mime-Version: 1.0 (1.0)
From: Stefan Hagen <stefan@dilettant.eu>
X-Mailer: iPhone Mail (13F69)
In-Reply-To: <45878809-7718-fc38-a8ec-d8c5654c66cd@gmail.com>
Date: Thu, 26 May 2016 13:00:18 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <D0329673-F921-4AB4-BCA6-CC34B979308A@dilettant.eu>
References: <9ec25767-7471-2ca3-ded5-afed67863742@gmail.com> <07aea2e2-a675-797b-eab6-7cd7ccc5d2d1@seantek.com> <21160816-48c7-169e-5a83-19b7601420a0@gmail.com> <45878809-7718-fc38-a8ec-d8c5654c66cd@gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/2RrKt5cG8L250Pf3BWQ-TMUnxL8>
Cc: Christian Zangl <coralllama@gmail.com>, json@ietf.org
Subject: Re: [Json] Comments in JSON = De facto standard. 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: Thu, 26 May 2016 11:00:24 -0000

> On 2016-05-26 at 06:53 Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
> 
> Adding comments to JSON would IMO solve the "human" part.
> It is already used in Chrome config files since ages back.

I second that. Nearly always switcted to using python dicts for edited config / foxtite files from JSON for the good readabiloty of commented entries and editor support.

"Stefan" # Like so ;-)

v2.23.0 | Report a Bug | By Email