[tz] [PROPOSED 3/3] Vanguard form now uses subsecond precision

Howard Hinnant howard.hinnant at gmail.com
Fri Jul 29 13:32:24 UTC 2022

I strongly support the positions of Stephen and Jon.  I recall we had a big precision discussion several years ago, and the arguments against changing the precision made then are just as applicable today.


On Jul 29, 2022, at 3:26 AM, Jon Skeet via tz <tz at iana.org> wrote:
> On Fri, 29 Jul 2022, 08:04 Stephen Colebourne via tz, <tz at iana.org> wrote:
> FWIW, while I'm content that this is for Vanguard only, I don't
> personally think this change should be made.
> I second this. From the perspective of Noda Time (the project I maintain) we decided long ago that the precision of UTC offsets would be one second.
> Basically this change will mean extra work for me to truncate back to seconds. (I'm pretty sure we're using the vanguard data - I'd need to double check.)
> Obviously the small inconvenience for one developer shouldn't be regarded as a veto, but I wanted to mention it as one data point. There are definitely costs to this - are there also known concrete benefits, in terms of consumers wanting to use this data?
> Jon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://mm.icann.org/pipermail/tz/attachments/20220729/aded1485/attachment.sig>

More information about the tz mailing list