From owner-freebsd-arch@FreeBSD.ORG Mon Jul 28 05:53:43 2014 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F47B72D for ; Mon, 28 Jul 2014 05:53:43 +0000 (UTC) Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A8127201F for ; Mon, 28 Jul 2014 05:53:42 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id n3so3759709wiv.1 for ; Sun, 27 Jul 2014 22:53:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=6IC+o15CyE4Mv5sFfnSSRm4HbaF9K9aA9jPkdj0v+PE=; b=f2a761Arm/ya7qNPYbYwQIesm+fIR2+TZnO9QTdly7QJDj8kNM5x9qdmI7wP2KFy1B +gvrZHg2G2MVz6hZi6CTQ2dlsEitQNN9BYMxr7STTkm4ZbH0SnZ1c+TdG0cSrziYFzZZ YFadK2WFvg0Kvxz5mWko59XOK9rSgR9TlaERPC4GJSkvgxWUWkVJ6IlivXzEjcNrBCNX /olQcrGkeetZE+Vlqet2pMgOmQLsoXhYRmpK+RdTgf676e9bjHLrmTTXd2lASo3BAGEK qjt01kK/4RjlR5AwhQrYQxrrwQeYe6sPMCP2niZmCXfZzaElgkzMnZcCwQMFTUKd0YqD qbCA== X-Received: by 10.194.63.228 with SMTP id j4mr46249053wjs.7.1406526820159; Sun, 27 Jul 2014 22:53:40 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id p3sm46874589wjw.13.2014.07.27.22.53.38 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 27 Jul 2014 22:53:39 -0700 (PDT) Sender: Baptiste Daroussin Date: Mon, 28 Jul 2014 07:53:37 +0200 From: Baptiste Daroussin To: "Simon J. Gerraty" Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <20140728055336.GJ50802@ivaldir.etoilebsd.net> References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <20140728054217.AC1A0580A2@chaos.jnpr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zOcTNEe3AzgCmdo9" Content-Disposition: inline In-Reply-To: <20140728054217.AC1A0580A2@chaos.jnpr.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: 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: Mon, 28 Jul 2014 05:53:43 -0000 --zOcTNEe3AzgCmdo9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 27, 2014 at 10:42:17PM -0700, Simon J. Gerraty wrote: >=20 > On Sat, 26 Jul 2014 19:29:04 -0700, Jos Backus writes: > >It's a little sad to see that the more human-friendly and expressive YAML > >format appears to not be supported. Instead, here too we are stuck with >=20 > Is there a use case for something like vmstat outputting YAML? > It is a simple format, I guess it could be added, especially if it has > no format quirks worse that HTML and JSON. > Note: I'm just speculating. YAML is all but a simple format, creating a subset of YAML that is good eno= ugh is a simple format :), exporting a complete YAML (strongly typed etc) is something else. As machine readable format YAML is a nightmare to parse, JSON is very simpl= er and easier (while json being a valid subject of YAML). regards, Bapt --zOcTNEe3AzgCmdo9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlPV5WAACgkQ8kTtMUmk6EyfugCfWrlwpOwBZjZ/jCgEz5k2qm1V RjAAnA9RdYqV7tewWGMoiKbmyc1I/r9c =MAOM -----END PGP SIGNATURE----- --zOcTNEe3AzgCmdo9--