W3C home > Mailing lists > Public > www-html@w3.org > May 2003

Re: XHTML 2.0 to contain long element names

From: Jens Meiert <jens.meiert@erde3.com>
Date: Mon, 12 May 2003 12:40:49 +0200 (MEST)
To: Vix <vixcc@yahoo.com>, www-html@w3.org
Message-ID: <26831.1052736049@www8.gmx.net>

> WYSIWYG Editors are very helpful in creating documents. In such editors,
> no knowledge of the tag
> is usually required. Therefore, b and bold will both have the same value
> from a functional point
> of view.

a) That is right, no knowledge is required. But even take a look at
Frontpage or Dreamweaver generated code. It is my worst nightmare viewing at this
kind of source code.

b) I do not agree to 'b and bold will both have the same value'. Implement a
class for bold text in Netscape 4.x or in Konqueror and look at the result:
Bold marked text will not be displayed bold. This is a fault in the CSS
integration of these browsers. (Nevertheless I only use CSS to realize the
presentation layer of my web sites because of the minor impact caused by failing
styles I use, e.g. in this case).


> On the other hand, consider an HTML file with 500 table rows where bold
> and italic characters are
> being used. If we use tablerow cell bold italic and underline instead of
> tr td b i and u, there
> will be a negative impact on two things: file size and parsing time.

That is another important aspect of huge element names: Every character
causes traffic... But I am not sure if larger element names would affect parsing
time.


Regards,
 Jens Meiert.


<snip />

-- 
Jens Meiert

Steubenstr. 28
D-26123 Oldenburg

Telefon +49 (0)441 99 86 147
Telefax +49 (0)89 1488 2325 91
Mobil +49 (0)175 78 4146 5

eMail <jens@meiert.com>
Internet <http://meiert.com>
Received on Monday, 12 May 2003 06:40:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:55 GMT