ISSUE-81: How to represent dates? ES has Date but with no TZ information; using strings is less than ideal; do we have to create a Web Dates specification?

timezonedDate

How to represent dates? ES has Date but with no TZ information; using strings is less than ideal; do we have to create a Web Dates specification?

State:
CLOSED
Product:
Calendar API
Raised by:
Robin Berjon
Opened on:
2010-03-17
Description:
See http://www.twinsun.com/tz/tz-link.htm and below for more information.
Related Actions Items:
Related emails:
  1. RE: Agenda - Distributed Meeting 25 April 2012 (from travis.leithead@microsoft.com on 2012-04-25)
  2. Agenda - Distributed Meeting 25 April 2012 (from Frederick.Hirsch@nokia.com on 2012-04-25)
  3. 2009/dap/calendar Overview.html,1.16,1.17 (from cvsmail@w3.org on 2011-03-16)
  4. Re: Feedback on Calendar API editors draft (was: Agenda - Distributed Meeting 2011-01-12) (from rich.tibbett@gmail.com on 2011-02-09)
  5. Feedback on Calendar API editors draft (was: Agenda - Distributed Meeting 2011-01-12) (from dom@w3.org on 2011-02-01)
  6. Re: TZDate (formerly TimezonedDate) F2F notes (from dom@w3.org on 2010-11-09)
  7. Re: Calendaring I18N (from norbert.lindenberg@yahoo-inc.com on 2010-04-30)
  8. Re: Calendaring I18N (from norbert.lindenberg@yahoo-inc.com on 2010-04-29)
  9. Re: Calendaring I18N (from norbert.lindenberg@yahoo-inc.com on 2010-04-28)
  10. Re: Calendaring I18N (from norbert.lindenberg@yahoo-inc.com on 2010-04-21)
  11. Draft minutes 2010-04-21 (from frederick.hirsch@nokia.com on 2010-04-21)
  12. [calendar] TimezonedDate (from richard.tibbett@orange-ftgroup.com on 2010-04-14)
  13. Re: Calendaring I18N (from robin@robineko.com on 2010-04-14)
  14. RE: ACTION-129: Expressing timezones in the Calendar API (from dom@w3.org on 2010-03-29)
  15. Draft Minutes F2F Day 2, 2010-03-17 (from frederick.hirsch@nokia.com on 2010-03-18)
  16. ISSUE-81: How to represent dates? ES has Date but with no TZ information; using strings is less than ideal; do we have to create a Web Dates specification? (from sysbot+tracker@w3.org on 2010-03-17)

Related notes:

I prefer the approach of using Julian dates in double precision floating point UT timestamp format internally, and ISO 8601 date format for machine-readable notation. Please see http://en.wikipedia.org/wiki/ISO_8601 for more information.

For human readable format, there are maps, border wars, daylight savings times, and other problems which complicate things and make a stable definition very unlikely. See http://www.twinsun.com/tz/tz-link.htm and e.g. http://www.php.net/manual/en/datetimezone.gettransitions.php for an example (at the end) of how PHP addresses the issue.

James Salsman, 16 Jun 2010, 16:03:15

[dom]: http://dev.w3.org/2009/dap/calendar/TimezonedDate.html proposal that will need to be reworked to avoid extending a host object

4 Nov 2010, 16:59:44

[dom]: since extending a host object is a bad idea in case the original object evolves (and would aslo implies stringification nightmares)

4 Nov 2010, 17:00:07

Display change log ATOM feed


Anssi Kostiainen <anssi.kostiainen@intel.com>, Chair, Dominique Hazaƫl-Massieux <dom@w3.org>, Fuqiao Xue <xfq@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.325 2014-09-10 21:42:02 ted Exp $