> The only difficulty is that the translation from Calendar A to Calendar B is > undefined for dates after 2019-06-30 -- for a standard such as CF this is > problematic.
Is it? It's terribly problematic for libraries -- which is why most of them don't deal with it at all. But for CF, I'm not sure it matters: datetimes are encoded as: a_time_unit since a_datetime_stamp. TIA and UTC define seconds the same way. And no one should use a time unit that isn't clearly defined multiple of seconds. The only difference between TIA and UTC here is when you want to convert that encoding to a datetime stamp -- exactly what datetime stamp you get depends on whether you are using TIA or UTC, but the seconds are still fine. If someone encodes a datetime in the future, and specifies TIA time, then clients will not be able to properly convert it to a datetimestamp -- but that isn't a CF problem. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/148#issuecomment-434372733
