Lists Home |
Date Index |
- From: Dean Roddey <firstname.lastname@example.org>
- To: <email@example.com>
- Date: Fri, 11 Sep 1998 13:47:06 -0400
Andy Dent wrote:
>> Why can't a product like our report-writer take
>> - XML describing content
>> - XSL specifying layout
>> and produce, for example, a report preview window on a Mac?
>> After all, if you regard a browser, it's doing something very similar.
> The result of an XSL process must be well-defined, right? So the most
> logical thing to create as the result of the process is an XML document.
> To me, your question is equivalent to "Why can't my car producing product
> take an XML document describing content, and an XSL describing the
> automobile to produce and generate the car?" Well, if XSL were an
> automobile producing language, that would make sense, but it isn't, it is
> an XML producing language.
That's not to say of course that, if I am writing an XSL engine, I cannot
provide a programatic object
interface that normally plugs in a "create XML output" widget, but which can if
desired plug in a "spit
out any danged thing you want" widget. In fact, it would be kind of crazy to
write an XSL engine that
did not provide that kind of flexiblity, since it would provide as much "future
proofness" for the
maintainer of the product as it would for his/her customers.
Of course you have to write some code to take advantage of it, but it also
opens the door for pre-fab
(even pre-fab third party) widgets that spit out particular types of output
given a few hints about the
desired attributes of the target output.
IBM Center for Java Technology - Silicon Valley
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)