Re: [xsl] Timezone concept broken in XPath 2.0?

[David Carlisle <davidc@xxxxxxxxx>]

>  Or would the system still be conformant if it returned an arbitrary,
> but formally correct datetime

I think so.

> which the system could claim is the correct system time, 

In particular it may be the system time. If the xslt engine asks the
system for the time/date, and it returns a syntactically valid time eg
1st jan, year 0 then I don't think it has to check that for accuracy. So
if you are implementing on some embedded system without a real time
clock so long as you actually return a valid datetime for
current-dateTime() I think that's OK. Of course user expectations will
force systems to offer a more intuitive implementation where possible:-)

David



________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________