<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">As far as Yukon is concerned, I will send you all a link to the regulation, once it is law. Along with that, I will describe what we
did in a legal sense, where those authorities come from, and how it is described. I am confident with what I’ve submitted for approval to our government, but it is inappropriate for me to describe it publicly before Cabinet approves our regulation.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Will be in touch. Thanks for keeping me in on the conversation. I don’t know how many people are on this TZ mailing list, hopefully
the information coming from Yukon isn’t just noise in your inboxes. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#244C5A">Andrew G. Smith<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D">Intergovernmental Relations</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#F2A900"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D">Executive Council Office<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D">Government of Yukon<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D">C: 867-335-6008<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Arthur David Olson <arthurdavidolson@gmail.com>
<br>
<b>Sent:</b> July 3, 2020 2:29 PM<br>
<b>To:</b> Time zone mailing list <tz@iana.org><br>
<b>Cc:</b> Andrew.Smith <Andrew.Smith@gov.yk.ca><br>
<b>Subject:</b> Re: [tz] [IANA #1173666] Time zone change - Yukon Canada<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">One other piece of information to solicit from governments who switch to permanent DST: is the new scheme permanent daylight time, or does it establish a new standard time?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">(This can be of importance in dealing with laws or contracts written in terms of "standard time.")<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> @dashdashado<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Fri, Jul 3, 2020 at 5:22 PM Brian Inglis <<a href="mailto:Brian.Inglis@systematicsw.ab.ca">Brian.Inglis@systematicsw.ab.ca</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">We should also ask all government folks to provide web links to officially<br>
published acts, decrees, laws, orders, regulations, or statutes available online<br>
at a government web site, with the document providing full details including<br>
dates, times, and the zones in effect when any changes or transitions in time<br>
are to be made, plus any preferences as to normal English names or<br>
abbreviations, as well as the legally effective date (time, zone) of publication.<br>
These official document links avoid any possible later issues, should anyone<br>
dispute and solicit changes to the time keeping practice in effect at any<br>
location within that legal jurisdiction, as we are aware of both official and de<br>
facto variances in practices near many time zone boundaries.<br>
<br>
On 2020-07-03 12:40, Tim Parenti wrote:<br>
> Thanks for keeping us in the loop, then.<br>
> Since tz is used directly by many operating systems — Apple (including iOS),<br>
> Google (including Android), and most Linux distributions — most day-to-day users<br>
> should be good to go when the change is finalized, if they aren't already. For<br>
> what it's worth, it seems Microsoft have also picked up on the change<br>
> <a href="https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/time-zone-updates-for-yukon-canada/ba-p/1334689" target="_blank">
https://techcommunity.microsoft.com/t5/daylight-saving-time-time-zone/time-zone-updates-for-yukon-canada/ba-p/1334689</a>,<br>
> though from the date of their announcement, it's possible they got the news <br>
> from us.<br>
> Other software which does not rely on the operating system's timezone <br>
> definitions may require their own updates; those concerns are downstream<br>
> from this project.<br>
<br>
> On Fri, 3 Jul 2020 at 14:31, Andrew Smith wrote:<br>
> That is excellent to hear, Tim. <br>
> Yes, I had known that some time services has interpreted our announcement as <br>
> the ‘done and dusted’ finalization. At that point in March it was a policy <br>
> commitment, and the news on that nuance was not totally clear. We just do <br>
> have some legal process to finish off, which we are on track to do, so I <br>
> don’t think we will end up in a tough spot. <br>
> I will let you know when we make our change legally final so we can all rest <br>
> assured that November 2 will still see us on UTC -7.<br>
<br>
> On July 3, 2020 11:24 AM, Tim Parenti wrote:<br>
> We made this change in our codebase on 5 March 2020, based on 4 March CBC <br>
> reporting and a government press release stating that Yukon would be <br>
> remaining permanently on UTC-7 following its spring-forward transition on 8 <br>
> March. As such, both America/Dawson and America/Whitehorse have been updated<br>
> accordingly:<br>
> <a href="https://github.com/eggert/tz/commit/e6c1f0e7daa0b6c5131b2976c6be9190845d2b49" target="_blank">
https://github.com/eggert/tz/commit/e6c1f0e7daa0b6c5131b2976c6be9190845d2b49</a><br>
> (Canada/Yukon is a long-deprecated backwards-compatibility link to <br>
> America/Whitehorse, so need not be updated separately.)<br>
> This change is already included in our latest release, 2020a, which was <br>
> published on 23 April 2020. Although it can sometimes take several weeks or <br>
> months after publication for our releases to make it to downstream <br>
> distributions and software updates for various computer and mobile platforms,<br>
> many recent devices that are receiving regular updates should already have<br>
> this change, and many more are likely to receive it before Yukon time<br>
> diverges from our old predictions in November.<br>
> One (hopefully small) point: Our understanding from the press release at <br>
> <a href="https://yukon.ca/en/news/yukon-end-seasonal-time-change" target="_blank">
https://yukon.ca/en/news/yukon-end-seasonal-time-change</a> was that this <br>
> decision was already finalized. If it is not, this is not a major issue,<br>
> but do note that tz's current predictions published in 2020a do not have<br>
> Yukon falling back on 1 November 2020… so if for some reason the regulatory <br>
> processes should be delayed, please contact us as soon as that's apparent.<br>
> On July 2, 2020 3:48 PM, Amanda Baber via RT wrote:<br>
> Thank you for contacting us.<br>
> IANA hosts the Time Zone Database, but the database is managed by the Time<br>
> Zone Coordinator in conjunction with a mailing list. You can find find<br>
> mailing list information here:<br>
> <a href="https://www.iana.org/time-zones" target="_blank">https://www.iana.org/time-zones</a><br>
> This document should have or point to much of the information you're looking<br>
> for:<br>
> <a href="https://data.iana.org/time-zones/tz-link.html" target="_blank">https://data.iana.org/time-zones/tz-link.html</a><br>
> As is noted at the link above, "If your government plans to change its time <br>
> zone boundaries or daylight saving rules, inform <a href="mailto:tz@iana.org" target="_blank">
tz@iana.org</a> well in advance,<br>
> as this will coordinate updates to many cell phones, computers, and other<br>
> devices around the world. With less than a year's notice there is a good<br>
> chance that some computer-based clocks will operate incorrectly after the<br>
> change, due to delays in propagating updates to software and data. The<br>
> shorter the notice, the more likely clock problems will arise; see<br>
> <a href="https://codeofmatt.com/on-the-timing-of-time-zone-changes" target="_blank">
https://codeofmatt.com/on-the-timing-of-time-zone-changes</a><br>
> for examples."<br>
<br>
> On Thu Jul 02 22:20:44 2020, Andrew Smith wrote:<br>
>> I work for the Government of Yukon in Canada. We are in the process of <br>
>> revising our definition of time to be permanently on UTC -7, no longer <br>
>> observing a twice-annual time change. I was on the hunt for authoritative<br>
>> standards related to time, and saw the IANA come up as caretaker of the<br>
>> time zone database, which appears to be relied on for software and systems.<br>
>> I started with ISO 8601, but couldn't see the full text to know if there<br>
>> are time zone standards there. I am contacting you to see your TZ database<br>
>> is a widely adopted and authoritative as it seems, to see if there is any<br>
>> process to making this adjustment in your TZ database, and perhaps to know<br>
>> if there are other agencies that should be aware of what Yukon is <br>
>> planning.<br>
>> From what I see now, TZ database names "America/Dawson", <br>
>> "America/Whitehorse" and "Canada/Yukon" would be affected by this change.<br>
>> <br>
>> Our regulation is not yet complete, so it is not law at this time and I am<br>
>> not looking for immediate change. We are aiming for finalization here by<br>
>> November 1, 2020.<br>
<br>
-- <br>
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada<br>
<br>
This email may be disturbing to some readers as it contains<br>
too much technical detail. Reader discretion is advised.<br>
[Data in IEC units and prefixes, physical quantities in SI.]<o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>