Hello all,

I apologize, to bring it back to a discussion on the merits of the change.
I believe a new TZ name should be created with an update to the database 
because the situation in B.C. specifically (as opposed to areas to the east) 
satisfies all three criteria in RFC6557.

According to the "Best Current Practices”:

1: "New TZ names (e.g., locations) are only to be created when the scope of the 
region a name was envisioned to cover is no longer accurate."

— America/Vancouver and, for example, America/LosAngeles used to be effectively 
equivalent. This is no longer the case and is now causing significant and 
widespread confusion and disruption.  The scope of the name America/Vancouver 
is now -7 in the province of British Columbia and thus should either use 
Pacific Daylight/PDT or Pacifc Time/PCT. PDT is inconsistent with law in BC. 
“Pacific Time” is specified and there is no longer a legal concept of “Daylight 
Savings Time” with all previous legislation mentioning Daylight Savings having 
been modified or repealed.

2: "In order to correct historical inaccuracies, a new TZ name MAY be added 
when it is necessary to indicate what was the consensus view at a given time 
and location.  Such TZ names are usually not added when the inaccuracy was 
prior to 1970.”

— this doesn’t apply here as this is a new change. However, it does lend 
credence that a historical consensus view carries weight for a region. Outside 
of very small sub-regions, Mountain Standard Time has never been used, be it 
officially or otherwise, in the territory of British Columbia since WWI and has 
never been mentioned as the official time standard in legislation.  The 
reference has always been to a timezone under the moniker “Pacific”.  The 
change made by the political body (Government of BC) and associated legislation 
continues that trend with “Pacific Time” and the abbreviation of “PCT”.

3: "Changes to existing entries SHALL reflect the consensus on the ground in 
the region covered by that entry. “

— The consensus in British Columbia officially is that “Pacific Time” is in the 
legislation. This is now being used on official Government of BC and Canada 
websites, news outlets, and information portals. In a wider community sense, 
the term “Pacific” is the expectation from the wider public, not Mountain.

The September 17, 2026 press release from the Government of BC specifically 
mentions "communications and operational systems" which one can infer to mean 
systems like those reliant on the tzdata IANA database.

Quote: "Establishing PCT as the abbreviation for Pacific Time in advance of the 
usually anticipated time change in November 2026 provides clarity and 
consistency for businesses, organizations and people referencing it in 
communications, operational systems and public-facing materials”


https://archive.news.gov.bc.ca/releases/news_releases_2024-2028/2026CITZ0009-001073.htm
I don’t believe I can contribute more to this discussion than I already have. I 
hope this can lead to a resolution where the Pacific Time/PCT name is adopted.

Cheers
Chris






> On Nov 12, 2026, at 10:30, James Bellaire <[email protected]> wrote:
> 
> Take a look at Europe/Berlin. Multiple countries sharing a single zone since 
> they all have a shared time since 1970.
> 
> The standard for an area getting a different Zone entry is a difference in 
> the clock on the wall time since 1970. Not local preferences or political 
> issues.
> 
> If MST is offensive then Paul has offered the option of -07 for 
> America/Vancouver and -06 for America/Edmonton. CLDR has gone with PDT and 
> MDT. 
> 
> On November 12, 2026, at 10:19, Chris Alemany <[email protected] 
> <mailto:[email protected]>> wrote:
> 
> 
>> Hi James,
>> 
>> I am sorry but I do not understand the logic here:
>> "The ask for each province and territory in Canada to get a unique zone for 
>> the purpose of providing a unique name is out of scope for the tzdata 
>> project.”
>> 
>> The provinces and territories are larger than most countries and many cover 
>> more than one time zone in north america.  These are the jurisdictions that 
>> control time zones in Canada and have done since WWI. The timezones have not 
>> changed in 100 years, since the advent of computers.
>> 
>> We are simply asking tzdata to follow the law, so that we can follow the law.
>> This output from ‘date’ from my servers located in Port Alberni, BC, Canada, 
>> does not follow the law. Tzdata is the package that controls that output.
>> 
>> Thu 12 Nov 2026 08:16:37 AM MST
>> 
>> Please follow the law.
>> 
>> Cheers
>> Chris
>> 
>> 
>>> On Nov 11, 2026, at 04:15, James Bellaire via tz <[email protected]> wrote:
>>> 
>>> On 11/11/2026 1:31 AM, Brian Inglis via tz wrote:
>>> The lack of effort by application vendors, and input from international 
>>> contributors, are influencing the couple of volunteer maintainers to switch 
>>> to just straight numeric UTC offsets (format %Z -> %z), in the hopes that 
>>> applications will do their jobs better.
>>> 
>>> I did a quick count and there are approximately 439 "Zone" entries in 
>>> tzdata, including all regions and the back zones that exist for 
>>> users/applications who want historical time stamps. 173 zones use the "%z" 
>>> format that passes through an offset or a fixed numeric format such as 
>>> "+05" that would provide a similar result in areas that don't have DST. 132 
>>> zones have names that change during DST (such as PST becoming PDT, CET 
>>> becoming CEST or GMT becoming BST). Note that due to the support of 
>>> historic times there are many zones that get limited use.
>>> 
>>> Support of accurate times since 1970 is within the scope of tzdata. I 
>>> appreciate the abbreviations being present. It is certainly easier when all 
>>> areas within a zone share a common name for their shared time zone. For 
>>> example, CET/CEST works nicely in Europe for Central European Time instead 
>>> of each country getting a unique name (which would require each country 
>>> getting their own zone in the main data).
>>> 
>>> The ask for each province and territory in Canada to get a unique zone for 
>>> the purpose of providing a unique name is out of scope for the tzdata 
>>> project. The focus is providing accurate times since 1970.
>>> 
>>> 
>>> I appreciate having names in tzdata and not %z. But areas that share a time 
>>> zone (such as America/Edmonton covering Alberta, eastern NWT and part of 
>>> BC) not agreeing on a common name for their zone leads to either the 
>>> assignment of an internationally known zone (such as CST which could be 
>>> considered "well known" as UTC-06 - unless you're referring to UTC+08 in 
>>> China or UTC-05 in Cuba). Or setting something less descriptive such as %z 
>>> (-06 appearing in applications relying solely on tzdata).
>>> 
>>> I will note that CLDR is passing daylight times for the recently changed 
>>> zones in Canada: PDT, MDT, CDT instead of MST, CST and EST. I would accept 
>>> that as a solution since those abbreviations have well known offsets (with 
>>> CDT being UTC-04 in Cuba being a minor confusion). There was some 
>>> discussion earlier this year about not wanting to use xDT names in zones 
>>> where there is no xST time to fall back to. The preference of using 
>>> MST/CST/EST in areas that have recently been PT/MT/CT vs following the CLDR 
>>> example of using xDT names without xST vs not providing a name (%z) is the 
>>> choice being presented. %z seems to be the least controversial.
>>> 
>> 

Reply via email to