Time database: Difference between revisions

Revision as of 2013-09-20T19:54:31

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"
Stable boundaries of sectors, new sectors are created by splitting and deprecating old sectors, so users can know if they need to check their IDs for correctness.	/1/ user can link his computer to a tzid, but get's no notification if later his real location is in another zone, /2/ different locations are linked, e.g. Vaduz points to Zurich, Tel Aviv to Jerusalem
Record all legal time	/1/ no time for Bouvet Island, while Norwegian government has defined it, /2/ limited support for pre-1970 data
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.

@@ Line 5: / Line 5: @@
 |-
 | Exactly one term for one kind of object
-| IANA uses zone and region interchangeably, and zone has two meanings
+| 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"
 |-
 | Stable boundaries of sectors, new sectors are created by splitting and deprecating old sectors, so users can know if they need to check their IDs for correctness.