W3C home > Mailing lists > Public > public-device-apis@w3.org > November 2010

TZDate (formerly TimezonedDate) F2F notes

From: Rich Tibbett <richt@opera.com>
Date: Mon, 08 Nov 2010 11:01:50 +0100
Message-ID: <4CD7CA8E.9060604@opera.com>
To: W3C Device APIs and Policy WG <public-device-apis@w3.org>
Here are the notes I took when we discussed TZDate (formerly 
TimezonedDate) at the F2F.

We decided that rather than build on the standard ECMA Date object (and 
then acquire some complex stringification changes) we should find an 
alternate solution.

Thanks, Robin, for taking on this specification.

- Rich


What might be the least painful change for a workable TZDate proposal 
without building on the ECMA Date object:

   Constructor(int year, int month, int day, int? hours, int? minutes, 
int? seconds, int? tz),
   Constructor(Date utcDate, DOMString? tz) // construct object from the 
*UTC* DOMString of the passed Date object
interface TZDate {
     attribute int year;
     attribute int month;
     attribute int day;
     attribute int? hours;
     attribute int? minutes;
     attribute int? seconds;

     attribute DOMString? tz; // designated timezone (if left blank then
                              // time is 'floating')

     getter Date toDate(); // produces a *local* Date object accounting
                           // for (designated timezone ± local offset).

     DOMString toString(); // stringifies the current object to ISO-8601.
                           // i.e.: YYYY-MM-DDThh:mm:ss±hh:mm

Received on Monday, 8 November 2010 10:02:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:46 UTC