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; Mon, 08 Aug 2005 23:31:02 +0200 X-Sieve: CMU Sieve 2.2 Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id E478B3200D4 for ; Mon, 8 Aug 2005 23:31:01 +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 26013-04 for ; Mon, 8 Aug 2005 23:30:56 +0200 (CEST) X-Greylist: domain auto-whitelisted by SQLgrey-1.4.8 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by eikenes.alvestrand.no (Postfix) with ESMTP id 2B3F63200D1 for ; Mon, 8 Aug 2005 23:30:56 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2FCY-0000lb-Pj; Mon, 08 Aug 2005 17:30:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E2FCW-0000l6-Vg for ltru@megatron.ietf.org; Mon, 08 Aug 2005 17:30:29 -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 RAA25924 for ; Mon, 8 Aug 2005 17:30:26 -0400 (EDT) Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E2FkI-0007TI-Di for ltru@ietf.org; Mon, 08 Aug 2005 18:05:23 -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 1E2FCP-0004qZ-NR; Mon, 08 Aug 2005 14:30:22 -0700 Message-Id: <6.2.1.2.2.20050808210443.03f5ceb0@mail.afrac.org> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Mon, 08 Aug 2005 23:30:13 +0200 To: "L.Gillam" , ltru From: r&d afrac Subject: RE: [Ltru] Re: W3C tag policy disclaimers and IETF RFCs In-Reply-To: <4A7C6FA2AB31194E80E13FE585F6A212DFFB46@EVS-EC1-NODE1.surre y.ac.uk> References: <4A7C6FA2AB31194E80E13FE585F6A212DFFB46@EVS-EC1-NODE1.surrey.ac.uk> 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-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 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: by amavisd-new at alvestrand.no At 19:02 08/08/2005, L.Gillam wrote: > > No intent to oppose. I just add the "0-" sequence. >Jefsey, >Do you mean that you will create an RFC that takes in whatever is in the >current draft and expands it with 0- to provide whatever it is that you >want, such that the following would be allowed: Dear Lee, The result is certainly in the form you say. But it cannot be documented in any other RFC if not permitted by this Draft. It needs the paragraph I introduced. >en-US-0-jefsey.wants.this.to.be.possible? >en-US-x-private-0-jefsey.wants.this.to.be.possible? >0-jefsey.wants.this.to.be.possible? Yes. Or respecting the K/H RFC: en-0-sheme.sub-scheme:subname.name. I then have two possibilities: either to propose the IESG to review the K/H RFC before it is published, to have a unique RFC or to introduce a generalised multilngual tagging system where the K/H RFC "tags:" scheme would be replaced by the "0-" sequence. All this is compatible with the Draft ABNF since it is made to stop at "0-". jfc _______________________________________________ Ltru mailing list Ltru@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ltru