- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Tue, 6 Nov 2012 15:17:03 +0100
- To: Smylers <Smylers@stripey.com>
- Cc: public-html@w3.org
Smylers, Tue, 6 Nov 2012 14:02:18 +0000: > Lachlan Hunt writes: > >> Subject to the condition that the spec clearly states that everything >> else in the document is non-normative, I would be satisfied with a >> normative definition of the term "polyglot markup" (or similar) as >> being markup that conforms with the intersection of the HTML and XHTML >> serialisations, such that the markup meets the following constraints: >> >> 1. Conforms to the syntactic requirements of the HTML serialisation >> 2. Conforms to the syntactic requirements of the XHTML serialisation >> (including well-formedness) >> 3. Results in a *conforming document* when parsed with either an HTML or >> XML parser >> 4. Results in equivalent tree representations (e.g. DOM) when parsed >> using either HTML or XML parsers, subject to the known exceptions >> for: >> a. xml, xmlns and xlink namespaced attributes, >> b. Any insignificant differences in the value of textContent >> for script and style elements. >> c. Any semantically insignificant whitespace differences. > > Thanks. > > It sounds like we may be able to get consensus (or at least a lack of > formal objections) around that. For me to not object this, the principles would need to be extended with a 5th principle: 5. Limits itself to "the encoding" - that is: UTF-8. It doesn't matter to me whether you accept that principle as a "known exception" or as a logical reading of the specs that polyglot markup relies on. -- leif halvard silli
Received on Tuesday, 6 November 2012 14:17:34 UTC