Welcome to WebHeadStart.org

Web Technologies

Sponsored By

WebHeadStart.org is currently in beta.
Please pardon our appearance as we work to provide you with the most comprehensive reference on today's web technologies.

Interested in advertising on WebHeadStart? Become an advertising partner today!

[WWW-HTML Mailing List Archive Home] [Messages By Thread] [Messages By Date]

RE: Structure vs Semantics

From: Jewett, Jim J <jim.jewett@eds.com>
Date: Thu, 11 Dec 2003 10:43:19 -0500
Message-ID: <B8CDFB11BB44D411B8E600508BDF076C1A745BA8@usahm010.exmi01.exch.eds.com>
To: "'ernestcline@mindspring.com'" <ernestcline@mindspring.com>, Chris Moschini <cmoschini@myrealbox.com>, www-html@w3.org


Chris Moschini asked:

> > Why does EM have to be inline and contain inline-only?
> > What's wrong with it containing a DIV, even if it's empty?

Ernest Cline wrote:
 
> [worries about pages of upper case]

A typical contract (including many software licenses) will
contain several paragraphs of upper-case, because the law
says that something needs to be emphasized.

Emphasizing with an <em> is better than just upper-casing,
for the same reasons that <strong> is better than <b>.  (And
for several additional reasons as well, such as readability.)

> [How should default styling work?]

Chris' suggestion of "em" vs "p em" is reasonable.  It isn't perfect,
but it is a reasonable default.  Individual authors can override,
perhaps with a display attribute.

That said, I will agree that many things would be nicer if it were
possible to look at child elements in CSS, just as it would be nice
to restrict descendent elements in XML.

-jJ
Received on Thursday, 11 December 2003 10:44:13 GMT
Valid XHTML 1.0! Valid CSS! Site Map | Privacy Policy | Terms of Use | WebHeadStart.org © 2005 All Rights Reserved.