On Tue 2015-01-13T07:44:42 -0500, Brooks Harris hath writ: > That's what I meant - there needs to be multiple ways, appropriate > to each architecture or purpose, to obtain the information. So, > that's why I suggested it as an "API": a clearly defined set of > metadata that could be implemented in compatible ways in many forms.
Please look at the IETF tzdist charter https://datatracker.ietf.org/wg/tzdist/charter/ and its draft document https://datatracker.ietf.org/doc/draft-ietf-tzdist-service/ In the discussion list it has already been demonstrated how this service can supply the leap second information as well as all the time zone information. There is already a test implementation serving that data in the form of "TAI as a timezone offset from UTC". The announcement of the serving providing that is in the e-mail at http://www.ietf.org/mail-archive/web/tzdist/current/msg01085.html There are currently two forms in which the data are served, as iCalendar (RFC 5545) VTIMEZONE records and as json. In addition the discussion has contemplated the possibility of serving the binary data chunks which are the result of the TimeZone zic and typically found in Unix /usr/share/zoneinfo -- Steve Allen <[email protected]> WGS-84 (GPS) UCO/Lick Observatory--ISB Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m _______________________________________________ LEAPSECS mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/leapsecs
