Re: [Ietf-languages] Latin Sub tags

Hugh Paterson III <sil.linguist@gmail.com> Fri, 01 December 2023 22:04 UTC

Return-Path: <sil.linguist@gmail.com>
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 71B5EC14F5EE for <ietf-languages@ietfa.amsl.com>; Fri, 1 Dec 2023 14:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.439
X-Spam-Level:
X-Spam-Status: No, score=-6.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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=pass (2048-bit key) header.d=gmail.com
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 FsTyn4NIb6-K for <ietf-languages@ietfa.amsl.com>; Fri, 1 Dec 2023 14:04:04 -0800 (PST)
Received: from out.mail.icann.org (out.mail.icann.org [64.78.33.6]) (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 EB3EDC14F601 for <ietf-languages@ietf.org>; Fri, 1 Dec 2023 14:03:54 -0800 (PST)
Received: from MBX112-E2-CO-1.pexch112.icann.org (10.226.41.200) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) 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 14:03: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 14:03:53 -0800
Received: from aesc112-co-1-2.serverpod.net (aesc112-co-1-2.serverpod.net [10.224.76.91]) (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 E94E940003 for <ietf-languages@ex.icann.org>; Fri, 1 Dec 2023 14:03:53 -0800 (PST)
Received: from exmx112-co-1-2.serverpod.net (exmx112-co-1-2.serverpod.net [10.224.72.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 aesmt112-co-1.serverpod.net (Postfix) with ESMTPS id C55FE120002 for <ietf-languages@ex.icann.org>; Fri, 1 Dec 2023 14:03:53 -0800 (PST)
Received: from pechora5.dc.icann.org (pechora5.icann.org [192.0.46.71]) (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 902DB140002 for <ietf-languages@ex.icann.org>; Fri, 1 Dec 2023 14:03:53 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pechora5.dc.icann.org (Postfix) with ESMTPS id 56D817000343 for <ietf-languages@iana.org>; Fri, 1 Dec 2023 22:03:52 +0000 (UTC)
Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-54c77e0835bso296754a12.2 for <ietf-languages@iana.org>; Fri, 01 Dec 2023 14:03:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701468211; x=1702073011; darn=iana.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7ueLZNiVNreVJ/uG8GLfF9p/QzFoZD0z0hxmr4nbLFE=; b=mKYlTlbjHG51NPze0hfWWbaGqNRU5uveX4BgXtryGcg87TpWPGvHX7iNS82uy/Om4g q08ar9q+J07JqkgRvQ1iw4u7BMMjX7r0PwDAno43s861wokFIl8/XlH1mljYZ9s6sn+z Q+oaPt2Fa62YiqZu9gS/UpjfNOrxDj6E2O3oBenlGNBbZboydeNwFLhGreq9jAz35Kb1 P/MXYz0nvgA075VMolfxEiGk8CNaTM2GIBOa0YR5cNvZesdhGqF7dEh1uYwCyaHB6s8a dCp4q8IzHk3/jxFbPLynzQAmJAFVM932CSRvIotipplGD9v+HWJl84kCXUlaCmCRsuUa JfAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701468211; x=1702073011; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7ueLZNiVNreVJ/uG8GLfF9p/QzFoZD0z0hxmr4nbLFE=; b=exQpxb90v4buvtG0KLhj7ykQG8cGObvHZng3k02K2FpZDaTwtM84Ih9LElBZdrcPh3 tftzkgc4P3H5XI6yuTpro/qkC8ECrnBwMaBJjHd06uxVMCg8Jh6sOgfcBtNyMQ3g+CLi 3d0tYbe5a2MWebyR7qF1kOa4SvvetPOVTjg4C+PZw7k2CLB0z2R056ONljC+6ZnhTwfk oCK4DpVQjWFfd01xnbIXHW4gKERl6bzNiI996EhTQSPHkmFZXzpQj1G3MM3NzblqnTEw 58y+1YnnxvYikg3AYOBh8Dj4yb27fc+n4w3KxxrJMaNvZgbY74beIKpdw8DCeLxSP7mR iozA==
X-Gm-Message-State: AOJu0YwCoaB8ZRdFM5Pg6osazKZSrl88JvwUaYCLrjhCEcmgxLSqXgKK KUuIgXrFDHsSqSVd8mKWVKhb4NwR/2Ht6POdOQc=
X-Google-Smtp-Source: AGHT+IEyipVdqS0SA69ysq+zIK8m6PPpYCy8tomaVpPbekifRe/uwCz8lJDeW+9hTHO6QTdPc9hB+okrktCauZs51zI=
X-Received: by 2002:a50:d612:0:b0:545:4bf3:ac89 with SMTP id x18-20020a50d612000000b005454bf3ac89mr1423175edi.23.1701468210675; Fri, 01 Dec 2023 14:03:30 -0800 (PST)
MIME-Version: 1.0
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> <SJ0PR03MB6598D48CD059645543661CA4CA81A@SJ0PR03MB6598.namprd03.prod.outlook.com> <018b01da2497$5094ed90$f1bec8b0$@xs4all.nl> <SJ0PR03MB65988A4F7614E585DF2BA6CBCA81A@SJ0PR03MB6598.namprd03.prod.outlook.com>
In-Reply-To: <SJ0PR03MB65988A4F7614E585DF2BA6CBCA81A@SJ0PR03MB6598.namprd03.prod.outlook.com>
From: Hugh Paterson III <sil.linguist@gmail.com>
Date: Fri, 01 Dec 2023 14:03:18 -0800
Message-ID: <CAE=3Ky-jSJPg4pdKFbeabzHjOHzppasFV88J_v22RxKhATzxHA@mail.gmail.com>
To: Doug Ewell <doug@ewellic.org>
Cc: "drude@xs4all.nl" <drude@xs4all.nl>, IETF Languages Discussion <ietf-languages@iana.org>
Content-Type: multipart/alternative; boundary="0000000000004b4571060b79f0a5"
X-CMAE-Score: 0
X-CMAE-Analysis: v=2.4 cv=a9IjSGeF c=1 sm=1 tr=0 ts=656a5849 a=SRSNG2tq5TuPtBd2c0+Vew==:117 a=SRSNG2tq5TuPtBd2c0+Vew==:17 a=xqWC_Br6kY4A:10 a=e2cXIFwxEfEA:10 a=x7bEGLp0ZPQA:10 a=7MiK3HiER0sA:10 a=06aqjJ_2AAAA:8 a=nORFd0-XAAAA:8 a=xOd6jRPJAAAA:8 a=wEidUXOn-CtzxHsciG4A:9 a=QEXdDO2ut3YA:10 a=swG2Z8moZMEOODKuyBIA:9 a=lLNG8fgnTm62FyGo:21 a=lqcHg5cX4UMA:10 a=AYkXoqVYie-NGRFAsbO8:22 a=vexicnJHVZC5-rvN4z9Y:22
X-SOURCE-IP: 192.0.46.71
X-SPF-STATUS: soft_fail
X-SPF-FROM-STATUS: not_checked
X-RDNS-STATUS: pass
X-HELO-STRING: pechora5.dc.icann.org
Spam-Stopper-Id: 9e00f1d6-35d7-41f3-bbfe-93348008fa69
Spam-Stopper-v2: Yes
X-Envelope-Mail-From: sil.linguist@gmail.com
X-Spam-Reasons: None
X-AES-Analytics-Data: eyJ0aW1lc3RhbXAiOiAiMjAyMy0xMi0wMVQyMjowMzo1My44NzNaIiwgIm1lc3NhZ2VUcmFja2luZyI6IHsiaGFuZGxpbmciOiBbIlRISVJEIFBBUlRZIEJZUEFTUyJdLCAidW5pZmllZENhdGVnb3J5IjogIlVOQ0FURUdPUklTRUQifSwgImVuZ2luZXMiOiB7fX0=
X-Spam-Category: None
X-AES-Category: LEGIT
X-Auto-Response-Suppress: DR, OOF, AutoReply
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/V-VO6XpMpPERMAVSvxGgf-ky57Y>
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 22:04:09 -0000

As a matter of practicality, it would be helpful for my processes if the
format of the data files would remain tab delimited or CSV. Sebastian
mentions a "database format". I can imagine that as an SQL dump or JSON
file, which are valid and in some cases useful formats. However, as a
current data consumer of these standards I do prefer the tab and CSV
formats that have existed for some time. It would be useful if there was a
single URI to download from. My classic example has been wordpress.
https://wordpress.org/latest if one follows the included link, "latest"
will allow curl or wget type resources to always get the latest "version"
of wordpress. This URL strategy is really helpful in automation contexts
where content is fetched. Note that even though wordpress is versioned with
a semantic versioning system for releases, "latest" in the URL is a generic
pointer to the latest version.

I am curious how the MA will approach the matter of data versioning. This
is something that some of my colleagues and I have often desired from
downloaded data (from various sources) in the BCP-47 space. Versions allow
us to quickly look at the state of our systems and determine if we need to
update data.

- Hugh

On Fri, Dec 1, 2023 at 1:04 PM Doug Ewell <doug@ewellic.org> wrote:

> drude@xs4all.nl wrote:
>
> > I am sorry to read this; I was under the impression that core members
> > of this list were aware of the revision of ISO 639 and the setting up
> > of a Maintenance Agency; this process has been ongoing for many
> > years...
>
> I had heard in very broad, general terms that administration of the parts
> of 639 was to be consolidated, at some point in the future.
>
> I had not heard any details about how the process of updating the code
> lists will change, how frequently the changes will occur, how they will be
> announced, whether and how the format of official data files will change,
> etc.
>
> None of this is meant to suggest that these changes are a bad thing. I
> think they will greatly reduce the confusion people have about ISO 639.
>
> > I am not so sure about that the new setting for ISO 639  really means
> > profound changes for BCP 47.  There will still be a new version of the
> > ISO 639 database (file) in regular points in time (I believe this will
> > certainly not become a continuous process, but rather be bundled to
> > one to a few times per year) which will have to formally be adopted by
> > the BCP 47 registry.
>
> Please do keep this list informed as details become available.
>
> --
> Doug Ewell, CC, ALB | Lakewood, CO, US | ewellic.org
>
>