PUBLIC MARKS with search dtd

Submitted by Philip Jägenstedt (not verified) on Sun, 08/23/2009 - 14:44.

Sounds like you want a DTD or XML Schema that you can edit to your satisfaction.

Et lui, on dirait qu'il est resté dans sa grotte pendant 10 ans et qu'il n'a jamais vu XHTML M12N. En même temps, c'est un peu le cas de tous les HTML 5 fanboyz.

The HTML 2.0 specification, RFC1866, defines an SGML application and an Internet media type. The specification notes that extensions are planned, but only the text/html; level=2 internet media type and the "-//IETF//DTD HTML 2.0//EN" document type are defined. This document suggests the use of URIs as system identifiers for document type definitions, allowing decentralized evolution of the language. The use of marked sections as a transition technique and the continued use of the level mechanism for standardized points in the evolution path are discussed.

The HTML 2.0 specification, RFC1866, defines an SGML application and an Internet media type. The specification notes that extensions are planned, but only the text/html; level=2 internet media type and the "-//IETF//DTD HTML 2.0//EN" document type are defined. This document suggests the use of URIs as system identifiers for document type definitions, allowing decentralized evolution of the language. The use of marked sections as a transition technique and the continued use of the level mechanism for standardized points in the evolution path are discussed.

very generic script. The downside is of course that it can only have a subset of the functionality — namely verifying that the files are valid UTF-8, don’t have a BOM and that the syntax is correct. It also happens to recognize a larger part of the DTD syntax than the Adblock Plus script because it doesn’t need to extract the data out of the DTD files.

Many browsers now go beyond the current DTD and it is only right that we update the DTD to reflect the best ideas. I hope to have a preliminary draft available within a week or two to fire off discussions. The aim is to evolve a consensus view of what extensions are appropriate and which preserve the overall simplicity of HTML.