Re: [Ietf-languages] Fwd: RE: can I share the drafts of ISO 21636

Peter Constable <pgcon6@msn.com> Tue, 08 December 2020 20:33 UTC

Return-Path: <pgcon6@msn.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 CF4C83A0803 for <ietf-languages@ietfa.amsl.com>; Tue, 8 Dec 2020 12:33:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=msn.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 31O_vL1G6ToM for <ietf-languages@ietfa.amsl.com>; Tue, 8 Dec 2020 12:33:06 -0800 (PST)
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12olkn2040.outbound.protection.outlook.com [40.92.21.40]) (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 228853A07F9 for <ietf-languages@ietf.org>; Tue, 8 Dec 2020 12:33:05 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oNhTosjcqUgoh3Qy/R516O4VHGUaU9XuqiyRxFTuQPKQ4IhamfYKAnGPsgor7LEsy4JswopSVqvO2YkJ3B9sLyZ4cwQqhCliAkCkuCVaZ+1WEwfO9z5eVQo+Zl3YgeJDQRa1EhbvjnavrGdlcgu+2zJvXkOF959jtaXR9Ws3gfJnpXUV2cH/wKNR8xmWkCcBFSM+3PNEYzoDNg0E9SrrUR8CoQWFF2l2b00t+z/ZU2LDetPXYvl4w2/veQXEaHE2/H8b42A9ObPUig0HBOL6AlH1TZi4jAfH3WKDc5Hsw8L5DBsU8dosItyzhKetNSUH8ems5OYT3o9zBbLiecV5Ww==
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=DDz6SOpgweARSJt4klFR58noPhMt22l98dNNz3lTAsI=; b=S8OWy6HNgtZCXki52VWF6pTEsvJn4HoMfQ30YUJTImsau4LWoQCnKopTNxwsvqP15NeZziJKwfW40TwXqZnAVyQE59bhu7V51t/hHtj00mbOeR8C/kbd8Tbi5XQ8IGTqtj17lfLL66kVKsP/QzKU2jeVCEEp9QD0DvBvSAaVcrCcJp8RVGUjr1dz3FiqOj9zY4dBHpOs7FoI/SZ8hgM7A8TIMVVfsGUh+S2+2GpAM7mrfi8UyPKQxHTh1Pe3CrvEbMeZfy4nkUaCO6wwo9MYGREkZxkNctCQRupYCYihdkr52FSLkrkde8Rq8L+kZYgQ36xgHu4+B3QhPfulkgXzaw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=msn.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DDz6SOpgweARSJt4klFR58noPhMt22l98dNNz3lTAsI=; b=qJxZXrR3i7F5c5zHOgqNwVnYlq3N0CcUQFXALZ78CzbOsmQdkqu/KAtHFXV/dJeX1olxTQGIvzHU8PYF2HSi4qJKNx9AC2DTvFFTeZCV8ON6RyOVwfsGXFQ9EozYCrTX3UZMYvyvytOlGorhpGxMGQGo8W41f3u6KJ/GB1TX3JxtqNuxpP/oDxB27U9kqXp8AMFSJB2SWtDieGneusnidrY8aaPDNSgLbY+gzTiNzNL0kB2P3S3Ix2Pe35/WA7L8uOT7I3jg/Rc9o//GgzLw0Epdp0utdHhYH/l6XHr1oEW8tpkXLzLoqBpXT/apnWe9vnZanOy13ALbjqIBuU1cRg==
Received: from MWHPR1301MB2112.namprd13.prod.outlook.com (2603:10b6:301:36::19) by MWHPR1301MB1966.namprd13.prod.outlook.com (2603:10b6:301:30::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3654.12; Tue, 8 Dec 2020 20:33:04 +0000
Received: from MWHPR1301MB2112.namprd13.prod.outlook.com ([fe80::4090:296d:a595:b968]) by MWHPR1301MB2112.namprd13.prod.outlook.com ([fe80::4090:296d:a595:b968%2]) with mapi id 15.20.3632.016; Tue, 8 Dec 2020 20:33:04 +0000
From: Peter Constable <pgcon6@msn.com>
To: Sebastian Drude <drude@xs4all.nl>, Doug Ewell <doug@ewellic.org>, "ietf-languages@ietf.org" <ietf-languages@ietf.org>
Thread-Topic: [Ietf-languages] Fwd: RE: can I share the drafts of ISO 21636
Thread-Index: AQHWxRKkND4gkHqntE6CtCxruFwDOKnglxCAgAAZYACAAInbAIAAN1OAgArb9wCAAAw3MIABT7KAgAALgVA=
Date: Tue, 08 Dec 2020 20:33:04 +0000
Message-ID: <MWHPR1301MB2112DC5EC7AD9817803D8F3D86CD0@MWHPR1301MB2112.namprd13.prod.outlook.com>
References: <VI1PR0502MB3757E8E4D7D531F12F42E2CECEF50@VI1PR0502MB3757.eurprd05.prod.outlook.com> <0f502d82-9518-70df-3451-a3513d30f65c@xs4all.nl> <000601d6c762$39955a20$acc00e60$@ewellic.org> <c8ffc281-b0b3-e10f-b127-ff9dc48aa7f7@xs4all.nl> <000501d6cceb$dfa2af10$9ee80d30$@ewellic.org> <MWHPR1301MB2112248CF990ED53E333EC4B86CE0@MWHPR1301MB2112.namprd13.prod.outlook.com> <2651c4c7-cbd2-736c-6fdb-350163d7cc50@xs4all.nl>
In-Reply-To: <2651c4c7-cbd2-736c-6fdb-350163d7cc50@xs4all.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tmn: [hPWgLNXXAOI4wOZzX73KYRP6QHwYWAMy]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 40f12003-2432-43c3-eafd-08d89bb876f0
x-ms-traffictypediagnostic: MWHPR1301MB1966:
x-ms-exchange-minimumurldomainage: iso.org#9130
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6AaF7RBskCxHw4b2S85LTL1fOFvEJc1fPXtFPSrHccEfv7ioiHTnNM2x2OF47wAIpR2oHWNZ/6GSOlyuf2r8PwDYxkWsLRi3rzzucYw8Mu/39u9eLY/zhG7kJb6n18tEGkP0ojFUPhVih3NHbm8VLWNGoL9neB31/wRWHkPDMLA2BRx1Q5aCqYgzT9KK6Yv16oHYQY3flWXXN5o2LtQZICQIHIzPwTPoEVYX3anmnBbg335AEHyLo7p8NyigtrPr
x-ms-exchange-antispam-messagedata: QjjGSyo7TM0yDPQ/JowBqv7+b2st8btl8vNJnw4wRw1CACgJMwZJ46VQUzUQIC0WsgkYButkM+4vR6UPH7B+SYi2/zf1d0eTR9zWn7PzO0icRCq/x5LYkVghaZcId7XImbpIOlbDyEdpmatqzdAiwg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: sct-15-20-3174-8-msonline-outlook-32ef5.templateTenant
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MWHPR1301MB2112.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 40f12003-2432-43c3-eafd-08d89bb876f0
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Dec 2020 20:33:04.4043 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR1301MB1966
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/hyyOmNtvsHnY6HlBYXrYWc_rF6o>
Subject: Re: [Ietf-languages] Fwd: RE: can I share the drafts of ISO 21636
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, 08 Dec 2020 20:33:08 -0000

Because the parts of 639 have publicly accessible code lists, it means the most interesting content for those standards is publicly available. For ISO TR 21636, it will by default be behind a paywall: people will need to shell out $. You might want to think of possible strategies to work around that.

For standards developed within ISO/IEC JTC1, there is an option of making an approved standard or TR publicly accessible at no cost:

https://standards.iso.org/ittf/PubliclyAvailableStandards/

I don't know if there's any such option for standards or TRs developed in any other ISO TC, but you could inquire.

I don't know if there might be a way for a TR to establish a registry. (As a TR, it would be strictly informative, and an informative registry might be seen as unusual.) If so, that might be a way to make 21636 more like the parts of 639, providing a way for an RA to publish the relevant details of 21636 (since a registry needs to provide some documentation so the registry makes sense).


Peter

-----Original Message-----
From: Sebastian Drude <drude@xs4all.nl> 
Sent: Tuesday, December 8, 2020 11:39 AM
To: Peter Constable <pgcon6@msn.com>; Doug Ewell <doug@ewellic.org>; ietf-languages@ietf.org
Subject: Re: [Ietf-languages] Fwd: RE: can I share the drafts of ISO 21636

That may be a good interim solution, Peter, thanks,

but I still believe that there must be more sustainable ways.

Best, Sebastian

-- 

Museu P.E. Goeldi, CCH, Linguistica ▪ Av. Perimetral, 1901 Terra Firme, CEP: 66077-530 ▪ Belém do Pará – PA ▪ Brazil drude@xs4all.nl ▪ +55 (91) 3217 6024 ▪ +55 (91) 983733319
Priv: Tv. Juvenal Cordeiro, 184, Apt 104 ▪ 66070-300 Belém

On 07/12/2020 20:40, Peter Constable wrote:
> Perhaps as Unicode liaison to TC37/SC2, I should post the draft to the UTC doc register for consideration of Unicode members...
>
> -----Original Message-----
> From: Ietf-languages <ietf-languages-bounces@ietf.org> On Behalf Of 
> Doug Ewell
> Sent: Monday, December 7, 2020 2:54 PM
> To: 'Sebastian Drude' <drude@xs4all.nl>; ietf-languages@ietf.org
> Subject: Re: [Ietf-languages] Fwd: RE: can I share the drafts of ISO 
> 21636
>
> Sebastian Drude wrote:
>
>>> I don’t think it would be helpful to establish a liaison with IETF 
>>> proper, that is to say, Area Directors and above. They have little 
>>> to no idea what this group does.
>>>
>>> Michael and I are IETF Designated Experts for BCP 47. I wonder if 
>>> SC2 would consider that.
>> That is a good question, Michael,
> Doug :)
>
>> although I am not sure what exactly 'consider' means, in this context.
>> What would be the goal, that you as individual experts enter into a 
>> special realtionship with ISO TC37/SC2?
> That's kind of what I meant, I guess. Perhaps other experts from this list could participate as well. The list at large is not really a committee with a fixed membership that could itself constitute a liaison group. And again, IETF leadership would not have any idea where to begin with this project.
>
>> I did not conclude my first experience with getting an institution
>> (CLARIN) to be a ISO liaison, so I really do not have much expertise 
>> here how to proceed.  I will consult with colleagues within ISO.
> That would be helpful. The proposal has a stated goal of being interoperable with BCP 47, but BCP 47 experts are not allowed to view it or provide constructive feedback that could facilitate that interoperability. That doesn't feel much like a plan for success.
>
> --
> Doug Ewell, CC, ALB | Thornton, CO, US | ewellic.org
>
>
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages@ietf.org
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.i
> etf.org%2Fmailman%2Flistinfo%2Fietf-languages&amp;data=04%7C01%7C%7C70
> 326205b839450045f808d89bb0f8d4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%
> 7C0%7C637430531682665598%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL
> CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Xscnww%
> 2FeY7um1wBUkP3hu%2FZLXK2kDOzvQRnvt55K1d4%3D&amp;reserved=0
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages@ietf.org
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.i
> etf.org%2Fmailman%2Flistinfo%2Fietf-languages&amp;data=04%7C01%7C%7C70
> 326205b839450045f808d89bb0f8d4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%
> 7C0%7C637430531682665598%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL
> CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=Xscnww%
> 2FeY7um1wBUkP3hu%2FZLXK2kDOzvQRnvt55K1d4%3D&amp;reserved=0