[Ltru] The third level of conformance (Was: Updated draft-4646bis...

Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 01 August 2007 15:48 UTC

Return-path: <ltru-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGGQv-0003AP-AW; Wed, 01 Aug 2007 11:48:21 -0400
Received: from ltru by megatron.ietf.org with local (Exim 4.43) id 1IGGQu-0003AK-Sx for ltru-confirm+ok@megatron.ietf.org; Wed, 01 Aug 2007 11:48:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGGQu-0003AC-IG for ltru@ietf.org; Wed, 01 Aug 2007 11:48:20 -0400
Received: from mx2.nic.fr ([192.134.4.11]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IGGQu-0002kq-6f for ltru@ietf.org; Wed, 01 Aug 2007 11:48:20 -0400
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 787221C0100; Wed, 1 Aug 2007 17:48:19 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id 73F5D1C00FA; Wed, 1 Aug 2007 17:48:19 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id 70EA358EBF0; Wed, 1 Aug 2007 17:48:19 +0200 (CEST)
Date: Wed, 01 Aug 2007 17:48:19 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Debbie Garside <debbie@ictmarketing.co.uk>
Message-ID: <20070801154819.GA13548@nic.fr>
References: <46AF5A83.5040805@yahoo-inc.com> <E1IGDYR-0004GA-3t@megatron.ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E1IGDYR-0004GA-3t@megatron.ietf.org>
X-Operating-System: Debian GNU/Linux 4.0
X-Kernel: Linux 2.6.18-4-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.13 (2006-08-11)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: 'LTRU Working Group' <ltru@ietf.org>
Subject: [Ltru] The third level of conformance (Was: Updated draft-4646bis...
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>
Errors-To: ltru-bounces@ietf.org

On Wed, Aug 01, 2007 at 01:43:40PM +0100,
 Debbie Garside <debbie@ictmarketing.co.uk> wrote 
 a message of 83 lines which said:

> I would propose one of the following:
> 
> ---
> A tag can be well formed yet meaningless.
> 
> A tag can be well formed in terms of syntax, and thus valid, yet meaningless
> in terms of its attributes. For example, ... 

Sorry, neither of these sentences is correct in the context of
4646bis-07.

Being "well-formed" and being "valid" are two different things
(section 2.2.9 of 4646bis-07). Thus saying "A tag can be well formed
in terms of syntax, and thus valid" is wrong.

And the first sentence is not strong enough. ar-Cyrl-CO is well-formed
but it is also valid (in the 4646bis-07 sense of the word, defined in
section 2.2.9). 

The discussion is how we should label the informal "third level",
after well-formedness and validity. Meaningfulness? Reality? 


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