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

Sebastian Drude <drude@xs4all.nl> Thu, 10 December 2020 01:07 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 5326C3A09E9 for <ietf-languages@ietfa.amsl.com>; Wed, 9 Dec 2020 17:07:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.433
X-Spam-Level:
X-Spam-Status: No, score=-1.433 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=xs4all.nl
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 jhGsebwwYzST for <ietf-languages@ietfa.amsl.com>; Wed, 9 Dec 2020 17:07:36 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ABDF3A0317 for <ietf-languages@ietf.org>; Wed, 9 Dec 2020 17:07:36 -0800 (PST)
Received: by mork.alvestrand.no (Postfix) id AF6CA7C5CB5; Thu, 10 Dec 2020 02:07:34 +0100 (CET)
Delivered-To: ietf-languages@alvestrand.no
X-Comment: SPF skipped for whitelisted relay - client-ip=2620:0:2830:201::1:73; helo=pechora3.dc.icann.org; envelope-from=drude@xs4all.nl; receiver=ietf-languages@alvestrand.no
Received: from pechora3.dc.icann.org (pechora3.icann.org [IPv6:2620:0:2830:201::1:73]) by mork.alvestrand.no (Postfix) with ESMTPS id 6B3177C52E9 for <ietf-languages@alvestrand.no>; Thu, 10 Dec 2020 02:07:34 +0100 (CET)
Received: from lb1-smtp-cloud9.xs4all.net (lb1-smtp-cloud9.xs4all.net [194.109.24.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by pechora3.dc.icann.org (Postfix) with ESMTPS id 5597A7000A5D for <ietf-languages@iana.org>; Thu, 10 Dec 2020 01:07:32 +0000 (UTC)
Received: from cust-d2ef4cbd ([IPv6:fc0c:c138:75cc:34bc:4631:c48c:494:61cb]) by smtp-cloud9.xs4all.net with ESMTPA id nAQBkVoXAarN7nAQGk71t0; Thu, 10 Dec 2020 02:07:10 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xs4all.nl; s=s2; t=1607562430; bh=9H3OqSA/OuTuLnpXwMRhArS3/Ors7dkn3nT2nJ/r3hc=; h=Subject:To:From:Message-ID:Date:MIME-Version:Content-Type:From: Subject; b=f3j1aBzQfBGsflcRLCLbzk8AWxgu8YNgrWKJYXXtVcItfuWaen6Y3vwQUnpD7NCVF Lussh9NEWuB3Q2oQ8/rzqMet4hjDeuKPiWlHQezqCQFPzOzR0j/Lt2va09VRJBNzot usIPhvkSrnJ6s+wmm32RnK4HLYVZrJ2/6wzX1ZtWMG8F/S5KFQSXBvUYNteHpD3g8V KwPtM8R7Keh5Xfv4WHC3Hr6nBiNOIS5fLheqMLZf4uuaGa3e2MA2Oqten4MTZuXbys aWrkQFKgFFPyMHJ3XUA8mM0zabSomL2deOgmGLxWCA5ybrbRsjjuRu4OW5SY5d/2ad dGiJ+V0fFYgeQ==
References: <VI1PR0502MB37571FFEABA44E8C316DEB48CECC0@VI1PR0502MB3757.eurprd05.prod.outlook.com>
To: IETF Languages Discussion <ietf-languages@iana.org>
From: Sebastian Drude <drude@xs4all.nl>
X-Forwarded-Message-Id: <VI1PR0502MB37571FFEABA44E8C316DEB48CECC0@VI1PR0502MB3757.eurprd05.prod.outlook.com>
Message-ID: <ca663582-aed1-f283-f43c-e0eeb5f56675@xs4all.nl>
Date: Wed, 09 Dec 2020 22:07:03 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <VI1PR0502MB37571FFEABA44E8C316DEB48CECC0@VI1PR0502MB3757.eurprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------4C99C9DDA9F46939ABB1D5A3"
Content-Language: pt-BR
X-CMAE-Envelope: MS4xfO7+fBYexE9R5IsbpcOH8YHB0p8TN7EDxkJNQwJdGXlHnRGmJx0pc6shwb6HLcpPkiisbf4VWrti16KzGH68lido+S9/49HBMkZBN2yqp4ukoLF48nu0 lOftxUwlDcEx8qhvTBMZH4BymlYLfhrfUzyNg8iy6RD6M4OWeXIaw5Wp77HuXT7n5jbl9yG7OpjLyQywKpQTdnOu3yKGgTJ+5PP1yncVAgZfrfNwrPOXQOZr XSkpcLk1R27KVq+UmBDdcz0dicSagCNxWF0wiZJmtMGSFkNMUKbtL3FZxf6vylrJ
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (pechora3.dc.icann.org [0.0.0.0]); Thu, 10 Dec 2020 01:07:32 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/LUExpT2UzmNJTpqN8IjyKcOr-KM>
Subject: [Ietf-languages] Fwd: RE: Re: 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: Thu, 10 Dec 2020 01:07:48 -0000

Dear IETF-Languages group,


just to let you know, I got a response from the responsible ISO 
secretariat (below).

I hope that it may be a possibility that those IETF-experts interested 
in collaborating with us on making ISO TR 21636 and BCP 47 interoperable 
be recognized as experts sent by ANSI (and/or NIST?) to participate in 
ISO TC 37 / SC 2.  That is how I am participating, as a German DIN 
delegate expert (via University Frankfurt).

Perhaps it would be worthwhile to contact the corresponding ANSI 
people?  I guess you may have better contacts than "info@ansi.org 
<mailto:info@ansi.org>".

Or you see other possibilities.

Best wishes,
Sebastian

-------- Forwarded Message --------
Subject: 	RE: Re: [Ietf-languages] Fwd: RE: can I share the drafts of 
ISO 21636
Date: 	Wed, 9 Dec 2020 08:21:21 +0000
From: 	FERRES Mercè <FERRES@iso.org>
To: 	Drude Sebastian Mr <drude@xs4all.nl>, Galinski Christian Dr 
<christian.galinski@chello.at>



Dear Sebastian,

Thanks for your request.

Technical participation in ISO is restricted to the ISO member bodies 
and liaison organisations.

The US member body for ISO is ANSI: experts would have to be appointed 
by ANSI. But I can see we have very many expert from NIST in ISO, so 
although I do  not know how NIST and ANSI coordinate, it seems possible 
that the experts come from NIST.

This is a general ANSI contact, in case it helps: 
https://www.iso.org/member/2188.html <https://www.iso.org/member/2188.html>

Best regards,

Mercè

mercèferrés hernández
technical programme manager | standardization department | 
iso central secretariat <http://www.iso.org/iso/contact_iso> | 
phone: +41 (0)79 222 53 54

*From:* Sebastian Drude <drude@xs4all.nl>
*Sent:* 2020-12-08 20:57
*To:* FERRES Mercè <FERRES@iso.org>; Galinski Christian Dr 
<christian.galinski@chello.at>
*Subject:* Fwd: Re: [Ietf-languages] Fwd: RE: can I share the drafts of 
ISO 21636

Dear Mercé,

let me please come back to you with the question of how the Internet 
Engineering Taskforce on languages can collaborate with ISO TC 37 / SC 
2.  The colleagues at the IETF are not convinced that it would be a good 
move to enter a formal liaison.

Please see the dialogue below.  Doug has a point there at the end -- it 
is *both* our interest, also ours at ISO, that the two frameworks are 
interoperable.

Besides asking them to join ISO, are there other ways?  Can individual 
members of the IETF be nominated experts by NIST, for instance?  Or can 
there an official joint working group be established without the IETF 
entering a liaison?

Thanks again in advance for your help and for trying to think out of the 
box.


Best wishes, Sebastian



        Doug Ewell: 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 [Everson] and I are IETF Designated Experts for BCP 47. I wonder if SC2

        would consider that.

    SD: 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?

DE: 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.

    SD: 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.

DE: 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.*