I haven’t been able to spend much time (heh heh) following this thread, but I 
have noticed a couple of lines along the way which raised questions for me. I’m 
hoping either the original poster or someone else can help with my 
understanding.

> Please follow the law.

I’ve noticed this one several times. To me, the natural opposite of “following 
the law” is “violating” or “breaking” the law. It seems that tzdb falls into a 
third category: not being subject to the law at all, such that adhering or not 
adhering to it is a moot point. Is there a passage, either in tzdb or in 
Canadian federal or provincial law, that makes tzdb subject to the law in 
question?

> 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.

I thought there was already a zone in tzdb, America/Vancouver, which covered 
all of British Columbia except for a small area in the southeast. Is 
America/Vancouver no longer adequate to represent the intended area? What 
regions that formerly observed America/Vancouver now require a different zone?

> Again a reminder from RFC6557: "To be clear, the TZ Coordinator SHALL
> NOT set time zone policy for a region”.

I definitely missed this one. Has the TZ coordinator attempted to set time zone 
policy? Is there part of the definition of America/Vancouver where the TZ 
coordinator has misrepresented the UTC offsets and DST transition dates for the 
zone, other than the “temporary hack” section which is intended to work around 
technical constraints?

> Canada, as a sovereign country, gets to decide its timezones.

Again, this is something I missed from scanning the thread quickly. Has some 
action of the TZ coordinator deprived Canada of its right to determine its own 
time zones? This is perhaps related to the question above.

I will try to keep up better with the full discussion going forward.

Thanks,

--
Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org


Reply via email to