- From: Phillips, Addison <addison@lab126.com>
- Date: Wed, 12 May 2010 11:05:35 -0400
- To: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
FYI, Hixie's response. Addison Phillips Globalization Architect (Lab126) Chair (W3C I18N, IETF IRI WGs) Internationalization is not a feature. It is an architecture. -----Original Message----- From: Ian Hickson [mailto:ian@hixie.ch] Sent: Tuesday, May 11, 2010 11:43 PM To: Phillips, Addison Cc: public-html@w3.org Subject: Re: [I18N] questions about date-local On Wed, 12 May 2010, Phillips, Addison wrote: > > The I18N WG has tasked [1] me with asking your WG about the usage > scenarios you envision for the 'date-local' input type (see [2]). Our > concern is that it is unclear what format this field produces, why this > field omits local time zone, and whether the format of the field is > sufficiently specified. We often see problems with time and date values > and would like to better understand the implications of this field type > and the usage scenarios you have developed for it. It's intended for situations where the time zone is implied out-of-band. For example, flight reservation systems determine the time zone from the location of the airport (all flight reservation interfaces work in local time zones). -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 12 May 2010 15:06:06 UTC