Another approach is for the processor to analyze the stylesheet and adaptively figure out what subsets of the document are needed within each streaming scope. This may be much easier to do if schema are available. -Ed Staub > In the database/XML environment the problem is typically > transforming huge XML documents which are huge because > they are thousands or millions of repeating "subdocuments" > wrapped by an outer, containing element. Not unsurprisingly > these "subdocuments" often are produced from rows in a > database query. If the transformation that needs to be > performed just needs to work on each <ROW> at a time > (that is, each "subdocument") -- but never needs to > do things like select the last() element or navigate > back to the "/" root -- it seems like this kind of > solution may be workable. > > Is the "streamable subset" you're thinking > of trying to solve the "large document" problem, or some > kind of browser-side, incremental transformation? > > Just curious. > > ______________________________________________________________ > Steve Muench, Lead XML Evangelist & Consulting Product Manager > BC4J & XSQL Servlet Development Teams, Oracle Rep to XSL WG > Author "Building Oracle XML Applications", O'Reilly > http://www.oreilly.com/catalog/orxmlapp/ > >
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