11524 2010-12-10 13:09:07 +0000 valid XML documents. 2011-08-04 05:07:26 +0000 1 1 1 Unclassified HTML WG LC1 HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) unspecified PC Windows NT RESOLVED FIXED P2 normal --- 1 davidc eliotgra eliotgra mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 43247 0 davidc 2010-12-10 13:09:07 +0000 the introduction says: It is often valuable to be able to serve HTML5 documents that are also valid XML documents. It would be better to say It is often valuable to be able to serve HTML5 documents that are also well formed XML documents. that is "well formed" as opposed to "valid" since most documents conforming to this spec are not valid according to the XML definition of validity. No documents using the preferred doctype <!DOCTYPE html> can be valid, the only ones that can be valid are documents that (a) use an xhtml1 "legacy" doctype, and don't use any new html5 features. A related, but separate issue that has been commented on before is that this document would be clearer (and shorter) if it restricted itself to the additional constraints that need to be followed to get compatible doms from html and xml parsing, given a document assumed to be valid html5 and well formed xml. So requirements like DOCTYPE being uppercase and attribute values being quoted could be dropped as they are implied by the document being well formed. 43647 1 eliotgra 2010-12-29 19:41:33 +0000 Introduction now starts: It is often valuable to be able to serve HTML5 documents that are also well formed XML documents. Thanks for catching this. Eliot 53140 2 mike 2011-08-04 05:07:01 +0000 mass-move component to LC1 53187 3 mike 2011-08-04 05:07:26 +0000 mass-move component to LC1