Lists Home |
Date Index |
- To: "Peter Hunsberger" <email@example.com>
- Subject: Re: [xml-dev] xml xsl web architecture
- From: "Anthony Ettinger" <firstname.lastname@example.org>
- Date: Fri, 24 Feb 2006 09:26:27 -0800
- Cc: ElektonikaMail@tetro.net, email@example.com
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kRbakR+6Gc6GUB5wY6P7WEcNgxIDJrphbgBr5ZBq4mIjooxyeINBUnYqgj79D5zh+IzIAfhDIa7kLR/OnR72cOswmAZtrDddZk3Ke2EGlVCPReq5BGlBhLCxvic7xv01xYzZ9t94mUqK0VXXz76MrrgPvzSBEIzg0e8mgazvX9A=
- In-reply-to: <000001c63953$0b6d7770$0115a8c0@Elektonika.local>
- References: <firstname.lastname@example.org> <43fed8d9.1b699f62.69bd.5c39SMTPIN_ADDED@mx.gmail.com> <000001c63953$0b6d7770$0115a8c0@Elektonika.local>
- Sender: email@example.com
On 2/24/06, Peter Hunsberger <firstname.lastname@example.org> wrote:
> On 2/24/06, Michael Kay <email@example.com> wrote:
> > > I'd personally advise against using XSLT as a templating language (for
> > > several reasons I don't have time to go into at the moment) unless you
> > > have a single person with good XSLT skills maintaining the site.
> > I'd advise against using any technology without the appropriate skills: but
> > if you're saying more than this, then I think you need to expand your
> > statement.
> Generally the rational for using templates to build a Web site is to
> make it easy for some larger group (over space and/or time) than the
> original developers to maintain the site. XSLT would not be my first
> choice for the development and maintenance of the higher level
> abstractions that can be used to build a Web site. Rather, build a
> vocabulary designed for those needs and keep the XSLT in the core
> where it's not going to be exposed to random Web designers.
> Peter Hunsberger
From my experience you have this problem regardless of what
vocabulary/technology you're using. Recreating a presentation
vocabulary, or simply using xhtml may still result in "bad design"
phenomenon. My reasoning for using xsl is to have an include/component
type functionality with parameter passing. And simply creating a new
markup to facilitate this seems redundant.