If it ain't broke, don't fix it. ISO 8601 provides for 20070709T091029 for your compressed value below: one character more, and that "T" makes is easy for a human to parse the figure (there are many more formats in 8601). You didn't provide seconds, nor a way to deal with fractions of a second; 8601 does. And, your computer today most likely supports that somewhere or another. Now, if we only had a decimal-based (divisible only by 10) number of seconds in a minute, minutes in an hour, hours in a day, days in a month and month in a year, we'd have something. John Willkie _____ De: opendtv-bounce@xxxxxxxxxxxxx [mailto:opendtv-bounce@xxxxxxxxxxxxx] En nombre de negrjp Enviado el: Monday, July 09, 2007 3:36 AM Para: opendtv Asunto: [opendtv] UTC numerator mn 200707091029 Dear OPENDTV friends, Cheers for all! To participate of this international forum is very pleasant. Sometimes, I follow the messages from the opendtv archives. I wish to suggest a simple way for organize the real sequence of messages: GMT/UTC numerator. Example: Today is 20070709, (like Mark Schubin's numerator) The local time im my contry is 7:16 The GMT/UTC time is 10:29 The composed message number is 200707091029 What do you think so? [s] Jonas