W3C home > Mailing lists > Public > www-tag@w3.org > December 2012

Re: HTML/XML TF Report glosses over Polyglot Markup

From: Noah Mendelsohn <nrm@arcanedomain.com>
Date: Tue, 04 Dec 2012 11:35:29 -0500
Message-ID: <50BE2651.8030906@arcanedomain.com>
To: "www-tag@w3.org List" <www-tag@w3.org>
CC: Henri Sivonen <hsivonen@iki.fi>, public-html WG <public-html@w3.org>, Sam Ruby <rubys@intertwingly.net>, Norm Walsh <ndw@nwalsh.com>
I strongly urge TAG members to read Sam Ruby's posting [1] and the comment 
thread that follows from it. Although I am not prepared to say that I agree 
(or disagree) with its conclusions, I think it is one of the more 
interesting and cogently presented defenses of polyglot. Furthermore, the 
comment thread includes an interesting debate between Henri and Sam, among 
others. It also includes a link to a proposal [2] to drop the reference to 
XHMTL from the title of the polyglot specification.

I think it will be helpful if TAG members are up on all this for our 
Thursday discussion. Thank you.


[1] http://intertwingly.net/blog/2012/11/09/In-defence-of-Polyglot
[2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=19925

On 12/4/2012 9:29 AM, Henri Sivonen wrote:
> On Mon, Dec 3, 2012 at 3:26 PM, Sam Ruby <rubys@intertwingly.net> wrote:
>> If three people want to get together and collaborate, should the fact that
>> some (and indeed many) may not want to participate be ground for stopping
>> them?
> I think it’s fine for 3 people to participate and create a coding
> style for their blogs[1] that suits their use of non-conforming
> parsers and publish the coding style on their blogs. Publishing such a
> house style as a W3C REC will generate another decade of
> http://xkcd.com/386/ like the infamous Appendix C did for the previous
> decade.
> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=19925 together with
> http://intertwingly.net/blog/2012/11/09/In-defence-of-Polyglot suggest
> the goals of the polyglot guide might morph as the goals of the coding
> style on intertwingly.net shift from catering to both to IE8 and
> browsers that required XHTML for inline SVG (goal obsoleted by the
> SVG-in-text/html capabilities of IE9 and of browser that have
> HTML5-compliant parsers) to making the markup work in the
> HTML5-incompliant *HTML* parser of libxml2. (It’s worth noting that
> one could already use a compliant HTML parser to convert HTML to XHTML
> and then use libxml2’s *XML* parser. For example, the Validator.nu
> HTML Parser comes with a sample tool called
> nu.validator.htmlparser.tools.HTML2XML .)
Received on Tuesday, 4 December 2012 16:36:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:33:17 UTC