W3C home > Mailing lists > Public > xmlschema-dev@w3.org > July 2001

Re: Date

From: Martin Duerst <duerst@w3.org>
Date: Mon, 09 Jul 2001 14:59:47 +0900
Message-Id: <4.2.0.58.J.20010709144645.03fc7ad0@sh.w3.mag.keio.ac.jp>
To: Frank Olken at LBNL <olken@lbl.gov>, Noah_Mendelsohn@lotus.com
Cc: "Henry S. Thompson" <ht@cogsci.ed.ac.uk>, Jeff Rafter <jeffrafter@definedweb.com>, vdv@dyomedea.com, xmlschema-dev@w3.org, olken@lbl.gov
At 12:54 01/07/08 -0700, Frank Olken at LBNL wrote:

>Dates should have (mandatory) time zone designations also!!!

I'm really not sure about this. They can have timezones
or not in XML Schema, and as a Schema user, it's importan
to decide to use either dates with timezones or dates without
timezones (and not mix them up).

But most applications and systems that I know don't use
a timezone with dates, so you may get conversion problems.
Also, most applications use dates when they don't need
to date something to the minute, or get the necessary
context from somewhere else (e.g. in paper signatures,
you often find place and date).

I personally would use dates without timezones for more
'loose' needs, and would use timespans with a start and
an end datetime for more precise needs. And I strongly
suggest to do the same to everybody else.

Dates with timezones have one serious problem: They
don't work with the days (usually Sundays) when timezones
get shifted (from summer time to winter time or back),
because that date starts in one timezone and ends in another.

Regards,   Martin.
Received on Monday, 9 July 2001 02:00:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:22 GMT