Re: [Ietf-languages] [EXTERNAL] Re: language identifiers for sign languages (incl. sgn) vs. attribute for indicating the representation of an individual language in "sign language modality"

Peter Constable <petercon@microsoft.com> Tue, 26 November 2019 23:35 UTC

Return-Path: <petercon@microsoft.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 734C012091A for <ietf-languages@ietfa.amsl.com>; Tue, 26 Nov 2019 15:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.797
X-Spam-Level:
X-Spam-Status: No, score=-1.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_FAIL=0.001, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001, URI_HEX=0.1] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T_17pc3rzv34 for <ietf-languages@ietfa.amsl.com>; Tue, 26 Nov 2019 15:35:01 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A25C12013B for <ietf-languages@ietf.org>; Tue, 26 Nov 2019 15:35:01 -0800 (PST)
Received: by mork.alvestrand.no (Postfix) id B87417C3971; Wed, 27 Nov 2019 00:34:59 +0100 (CET)
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 9BB837C38C1 for <ietf-languages@alvestrand.no>; Wed, 27 Nov 2019 00:34:59 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Authentication-Results: mork.alvestrand.no (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nCxrCGMT8u32 for <ietf-languages@alvestrand.no>; Wed, 27 Nov 2019 00:34:55 +0100 (CET)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
X-Comment: SPF skipped for whitelisted relay - client-ip=192.0.46.74; helo=pechora8.dc.icann.org; envelope-from=petercon@microsoft.com; receiver=ietf-languages@alvestrand.no
Received: from pechora8.dc.icann.org (pechora8.icann.org [192.0.46.74]) by mork.alvestrand.no (Postfix) with ESMTPS id 1B0287C080E for <ietf-languages@alvestrand.no>; Wed, 27 Nov 2019 00:34:54 +0100 (CET)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on071d.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe49::71d]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora8.dc.icann.org (Postfix) with ESMTPS id 637ACC0736 for <ietf-languages@iana.org>; Tue, 26 Nov 2019 23:34:53 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CQ6MZe+hTjR3LOWDNcu7DmYo/vDR2ER8CCoak1lXtDJPdR2B9ws+BfVRsDwU4XQMw2SV4+/bv15rDI4+xoBrs+zx6K0MoDEJ4DjG3Z3iAfcAyFzuDnBYCSt7DjQeiYKu+8vCt5ykEU6WK9n+nmG6sVInCk/rlDazkp6M+i84QMtzPMF2j6RDvKnzuM9bwLXDTtBXpvYMVaZdG6SK35/PyfNra2yuBSxC6KgppDyAbexImMWo+n2/BlChp4OvZxZqDT7QEPrNnyZHgLMWFZBKHo6lFUd7jZGxEtGwSJBdvpwDR/rY4O1/D4b8cfE/M63Kce6GbBc3KjZKvnNaoQgYqA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1WSqevo+0MWvC2ddMlDy5Ez1+iHYSPvvwdiIe3N2RsM=; b=IvyOjG9cdaHyUhzlsuLbnEy8/xpGspshrGMBLvlP+sL1xm67+jPy4MlmiZLwQXv8yZldbCez77M43YkZixlCvH+M8q2ttHjKyhRjqqr9KJ61h/g6tnCdpGFTd8DtTJZXx1cZdxtMPbVRlVB0UqkggJQ/YiAxC0obxwZCdzpPqX9R4ZiNDSKY0TiKLKjmRw8dtGBKjWXWOr4o0fO24croh9OYn0j9zsy/qKhPovq3BahoGQ+RdnQTpMdJjvozFv1UxHUVg//gsWO5XeUNGxLE7iYnznMXQBE54G/tTlktevg46san2FZlJLCaxZMhGvRLuhrxm86Z6THy4wlJxmnyXg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1WSqevo+0MWvC2ddMlDy5Ez1+iHYSPvvwdiIe3N2RsM=; b=G5NLCmsul9qX/wWPPLDMrcj/SR2n4JvRxkDSVl+1VmgpTSdGFyoycirHh9nzEz44pFDKbggQkYb4Jk3SgV9lXXrDjtLgZwsKUbtVIOgffdkjf4Sq2Xx9iDWaotEEsSG2YWFZo4DLieCwhN23L3//g7vOAqzOAXY7u8v3JAHvd/c=
Received: from MW2PR2101MB1065.namprd21.prod.outlook.com (52.132.149.18) by MW2PR2101MB1018.namprd21.prod.outlook.com (52.132.146.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.2; Tue, 26 Nov 2019 23:34:32 +0000
Received: from MW2PR2101MB1065.namprd21.prod.outlook.com ([fe80::1d78:3c60:621c:7fe8]) by MW2PR2101MB1065.namprd21.prod.outlook.com ([fe80::1d78:3c60:621c:7fe8%7]) with mapi id 15.20.2516.003; Tue, 26 Nov 2019 23:34:32 +0000
From: Peter Constable <petercon@microsoft.com>
To: Shawn Steele <Shawn.Steele=40microsoft.com@dmarc.ietf.org>, ietf-languages <ietf-languages@iana.org>
Thread-Topic: [Ietf-languages] [EXTERNAL] Re: language identifiers for sign languages (incl. sgn) vs. attribute for indicating the representation of an individual language in "sign language modality"
Thread-Index: AQHVo6jjJMCGkRpKoku3aX5ETivPX6ecK8iAgAHWirCAABovgA==
Date: Tue, 26 Nov 2019 23:34:32 +0000
Message-ID: <MW2PR2101MB10655D098DDA1B423F01D9FCD5450@MW2PR2101MB1065.namprd21.prod.outlook.com>
References: <20191125085545.665a7a7059d7ee80bb4d670165c8327d.06623292b8.wbe@email03.godaddy.com> <SN6PR2101MB09890A0EBCA22C54D2728F6C824A0@SN6PR2101MB0989.namprd21.prod.outlook.com> <MW2PR2101MB1065B58727E08203C2F823F6D5450@MW2PR2101MB1065.namprd21.prod.outlook.com>
In-Reply-To: <MW2PR2101MB1065B58727E08203C2F823F6D5450@MW2PR2101MB1065.namprd21.prod.outlook.com>
Accept-Language: en-US, en-CA
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=shawnste@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-11-25T17:55:40.7413861Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=6650ce36-ff12-4981-aeea-1eaa81e6eebc; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic
authentication-results: spf=none (sender IP is ) smtp.mailfrom=petercon@microsoft.com;
x-originating-ip: [2001:4898:80e8:3:8143:99d7:33bf:19b4]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 71eff276-02e2-4ed5-dd5a-08d772c93069
x-ms-traffictypediagnostic: MW2PR2101MB1018:
x-microsoft-antispam-prvs: <MW2PR2101MB1018FDA41D0B2C5936A1BEF2D5450@MW2PR2101MB1018.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0233768B38
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(39860400002)(396003)(136003)(346002)(13464003)(51444003)(189003)(199004)(2940100002)(6436002)(86362001)(14454004)(606006)(74316002)(186003)(99286004)(110136005)(25786009)(22452003)(446003)(316002)(2906002)(6116002)(790700001)(6506007)(53546011)(64756008)(8990500004)(76116006)(7696005)(102836004)(9686003)(10090500001)(229853002)(55016002)(7736002)(8676002)(236005)(66946007)(5660300002)(76176011)(14444005)(81166006)(66476007)(66574012)(81156014)(256004)(66556008)(66446008)(54896002)(966005)(11346002)(10290500003)(46003)(6246003)(71190400001)(478600001)(71200400001)(52536014)(6306002)(33656002)(8936002); DIR:OUT; SFP:1102; SCL:1; SRVR:MW2PR2101MB1018; H:MW2PR2101MB1065.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: AvF6Voptd0QHnzuFGm+lnyD+d8wEEeLPWcNn3pAR8vvDbq3Ierba1zNNzxWB+wRdftuVji+rYaWYywaTq5UWGnnLIbCjCnLE3c0LftQIWbt2l3GZhrU/ZITVYiIBLyHiqtxOzCiDon5Zzf9CxEV13C6jaIhs+dq917JMC668LekymN80V6GXnnKsVticuiKc7UVZ21tgCQVyikgYDi4VzK1fTxJsBxZ7cYdeKaxkHh/X/Az0zNObiGnFOcDgMWYpqq3JmHcZ4889hF6B1v2cHm7ThO96niBb8FEa/TLpfpWfiXeDQgjGNViiWMagY5l9/R1QtajqCis6Ik3lv32r9qSyQCzPVL6euweX15REHDWpsTFFwd6wra2zlSyWEqKWkM9UzyJ2DfXV5DnOuZmZDWFLi9irFLaJFPyUK3pywYddp9ufmpYBYJ6yIwry84LZPtFyLPj8+w1mwJ5PQ7lgHcY06nM/7FHTPBbDKATWMPQ=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW2PR2101MB10655D098DDA1B423F01D9FCD5450MW2PR2101MB1065_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 71eff276-02e2-4ed5-dd5a-08d772c93069
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Nov 2019 23:34:32.0932 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: KgfIn+tJ2gjj6em0zdrzUFSEDrfkZKCoRxFeZLwpNgnd82L1xkK8YogPFVeLiZ19pKIasOWWHV8fOiuoGahi3w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2PR2101MB1018
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/Sr3LWPAxQ_2DW01ShfchVUz6ybE>
Subject: Re: [Ietf-languages] [EXTERNAL] Re: language identifiers for sign languages (incl. sgn) vs. attribute for indicating the representation of an individual language in "sign language modality"
X-BeenThere: ietf-languages@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Tue, 26 Nov 2019 23:35:05 -0000

Re-sending with trimmed to/cc (to avoid being blocked by list)


From: Peter Constable
Sent: Tuesday, November 26, 2019 2:08 PM
To: Shawn Steele <Shawn.Steele=40microsoft.com@dmarc.ietf.org>rg>; Doug Ewell <doug@ewellic.org>rg>; Pyatt, Elizabeth J <ejp10@psu.edu>du>; Mark Davis ☕️ <mark@macchiato.com>
Cc: John Cowan <cowan@ccil.org>rg>; Fourney, David <david.fourney@usask.ca>ca>; Sebastian Drude <Sebastian.Drude@outlook.com>om>; Christian Galinski <christian.galinski@chello.at>at>; ietf-languages <ietf-languages@iana.org>rg>; Melinda_Lyons@sil.org
Subject: RE: [Ietf-languages] [EXTERNAL] Re: language identifiers for sign languages (incl. sgn) vs. attribute for indicating the representation of an individual language in "sign language modality"

If “signed” were registered as a subtag, it should be explicitly defined to denote a signed modality for an oral language, and should not be used in combination with a primary language tag for a signed language. Of course, the registry doesn’t identify what are signed languages, so that constraint couldn’t be validated.

But “signed” would inherently be limited in its utility—which I think is John’s point. As an rough analogy, it would be a bit like tagging content to indicate that the speaker/author has a language impediment, but without any indication as to the nature of that impediment. So, maybe they can’t pronounce interdental fricatives or maybe they haven’t learned a dual/plural distinction in inflections or any other number of possibilities. Would that really be useful? It might be, but I gather John thinks not, and it certainly wouldn’t satisfy requirements in all scenarios.


Peter

From: Shawn Steele <Shawn.Steele=40microsoft.com@dmarc.ietf.org<mailto:Shawn.Steele=40microsoft.com@dmarc.ietf.org>>
Sent: Monday, November 25, 2019 9:56 AM
To: Doug Ewell <doug@ewellic.org<mailto:doug@ewellic.org>>; Pyatt, Elizabeth J <ejp10@psu.edu<mailto:ejp10@psu.edu>>; Mark Davis ☕️ <mark@macchiato.com<mailto:mark@macchiato.com>>
Cc: John Cowan <cowan@ccil.org<mailto:cowan@ccil.org>>; Peter Constable <petercon@microsoft.com<mailto:petercon@microsoft.com>>; Fourney, David <david.fourney@usask.ca<mailto:david.fourney@usask.ca>>; Sebastian Drude <Sebastian.Drude@outlook.com<mailto:Sebastian.Drude@outlook.com>>; Christian Galinski <christian.galinski@chello.at<mailto:christian.galinski@chello.at>>; ietf-languages <ietf-languages@iana.org<mailto:ietf-languages@iana.org>>; Melinda_Lyons@sil.org<mailto:Melinda_Lyons@sil.org>
Subject: RE: [Ietf-languages] [EXTERNAL] Re: language identifiers for sign languages (incl. sgn) vs. attribute for indicating the representation of an individual language in "sign language modality"

If I understood correctly, the original question was about a way to tag signed variants for spoken English vs the language codes for the signed languages.

It would seem to me that “en-signed” and “ase” solve those reasonably well.  So I think that adding a “signed” subtag would be a reasonable solution to the problem.  I’m not sure how you’d avoid having naïve users choose “en-signed” for ASL though.

The discussion also asked about regional variations, however I’d like to point out that we don’t do well with those for spoken languages either.  (Just watched an “English” movie with my reasonably fluent Chinese exchange student and I’d be surprised if he understood half of it… heck, I had trouble with parts!  And I remember arriving in Stuttgart, hearing the airport paging system and thinking “I haven’t been in Germany for a couple years, but surely my German isn’t that bad!” – and then learning about Swabian…)  Probably a mechanism would work as well for those would also work for dialects of signed languages.

-Shawn

From: Ietf-languages <ietf-languages-bounces@ietf.org<mailto:ietf-languages-bounces@ietf.org>> On Behalf Of Doug Ewell
Sent: Monday, November 25, 2019 7:56 AM
To: Pyatt, Elizabeth J <ejp10@psu.edu<mailto:ejp10@psu.edu>>; Mark Davis ☕️ <mark@macchiato.com<mailto:mark@macchiato.com>>
Cc: John Cowan <cowan@ccil.org<mailto:cowan@ccil.org>>; Peter Constable <petercon=40microsoft.com@dmarc.ietf.org<mailto:petercon=40microsoft.com@dmarc.ietf.org>>; Fourney, David <david.fourney@usask.ca<mailto:david.fourney@usask.ca>>; Sebastian Drude <Sebastian.Drude@outlook.com<mailto:Sebastian.Drude@outlook.com>>; Christian Galinski <christian.galinski@chello.at<mailto:christian.galinski@chello.at>>; ietf-languages <ietf-languages@iana.org<mailto:ietf-languages@iana.org>>; Melinda_Lyons@sil.org<mailto:Melinda_Lyons@sil.org>
Subject: Re: [Ietf-languages] [EXTERNAL] Re: language identifiers for sign languages (incl. sgn) vs. attribute for indicating the representation of an individual language in "sign language modality"

Elizabeth is correct that a BCP 47 tag like "it-signed" would be appropriate for a true signed version of Italian, but not for Italian Sign Language, which is a different language and would be tagged "ise".

Similarly, signed spoken English (any variety) is not the same as American Sign Language. The former could be "en-signed"; the latter is "ase".

ISO 639-3 has code elements for more than 140 sign languages, in addition to the generic [sgn], plus a well-defined mechanism to add more as needed. They are not the issue here. The issue is how to tag signed forms of non-sign languages, such as Signing Exact English.

As a side note, I wish Bickford had not included the following in the article Elizabeth cited:

> ISO 639-3 announces to the world that your language exists and that
> it is different from all other languages. This can give it more
> prestige and respect.

because there are already too many people who request an ISO 639 code element for a language because they think it will give it prestige and respect. (This is usually a problem with new constructed languages, not with established sign languages. But still.)

--
Doug Ewell | Thornton, CO, US | ewellic.org<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fewellic.org&data=02%7C01%7Cpetercon%40microsoft.com%7Ca297710b4d3e41d09f7f08d771d0b844%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637103013822669086&sdata=QHbtdpJAbDitNEilaayLLmetWim6vi84aEEunDC8vxw%3D&reserved=0>

-------- Original Message --------
Subject: Re: [Ietf-languages] [EXTERNAL] Re: language identifiers for
sign languages (incl. sgn) vs. attribute for indicating the
representation of an individual language in "sign language modality"
From: "Pyatt, Elizabeth J" <ejp10@psu.edu<mailto:ejp10@psu.edu>>
Date: Mon, November 25, 2019 7:18 am
To: Mark Davis ☕️ <mark@macchiato.com<mailto:mark@macchiato.com>>
Cc: <many>

In terms of identifying sign languages, it's important to note that languages such as ASL (American Sign Language) are not variants of a spoken language, but can be independent grammatical systems.

Finger spelling in ASL can provide a phonetic translation of specific spoken words, but the primary signs have nothing to do with English phonology or grammar. In fact, ASL was an adaptation of French Sign Language (FSL) and as such has object pronouns. It

https://www.accreditedlanguage.com/interpreting/types-of-sign-language-and-their-development/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.accreditedlanguage.com%2Finterpreting%2Ftypes-of-sign-language-and-their-development%2F&data=02%7C01%7Cpetercon%40microsoft.com%7Ca297710b4d3e41d09f7f08d771d0b844%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637103013822679086&sdata=Wi6cLDFGsNmIQTJw%2BJ%2Fi3SlbfbhLN%2Fjy3e1SeFlBtr8%3D&reserved=0>

ASL also has second person plural pronouns and apparently does not always distinguish gender in the third person.
https://www.lifeprint.com/asl101/pages-layout/possession.htm<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.lifeprint.com%2Fasl101%2Fpages-layout%2Fpossession.htm&data=02%7C01%7Cpetercon%40microsoft.com%7Ca297710b4d3e41d09f7f08d771d0b844%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637103013822679086&sdata=pL1rRjd3B0EdKAW76w3HYqYNpigFrd7N18AJzhklxNk%3D&reserved=0>

Tagging ASL as a variant of English would be incorrect. Tagging ASL as a sign language associated with the U.S.(i.e. sgn-us) might be more accurate. But having appropriate identification tags for the languages would be better, because there are dialects and "accents" in different sign languages.

FYI - SIL does have a mechanism to register specific regional sign languages.
https://www.sil.org/system/files/reapdata/49/93/30/4993307252502011969228542832463330862/ISO_639_3_for_Deaf_Communities__English_.pdf<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.sil.org%2Fsystem%2Ffiles%2Freapdata%2F49%2F93%2F30%2F4993307252502011969228542832463330862%2FISO_639_3_for_Deaf_Communities__English_.pdf&data=02%7C01%7Cpetercon%40microsoft.com%7Ca297710b4d3e41d09f7f08d771d0b844%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637103013822689084&sdata=0PHUNeiAqe5G1HBfRcKGZbcTPGOAZHl39m8m8LEe1VQ%3D&reserved=0>

Hope this is useful.

Elizabeth