[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re: [equinox-dev] Incubator commit rights for Kim Horne
- From: "Alex Blewitt" <alex.blewitt@xxxxxxxxx>
- Date: Thu, 26 Oct 2006 22:04:37 +0100
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=X+9P8CAGALPVXeSogoF81+nJzDbKuPOL+dcKZD5jRKf+vWzVYdzA3rlqYyyV+bn+gogkl9b48ceKVDHDBv4KB3Q6agjMc5XASd11haa+mevMTLnTQ8sQM86Phs2QvUymxSvqp5ha2xfsCp8n6lupSW70m+IlGC2VKSyncF/5zls=
On 25/10/06, BJ Hargrave <hargrave@xxxxxxxxxx> wrote:
But I find the use of XSLT to be stomach turning. XSLT programming is not
easy. I support Peter's thoughts on having a programmatic way of
I think XSLT is *exactly* the kind of thing to use here. XPath is an
incredibly flexible way of being able to filter and transpose XML
documents, and is definitely the right choice.
A dumb programmatic API might be able to generate simple XPath
expressions for those that prefer writing in code, but don't turn a
great solution into a weak one just so that it can be written in a way
unsuited to the task.