RE: [xsl] Namespace-alias using #default with no default namespace in sc

The main one is the namespace change (affecting 
> xpath and xquery more than xslt, really)
>
>
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=2548
Yes, I think that's pretty well the only change that will cause anyone other
than conformance-testers to have to change any code.

(In practice, you're more likely to be affected by product changes rather
than spec changes, as the testing activity currently underway picks up areas
where Saxon's not quite in sync with the latest spec. But these are pretty
minor too - how many people are using relative collation URI's, for
example?)

Michael Kay
http://www.saxonica.com/


--~------------------------------------------------------------------
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(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--