Time database: Difference between revisions
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
| Smallest geographic unit is named "zone" | | Smallest geographic unit is named "zone" | ||
|- | |- | ||
| | | New sectors are created only by splitting and deprecating old sectors, so a user can know if an ID needs a check for correctness. | ||
| | | | ||
* | * User can link an object to a tzid, but get's no notification if later the object is located in another zone having a different tzid | ||
* | * Different locations are linked, e.g. Vaduz points to Zurich, Tel Aviv to Jerusalem | ||
|- | |- | ||
| Record all legal time | | Record all legal time |
Revision as of 2013-09-20T20:05:20
Desired features:
Time keeping database (tkdb) | IANA time zone database (tzdb) |
---|---|
Exactly one term for one kind of object | Uses terms interchangeably (region, zone), and uses ambiguous terms (zone for IANA zones and real world zones) |
Provisional name for smallest geographic unit: "sector" | Smallest geographic unit is named "zone" |
New sectors are created only by splitting and deprecating old sectors, so a user can know if an ID needs a check for correctness. |
|
Record all legal time |
|
Provide time zone acronyms that are unique within each country and at any given point in time refer to only one offset from a base time | Uses EST and CST for time stamps of zones in Australia that use DST and those that do not. That means for a given point in time during summer the offset from UTC and therefore UTC itself cannot be derived from the local time representation. |
ISO 3166-1 alpha-3 codes for countries | ISO 3166-1 alpha-2 codes for countries. Some of the codes have been re-assigned, e.g. CS can refer to Czechoslovakia or Serbia and Montenegro. |