- From: <bugzilla@jessica.w3.org>
- Date: Tue, 10 Jul 2012 14:21:47 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17710
Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xn--mlform-iua@xn--mlform-i
| |ua.no
Summary|Polyglot Markup: Make XML |Polyglot Markup: Remove XML
|validity a principle. |validity completely
--- Comment #2 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2012-07-10 14:21:47 UTC ---
(In reply to comment #1)
> <!DOCTYPE html>
[ ... ]
> It is not accurate to say that this DOCTYPE adds no constraints, it
> is more accurate to say that it declares no elements, so any use of
> any element is invalid.
He, he ... good point. Yeah, in that case then there should be no point in
focusing on the casing of the 'html' string inside <!DOCTYPE html> since, if
the validating XML parser does not whine about the DOCTYPE, in will - anyhow -
whine about undeclared elements ...
> This is why it is important only to depend on XML well-formedness and not XML
> validity when defining polyglot documents.
Yeah, it shows that the DOCTYPE is only for HTML compatibility - and not for
XML compatibility …
> You are correct however that the requirement that "html" be in lowercase is on
> consistent with the stated aims as it is neither required for the document to
> be XML well formed nor for it to be conforming HTML5. I suggest this
> requirement be dropped. (your ALT 2)
Yes, that seems like the right conclusion then. I changed the title of the
bug, accordingly.
Btw, are you 100% that there is no trouble for someone with an XML toolchain if
the casing of the 'html' string of the DOCTYPE is 'wrong'?
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 10 July 2012 14:21:59 UTC