From owner-freebsd-arch@FreeBSD.ORG Mon Jul 28 06:07:05 2014 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AC36EB8B for ; Mon, 28 Jul 2014 06:07:05 +0000 (UTC) Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) (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 81E0E214D for ; Mon, 28 Jul 2014 06:07:05 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id lf10so9867171pab.2 for ; Sun, 27 Jul 2014 23:06:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=YdOCZ0nl3umXAUuF9MKMd40LedwHNE7RGeBESD1ZUjU=; b=iOoC2JjY+K7O2HNejTg58/RQ6X9mblG4taJnP8ellRdiNZ29y6wKEnYDv6SnsVHH6B lVNJh0YNeOOc0RWdekYKdd4LdZFKmADl6yItGoy1J9fOI1hUAUR2OS6HOr06n/Jsrot8 EhbbXdX6Auj9XQHTzwQ8cyf9wWObXoyc1vXvFKrzZKj/54FKnCwXU90cnjJb72s8a4xb MZd44q8SIGy4dtLnCoAnb1MKqHQ+TJ3xcnvIG7aNaYczbow6fo82LDQZYY3Fz9aFIWbO /ZjKkOpK7kgt/xTWZPl8M46AODYB5hVKacJqx5rmLl7P29ifPN9upIMdXcL7nKHVRnCN 2g/g== X-Gm-Message-State: ALoCoQm0KuU0zcrPjP3By4YiurmHd9ig5VD8GzQL2I1E8NNZtPZGYRIGK51eCJ4MZnxY5SKGd05W MIME-Version: 1.0 X-Received: by 10.66.180.98 with SMTP id dn2mr29782798pac.83.1406527616756; Sun, 27 Jul 2014 23:06:56 -0700 (PDT) Received: by 10.70.101.41 with HTTP; Sun, 27 Jul 2014 23:06:56 -0700 (PDT) Received: by 10.70.101.41 with HTTP; Sun, 27 Jul 2014 23:06:56 -0700 (PDT) In-Reply-To: <20140728055336.GJ50802@ivaldir.etoilebsd.net> References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> Date: Sun, 27 Jul 2014 23:06:56 -0700 Message-ID: Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML From: Jos Backus To: arch@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 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 06:07:05 -0000 On Jul 27, 2014 10:53 PM, "Baptiste Daroussin" wrote: > > On Sun, Jul 27, 2014 at 10:42:17PM -0700, Simon J. Gerraty wrote: > > > > 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 > > > > 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 enough > is a simple format :), exporting a complete YAML (strongly typed etc) is > something else. The full power/expressiveness of YAML may not be needed, we may just want the right subset. And there may be cases where the extra expressiveness is useful as more utilities are converted. > > As machine readable format YAML is a nightmare to parse, JSON is very simpler > and easier (while json being a valid subject of YAML). Well, the work has been done already (libyaml), so barring any bugs and maintenance it's not an issue, no? It would be great if libyaml and libucl would converge, but instead it's likely that the number of solutions trying to solve the same problem will continue to proliferate, and we are stuck with more and more configuration file formats :-( Jos > > regards, > Bapt