W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2011

[Bug 11910] @id values in polyglot markup should be XML-valid (or not?)

From: <bugzilla@jessica.w3.org>
Date: Sun, 30 Jan 2011 14:24:59 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PjYD5-0001id-42@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11910

--- Comment #6 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-01-30 14:24:58 UTC ---
(In reply to comment #5)
> (In reply to comment #4)
>  what do you think about splitting the document as I suggested?
> 
> I think the document should only concern itself with conforming html(5)
> documents. Otherwise it will get totally out of hand,

As I show in my comments in Bug 11909, I think it gets out of hand if it is
*not* split. The document needs to discern between principles and praxis.

> for example, the  following fragment
> 
> <p>aaa<ul><li></li></ul>kkk</p>
> 
> is well formed xml with wildly incompatible xml and html dom. This (along with
> most of the "special parsing rules" of the html parser are not covered by the
> rules in the polyglot spec.

The <p> is already mentioned in the polyglot spec, no? HTML5 also mention it in
the "restricitons on the content model" seciton. It would be simple to provide
a list of those element that have special parsing attached to them. 

> This is OK so long as the polyglot spec only
> concerns itself with conforming documents. The above fragment is not conforming
> html because of the </p>.
> 
> Unfortunately the document is still not sufficiently explicit that the rules
> that it gives are only sufficient to produce compatible DOM if the document is
> well formed xml and conforming html.

Here I think you are mixing things: XML is not alone in discerning between
"working" (aka "well-formed") and valid (aka "conformance"). HTML has the same
concept.

 E.g. HTML5 says that it is forbidden to set the value of the img@border to a
non-zero value. Thus, this is forbidden <img border="9" src="i" alt="i">. We
can both agree that it is not an issue, with regard to getting the exact same
DOM, whether @border is set to "9" or "0". 

If this document is supposed to replace Appendix C, then it must, in my view,
also describe principles.

-- 
Configure bugmail: http://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 Sunday, 30 January 2011 14:25:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 30 January 2011 14:25:08 GMT