From owner-freebsd-arch@FreeBSD.ORG Tue Jul 29 23:04:01 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 C805A631 for ; Tue, 29 Jul 2014 23:04:01 +0000 (UTC) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0204.outbound.protection.outlook.com [207.46.163.204]) (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 6B1F322A3 for ; Tue, 29 Jul 2014 23:03:59 +0000 (UTC) Received: from BY2PR05CA001.namprd05.prod.outlook.com (10.242.32.31) by DM2PR05MB733.namprd05.prod.outlook.com (10.141.178.18) with Microsoft SMTP Server (TLS) id 15.0.995.14; Tue, 29 Jul 2014 23:03:51 +0000 Received: from BN1BFFO11FD013.protection.gbl (2a01:111:f400:7c10::1:179) by BY2PR05CA001.outlook.office365.com (2a01:111:e400:2c2a::31) with Microsoft SMTP Server (TLS) id 15.0.995.14 via Frontend Transport; Tue, 29 Jul 2014 23:03:50 +0000 Received: from P-EMF02-SAC.jnpr.net (66.129.239.16) by BN1BFFO11FD013.mail.protection.outlook.com (10.58.144.76) with Microsoft SMTP Server (TLS) id 15.0.990.10 via Frontend Transport; Tue, 29 Jul 2014 23:03:50 +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:03:47 -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 s6TN3jn05862; Tue, 29 Jul 2014 16:03:45 -0700 (PDT) (envelope-from sjg@juniper.net) Received: from chaos (localhost [127.0.0.1]) by chaos.jnpr.net (Postfix) with ESMTP id 31E9B580A2; Tue, 29 Jul 2014 16:03:45 -0700 (PDT) To: Jordan Hubbard 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: Jordan Hubbard message dated "Mon, 28 Jul 2014 21:49:08 -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:03:45 -0700 Message-ID: <20140729230345.31E9B580A2@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)(69596002)(76176999)(50226001)(21056001)(77156001)(93886003)(104166001)(33656002)(107046002)(97736001)(93546004)(102836001)(64706001)(81542001)(48376002)(50986999)(79102001)(68736004)(93916002)(110136001)(62966002)(99396002)(77982001)(4396001)(80022001)(76506005)(57986006)(101356003)(102176002)(81342001)(92566001)(85852003)(83072002)(76482001)(90896003)(92726001)(83322001)(46102001)(44976005)(20776003)(47776003)(88136002)(89996001)(87286001)(87936001)(81156004)(106466001)(31966008)(6806004)(86362001)(70486001)(95666004)(74502001)(85306003)(42262001); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB733; 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: 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:04:02 -0000 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.