Good point; the target for 639-1/2 is different, and the threshold for deprecation is different. And given this conversation, I think it is pretty clear that we should un-deprecate sh in the registry; we are following 639-3 in not being restrictive about the codes we add (understatement) to the registry, they considered the issue of deprecating hbs (=sh) and decided not to, so we should follow their lead.<br>
<br clear="all">Mark<br>
<br><br><div class="gmail_quote">On Mon, Jun 29, 2009 at 13:22, John Cowan <span dir="ltr"><<a href="mailto:cowan@ccil.org">cowan@ccil.org</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;">
Mark Davis â?? scripsit:<br>
<div class="im"><br>
> hbs = sh, yet<br>
> hbs is not Deprecated, and<br>
> sh is Deprecated<br>
<br>
</div>It's actually worse than that. hbs in 639-2 is deprecated ("retired"),<br>
but hbs in 639-3 is not deprecated.<br>
<div class="im"><br>
> We could take ISO 639-3 as superseding 639-1 on the issue of deprecation,<br>
> and I think that would be the right thing to do. However, it would be<br>
> cleaner yet if ISO 639-1 were to un-deprecate sh, so that it was consistent<br>
> with ISO 639-3.<br>
<br>
</div>For "639-1" read "639-1 and 639-2". But there's a policy question here:<br>
coding a language in -1 or -2 is a policy decision, not merely a technical<br>
one: it involves an explicit value judgement on which languages are considered<br>
important enough to get -1 codes or membership in the -2 set. The various RAs<br>
reserve the right, it seems to me, to change their minds about this (as we<br>
reserve the right to ignore it when they remove codes).<br>
<font color="#888888"><br>
--<br>
My corporate data's a mess! John Cowan<br>
It's all semi-structured, no less. <a href="http://www.ccil.org/%7Ecowan" target="_blank">http://www.ccil.org/~cowan</a><br>
But I'll be carefree <a href="mailto:cowan@ccil.org">cowan@ccil.org</a><br>
Using XSLT<br>
On an XML DBMS.<br>
</font></blockquote></div><br>