Um... No. Wrong. It's not that simple. Sorry.
> This is the basis why lynx etc., decent/friendly non-table browsers can
> deal with my examples gracefully, because they can conveniently ignore any
> unrecognized tags and correctly interpret the remaining ones.
The fact that the HTML 2.0 spec was forced to grandfather in a bad
practice is hardly a license to make that practice the basis for a
future architecture. Inserting all kinds of garbage into the data
stream on the principle that browsers should just ignore what they
can't handle is a bad idea on the face of it. Please imagine what
this argument would look like if translated to compiler design,
database design, or any other kind of computer processing that expects
structured input.
Jon
========================================================================
Jon Bosak, Novell Corporate Publishing Services jb@novell.com
2180 Fortune Drive, San Jose, CA 95131 Fax: 408 577 5020
A sponsor of the Davenport Group (ftp://ftp.ora.com/pub/davenport/)
------------------------------------------------------------------------
The Library is a sphere whose consummate center is any hexagon, and
whose circumference is inaccessible. -- Jorge Luis Borges
========================================================================