Date: Tue, 29 Jul 2014 16:03:45 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Jordan Hubbard <jkh@mail.turbofuzz.com> Cc: arch@freebsd.org Subject: Re: XML Output: libxo - provide single API to output TXT, XML, JSON and HTML Message-ID: <20140729230345.31E9B580A2@chaos.jnpr.net> In-Reply-To: <A1E63A7A-BB38-4CC3-B5EC-B251BE990572@mail.turbofuzz.com> References: <20140725044921.9F0D3580A2@chaos.jnpr.net> <CAETOPp13H7kyLy-1VJRDOsDbOh8A1MWZDxw1xHUBsxTRtMfc7g@mail.gmail.com> <20140728054217.AC1A0580A2@chaos.jnpr.net> <20140728055336.GJ50802@ivaldir.etoilebsd.net> <CAETOPp3hJB8Gj%2BPMj3N951krnNqCYiAOY-cPHxMCBy1CQXWJaQ@mail.gmail.com> <A1E63A7A-BB38-4CC3-B5EC-B251BE990572@mail.turbofuzz.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140729230345.31E9B580A2>