W3C home > Mailing lists > Public > public-html@w3.org > December 2010

[Bug 11524] New: valid XML documents.

From: <bugzilla@jessica.w3.org>
Date: Fri, 10 Dec 2010 13:09:07 +0000
To: public-html@w3.org
Message-ID: <bug-11524-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11524

           Summary: valid XML documents.
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot
                    Graff)
        AssignedTo: eliotgra@microsoft.com
        ReportedBy: davidc@nag.co.uk
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, eliotgra@microsoft.com


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.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 10 December 2010 13:09:08 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:07 UTC