Subject: RE: Using Sun for XML Parsing and XSL Processing? From: "Pawson, David" <DPawson@xxxxxxxxxxx> Date: Thu, 29 Jun 2000 08:38:19 +0100 |
: Brian Young >Am I off-base for wanting to keep the parser and processor >from the same vendor? I might suggest an alternative approach, rather than looking for the same name badge on a product pair, look for ones which comply with the W3C recs? > And, to make my head spin even more, >where does the just released Sun XSLT compiler fit in? I've >yet to research it, but it doesn't seem to be what I'm looking >for (and a little bit too early to consider using in >production mode, anyway). It fits into the 'I want it yesterday' brigade. A long standing request has been for speed of transformation. Use case is the busy server dishing up lots of output. It also fits into the 'this is interesting' (but not finished) block. If you like the label 'bleeding edge' then give it a try. When our list cynics start to align it with our most compliant processors, then we can start to have confidence in its ability to implement the rec fully and in a compliant manner. HTH DaveP XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Using Sun for XML Parsing and XSL P, Brian Young | Thread | RE: Using Sun for XML Parsing and X, Trevor de Koekkoek |
RE: xsl self-documentation - trace, Pawson, David | Date | Re: Complex table of content genera, Jean-Claude Tarby |
Month |