Walter Underwood wrote:
--On February 4, 2005 6:46:33 PM +0100 Julian Reschke <[EMAIL PROTECTED]> wrote:
Also, we have an unresolved issue with historic Livejournal entries,
which do not have timezones. XML Schema explains exactly how to
So what does it recommend?
handle those. We can have a SHOULD for timezone info, with an explanation of what you lose without that.
Treating the datetime value as if it has an uncertainty equal to the maximum possible timezone offset. The other advantage of use XML Schema
Just to clarify: do you see that as as MUST or MAY level requirement? I'm pretty sure that most recipients that actually parse the date will only persist a timestamp (such as ms since the epoch), and not bother with any addutional information.
is that is defines how to order timestamps, which is the main thing we want to do with them.
I think the section is pretty clear, and I'm picky about specs:
<http://www.w3.org/TR/xmlschema-2/#dateTime>
As far as I am concerned, the problem with xsd:dateTime is that it includes features (such as the aforementioned TZ uncertainty) that most recipients aren't prepared to handle. So, we need to
1) either subset it so that that syntax is not allowed, or
2) define what recipients should do with these timestamps.
I'm -1 on option 2).
Julian
-- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
