But for something to be coded in 639-1, 639-2 or 639-3, it must be a distinct language. That is a sufficient condition for encoding in 639-3. Therefore, by simple deduction, to be encoded in 639-1 or 639-2, the concept must first be demonstrated that it qualifies for encoding in 639-3.
Your approach, Gerard, appears to be to say that something meets necessary conditions of 639-1, therefore qualifies for encoding in 639-1 (without any additional consideration of sufficient conditions), and subsequently there is an obligation for encoding in 639-2 and 639-3. IMO, that is totally backwards and would lead to significant damage to the standard as well as significant problems for implementers and users.
John, I will add to my earlier comments observations on this information in the request:
>> Evidence: All federal laws of Comoros>> All local laws in each of the three federated islands Treaties with other countries>> National Evidence: Government of Comoros>> Size Evidence: national literature>> Official Evidence: National language by article 1 of the Constitution>> Education Evidence: In the three federated islands of Comoros
These are assertions without any ostensive evidence. In this case, based on other information I have seen, I think this evidence is suspect.
Also, there is no indication of any end users or implementers requesting this. All we know is that, having come from the TC46 liaison, it appears that TC46 thinks this is needed. Yet I haven’t heard any of the TC46 representatives hear speak up to explain why it’s needed, nor do I know that this is based on a consensus decision within TC 46 rather than an independent action on the part of certain individuals.
What I know from history is that a _different_ part of TC46 that maintains ISO 3166-1 has a table they maintain and that they like to fill it in with identifiers from 639. Yet this JAC, with representation from TC46, gave clear indication years ago that the table in 3166-1 in question was ill-advised. If the basis of this request is in relation to that table in 3166-1, then TC46 should not expect the JAC to support it.
So, I would find it helpful if our TC46 representatives could clarify the basis of this request coming from TC46, and what the intended usage would be.
Dear All,In my opinion, there is no doubt that the correct interpretation of the current text of ISO 639 is the "blunt" one:- every language name coded in ISO 639-1 must also be coded in ISO 639-2, and- every individual language name coded in ISO 639-2 must also be coded in ISO 639-3.This is most clearly made explicit in clause "5 Relations entre les parties de l'ISO 639", more specifically in subclause "5.3 Principes", of ISO 639-4 "General principles of coding of the representation of names of languages and related entities, and application guidelines".Bien amicalement.Gérard LangLe 10 avr. 2014 à 09:32, Sebastian Drude a écrit :Yes, Peter.I did not want to formulate it so bluntly, but I fully agree, although that passage could also be interpreted as “if something is accepted in part (1 and) 2, it is also automatically included in part 3” – but that is clearly not appropriate as part 3 has its own mechanism for inclusion of new code points.Best,Sebastian DrudeI ask for your understanding if, in the interest of being quick and short, this mail may not fulfil all requirements on form and politeness.--PD Dr. Sebastian Drude, The Language ArchiveMax-Planck-Institute for PsycholinguisticsP.O. Box 310, 6500 AH Nijmegen, The NetherlandsEmail: [log in to unmask] – Phone: (+31) 24-3521.470