Peter Constable wrote: > why don't you start with 639-1 and 639-2 since those are far more > tractable sets and would be part of vetting 639-3 anyway. (My point > isn't to actually get you to do that but rather to point out you're > being somewhat arbitrary here.) Yes, and "tlh" is IMO a border case, I've some doubts about it as a "language subtag". But otherwise it's something real, not only the movies and the books, folks take it as some kind of ethics or religion. For slightly different reasons "sjn" is also okay from my POV. About 25 years ago I collected a word list - the German translation didn't offer this. For "jbo" I trust that John knows why it's okay, I had no reason to check it. But that "orq" case triggered all my "Wikipedia list of micronations" alarm bells at once. There are folks out there who try to smuggle in nonsense, and some not for fun but for dubious purposes, also known as "search engine optimization" or "spam". Some "micronations" are obscure pyramid schemes or worse. And I trust that "Sea Island" in "gul" is unrelated to "Sealand". As micronation Sealand is mostly harmless, but there's a lot of fine print, "mostly" does not mean "completely", gullible folks lost some real money. > the job of LTRU is to work on 4646bis, not to sift through 639-3 and > cherry pick. It is *NOT* the role of LTRU > to vet registration requests for variant or 5..8 language subtags; > that the job of ietf-languages. Sure, but LTRU could decree that 639-3 type "C" is only registered on demand after approval by the subtag list. Probably that's pointless if there's no way to get rid of it in 639-3 later, the alpha3 code is then "lost" (occupied forever) anyway, not copying it to the registry doesn't help. A more effective procedure could be that the subtag review list gets a copy of all proposals for new code elements - maybe that boils down to "subscribe some newsletter to the subtag review list". Frank _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.