Apologies -- Re: Internationalized CLASS attributes

Item Subject: Re: Internationalized CLASS attributes
Received: from relay.hp.com by vivaldi.grenoble.hp.com with ESMTP
	( 3.4 Openmail) id AA275138176; Thu, 17 Oct 1996 14:16:17 +0100
Received: from www19.w3.org by relay.hp.com with ESMTP
	( 3.3) id AA094144557; Thu, 17 Oct 1996 05:15:57 -0700
Received: by www19.w3.org (8.6.12/8.6.12) id HAA16951; Thu, 17 Oct 1996 07:45:45 -0400
Resent-Date: Thu, 17 Oct 1996 07:45:45 -0400
Resent-Message-Id: <199610171145.HAA16951@www19.w3.org>
X-Openmail-Hops: 1
Date: Thu, 17 Oct 96 13:44:41 +0100
Message-Id: <H000076703dacff2@MHS>
In-Reply-To: <"96Oct17.095015bst.38615(3)(a)u-net.net*"@MHS>
Subject: Re: Internationalized CLASS attributes
To: www-international@w3.org
X-List-Url: http://www.w3.org/pub/WWW/Archives/Public/www-international
Resent-From: www-international@w3.org
X-Mailing-List: <www-international@w3.org> archive/latest/108
X-Loop: www-international@w3.org
Sender: www-international-request@w3.org
Resent-Sender: www-international-request@w3.org
Precedence: list


Item Subject: Re: Internationalized CLASS attributes
My appologies. New mail system, badly-configured signature file ... so there was
no signature on the original.

Nick Downes

Hewlett-Packard France


Bert Bos wrote:

>> The next version of HTML will have a CLASS attribute on (nearly) all 
>> elements, as described in several documents ([1], [2], [3], [4]). The 
>> intention is to allow authors to attach semantic information to 
>> element

>> So it appears that case-conversions are language dependent. That's 
>> why, for example, there is setlocale() in POSIX. But is it practical 
>> to make the case rules for CLASS dependent on the language? Where 
>> would you get the language from?
>> Or do we change the interpretation of CLASS, and say that it is just a 
>> code (class=xyz12, class=p-89x), that doesn't have to be 
>> human-readable? In that case ASCII is all we need. 
>> What do people think?

I assume that most "code" will be generated by software, rather than by a person
and a text editor. If there is some form of interface or tool between the 
information provider and the "code" they generate, and a similar isolating layer
between the end-user and the underlying code, then I don't mind what language or
code is used to name the class, so long as there is a meaningful, well-known 
mapping between the value used to name the class and the word, phrase or 
icon the user uses to access the information in the entity. 

Given the choice, I'd leave it in ascii.

Martin Bryan wrote:

> What we really need is something, like the RFCs relating to REV and REL, 
> which suggest a set of useful class names that could be applied by anyone, 
> irrespective of their country of origin. Admittedly most people would not 
> then be able to use their native language to name such transportable 
> classes, but the up-side would be that they would be able to identify 
> information of the class they require without having to search for all the 
> possible names for the class.

If standard classes are to be really useful, we need some kind of language, 
country, and culture-independant semantic description of each one. Even in the 
restricted information systems I play with, trying to define genuinely useful 
classes which mean something to both the info provider and the end user is a 
nightmare.  I like the idea of standard class names, but I'm not sure how 
realistic it is to expect to be able to define a standard set which would have 
any kind of universal applicability, irrespective of the linguistic or cultural 


TO: www-international@w3.org