Message-Id: <v03007801aed8a7a3c1a5@[129.46.151.190]>
Date: Sat, 14 Dec 1996 12:04:02 -0700
To: www-html@w3.org
From: David Blyth <dblyth@qualcomm.com>
Subject: Re: HTML 3.2 PR
I'm concerned that there does not seem to be any provision
by which HTML containers are strictly enforced. If one
wants to write the code....
<ul>
<li>Bullet One
<li>Bullet Two
</ol>
Then nothing happens - events proceed normally. Or
for another example....
<h1>Start a header </b> but stop bold <b> restart bold and end header </h1>
In the latter case, the <b></b> container is being used in reverse order.
I've also seen cases where <ul> is simply used to shove text over to
the right.
In short, HTML containers acquire multiple sets of attributes but are
sometimes used (or abused) for only one attribute. SGML containers
seem to be more carefully defined and enforced.
IMHO, either HTML containers should be as strictly enforced as SGML,
xor HTML should no longer be treated as a subset of SGML. It's simply
to easy to hack HTML in a way that violates the _spirit_ of SGML.