Hallam-Baker, Phillip wrote:
I don't like seconds from 1970 but I like RFC 3339 even less.
Seconds since 1970 is unambiguously UTC. RFC 3339 means well but there is no
practical way to insist on UTC and no practical way to ensure that
developers encode local time reliably.
With seconds since 1970 all I have to worry about is whether the machine is
set up correctly which these days is usually the case.
What is utterly bizare is the failure of virtually every callendaring scheme
to work reliably due to the insistence of the dufus programmers of coding
into local time then getting it wrong. You would think someone writing an
application that has the job of reading an air travel itinerary and
installing it in a calendar would figure out the need to adjust for local
time but no...
Empirically the programers cannot handle human friendly time.
Well, that was pretty much my motivation to Sf70. A close runner up was
Kingon Kliques. But human readable stuff makes my hurt if I actually want
to perform some operation on it. If there isn't some posix-y like thing
to do
it for me, I shudder in fear. Luckily Sf70 has all of those in spades.
Mike
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html