Re: [xsl] Namespace-alias using #default with no default namespace in scope

Subject: Re: [xsl] Namespace-alias using #default with no default namespace in scope
From: Frans Englich <frans.englich@xxxxxxxxx>
Date: Fri, 12 May 2006 12:04:14 +0000
On Friday 12 May 2006 11:32, Michael Kay wrote:
> 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?)

Or declare a function argument to be of type empty-sequence()? Or test whether 
the return value of fn:error is xs:dayTimeDuration? XQuery surely got its 
gems ;-)

(Yes yes, it's off-topic in this thread.)


Cheers,

		Frans

Current Thread