Why a DTD for HTML 3.2?

HTML 2.0 (RFC1866) is and for the forseeable future its successors should be an
SGML application.  This requirement was largely responsible for the seemingly
interminable delays in producing RFC1866, historical warts and all.

Since SGML systems are not deployed* nor implemented* on the WWW, and HTML 3.2
is an effort to document and standardize some of the less-worse newer current
practices, why then allocate scarce time and resources to build a DTD for HTML
3.2?

-marc
*the number of regularly used SGML implementations as a fraction of all WWW
systems rounds to zero?

--

Received on Tuesday, 21 May 1996 19:02:19 UTC