Re: [Ietf-languages] Latin Sub tags

drude@xs4all.nl Fri, 01 December 2023 14:41 UTC

Return-Path: <drude@xs4all.nl>
X-Original-To: ietf-languages@ietfa.amsl.com
Delivered-To: ietf-languages@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA7EC14F74A for <ietf-languages@ietfa.amsl.com>; Fri, 1 Dec 2023 06:41:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.04
X-Spam-Level:
X-Spam-Status: No, score=-6.04 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" header.d=xs4all.nl
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qVbYTp9nrRq for <ietf-languages@ietfa.amsl.com>; Fri, 1 Dec 2023 06:40:55 -0800 (PST)
Received: from out.mail.icann.org (out.mail.icann.org [64.78.33.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 237DBC15108F for <ietf-languages@ietf.org>; Fri, 1 Dec 2023 06:40:54 -0800 (PST)
Received: from MBX112-E2-CO-1.pexch112.icann.org (10.226.41.200) by MBX112-E2-CO-1.pexch112.icann.org (10.226.41.200) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Fri, 1 Dec 2023 06:40:53 -0800
Received: from aesmt112-co-1-1.serverpod.net (10.224.74.75) by MBX112-E2-CO-1.pexch112.icann.org (10.226.41.201) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27 via Frontend Transport; Fri, 1 Dec 2023 06:40:53 -0800
Received: from aesc112-co-1-1.serverpod.net (aesc112-co-1-1.serverpod.net [10.224.76.90]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by aesmt112-co-1.serverpod.net (Postfix) with ESMTPS id 4B12340003 for <ietf-languages@ex.icann.org>; Fri, 1 Dec 2023 06:40:53 -0800 (PST)
Received: from exmx112-co-1-1.serverpod.net (exmx112-co-1-1.serverpod.net [10.224.72.73]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by aesmt112-co-1.serverpod.net (Postfix) with ESMTPS id 251B240002 for <ietf-languages@ex.icann.org>; Fri, 1 Dec 2023 06:40:53 -0800 (PST)
Received: from pechora4.lax.icann.org (pechora4.icann.org [192.0.33.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by west.smtp.mx.icann.org (Postfix) with ESMTPS id 424A7180006 for <ietf-languages@ex.icann.org>; Fri, 1 Dec 2023 06:40:50 -0800 (PST)
Received: from ewsoutbound.kpnmail.nl (ewsoutbound.kpnmail.nl [195.121.94.168]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pechora4.lax.icann.org (Postfix) with ESMTPS id A50AA7000C06 for <ietf-languages@iana.org>; Fri, 1 Dec 2023 14:40:49 +0000 (UTC)
X-KPN-MessageId: 8d6584a6-9057-11ee-b097-005056aba152
Received: from smtp.kpnmail.nl (unknown [10.31.155.37]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id 8d6584a6-9057-11ee-b097-005056aba152; Fri, 01 Dec 2023 15:40:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xs4all.nl; s=xs4all01; h=content-type:mime-version:message-id:date:subject:to:from; bh=UOaiRjmVSWkSeYeFB6Uaut+Hk7/fwkS1WVE100Nizfg=; b=Rz8u/DatOn5i3YQ3/2CUsXEVKFCjXpHIOG/pxuSNsQMhXCxKJCJyZOXM2kj8SMMTssePBrysNS98s LTcLfK3GzYDVtJnGaOIH7m8i0tRTb2KTpDeK2Tk2IUOEYTqbz1XV6KbJNtU51Blhz2BF2kDxfJGpiO U8LH2emi9mtxK16en+11z+7JxcwuN+Yr4wnv1Snit88cMjvZsbgAa3a4IJK+Ud8Z5E8Ba8ZT/7Z3Vp YuYB+7nVJBgNYRz3xywMWNXPpaO9+Ntb8FZGqFFAhYfjqKrAqF89zCgrhjEmwhPxbT1S6mtnJ0jdUw slu501q01YF0fCcnZoA5A/yb+GI1OCQ==
X-KPN-MID: 33|LUdFoGbNxT4SoEvZ458eFUop+lkrHm/8X9+O1nHUs1tWp/4iGmU6w1Ty0aRGxB/ gf6F7EkaOhwp49TlAbTj2V8rN+EdsbHxB+qSqhEi+46c=
X-KPN-VerifiedSender: Yes
X-CMASSUN: 33|xsfrXSbTO4SB2JA9urOKa2LxGXfLbt+7qg2A/ilq5YcSmIORYRFrGGZg+pC+fDx ku3gBg4q3tYgz/6iMotiRag==
X-Originating-IP: 191.243.102.222
Received: from LAPTOPSTGT0CJL (unknown [191.243.102.222]) by smtp.xs4all.nl (Halon) with ESMTPSA id 8f13b126-9057-11ee-824c-005056ab1411; Fri, 01 Dec 2023 15:40:26 +0100 (CET)
From: drude@xs4all.nl
To: 'Registrar ISO639-3' <iso639-3@sil.org>, 'John Cowan' <cowan@ccil.org>
CC: 'Hugh Paterson III' <sil.linguist@gmail.com>, 'Doug Ewell' <doug@ewellic.org>, 'IETF Languages Discussion' <ietf-languages@iana.org>
References: <CAE=3Ky-swzNn1hXba=muJF_radLugdKxhJ=u-_DcLiysDbothw@mail.gmail.com> <SJ0PR03MB6598925FCBA24238F417BE25CA82A@SJ0PR03MB6598.namprd03.prod.outlook.com> <CAE=3Ky_g3Sd7eBNq7H7_5BvkP-2qCbyYzQdO_eCSDzc70kQbJQ@mail.gmail.com> <012401da23b4$a9a291a0$fce7b4e0$@xs4all.nl> <CAD2gp_RxAdYsrW9wGSmH=A98zAiFYpFfgMWbTGqWb9zPvZT2JA@mail.gmail.com> <CAKgG5bR5KjSE6Um8mTjp3zGFqzxBOt6ZHONJTFmjN_cvBjdUtg@mail.gmail.com>
In-Reply-To: <CAKgG5bR5KjSE6Um8mTjp3zGFqzxBOt6ZHONJTFmjN_cvBjdUtg@mail.gmail.com>
Date: Fri, 01 Dec 2023 11:40:19 -0300
Message-ID: <01de01da2464$510d3300$f3279900$@xs4all.nl>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_01DF_01DA244B.2BBFFB00"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDLQAA9IMh7Xlm6KelyaCw0s8JhTAGDerWTApsc6lgDWU7WUgJBPOrhAhrPI4ACgYNuuQ==
Content-Language: en-us
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.4 cv=UvJwis8B c=1 sm=1 tr=0 ts=6569f073 a=wX29lFdrCqJoa/4ja/1t1g==:117 a=wX29lFdrCqJoa/4ja/1t1g==:17 a=R863zJxarjkA:10 a=e2cXIFwxEfEA:10 a=DAwyPP_o2Byb1YXLmDAA:9 a=86U1H9NdAAAA:8 a=48vgC7mUAAAA:8 a=2tsvuTQuAAAA:8 a=xOd6jRPJAAAA:8 a=pGLkceISAAAA:8 a=nORFd0-XAAAA:8 a=I0CVDw5ZAAAA:8 a=YKbctoaF_PuJfh0dxNEA:9 a=QEXdDO2ut3YA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=Ujqc0IvplFr_1_JBgFwA:9 a=wfWmHFMRlLMXNqZN:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=lqcHg5cX4UMA:10 a=LwX-U-nOfP1m2u8RUeUA:9 a=KQqxNPgzF0kA:10 a=VEiTNn8F7TgA:10 a=3ocqyLwIp7_IhjRobAq6:22 a=w1C3t2QeGrPiZgrLijVG:22 a=w1QI8THEI4iyJQ0oNEIE:22 a=AYkXoqVYie-NGRFAsbO8:22 a=YdXdGVBxRxTCRzIkH2Jn:22
X-SOURCE-IP: 192.0.33.74
X-SPF-STATUS: soft_fail
X-SPF-FROM-STATUS: not_checked
X-RDNS-STATUS: pass
X-HELO-STRING: pechora4.lax.icann.org
Spam-Stopper-Id: 8ee02b21-9aaa-4423-b6aa-06e5e047737d
Spam-Stopper-v2: Yes
X-Envelope-Mail-From: drude@xs4all.nl
X-Spam-Category: None
X-AES-Category: LEGIT
X-Spam-Reasons: None
X-AES-Analytics-Data: eyJ0aW1lc3RhbXAiOiAiMjAyMy0xMi0wMVQxNDo0MDo1My4yMjBaIiwgIm1lc3NhZ2VUcmFja2luZyI6IHsiaGFuZGxpbmciOiBbIlRISVJEIFBBUlRZIEJZUEFTUyJdLCAidW5pZmllZENhdGVnb3J5IjogIlVOQ0FURUdPUklTRUQifSwgImVuZ2luZXMiOiB7fX0=
X-Auto-Response-Suppress: DR, OOF, AutoReply
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/1Js77fIo8AcdYEODGX3xnPVD0hY>
Subject: Re: [Ietf-languages] Latin Sub tags
X-BeenThere: ietf-languages@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Review of requests for language tag registration according to BCP 47 \(RFC 4646\)" <ietf-languages.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-languages/>
List-Post: <mailto:ietf-languages@ietf.org>
List-Help: <mailto:ietf-languages-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Dec 2023 14:41:00 -0000

Dear John, Hugh, all,

 

complementing what Janell and other have answered, also before, formally, the Ethnologue FOLLOWED the ISO 639-3 updates, although the two processes were difficult to distinguish, which was one of the reasons to revise ISO 639 in the first place.

 

Here are the Terms of Reference for the new Maintenance Agency: https://standards.iso.org/iso/639/ed-2/en/.  There is also a workflow for the processing of change requests.  In the deliberation phase, the members of the MA board can and should consult with experts, whose responses should be publicly available, but, answering Hugh’s question,  there is no central expert mailing list such as here at IANA/IETF.  Still, this seems better to me than the previous procedure, where the ISO 639-3 registrar asked undisclosed experts and decided basically alone, which was a critique I heard many times among colleagues.  (Usually, only cases involving the former Parts 1 and 2 were brought to the earlier JAC.)

 

Here is a graphic with the different subsets of the ISO 639 identifiers, corresponding to the earlier Parts 1-3 and 5 of ISO 639, and with links to the still separate databases (which should eventually be unified into a single source file/database with different views on the respective sites). https://standards.iso.org/iso/639/ed-2/en/Access%20to%20the%20databases%20of%20the%20ISO%20639%20Language%20Code.pdf  This graphic can be accessed at https://www.iso.org/iso-639-language-code

 

(I know it is confusing, also for me, that there are two ISO pages for ISO 639, https://www.iso.org/iso-639-language-code and https://standards.iso.org/iso/639/ed-2/en/.  I have already proposed that there are at least links from one page to the other.)

 

I hope this answers most questions that members of this list may have.  Otherwise Janell (I am sure) and myself are certainly willing to answer more questions.

 

Best, Sebastian

 

 

 

From: Ietf-languages <ietf-languages-bounces@ietf.org> On Behalf Of Registrar ISO639-3
Sent: Thursday, 30 November, 2023 16:39
To: John Cowan <cowan@ccil.org>
Cc: drude@xs4all.nl; Hugh Paterson III <sil.linguist@gmail.com>; Doug Ewell <doug@ewellic.org>; IETF Languages Discussion <ietf-languages@iana.org>
Subject: Re: [Ietf-languages] Latin Sub tags

 

Dear John,

 

The previous ISO change request cycle for 639-3 has been replaced by the more frequent cycle of the ISO639 Maintenance Agency as of the publication of ISO639:2023 earlier this month.  Once the MA has considered and decided on requests, they will be published.  The newsletter that will publish the requests for comment and the decisions should start up in 2024 and be released on a quarterly basis. Since the 639 revision, the changes are still being implemented so I don't have a definite date.  This will replace the usual update that would have been released in January 2024 by the 639-3 RA under the previous 639-3 standard, 

 

Kind regards,

 

Janell Nordmoe

ISO639-3 Registrar

 

On Thu, Nov 30, 2023 at 12:16 PM John Cowan < <mailto:cowan@ccil.org> cowan@ccil.org> wrote:

(I apologize for my previous null reply.)

 

On Thu, Nov 30, 2023 at 12:43 PM < <mailto:drude@xs4all.nl> drude@xs4all.nl> wrote:

 

 

just this month, the setting for ISO 639 has changed.  The earlier independently managed parts are now understood to belong to ONE code, the identifiers of the elements of which may belong to different SETS which correspond to the earlier PARTS 1 to 5.

 

This is excellent news.  I see that the Wikipedia article has already been updated.

 

So from now on, any changes to ISO 639 are presumably better coordinated, as any new requests (most are expected to come in via the earlier registrar of Part 3) will be considered right away as concerning the code as a whole, and then the consequences for possible needs to update different subsets of the identifiers will be considered simultaneously.

 

This is not very clear.  Does it mean, for example, that the existing Ethnologue annual approval cycle will continue, and only then will the resulting code changes be propagated to the various sets of ISO 639?  Or is the intention to speed up the approval process altogether?  Please help us understand this.

 

If you (or anybody else here) need further clarification about this, I am willing to answer this off-list, in order not to spam this list with ISO questions.

 

Although there is not and cannot be a formal relationship between this list and any ISO organization. I believe the members of this list would agree that this discussion is on-topic and indeed highly relevant to this list and would not be classified as spam even in the widest sense of that term, which is why I am sending this post to the list.

_______________________________________________
Ietf-languages mailing list
 <mailto:Ietf-languages@ietf.org> Ietf-languages@ietf.org
 <https://www.ietf.org/mailman/listinfo/ietf-languages> https://www.ietf.org/mailman/listinfo/ietf-languages




 

-- 

Janell Nordmoe

ISO 639-3 RA

SIL International

7500 W. Camp Wisdom Rd.

Dallas, TX 75236

+1 972-708-7400 x2420