Netscape knew that this could happen when they decided to implement
something out of a (now expired, I believe) discussion draft. So did
the users -- like me -- who decided to mark up tables that way and put
them out on the Web. I knew when I put a few thousand tables out on
our server that I had to be ready to change them all to keep them in
sync with a specification under development. Of course, since we use
style sheets to generate the tags, implementing a change across an
unlimited number of instances takes about five minutes; and, of
course, I deliberately confined the markup to a minimal set of tags
that appeared likely not to change and is consequently not affected by
this inconsistency between the old draft and the new one. But that's
not the point. The point is that you had better know what you're
doing when you start playing with moving targets or you should confine
your efforts to what's specified in finalized standards. To operate
any other way would be to say that the standard is whatever gets
implemented first.
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
========================================================================