> By keeping HTML 3.0 clean and simple, we can make this broad interoperability
> a reality. Any browsers that don't include the version number would be assume
> to lack support for 3.0. In this way servers can provide down graded HTML 2.0
> documents to older clients. Is anyone interested in helping to write a filter
> for 3.0 -> 2.0?
I'll volunteer! Just get me a DTD...
I'm currently working on some general-purpose SGML-to-HTML
utilities for CoST. CoST is currently much too slow to be
used as an on-demand server-side filter, but the basic ideas
should be transferable to other utilities.