- From: Phillips, Addison <addison@lab126.com>
- Date: Wed, 12 May 2010 00:53:39 -0400
- To: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
FYI... Addison Phillips Globalization Architect (Lab126) Chair (W3C I18N, IETF IRI WGs) Internationalization is not a feature. It is an architecture. -----Original Message----- From: Phillips, Addison Sent: Tuesday, May 11, 2010 9:53 PM To: public-html@w3.org Subject: [I18N] questions about date-local Dear HTML-WG: 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. Note: we are working on an update to our "Working with Timezones" WG-Note (see [3]) and have also begun a conversation with the DAP WG about time values and about non-Gregorian calendars that may have bearing here. Regards (for I18N), Addison [1] http://www.w3.org/2010/04/28-core-minutes.html#action02 [2] http://www.w3.org/TR/html-markup/input.datetime-local.html [3] http://www.w3.org/International/wiki/WorkingWithTimeZones Addison Phillips Globalization Architect (Lab126) Chair (W3C I18N, IETF IRI WGs) Internationalization is not a feature. It is an architecture.
Received on Wednesday, 12 May 2010 04:54:10 UTC