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

RE: XSL and HTML

Subject: RE: XSL and HTML
From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>
Date: Wed, 20 Mar 2002 11:11:27 -0500
changing xsl to html
Alia,

To what Mike says, I'd add the question, why do you find

> The fact
> is I needed to do an XSL file for each page even if the
> display is the
> same but because the contents is changing.

This makes me wonder what your approach to XSL coding is. If your XML source conforms to a single tag set, and your display is the same, why do you find that you have to write a stylesheet for each page? Another way of asking this: what is changing in your contents that requires rewriting your XSL?


Either your scenario is different from the one for which XML/XSLT is designed (range of inputs conforming to known tag set; one stylesheet for the lot to target any given format), or you just don't know how to write portable XSLT.

The latter might be the case, for example, if you don't understand how to use the "push" processing model (are you using lots of xsl:for-eaches and conditional tests, but not many templates?), and your source has variable structures (as is not uncommon for documentary data). That might result in very brittle XSLT that has to be retuned for every page.

Not that this is likely -- in your case, since your XML is coming out of a database -- but either way, you might find that whatever is changing in your source (that seems to require a change in your stylesheet) could be parameterized or otherwise handled with some smart code. But we'd have to see more detail to be able to say.

So please explain a bit more -- maybe with a code sample -- if you really want to know why you aren't getting the savings in work that other XSL developers are.

Cheers,
Wendell

At 06:30 AM 3/20/2002, Mike wrote:
XSLT will only give you savings in effort if it enables you to apply one
stylesheet to many different pages of your web site. If you're going to
write a different stylesheet for each page in your site, you might as well
have written the page in HTML in the first place.

> -----Original Message-----
>
> Hi everybody,
> I want to ask a question (maybe a silly one) about XSL and
> HTML. I've got
> a well-formed, valid XML-file (exported file from a database
> with ASP). I
> used XSL and ASP to get HTML pages for a design of a web
> site. The fact
> is I needed to do an XSL file for each page even if the
> display is the
> same but because the contents is changing. I used XML/XSL
> technology to
> reduce the work. But I found out it didn't! Is it because
> this technology
> is for other applications more complicated than a simple web design?
> Thx a lot
> Alia


======================================================================
Wendell Piez                            mailto:wapiez@xxxxxxxxxxxxxxxx
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
  Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list



Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.