Stream: fhir/infrastructure-wg
Topic: Timezones
Ewout Kramer (Sep 18 2019 at 19:24):
As a follow-up to our discussion in Q2 today, Josh and I were going to look at how popular platforms deal with timezones, so that if we pick a valueset of timezone names, it be supported broadly.
I found this page pretty helpful so far: http://w3c.github.io/i18n-drafts/articles/definitions-time/index.en.html,
but it does contain a slightly troubling statement:
The most definitive reference for identifying sets of time zone rules is the TZ database (also known as the Olson time zone database), which is used by systems such as various commercial UNIX operating systems, Linux, Java, CLDR, ICU, and many other systems and libraries. Other systems exist: for example, Microsoft Windows uses its own data set and identifiers.
Ewout Kramer (Sep 18 2019 at 19:25):
Which is what I noticed too. I found I can easily parse and handle timezones like "Afghanistan Central Time" but not "America/New York" on the .NET platform. But maybe I have not looked hard enough yet.
Brian Postlethwaite (Sep 18 2019 at 21:38):
I'll take a peek into the dotnet stuff. I did find some stuff earlier and will inform the discussion.
Ewout Kramer (Sep 19 2019 at 17:46):
See also: https://github.com/dotnet/corefx/issues/11897 for more discussion on the .NET support of these codes (read: there is no "standard" support for them in the platform, but there's a 3rd party library)
Ewout Kramer (Sep 19 2019 at 17:46):
And also: https://github.com/dotnet/corefxlab/issues/338
Last updated: Apr 12 2022 at 19:14 UTC
