[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Microsoft extensions to XSL
Thanks James, The best answer to our questions and the most instructive too. A strength of XML is the inclusion of the "composite" pattern which therefore creates a whole-part structure that can be accessed by a DOM. A certain class of problems is to change the underlying structure. Thus to transform not only a grammar into an other but also a structure into an other. Especially for knowledge management where you have to present the same document in different forms depending on the "perception intention" (a phenomenological approach). Elements of these structure could have to be processed (transformed) in different ways. So, if XSL still use the Strength of XML, we could get a quite powerful platform for document processing. Any mechanism that help to do that - in an elegant way - is useful. Thank James to bring the debate to a more intelligent and objective level. Didier PH Martin mailto:martind@xxxxxxxxxxxxx http://www.netfolder.com > -----Original Message----- > From: owner-xsl-list@xxxxxxxxxxxxxxxx > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxx]On Behalf Of James Clark > Sent: Thursday, November 12, 1998 12:44 AM > To: xsl-list@xxxxxxxxxxxxxxxx > Subject: Re: Microsoft extensions to XSL > > > Flow Simulation wrote: > > > To be the end-all solution to many things it needs an "escape > to scripting language" > > as was originally proposed. If you don't have it I think you > get another 4GL development > > tool which drops you off a cliff-edge when you are 95 percent there. > > I agree that without script there will always be cases that you can't > handle, and I agree it's a bad if you can't use XSL as part of a > solution if XSL can handle 95% of what you need. But I don't think it > follows that you need an "escape to scripting language". I find one of > the most interesting things in Microsoft's beta to be the way they have > integrated it into the DOM. They give you a DOM method on a node that > takes a DOM node containing the xsl:stylesheet element, and returns the > XML that results from transforming the tree rooted at that node using > that stylesheet. (Another nice feature is that their DOM allows you to > use XSL patterns to navigate the tree.) This gives you a clean way to > use script with XSL while keeping things nicely modular. I think you > would need a bit more that Microsoft has at the moment: for example, it > would be very desirable to be able to get the result of the transform as > a DOM tree or through something like a SAX DocumentHandler. > > James > (speaking for myself not the XSL WG) > > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|