---
title: Time Zone Data Reorganization
---
# Time Zone Data Reorganization
### Existing Data by Type
**a) alias mapping**
supplementalData.xml
\
...
\
...
\
**b) metazone -> golden zone**
supplementalData.xml
\
...
\
\
\
\
\
\
\
\
...
\
**c) historic metazone mapping**
metazoneInfo.xml
\
...
\
\
\
\
...
\
**d) zone -> territory**
supplementalData.xml
\
...
\
...
\
**e) territories where multiple time zones are available**
supplementalData.xml
\
**f) Mapping between Olson ID and Unicode time zone short ID (bcp47 ids)**
(1) bcp47/timezone.xml
Short ID -> Olson ID
\
(2) supplementalData.xml
Olson ID -> Short ID
\
...
\
...
\
...
\
...
\
**g) Windows tzid mapping**
supplementalData.xml
\
\ \
...
\
### Hige Level Proposal
- bcp47/timezone.xml must be there, because all keyword keys/types must reside in bcp47/\*.xml. Therefore, f) (2) \ should be deprecated (this is an invert mapping table)
- The set of canonical Unicode time zone IDs is defined by bcp47/timezone.xml. Because we do not want to maintain the set in multiple places, long ID aliases could be embedded in bcp47/timezone.xml.
- Metazone tables (b and c) should be in a single file
- Territory mapping is almost equivalent to zone.tab in tzdata (minor exception - zone.tab does not include deprecated zones). I think it is not worth maintaining the data in CLDR. Therefore, d) and e) should be deprecated / no corresponding data in 1.8
- Windows tz mapping is independently maintained - it should be moved into a new file. Side note: A single Windows tz could be mapped to multiple zones in future.
### New Data Organization
1. bcp47/timezone.xml
Add long aliases - for example
\
2. metazoneInfo.xml
Add b) into this file
3. wintz.xml (new)
Store only g).