Hi,

At 09:39 AM 1/30/2009, Mike wrote:
> >
> > As I'm not an expert on backward compatibility between XSLT
> > 2.0 and 1.0, and only having dabbled in things 1.0, which
> > parts of the code I submitted would need rewriting?
>
>If you've only dabbled, then the incompatibilities are in obscure corners of
>the language that you probably don't know about and probably don't want to.

This is true, and I haven't seen the code (or can't recall it in any 
case), but Mike forgets to mention the general possibility 
(likelihood) that a 2.0 stylesheet uses constructs in either XSLT or 
XPath that aren't supported in 1.0. Which is largely the point, of 
course. Such as xsl:for-each-group, xsl:analyze-string, fun XPath 
2.0, xsl:next-match, cool applications of modes, and what not. And 
those will need rewriting.

The easiest way of finding these is to run the code in a 1.0 
processor and reading the error messages. Other methods include using 
an XSLT IDE for 1.0 (also easy, and you can find the issues faster, 
but it requires the toolkit) and consulting the literature (not so 
easy, as you have to look for things that aren't there in 1.0, but 
possibly informative).

Cheers,
Wendell


======================================================================
Wendell Piez                            mailto:wapiez@m...
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================


--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe@l...>
--~--