Return-Path: Received: from murder ([unix socket]) by eikenes.alvestrand.no (Cyrus v2.2.8-Mandrake-RPM-2.2.8-4.2.101mdk) with LMTPA; Tue, 29 Mar 2005 04:03:46 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 4B6E261B44 for ; Tue, 29 Mar 2005 04:03:43 +0200 (CEST) Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19515-07 for ; Tue, 29 Mar 2005 04:03:10 +0200 (CEST) Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 41DE961AF1 for ; Tue, 29 Mar 2005 04:03:04 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DG642-0005AB-T5; Mon, 28 Mar 2005 21:02:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DG641-0005A6-R7 for ltru@megatron.ietf.org; Mon, 28 Mar 2005 21:02:42 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06943 for ; Mon, 28 Mar 2005 21:02:39 -0500 (EST) Received: from [63.247.76.194] (helo=montage.altserver.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DG6Ac-0008HS-UT for ltru@ietf.org; Mon, 28 Mar 2005 21:09:32 -0500 Received: from lns-p19-8-idf-82-65-71-22.adsl.proxad.net ([82.65.71.22] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DG63x-0008Cx-2x; Mon, 28 Mar 2005 18:02:37 -0800 Message-Id: <6.1.2.0.2.20050328230617.049c0430@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Mon, 28 Mar 2005 23:58:44 +0200 To: John Cowan From: "JFC (Jefsey) Morfin" Subject: Re: [Ltru] Re: XML registries now available In-Reply-To: <20050328172934.GQ24325@skunk.reutershealth.com> References: <20050327214939.GN24325@skunk.reutershealth.com> <6.1.2.0.2.20050328121911.037a4eb0@mail.jefsey.com> <20050328172934.GQ24325@skunk.reutershealth.com> 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 - jefsey.com X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Cc: ltru@ietf.org X-BeenThere: ltru@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Language Tag Registry Update working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ltru-bounces@lists.ietf.org Errors-To: ltru-bounces@lists.ietf.org X-Virus-Scanned: amavisd-new at alvestrand.no At 19:29 28/03/2005, John Cowan wrote: >JFC (Jefsey) Morfin scripsit: > > > I assume you consider the situation where: > > 1. the application gets a langtag > > 2. consider what do to with it. > > 3. there are three possible solutions? > > - it knows the langtag from it being built-in. > > - it does not know it but it has a filtering/negociation strategy > > built-in or based upon non IANA parameters > > - all this fails and its filtering/negociation strategy resort to a > > IANA input before concluding? > >In practice, the second and third strategies are a matter of using a >matching algorithm (which need not be standardized and can rely on local >knowledge as well) to reduce the unknown langtag to a known one. With an >absolutely unknown langtag, nothing useful can be done except to display >the full name of the language, which is useful but not very useful. >Without translators, spelling checkers, and other such tools, one can >do little with such a document. Yeap. But the first and second strategy has no big load on the IANA. The first point is to know if the langtag is registered. Then to know its environment. With the maximum of speed and the lowest load for the database system. The rest is a matter of other services as you say. >This is quite different from the DNS case, where given the mapping of >a computer's name to an IP address, one can indeed interact with that >computer in useful ways. If I know how to reach newmachine.somedomain.fi, >I can try to discover what resources it provides. If I receive a document >langtagged "sms", the most I could do with it is label it "Skolt Sami". I do not quote the DNS as a way to reach an IP (what can also be the use for). The IP address given by the DNS is just an information as another. The DNS is first a distributed database system, which can easily supports a billion of information at low load and low cost. With a distributed management system. > > I would say this is similar to anti-spam or to anti-virus strategies. > >Languages aren't constantly being created: In term of load, the problem is the same. What motivates a query is the change. Whatever it is. Actually this is not totally true: the number of _documented_languages_ is going to increase. >on the contrary, they are >constantly going extinct. The list of living languages will probably >shrink by 90% over the next century or two. Who knows? The change over the last 50 years when a cultural development policy is engaged is not necessarily that way. The debate I follow right now is for example to know if a regional language (Occitan) is to be registered as one (as today in the 639-3 draft) or as six languages. I see young kids in my family having more Breton than French. 20 years ago it was unthinkable. IMHO, Multilingual Internet MAY (I mean nothing more) lead to a change in the current trend. We start having statistics (it will still take time to have significant results in number of people and in number of languages and cultures). They seem to show that bilingual people have a slightly higher IQ and that "apparent IQ" (when you test the same person's IQ in different languages) is lower in English (common language) than in their mother tongue. > > Obviously codes change les frequently than spamming hosts and viruses, but > > the simple fact they change make the load similar (the load is not because > > there are a lot of changes, but because there is a check if nothing > > changed). > >In practice this table will probably be updated only when the operating >system is. Probably yes, and this is in line with/below the figures I gave. Question is from where: from the OS CD or from IANA? jfc _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru