Re: [Json] Schema for config files Re: Human JSON (Hjson)
Carsten Bormann <cabo@tzi.org> Thu, 26 May 2016 16:56 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 22A2912D671 for <json@ietfa.amsl.com>; Thu, 26 May 2016 09:56:16 -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 GlyBg2KdyK-r for <json@ietfa.amsl.com>; Thu, 26 May 2016 09:56:15 -0700 (PDT)
Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [IPv6:2001:4b98:c:538::196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19D5512D0F3 for <json@ietf.org>; Thu, 26 May 2016 09:56:15 -0700 (PDT)
Received: from mfilter23-d.gandi.net (mfilter23-d.gandi.net [217.70.178.151]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id E6B7117212E; Thu, 26 May 2016 18:56:13 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter23-d.gandi.net
Received: from relay4-d.mail.gandi.net ([IPv6:::ffff:217.70.183.196]) by mfilter23-d.gandi.net (mfilter23-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id O-J2DQRDgW3U; Thu, 26 May 2016 18:56:12 +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 relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 3F3D61720D5; Thu, 26 May 2016 18:56:11 +0200 (CEST)
Message-ID: <57472AA9.60405@tzi.org>
Date: Thu, 26 May 2016 18:56:09 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Phillip Hallam-Baker <ietf@hallambaker.com>
References: <CAMm+LwjmR7JnhkoOKsYRhVLR5DJ5r=mLP+uoOTjGOgKx_zi-5Q@mail.gmail.com>
In-Reply-To: <CAMm+LwjmR7JnhkoOKsYRhVLR5DJ5r=mLP+uoOTjGOgKx_zi-5Q@mail.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/ZEb3pXIGsstjuOYTBx2thbZDcpc>
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] Schema for config files 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 16:56:16 -0000
Phillip Hallam-Baker wrote: > This is very useful in config files because it allows you to do things > like specify the parameters for a network connection in one place and > then instantiate it in multiple places. Yep, that is exactly why YAML turned out to be more useful for configuration files than other formats I have tried. Grüße, Carsten
- [Json] Schema for config files Re: Human JSON (Hj… Phillip Hallam-Baker
- Re: [Json] Schema for config files Re: Human JSON… Carsten Bormann