Marc suggested we issue an informational RFC to document basically
what Mosaic and lynx do.
Somebody even piped up about doing something through an ISO WG or some
such.
I'm interested in establishing a formal definition of HTML -- perhaps
a few variants including "Minimal HTML Support" (no forms, no nested
lists, conforming SGML), "Mosaic-2.x Support" (where 2.x is some
future release of Mosaic which coincides with publication of a DTD
that it supports).
Perhaps HTML+ could be incorporated as a level of support.
I'm willing to maintain a test suite that defines the variants
of conformance.
But I discovered some time ago that writing user documentation is
beyond my scope of expertise. And we certainly need human-readable
descriptions of HTML to go along with the machine readable DTD and
test suite.
I have talked some with a writer from NCSA who might be able to help,
but it didn't sound like he had a lot of time to contribute.
Are most folks (including the NCSA Mosaic licensees) content to define
HTML as "whatever the latest release of Mosaic supports", or are we
interested in published specifications? And do we have resources to
contribute toward that end?
Dan