Speaking to "I don't think I'd want Unicode specifying any of:"<br><br>We'd be hosting the TZ group; the process the group uses and its output would be up to the group. (The only thing we'd need is for the group to provide a description of whatever process <i>is</i> being followed.)<br>
<br clear="all">Mark<br><br>And by the way, even for Unicode, the consortium is not in the business of specifying APIs or binary file formats; I don't know where that perception arose.<br><br><div class="gmail_quote">
On Thu, Aug 27, 2009 at 14:33, Bill Seymour <span dir="ltr"><<a href="mailto:stdbill.h@pobox.com">stdbill.h@pobox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Thu, Aug 27, 2009 at 2:58 PM, John Emmons<<a href="mailto:emmo@us.ibm.com">emmo@us.ibm.com</a>> wrote:<br>
><br>
> I would think this would be a good move for both TZ and Unicode.<br>
><br>
<br>
</div>Why? Beyond getting localized time zone names in the CLDR,<br>
where's the expertise?<br>
<br>
If this is just an offer for hosting an HTTP and FTP site, then cool;<br>
but I don't think I'd want Unicode specifying any of:<br>
- source file formats.<br>
- binary file formats.<br>
- APIs.<br>
<font color="#888888"><br>
--Bill Seymour<br>
<br>
</font></blockquote></div><br>