Re: [whatwg] <time>

> These XPath passages you cite appear to punt on these issues in  
> much the same way that ISO 8601 does

well it extends in some places, punts on others (and they spent years of
working group time deciding which to do in each case:-)
But I was suggesting that if html does decide to leave some things
undefined, then the xpath operators spec might be a good model (eg allowing 
all positive dates not just those from 15whatever.

> XSD datatypes also allows for the representation of leap seconds (
that caused xpath/xquery particular problems, as you can see some drafts
of xquery had leap second support, some didn't but the final REC went
without leap second support Basically the situation is a lot easier for
XSD (and perhaps html) as it just needs to specify what the legal
lexical forms are for validity. If however you want to specify
operations on values as in xpath then it's harder, and in particular the
question of whether the duration returned by subtracting two future date
times should be something that can be specified, or if it depends
on when leap seconds are added is obviously much more tractable if you
decide that leap seconds are not supported.

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

Received on Friday, 13 March 2009 10:46:37 UTC