From owner-freebsd-arch@FreeBSD.ORG Tue Jul 29 23:19:34 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 5A087CC1; Tue, 29 Jul 2014 23:19:34 +0000 (UTC) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C4FD324C2; Tue, 29 Jul 2014 23:19:32 +0000 (UTC) Received: from BY2PR05CA045.namprd05.prod.outlook.com (10.141.250.35) by DM2PR05MB736.namprd05.prod.outlook.com (10.141.178.25) with Microsoft SMTP Server (TLS) id 15.0.995.14; Tue, 29 Jul 2014 23:19:22 +0000 Received: from BN1AFFO11FD024.protection.gbl (2a01:111:f400:7c10::137) by BY2PR05CA045.outlook.office365.com (2a01:111:e400:2c5f::35) with Microsoft SMTP Server (TLS) id 15.0.995.14 via Frontend Transport; Tue, 29 Jul 2014 23:19:22 +0000 Received: from P-EMF02-SAC.jnpr.net (66.129.239.16) by BN1AFFO11FD024.mail.protection.outlook.com (10.58.52.84) with Microsoft SMTP Server (TLS) id 15.0.990.10 via Frontend Transport; Tue, 29 Jul 2014 23:19:21 +0000 Received: from magenta.juniper.net (172.17.27.123) by P-EMF02-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 29 Jul 2014 16:19:20 -0700 Received: from chaos.jnpr.net (chaos.jnpr.net [172.21.16.28]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id s6TNJJn17687; Tue, 29 Jul 2014 16:19:19 -0700 (PDT) (envelope-from sjg@juniper.net) Received: from chaos (localhost [127.0.0.1]) by chaos.jnpr.net (Postfix) with ESMTP id 75DF2580A2; Tue, 29 Jul 2014 16:19:19 -0700 (PDT) To: Adrian Chadd Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML In-Reply-To: References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> Comments: In-reply-to: Adrian Chadd message dated "Mon, 28 Jul 2014 22:57:23 -0700." From: "Simon J. Gerraty" X-Mailer: MH-E 7.82+cvs; nmh 1.3; GNU Emacs 22.3.1 Date: Tue, 29 Jul 2014 16:19:19 -0700 Message-ID: <20140729231919.75DF2580A2@chaos.jnpr.net> MIME-Version: 1.0 Content-Type: text/plain X-EOPAttributedMessage: 0 X-Forefront-Antispam-Report: CIP:66.129.239.16; CTRY:US; IPV:NLI; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(6009001)(189002)(199002)(70486001)(99396002)(87286001)(87936001)(74502001)(31966008)(57986006)(92566001)(92726001)(76506005)(81342001)(97736001)(77982001)(90896003)(79102001)(88136002)(76482001)(89996001)(85852003)(46102001)(83072002)(48376002)(85306003)(68736004)(69596002)(110136001)(21056001)(106466001)(81156004)(93916002)(86362001)(95666004)(4396001)(50226001)(20776003)(47776003)(93886003)(83322001)(62966002)(101356003)(50986999)(76176999)(64706001)(77156001)(80022001)(33656002)(93546004)(81542001)(102836001)(107046002)(104166001)(6806004)(44976005)(102176002)(42262001); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB736; H:P-EMF02-SAC.jnpr.net; FPR:; MLV:sfv; PTR:InfoDomainNonexistent; MX:1; LANG:en; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID: X-Forefront-PRVS: 0287BBA78D Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.16 as permitted sender) Authentication-Results: spf=softfail (sender IP is 66.129.239.16) smtp.mailfrom=sjg@juniper.net; X-OriginatorOrg: juniper.net Cc: Jordan Hubbard , "freebsd-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 23:19:34 -0000 On Mon, 28 Jul 2014 22:57:23 -0700, Adrian Chadd writes: >What really matter is whether the library API that you're going to >shoehorn into plenty of utilities is expressive enough to express a >whole bunch of different output types. Exactly. >So it doesn't matter if you want JSON, or YAML, or XML, or the native >tool output. The trick is whether the library API is good enough. Yes. If the API is sufficiently expressive you can add others renderings if needed. I think the API proposed meets that criteria - with the open issue of wide char support (or perhaps UTF8) to be resolved.