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; Thu, 14 Apr 2005 02:41:24 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 7266161B76 for ; Thu, 14 Apr 2005 02:41:24 +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 21722-01 for ; Thu, 14 Apr 2005 02:41:20 +0200 (CEST) Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id E6F0761B60 for ; Thu, 14 Apr 2005 02:41:19 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLsOg-0003Bh-Ap; Wed, 13 Apr 2005 20:39:54 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DLsOe-0003BM-Dn for ltru@megatron.ietf.org; Wed, 13 Apr 2005 20:39:52 -0400 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 UAA23910 for ; Wed, 13 Apr 2005 20:39:50 -0400 (EDT) Received: from [63.247.76.195] (helo=montage.altserver.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLsYW-0001Nk-Tp for ltru@ietf.org; Wed, 13 Apr 2005 20:50:05 -0400 Received: from lns-p19-1-idf-82-251-83-105.adsl.proxad.net ([82.251.83.105] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1DLsOY-0001lO-Fb; Wed, 13 Apr 2005 17:39:46 -0700 Message-Id: <6.1.2.0.2.20050414004401.02df77d0@mail.jefsey.com> X-Sender: jefsey+jefsey.com@mail.jefsey.com X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Thu, 14 Apr 2005 01:46:46 +0200 To: "Doug Ewell" , "LTRU Working Group" From: "JFC (Jefsey) Morfin" Subject: Re: [Ltru] Re: [psg.com #882] registry should copy non-English fields from ISO documents In-Reply-To: <003101c5403d$1e0bce00$030aa8c0@DEWELL> References: <20050413142051.UDNA2128.mta1.adelphia.net@megatron.ietf.org> <003101c5403d$1e0bce00$030aa8c0@DEWELL> 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: 9a2be21919e71dc6faef12b370c4ecf5 Cc: 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 17:26 13/04/2005, Doug Ewell wrote: >JFC (Jefsey) Morfin wrote: > > > 2. mixed feelings among English culture Members, where confusion > > results from the bundling of various questions in a single one "do you > > support Jefsey's non detailed provision". > >Speaking only for myself, I wasn't confused at all. Randy's blanket >term, "Jefsey's provisos," was sufficiently vague that I had to actually >go back and read the post(s) in question, which I had skimmed over >before. After reading them, I clearly understood Jefsey's various >suggestions, and was confident of my opposition to them. you increase the problem rather than clarifiy it. What you oppose is my bundled personal positions (plural). Not different questions (each singular). But may be this is a normal way of thinking in this group, since the main problem it faces is of same nature: the bundling of XML parameters. >Partitioning the group into "French culture Members" and "English culture >Members" See below. >and pitting the two against each other is not how I thought consensus was >built within Working Groups, but I could easily be wrong here. I feel the term "pitting" out of context. > I don't have 27 years of Internet experience to draw on. True. But this experience shown me that intelligence may replace it advantageously. BTW these different comments lead to realise how much one of the things which suprises non-English culture people on this kind of lists is the rudeness of people who are most probably very polite in normal life. I suppose this is part of the consensus undercovering in these IETF related Working Groups? Some IETF participants make a very common error using the formula "consensus building", which by essence has no meaning. This may result from the different motivations of people in participating in the IETF interestingly discussed on the main list rigth now. This seems to actually mean "to build a proposition" that "rough consensus rules" will permit to impose to the WG to obtain the publication of a document. By essence this is a Pyrhus victory, and the main reason why every RFC do not make a standard. By nature a consensus is something which pre-exists, otherwise it is a compromise or a trap. The difficulty is to discover it as it is hidden behind many conditions ("we are in agreement if you we agree on something else before" - governing by consensus is to make fulfil these condition so the consensus may survive). The reason why we need consensuses is it is the best hope we have that what is true in a WG will also be true in the real world. The reason why we are not interested in compromise, votes, positions, etc. is that they only concern the group which discusses them and not the real world. Here we have two consensuses (which is a normal possibility). One is clear and supported by determined and able people (the position of this WG will not affect the real world deployment and the plans we work on). The other is confuse and contradictory (it makes the registry empty since ISO 639-3 uses reference names which by essence are not of a language, therefore not English. And even if you twisted the text of the "consensus" in accepting ISO 639-3 reference names of English origin, the autonyms should stay blocked .... these people refusing "1000" languages, forgetting that ISO 639-3 uses probably more than 1000 languages ... So, we can only say from this that two opposing consensus emerged. These two consensus seem to be supported (a) by what seems to be an extended anglo-saxon culture group, (b) by a non-extended-anglo-saxon culture. The limited number of participants in (b) does not make it clear if that culture is limited to one single individual, extended to the cultures of the various authoritative entities he is related to. The response will be possibly observed during the Last Call, etc. , the IANA implementation and the MRP (market real practices). jfc >-Doug Ewell > Fullerton, California > http://users.adelphia.net/~dewell/ > > > > >_______________________________________________ >Ltru mailing list >Ltru@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/ltru _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru