<Nathan> Associating the term "style sheet" to XSL makes it sound easier than writing a program. But is it? I'd say that it just increases the programming workload. It seems to me that if you do the SQL to XML, and XML to ??ML transformations on your server it increases the server workload too. Or, am I missing something? </Nathan> Hopefully the transition phase (from XML to HTML or what have you) will become easier as tools get better. I have XMLSpy on my desktop, but to date I have only used it for Schemas and it isn't that friendly. They build tools to use terms that the W3C uses and that doesn't always help us lesser mortals. Too abstract if you know what I mean. I know how to use it well now, but that was only after a huge crash course weekend. Aaron Bartell -----Original Message----- From: Nathan M. Andelin [mailto:nandelin@xxxxxxxxxxxxxxxxxxx] Sent: Friday, August 29, 2003 2:44 PM To: Web Enabling the AS400 / iSeries Subject: Re: [WEB400] XML/XSL > From: "Metz, Zak" <Zak_Metz@xxxxxx> > That's just it. It's not necessarily a browser. It may be a > cell phone or a PDA, or something else tomorrow. > I don't want to send the same HTML to a device > that has a screen 200 pixels wide (or whatever)... Using the HTTP protocol, the client identifies itself and its capabilities through the USER_AGENT and other strings which are passed to your server. Your program is able to make a decision about what to return to the client. What will you return? What are your options? Return a program (XSL) and formatted data (XML), then have the client itself generate either HTML or WML? Or, have the server generate the HTML or WML depending on the client's capabilities? XSL may be characterized as a program because it contains variables, flow control, conditional logic, character and numeric expressions, and so forth. Aaron pointed out that an interpretive runtime environment for XSL (Transformer Factory) is available in Java. An XSL file is actually much like a Net.Data macro, Active Server Page, or Java Server Page in that formatted text (HTML or WML) is embedded in the same file as the control logic. The Transformer Factory is an interpretative runtime environment. The similarities between XSL, JSP, ASP, and Net.Data are striking. If your site supports WML as well as HTML clients, it seems to me that XSL forces you to write two (2) programs to support them - one XSL program for the HTML client, another XSL program for the WML client. Additionally you'd probably write a program to transform an SQL result set into XML. Associating the term "style sheet" to XSL makes it sound easier than writing a program. But is it? I'd say that it just increases the programming workload. It seems to me that if you do the SQL to XML, and XML to ??ML transformations on your server it increases the server workload too. Or, am I missing something? Nathan M. Andelin www.relational-data.com _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.