[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: xml xsl web architecture

• To: "Peter Hunsberger" <peter.hunsberger@g...>
• Subject: Re: xml xsl web architecture
• From: "Anthony Ettinger" <aettinger@s...>
• Date: Fri, 24 Feb 2006 09:56:12 -0800
• Cc: ElektonikaMail@t..., xml-dev@l...
• 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=TqBBoF67TyC+b/koo4/TIjK8vLUzXDl7rVGg5b2F8AOPwYxzws2FqUVomN/M282OvU2CynZ7hwmYHwCCtRfy8fOgcYkTJap/yUihhhXZEroNmNtb19SCkYw67qZeK11onVsQ5pKQ/ZzWItueOr141hqDhSN9TyC973tgwsiNl2g=
• In-reply-to: <cc159a4a0602240944y896718fh709bc602048e97ff@m...>
• References: <cc159a4a0602231903y14b37f71q627bad429559aa0d@m...> <43fed8d9.1b699f62.69bd.5c39SMTPIN_ADDED@m...> <000001c63953$0b6d7770$0115a8c0@E...> <3fc6b2fb0602240926p44d72e69v84263019d1230cef@m...> <cc159a4a0602240944y896718fh709bc602048e97ff@m...>
• Sender: ettinger@g...

On 2/24/06, Peter Hunsberger <peter.hunsberger@g...> wrote:
> On 2/24/06, Anthony Ettinger <aettinger@s...> wrote:
> <snip/>
>
> > > 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.
> >
> > 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.
> >
> Not sure what "problem" you're referring to?
>
> XSLT is a Turing complete language.  By using it as your template
> language you not only force everyone who designs for your site to
> learn XSLT you open a huge can of potential performance, maintenance
> and security issues.
>
> You don't need to invent any new languages for includes.
>
> Not sure what you're real use cases for parameter passing are?
> Generally I haven't found a need for such with a properly designed Web
> site (other than within the site controller itself, but that's another
> issue altogether).  Rather I end up including  XML fragments as
> needed.  Thus, every piece of information is maintained in one spot
> and one spot only.  The data that creates the site in the XML files,
> the presentation of that data in XSLT.  Separation of Concerns is a
> good thing in this case...
>
> --
> Peter Hunsberger
>
>

Hmmm....well if you had an xml fragment with 90% of the same code, but
you wanted a condition, you'd create a new markup for that?

--
Anthony Ettinger
Signature: http://chovy.dyndns.org/hcard.html

• References:
  • Re: xml xsl web architecture
    • From: "Peter Hunsberger" <peter.hunsberger@g...>
  • Re: xml xsl web architecture
    • From: "Anthony Ettinger" <aettinger@s...>
  • Re: xml xsl web architecture
    • From: "Peter Hunsberger" <peter.hunsberger@g...>

• Prev by Date: Re: xml xsl web architecture
• Next by Date: XSD processContents attribute usage question
• Previous by thread: Re: xml xsl web architecture
• Next by thread: RE: xml xsl web architecture
• Index(es):
  • Date
  • Thread