On Tue, May 7, 2013 at 8:42 PM, Paul Koning <span dir="ltr"><<a href="mailto:paulkoning@comcast.net" target="_blank">paulkoning@comcast.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ok then, should Asia/Taipei be listed with country code CN? Or not at all? </blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It seems to me the exact same reasoning that is being used here applies to both cases.<br>
</blockquote><div><br></div><div>Just to "piggy-back" on Paul's "case" here, let's look at this as a process-oriented detail ...</div><div><br></div><div>Whenever one makes a suggestion for a change, _please_ also: </div>
<div> A) State how it effects _more_ than just one (1) case -- aim for at least three (3) -- keep sigma in mind here</div><div> B) Put down explicit sets of logic, that are completely objective and technical, and run all three-plus (3+) cases through it</div>
<div> C) Evaluate if and how this will effect not only existing Zoneinfo history and approach, but what impacts it may have to code/files</div><div><br></div><div>I think people here are _failing_ to recognize that this isn't about one (1) case, and it has multiple impacts to many other cases. So ... if there is a strong case to make a change in not just logic, but how Zoneinfo does things and goes forward in doing things -- including possible changes to Zoneinfo code and/or formats (hopefully not, but at least assumptions) -- then make it, and make it objectively doing A-B-C together.</div>
<div><br></div><div>Just my $0.02, not speaking on-behalf of anyone else.</div><div><br></div><div><br></div></div>--<br>Bryan J Smith - Professional, Technical Annoyance<br>b.j.smith at <a href="http://ieee.org" target="_blank">ieee.org</a> - <a href="http://www.linkedin.com/in/bjsmith" target="_blank">http://www.linkedin.com/in/bjsmith</a><br>
<br>