From owner-freebsd-arch@FreeBSD.ORG Tue Jul 29 07:56:44 2014 Return-Path: Delivered-To: arch@freebsd.org Received: from ptrcrt.ch (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D8B2C574; Tue, 29 Jul 2014 07:56:42 +0000 (UTC) Date: Tue, 29 Jul 2014 09:56:40 +0200 From: Pietro Cerutti To: Stephen Hurd Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <20140729075640.GB76693@ptrcrt.ch> Reply-To: gahr@FreeBSD.org References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> <53D73796.9060102@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="RASg3xLB4tUQ4RcS" Content-Disposition: inline In-Reply-To: <53D73796.9060102@FreeBSD.org> X-PGP-Key: fp="DA6D E106 A5B8 54B8 5DD8 6D49 ADD0 D38E A192 089E"; id="0xA192089E"; get=; get=; User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Jordan Hubbard , arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jul 2014 07:56:44 -0000 --RASg3xLB4tUQ4RcS Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2014-Jul-28, 22:56, Stephen Hurd wrote: > Jordan Hubbard wrote: > > Is there some reason JSON is not sufficient? I think that=E2=80=99s a = better question to ask, since the conversation otherwise quickly tends to s= ound a little like =E2=80=9CI=E2=80=99ll accept any single unified format a= s long as it=E2=80=99s the specific one I like!=E2=80=9D :) I think the g= reater good argument would suggest just picking one that=E2=80=99s expressi= ve enough (roll a pair of dice), put on your bikeshed-proof sunglasses, and= proceed. >=20 > The biggest problem I tend to have with JSON is that there is no comment > format. I rarely update a configuration without adding a comment > regarding it, and since JSON doesn't have comments, it's simply a > non-starter for most of my usage. The whole "just a key that you know > isn't real" hack is terrible. There's an interesting post about whether this really is a problem: https://groups.yahoo.com/neo/groups/json/conversations/topics/156 I'm not saying it isn't, just that there are reasons why comments are not part of JSON. --=20 Pietro Cerutti The FreeBSD Project gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp --RASg3xLB4tUQ4RcS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJT11O3XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREQTZERTEwNkE1Qjg1NEI4NUREODZENDlB REQwRDM4RUExOTIwODlFAAoJEK3Q046hkgiectgP/jThW8PocDricR4t8lEDonyD PN8bNukxBSOLIaZMKRDlsomDWb2RCkgyKIotnpgBLzvAZeJolh8qz+scw3ZbSPuG vp95ly52HusOLOomFZELkfgQkS0w+wCoU4ztUwoxj92vagumjkR/PK+BEgUo44nF lZ27uonJGcv9SHQcpDjV2silZdd02PZFX49HqagSO1lJfeUCUrien2fu2AiO+XLP Xc2ovRSIzJRhJmWdX7KRB5CrqZBEdSoj6oRGlXrmBJpXGqCzYnoX6HQfBMmnEe+7 6YsAh4SI8RiWYGhnzi5q8tL/r5AzAuUZ3kr6df7N49EtVthJZtoDeG72VK0JHoN3 OW+D8rgNCG+Kc6XuJs1S0xIoRUoasDEdx1FvPP9UebO7lej02v+1AtaKTZLMr4Qv ybVkQvo8YuuLHAnoKxJ4qFoCz2tf2okIOCgSUsVNEIl9+oe1wGn+gThj4T02uYiL p+Z5ojCDzEssH+6wWONKSZYLyWlPxfrqCXtTSBrswRk32Z5kYv8lR/mJ0RMXpTRN Le+TdARqv7TYaONFEZkG745NG/P/BMZ1hAjqmZAMaMcRNXTw0aQ9nBXd/TXbcV1t Jfqd5WUl4hCiGlbEZBpLPIt91s+zFy3LZMhscwrdm4nvylCkQDd7iycswjO5ZAWN bg6cYbqLYBm7iT3njnC7 =PFlL -----END PGP SIGNATURE----- --RASg3xLB4tUQ4RcS--