Re: [Ltru] Re: Update ltru-initial-05

r&d afrac <rd@afrac.org> Sat, 15 October 2005 23:48 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQvlG-0001Ue-PI; Sat, 15 Oct 2005 19:48:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQvlE-0001UW-Cu for ltru@megatron.ietf.org; Sat, 15 Oct 2005 19:48:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02997 for <ltru@ietf.org>; Sat, 15 Oct 2005 19:48:14 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQvwE-0007yQ-DV for ltru@ietf.org; Sat, 15 Oct 2005 19:59:43 -0400
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1EQvkz-0005W3-0a; Sat, 15 Oct 2005 16:48:05 -0700
Message-Id: <6.2.3.4.2.20051016011735.053ba900@mail.afrac.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Sun, 16 Oct 2005 01:48:01 +0200
To: Frank Ellermann <nobody@xyzzy.claranet.de>, ltru@ietf.org
From: r&d afrac <rd@afrac.org>
Subject: Re: [Ltru] Re: Update ltru-initial-05
In-Reply-To: <4351774E.3D77@xyzzy.claranet.de>
References: <FA13712B13469646A618BC95F7E1BA8F1E1CFF@alvmbxw01.prod.quest.corp> <p06230903bf75e74feadd@[69.181.216.204]> <Pine.GSO.4.63.0510150953260.835@korppi.cs.tut.fi> <4351774E.3D77@xyzzy.claranet.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - afrac.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc:
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

At 23:40 15/10/2005, Frank Ellermann wrote:
>Jukka K. Korpela wrote:
> > we need to expect IANA to maintain such stability. The other
> > option is to find another registration authority.
>
>The latter option would require a lot of work:  Update several
>RfCs so that registries could be hosted elsewhere.  Or appoint
>somebody to maintain PURLs for the IETF if you trust that PURL
>lives longer than the direct URL.

I thought the idea was to eventualy merge width CLDR?
So the whole thing would be supported on the same machines by the same people?
Every time I asked about the dissemination system and its size, 
usage, etc. I was responded "like Unicode"?

>ACK.  But IMHO it's not the main issue here.  I'd gues that
>less than 1000 persons worldwide have ever heard of "3066bis".

Please do not say that after an IESG 3066bis LC.
Since I would say that at least 500 knows it through my team ....
and most of these people are concerned by the impact not much by the 
technical hosting details.

Now, you would also imply that may be less than 100 ever read it?
So that IETF would go by minority consensus?

>The relevant reality is defined by "Googlebot finds it" plus
>"Google shows it among the first 10 hits".  An absolute URL
>in an RfC is a guarantee to spread the news, even in the worst
>case (= IANA picks a new URL for the new registry).
>
>Without that guarantee we can still hope that IANA picks the
>old URL for the new registry, because then links on existing
>pages continue to work for what we want.  E.g. I have a link
><http://www.iana.org/assignments/lang-tags/>

This seems an odd discussion because "lang-tags" is a directory of 92 
files. Not a registry of hundredth and then thousands of entries?

>Okay, I'd update it when necessary, but numerous other folks
>won't, unless they check links and get a 404.  Standards and
>regitries are among other things wishful thinking, if nobody
>knows them or everybody ignores them they are dead.
>
>"Search Engine Optimization" is very important.  That's why I
>proposed to add <http://www.inter-locale.com> to the <author>
>section:  It will sky rocket Addison's page rank, this page
>will have an URL to the new registry, Googlebot will find it,
>and that's how "shaping reality" works today (AFAIK + IMHO).

I am not sure of the interest of the inter-locale.com site in this? A 
better IANA site design would be more suitable. You seem to consider 
the langtags will not really be used and known? Surprising.
jfc







_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru