From owner-freebsd-arch@FreeBSD.ORG Wed Jul 30 02:11:26 2014 Return-Path: Delivered-To: freebsd-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 6F486BEB for ; Wed, 30 Jul 2014 02:11:26 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 5A6A82600 for ; Wed, 30 Jul 2014 02:11:26 +0000 (UTC) Received: from u10-2-16-021.office.norse-data.com (unknown [50.204.88.51]) by elvis.mu.org (Postfix) with ESMTPSA id 0833B346DE0F for ; Tue, 29 Jul 2014 19:11:26 -0700 (PDT) Message-ID: <53D85495.4050408@mu.org> Date: Tue, 29 Jul 2014 19:12:37 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-arch@freebsd.org Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> <20140729230345.31E9B580A2@chaos.jnpr.net> In-Reply-To: <20140729230345.31E9B580A2@chaos.jnpr.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 30 Jul 2014 02:11:26 -0000 On 7/29/14 4:03 PM, Simon J. Gerraty wrote: > On Mon, 28 Jul 2014 21:49:08 -0700, Jordan Hubbard writes: >> I=92m a huge fan of unified data formats; Apple picked XML and the plist DT= > We did too, and it has indeed been useful. > Being able to render rich html has also proven very cool given the > improvment in browsers in the last several years. > > The point I was making earlier (perhaps not very well) was that the api > Phil has proposed provides enough clue to allow outputting plain text as > well as that rich html. IIRC the main wrinkle json imposes is a need for > extra structure calls - due to the way lists (I think) are handled, > anyway if the api can handle json and html it should be possible to add > rendering for others should that prove necessary one day - hopefully > without having to revisit any of the apps. > Is JSON not handled? How many utils are converted over at this point? Have you seen the GSOC project which aims to do this as well? "machine readable output from userland utilities" -> https://www.google-melange.com/gsoc/project/details/google/gsoc2014/zarko_korchev/5676830073815040 -Alfred