Re: Timezone concept broken in XPath 2.0?

Michael Kay schrieb am 11.11.2008 um 00:16:56 (-0000):
> The current date/time (and the implicit timezone) are part of the
> evaluation context. The spec doesn't say how values in the evaluation
> context are initialized or whether they are under user control. A
> system that always initialized the current date/time to 12:00:00 on 29
> Feb 1848 would be perfectly conformant - just not very saleable. The
> same is true of other aspects of the system context, for example an
> implementation could return <gotcha/> for every call on the doc()
> function, regardless of the URI.

Thanks Michael, and David.

That's an interesting new way of thinking to me.

Michael Ludwig