From cldr-users at unicode.org  Mon Oct 23 17:12:19 2017
From: cldr-users at unicode.org (Matt Johnson (AZURE) via CLDR-Users)
Date: Mon, 23 Oct 2017 22:12:19 +0000
Subject: Metazone timestamps
Message-ID: <CY4PR21MB0168901421245C263A60BA1092460@CY4PR21MB0168.namprd21.prod.outlook.com>

In http://www.unicode.org/reports/tr35/tr35-dates.html#Metazone_Names there is an example:

<timezone type="America/Indiana/Knox">
  <usesMetazone to="1991-10-27 07:00" mzone="America_Central"/>
  <usesMetazone to="2006-04-02 07:00" from="1991-10-27 07:00" mzone="America_Eastern"/>
  <usesMetazone from="2006-04-02 07:00" mzone="America_Central"/>
</timezone>

It also states: "Note that the dates and times are specified in UTC, not local time."

As currently presented, they appear to be local time.  Is there a reason these aren't just expressed as ISO 8601 timestamps with a trailing Z?  In other words:  "1991-10-27T07:00Z"

Note that ISO 8601 allows for a space instead of a T, so these timestamps are ISO 8601 compliant, but also that in absence of a Z or an offset they are required to be interpreted as local time.  I've certainly made this mistake in interpreting them before.  I'm sure others have as well.  Would it be possible to change this in a future version?

Thanks,
Matt Johnson
Microsoft


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/cldr-users/attachments/20171023/871cde86/attachment-0001.html>