That, I think, we are all in agreement on. And that follows what we do in BCP 47, which is that we say that people *should* tag as specifically as possible. So if I know that content is "en-US", I *should* say "en-US" and not just "en". But I *can* also use "en". It might not be the best choice, but it is a legitimate usage (although not optimal) usage. However, it is a perfectly reasonable choice if I don't know whether it is "en-US" or "en-CA", or it could be both.
<br><br>So what about "mis"? Once again, I *should* tag more specifically, if I have the information. No argument at all there. The question is whether it is non-conformant to BCP 47 to tag "kind" as "mis". For that, we need to establish whether there is sufficient grounds in the text and data of ISO 639-2 as of the time that "mis" was taken into BCP 47 to conclusively determine that "mis" is disjoint from other language codes. I don't see a conclusive case from what you and John have said so far, unless I'm missing something.
<br><br>I would not at all be adverse to saying that you shouldn't use "und" or "mis" or "mul" or any collections if you have any more specific information about the content. And I think it is clear that we need much more guidance in BCP 47 as to intended usage.
<br><br>Mark<br><br><div><span class="gmail_quote">On 4/13/07, <b class="gmail_sendername">Peter Constable</b> <<a href="mailto:petercon@microsoft.com">petercon@microsoft.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think ISO 639-2 is clear that the most specific category should be used. That principle is implicit in the "(Other)" collections. I also think that principle in combination with collections creates maintenance problems. (Which is why I suggested that all the "(Other)" entries should just be "languages" entries.)
<br><br>(Btw, I think I suggested some time ago it might not be a bad thing to deprecate use of collection IDs in IETF language tags.)<br><br><br>Peter<br><br><br>-----Original Message-----<br>From: John Cowan [mailto:<a href="mailto:cowan@ccil.org">
cowan@ccil.org</a>]<br>Sent: Friday, April 13, 2007 2:07 PM<br>To: Mark Davis<br>Cc: LTRU Working Group; <a href="mailto:ietf-languages@alvestrand.no">ietf-languages@alvestrand.no</a><br>Subject: [Ltru] Re: "mis" update review request
<br><br>Mark Davis scripsit:<br><br>> You might like this to be true, but I don't see any substantiation of<br>> it in the standard. If you could point me to that, I'd appreciate it.<br><br>It seems rather self-evident to me that 'ber' is a subset of 'afa',
<br>and so on; but no, the standard doesn't say so. It does, however, say:<br><br> A collective language code is not intended to be used when an<br> individual language code or another more specific collective
<br> language code is available.<br><br><a href="http://www.loc.gov/standards/iso639-2/normtext.html">http://www.loc.gov/standards/iso639-2/normtext.html</a> section 4.1.1<br><br>I take that to mean that "afa" is unsuitable for a Berber language, and
<br>"ger" is unsuitable for English. A fortiori, "mis" is unsuitable for<br>a language for which a better code is available.<br><br>Questionless, this contradicts the desire for stability, but I don't
<br>see what's to be done about it. I tried at one point to get all<br>language collection codes deprecated, but it was pointed out that<br>there are good reasons for having them, as when insufficient evidence<br>is available.
<br><br>--<br>John Cowan <a href="mailto:cowan@ccil.org">cowan@ccil.org</a> <a href="http://ccil.org/~cowan">http://ccil.org/~cowan</a><br>I must confess that I have very little notion of what [s. 4 of the British<br>
Trade Marks Act, 1938] is intended to convey, and particularly the sentence<br>of 253 words, as I make them, which constitutes sub-section 1. I doubt if<br>the entire statute book could be successfully searched for a sentence of
<br>equal length which is of more fuliginous obscurity. --MacKinnon LJ, 1940<br><br>_______________________________________________<br>Ltru mailing list<br><a href="mailto:Ltru@ietf.org">Ltru@ietf.org</a><br><a href="https://www1.ietf.org/mailman/listinfo/ltru">
https://www1.ietf.org/mailman/listinfo/ltru</a><br><br>_______________________________________________<br>Ltru mailing list<br><a href="mailto:Ltru@ietf.org">Ltru@ietf.org</a><br><a href="https://www1.ietf.org/mailman/listinfo/ltru">
https://www1.ietf.org/mailman/listinfo/ltru</a><br></blockquote></div><br><br clear="all"><br>-- <br>Mark