>>I'd like to propose a standard description of a higher order model of >>time and the transformation between raw clock and time (in some agreed >>upon time scale).
A good time transform will let you transform between time scales at points in the far future and far past. For example "what was the date on the Chinese calendar for Jan 11th in 1,500BC" My point is that you may want to apply your transform on times not near the present. Two timescales can have different phase and rate. At any instant in time two real numbers are enough to transform the time from one system to another. A linear equation is enough but the rate might change over time. I think this means a second order polynomial. Next I think you must always define the range where the polynomial is valid. For example adding a leap second to one time scale invalidates the polynomial and makes you use another one So a general purpose API would need to look at the epoch to be transformed then select the correct polynomial. This amounts really to a table look up. But you need that to handle things like conversion from UTC to a computer's internal time. A computer's time can depend in silly things like the air conditioner in the room cycling Chris Albertson Redondo Beach, California _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
