I think what you are saying is that "hbs" has been carefully considered and <i>knowingly</i> been marked as not-deprecated in ISO 639-3. I have no issue at all with that; I think that was the right thing to do.<br>
<br>However, that still leaves us with an issue in the iana registry (<i>after</i> the new version comes into force).<br><br>hbs = sh, yet<br>hbs is not Deprecated, and<br>sh is Deprecated<br><br>We could take ISO 639-3 as superseding 639-1 on the issue of deprecation, and I think that would be the right thing to do. However, it would be cleaner yet if ISO 639-1 were to un-deprecate sh, so that it was consistent with ISO 639-3.<br>
<br clear="all">Mark<br>
<br><br><div class="gmail_quote">On Mon, Jun 29, 2009 at 08:59, <span dir="ltr"><<a href="mailto:ISO639-3@sil.org" target="_blank">ISO639-3@sil.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;">
<br><font face="sans-serif" size="2">Hello All,</font>
<br>
<br><font face="sans-serif" size="2">I do not think that there is anything
requiring correction. There are other instances of macrolanguages in ISO
639-3 that do not exist in Part 2 (much less, Part 1). See [</font><a href="http://www.sil.org/iso639-3/documentation.asp?id=luy" target="_blank"><font color="blue" face="sans-serif" size="2">luy</font></a><font face="sans-serif" size="2">]
and [</font><a href="http://www.sil.org/iso639-3/documentation.asp?id=kln" target="_blank"><font color="blue" face="sans-serif" size="2">kln</font></a><font face="sans-serif" size="2">].
The deprecation of [sh] in Part 1, and the retirement of [hbs] from the
predecesor of Part 2 with the split into three individual languages were
actions taken before the notion of "macrolanguage" was in existence
in the 639 standards group. The decision to include [hbs] as a macrolanguage
in Part 3 was a separate decision, taken in 2005 and reiterated in 2007
with the adoption of ISO 639-3.</font>
<br>
<br><font face="sans-serif" size="2">Best regards,</font>
<br>
<br><font face="sans-serif" size="2">Joan Spanne<br>
ISO 639-3/RA<br>
SIL International<br>
7500 W Camp Wisdom Rd<br>
Dallas, TX 75236<br>
<a href="mailto:ISO639-3@sil.org" target="_blank">ISO639-3@sil.org</a></font>
<br>
<br>
<br>
<br>
<table width="100%">
<tbody><tr valign="top">
<td width="40%"><div><font face="sans-serif" size="1"><b>"Doug Ewell"
<<a href="mailto:doug@ewellic.org" target="_blank">doug@ewellic.org</a>></b> </font>
<br></div><font face="sans-serif" size="1">Sent by: <a href="mailto:ietf-languages-bounces@alvestrand.no" target="_blank">ietf-languages-bounces@alvestrand.no</a></font>
<p><font face="sans-serif" size="1">2009-06-29 08:04 AM</font>
</p></td><td width="59%">
<table width="100%">
<tbody><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">To</font></div>
</td><td><font face="sans-serif" size="1"><<a href="mailto:ietf-languages@iana.org" target="_blank">ietf-languages@iana.org</a>></font>
</td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">cc</font></div><div>
</div></td><td>
</td></tr><tr valign="top">
<td>
<div align="right"><font face="sans-serif" size="1">Subject</font></div>
</td><td><font face="sans-serif" size="1">Re: Anomaly in upcoming registry</font></td></tr></tbody></table>
<br>
<table>
<tbody><tr valign="top">
<td>
</td><td></td></tr></tbody></table>
<br></td></tr></tbody></table>
<br>
<br><div><div></div><div>
<br><tt><font size="2">Randy Presuhn <randy underscore presuhn at mindspring
dot com> wrote:<br>
<br>
>> ... It certainly isn't patently obvious to me that this is a bug
in <br>
>> the draft-4645bis Registry that needs to be fixed.<br>
><br>
> I think no one is suggesting that anything be done to draft-4645bis.
I <br>
> think re-opening 4645bis to make a change of this nature would be
<br>
> inappropriate.<br>
<br>
No, I agree that Mark was not calling to change anything in <br>
draft-4645bis, but rather in the "draft-4645bis Registry" --
the <br>
Registry to be supplied to IANA by draft-4645bis, whose method of <br>
construction is described in draft-4645bis.<br>
<br>
My position is that the change Mark suggests may not be appropriate, and
<br>
is certainly not a <span lang="en-US">slam dunk</span>.
It depends on <br>
our interpretation of draft-4646bis and any priorities it does or <br>
doesn't give to ISO 639-3 over other parts of ISO 639, and it depends on
<br>
whether the relevant RA or JAC decides to correct the inconsistency in
<br>
639 by either (a) reviving "sh" in 639-1 and adding "hbs"
to 639-2, or <br>
(b) withdrawing "hbs" from 639-3.<br>
<br>
I don't see why the philosophical discussion necessarily must wait until
<br>
the new Registry is in force, but if others want to wait, that's fine <br>
with me.<br>
<br>
--<br>
Doug Ewell * Thornton, Colorado, USA * RFC 4645
* UTN #14<br>
<a href="http://www.ewellic.org" target="_blank">http://www.ewellic.org</a><br>
<a href="http://www1.ietf.org/html.charters/ltru-charter.html" target="_blank">http://www1.ietf.org/html.charters/ltru-charter.html</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages" target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a> ˆ<br>
<br>
_______________________________________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no" target="_blank">Ietf-languages@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages" target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><br>
</font></tt>
<br>
</div></div><br>_______________________________________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no" target="_blank">Ietf-languages@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages" target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><br>
<br></blockquote></div><br>