[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Timezone concept broken in XPath 2.0?

Subject: RE: Timezone concept broken in XPath 2.0?
From: "Michael Kay" <mike@xxxxxxxxxxxx>
Date: Tue, 11 Nov 2008 00:16:56 -0000
RE:  Timezone concept broken in XPath 2.0?
> would the system still be conformant 
> if it returned an arbitrary, but formally correct datetime 
> "current at some time during the evaluation of a query or 
> transformation in which fn:current-dateTime() is executed", 
> which the system could claim is the correct system time, and 
> on which date arithmetic could be performed correctly?

Yes. 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

Michael Kay

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.